Alternatives to parameter sliders?

Hi All,

I'm looking to find an alternative means to adjust translate and rotate sliders. The lag between input and action makes them extremely frustrating to modulate, and the "-+" buttons are too small for quick, easy targeting. I'd much prefer a hardware jog dial or shuttle. I have a left/rignt scroll tilt function on my trackball that I could assign to this task, but I can find no keyboard binds for the sliders or their associated buttons. Ditto for a multimedia jog controller I have.

Anyone have a piece of hardware they use that does this, or info on the keybinds?

TIA,  Erik

 

Comments

  • CybersoxCybersox Posts: 9,463

    Hmmm.  Using a jog shuttle or such isn't likely to change things much as a lot of the lag you experience with DAZ Studio usually isn't so much of a result of the parameter dials themselves as it seems to be from your computer trying re-render the screen repeatedly as you keep updating the inputs, thereby slowing everything down the more you have loaded, how complex the lighting is, etc.  For any kind of major adjustment, I generally find that it's well worth switching to a faster renderer for a lot of the basic scene building and posing process, as the response time from moving a parameter dial is generally much faster with 3DL than it is Iray, with Filament being even faster, and plain old wireframe being better yet.  Now, all that said, have you tried using the puppeteer or powerpose panels?  They're both alternative means of manipulating objects and data within DS and many people find those options' manner of inputting data quicker and more intuitive once they get the hang of them.

     

     

  • Silas3DSilas3D Posts: 765
    Something else to consider with sliders is their width will affect value sensitivity - a narrow slider will be far more sensitive than a wide one, because there is less space between the start and end values. Therefore, if you have the screen real estate available, widen the parameters tab.
  • crosswindcrosswind Posts: 9,689

    I've ever seen some folks manipulate property sliders with some external devices + scripts, however, frankly speaking that approach more likely made the manipulation even more cumbersome / unefficient ~~ 

    In most cases, the lag between input / actions / sliding the T / R properties usually results from the settlement of Smoothing Iterations coming from the Smoothing Modifiers on the conformers / wearables on your character. You can check if that's your case.

    Then temporarily turning off Smoothing Modifiers may help a lot with speeding up the manipulation. Then turn on Smoothing Modifiers before rendering.

    Besides, in Parameter Settings... of the property slider, checking Use Limits may also speed up the manipulation. As for "small move of +/-" buttons, you may try increase Nudge value in Parameter Settings..., that may help to curtain extent.

  • jmucchiellojmucchiello Posts: 836

    Frankly, if my scene lags enough during parameter modification, I usually switch to entering values directly. It's generally cleaner and I can switch between jumps of +/-2 to +/-10 to +/-0.2 based on whatever I feel like typing in.

     

  • When wanting more control, I type the value in, or use the parameter setting window to set the jog value I want. There are occasions when it's slow and tedious, but over time you develop a feeling for it and get quite close fairly quickly. Regards, Richard.
  • ElorElor Posts: 3,454

    Some items (like hair) can make posing a character really slow, a possible solution is to pose the character naked then to add hair and clothes once done.

  • jmucchiellojmucchiello Posts: 836

    I try do posing in a separate scene file as much as possible. That lets me do stuff like run simulations on clothing in a scene with minimal content as well. Then save the character as a scene subset (with simulation data) and load it into the "real" scene duf. 

  • felisfelis Posts: 6,062

    jmucchiello said:

    I try do posing in a separate scene file as much as possible. That lets me do stuff like run simulations on clothing in a scene with minimal content as well. Then save the character as a scene subset (with simulation data) and load it into the "real" scene duf. 

    You can simulate it in a larger scene, if you select the items that should participate and then Simulate Selected.  

  • Richard HaseltineRichard Haseltine Posts: 109,076

    felis said:

    jmucchiello said:

    I try do posing in a separate scene file as much as possible. That lets me do stuff like run simulations on clothing in a scene with minimal content as well. Then save the character as a scene subset (with simulation data) and load it into the "real" scene duf. 

    You can simulate it in a larger scene, if you select the items that should participate and then Simulate Selected.  

    Remeber that that is both the dynamic items and the static scene elements they should collide with.

  • jmucchiellojmucchiello Posts: 836

    felis said:

    jmucchiello said:

    I try do posing in a separate scene file as much as possible. That lets me do stuff like run simulations on clothing in a scene with minimal content as well. Then save the character as a scene subset (with simulation data) and load it into the "real" scene duf. 

    You can simulate it in a larger scene, if you select the items that should participate and then Simulate Selected.  

    I've been using Simulate Selected since before the plugin was absorbed into Premiere. But since I'm already in a different scene, why reload? Pose, clothes, simulate, etc all in a mini scene. Then move it to the real scene with everything else, like the set and lighting, etc.

     

Sign In or Register to comment.