This is just an idea for developers or a petition
Can WIP Rhino7 somehow as for example scale down internally big objects and scale up smaller ones for each operation?
Accuracy is one of the grates points of Rhino, but we need more. Is not intuitive for users that you must stay on the grid and use default settings. And after years of experience, you learn the correct working zone.
Some research: User comments
Some modelling tools would need some refinement and increase in reliability (for example booleans and solid fillets)
Also if you are dealing with very small parts with a high level of accuracy, or very large file sizes, other programs may be better suited. I design boats and if you are not careful, it is easy to loose your center line which is a big problem when building symmetrical things. Using gumball (the Rhino command to move an object through a pop-up with x,y,z coordinates) is not always accurate and you need to keep an eye on your tolerances when using it.
It takes some time to learn how to use it, it is not very intuitive, much practice is required before you will be able to do complex shapes.
I’m having problems with tolerance. Does Rhino need to handle more precision in the workflow?
If I make a large vehicle, I wish to render in a big environment exterior and at the same time, provide the smallest modelled detail, working on the smaller part of the motor ( is not so simple). “So it’s quite good for basic modelling but for detailed models and mechanism probably it is not enough.” This is also because is missing radius injection but probably grasshopper fill this gap.
I wish the Rhino7 would improve and expand the working zone (the greatest permissible distance). Usually, I render outside, but so that we can work on a big vehicle with the same precision of smaller objects and not having problems making nuts fillets for example.
I’m not talking about changing higher than needed absolute tolerance to fit inside rhino needs. We don’t need intersections with many, many control points! I mean reduce the noise level, improving the Rhino functions accuracy or the size of the grid. To provide and ensure greater consistency across object size.
Actually, the object must not be too big or too small. That create issues and unnatural workflows.
Maby Rhino has a destructive workflow when you move and modify objects and that is the reason for using doubles? In that case, consider a fixed object in the centre or making no destructive workflow (like Substance Designer Layers).
In games, Kerbal Space Program was able to cover more play space and handle better position jumping from floats -+7 to double-precision floating-point. Rhino uses 64bit or double-precision but can’t handle that amount of space? we can only work in a limited zone size.
An internal automatic scaling of the object when making an operation, applying functions can improve software handling?