You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the autoscaleStrucutres option, there may be an issue with the relativeValue computations (state::lengthScale might not be updated properly). For instance, if you attach an ambient vector field to a structure, the length and radius slider limits are super small (when you scale down a huge object to the unit cube thx to the autoscale).
The text was updated successfully, but these errors were encountered:
Ah, this makes sense. If state::lengthScale seems fine then it might just be a UI issue, I still haven't figured out how to expose absolute/relative values in sliders intuitively--it might just be a matter of using different limits for absolute values.
Also, this raises another problem: if a structure is being scaled drastically via its model transform (like what happens due to autoscaleStructures), should data like radii be set in the original units, or the scaled units? Right now I think these values get set in the original units, and that's probably the only sane thing to do, but I'm not even sure.
I'll have to dig in to improving this for a future version. Let me know if you spot any concrete bugs, or have any ideas about how things should work!
(FYI for others: remember that you can always manually set a value by ctrl-clicking on the UI sliders as a workaround)
When using the
autoscaleStrucutres
option, there may be an issue with therelativeValue
computations (state::lengthScale
might not be updated properly). For instance, if you attach an ambient vector field to a structure, the length and radius slider limits are super small (when you scale down a huge object to the unit cube thx to the autoscale).The text was updated successfully, but these errors were encountered: