As you can see I “GoNuts4” using Rhino. But I gave UV map exporting problems.
- I make a simple polysurface.
- Unwrap it using
- Convert it to
As you can see looks perfect
but is not the case exporting
The uv-mapping looks like is not updating properly the uv mesh after the mesh conversion and for that reason when loading or saving a Rhino file is not recalculating the uv map.
Enclosed you will find the file example: Debug-UVunwrap.3dm (93.2 KB)
Rhino6 and Rhino7 WIP: If you try to export the content as OBJ or FBX and reimport, the UV map is not correct.
I remember having this problem before. I was fixing it not making a surface that can generate tringles that merge in the centre (in a tube or a sphere I create holes in the poles). Anyway
Doing some research looks like is a known Rhino5 bug reported in 2016 using Rhino6 hope for a fix in Rhino7…
I hope for a fix as soon as possible or I’m making something wrong?
Do I need to report it as a bug? if that is the case, I suggest to developers (as a partial solution) to recalculate the UV map from the mesh when
unwrap is press and check if match the stored UV data.
If that does not work, as a dirty fix when
unwrap is press you can export and reimport the mesh using FBX or OBJ. In this way will pop out the broken UV expose them to the users. So that the user is conscious of the problem much sooner. I mean as a partial solution until a real fix is done.
Possible solution for the Rhino6 user:
before we create our custom UV mapping we need to set up custom Render Mesh Quality in the Preferences and after that, we need to create or export mesh with the SAME SETTINGS as the Render Mesh Quality settings in the preferences. After that, no UV problem will appear. Mesh displayed in the UV map should be identical with the export mesh.
solution: Mesh UV export problem
2019: UV mapping issues, export model from Rhino5 to 3D Max
2018: UV map problem after export
2017: UV map distortion when exporting OBJ (or converting to mesh)