I also think that the needed values are always in a very minimal range. And that is at the moment really hard to finetune. That’s why we start typing it in manually.
I’d really prefer to have it setup with the reciprocal / inverse values.
That way we would get “faces per meter” ( along a single axis) wich is also a meaning that’s easy to grasp.
What is now really rough to setup, would get more finegrained (and vice versa). But that would be much better for typical value ranges.
The example of bobo_the _imp would be in a range from 50 to 100
That might be already too finegrained.
So we could add about a multiplier ( faces per meter (x10) ) --> facesPerMeter = 1.0 / (voxelsize * multiplier ) with multiplier =10
1 would be 10 faces per meter ( currently the default 0.1 voxelsize)
2 would be 20 faces per meter ( voxelsize = 0.05)
5 would be 50 faces per meter ( voxelsize = 0.02)
10 would be 100 faces per meter (voxelsize = 0.01)
100 would be 1000 faces per meter (voxelsize = 0.001) could be the future slidable maxvalue
1000 would be the current possible minvalue ( voxelsize = 0.0001)
by allowing the 2 digits in the slider as it’s the default for values > 0 choices should be fine enough for all our needs
( Edit: We could also call it voxels per meter to better indicate that the resolution refers to an axisaligned 3d grid stepping)
Alternatively it could be changed to logarithmic scale ( something like log10(voxelsize) + log10(minvoxelsize) ) as it would fit quite well to linearize it, but that way we’d loose to have a good imagination of what a value stands for