I’m almost always working with data sets that use meters for units. Therefore, sensible radius values are typically going to be on the order of 0.005-0.05. Having the Mesher radius default to the much to large 1.0 isn’t a big deal since it’s easy to use “Suggest Radius” to get a more sensible value. However, if I need to adjust that value the only way I can do it is by typing in to the box since the slider goes from 0-100 and is therefore much to sensitive to enter the very small values I need.
Since a reasonable range of values is going to depend on the units the data is in and the scale of object being worked on maybe it would be better to set the slider range as a percentage of the object’s bounding box? Having a slow adjust modifier for sliders would also probably be useful.
Thanks for the feedback, we are having a discussion about all possible solutions to this problem we could think of.
We will let you know once we have implemented one or more of them (unless you find them in a weekly build first).
They won’t be in today’s build though, but we got another wishlist item of yours checked off today, so things are moving along…
BTW, I’m liking the ability to turn on lighting for point clouds that have normals. Now we just need a way to estimate normals for point clouds that don’t have them…
We also need to expose to the UI the Diffuse and Specular colors of the 2-Lights rig and of the Headlight. It is on our To Do list, but some other things had priority. Note that you can tweak those via the sequoia_colors.json file right now.
