![]() ![]() In Rhino 5, the center of rotation ignores the invisible rendering mesh and properly snaps to the object(s) behind. To rotate or zoom-in or zoom-out the camera until Rhino 6 finally “sees” the projected line through the rendering mesh of the NURBS surface.Īnother problem with Rhino 6’s rendering solution (again, compared to Rhino 5 were everything was fine) is that when a NURBS surface or model is set to “wireframe” rendering mode through the “! _SetObjectDisplayMode” command and user wants to rotate the camera view around some other object behind the wireframed surface or model, the center of rotation still snaps to the latter even though it was supposed not to since the rendering mesh for this particular surface or model is invisible.To turn on the “Snap to occluded objects” which brings the problem with snapping to random objects behind (if any).To increase the file’s or object’s rendering mesh density (not a good option to do on complex models or waste time for every newly created surface).The only solutions to this issue currently are: I projected a straight line over a bent extrusion and now in 90% of the time Rhino 6 can’t snap to the projected line, even though it was supposed to work. Rhino 5 snap is better than Rhino 6 snap.3dm (58.4 KB) If you turn the “Snap to occluded objects” off, Rhino 6 will fail to snap to objects that are on a surface whose render mesh is covering the actual NURBS geometry. Well, one major problem with Rhino 6 is that it’s ability to snap to objects is worse than that of Rhino 5.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |