We’re looking to roll out Rhino 6 company-wide, and we have a few issues, the largest being the OBJ export bug. We have 6.3.18090, and we can’t export obj files at all. Generally, Rhino goes through and processes all objects in the scene, and freezes during the ‘Meshing’ phase.
Was there ever a fix for this? We’re looking to purchase around 100 licenses, and this is a major bug in our workflow.
From my testing, the mesh command works fine, it’s something to do with preparing the mesh to write to file. Based upon task manager, no actual information is written to disk at any time during export, though on occasion, Rhino creates an empty .obj with no information in it.
I’m having another big problem with obj export from Version 6 SR17 that doesn’t show in V 5.
In V5, exporting an obj with simple controls and the slider set all of the way to the left, or toward Fewer Polygons gives you an obj that is usually a near 1:1 match between the surface iso’s and the quads on the obj mesh.
In V6 and the WIP, exporting an obj with simple controls and the slider set all of the way to the left, or toward Fewer Polygons gives you an obj with NO match between the resulting obj file and the original surface. If you import the obj you just exported, you’ll notice that it is merged into a single polygon shape if the original surface was flat, and on objects with curvature, the polygons are nearly 1:1 where there is a lot of curvature, but merged in flatter areas. Also, if you use MeshFromSurface/Polysurface the result is nearly 1:1 iso-to-face until you export the mesh as an obj for use in other app’s, which gives you the same unwanted merged polygon object.
This is the result with all of the settings between V5 and V6 set to the same value.