Moving object breaks explicit texture mapping

Image 1: unwrapped and texture mapped object perfectly mapped
Image 2: moved object (happens with move command, gumball rotate, mirror, translate) with broken mapping
Image 3: correct mapping when I open texture map editor
Image 4: 2D image of correct mapping

When I close out of texture mapping the incorrect mapping returns. This happens in Rhino viewport and Enscape so it seems to be a Rhino mapping problem.


I am running latest release of Rhino 7 on a Windows 10 machine. XEON, Nvidia RTX 5000

Hi @Thomas_Moran

I’m not seeing this issue here in a quick mock up of what you described. Can you post your 3dm file with just this object in it and textures saved in the file. Use the Export command to save only the current selection.

Thanks for the quick response. I’ve discovered two workarounds. The first is to copy each polysurface to its new location and then unwrap it. This means then moving and scaling the render meshes in the UV editor but it seems to work. The second is to just use box mapping. This is less than ideal because the model was textured in Quixel Mixer to have specific object/texture relationships but it gets it done. At least every column won’t have the same obviously tiled brick material.

Thanks again!
Column Problem.3dm (19.3 MB)

Thanks for the file, I reported this as for future reference. You can alternately move the column closer to 0 and then rotated copies will preserve the mapping. Making a denser custom render mesh for the column also will diminish the artifacts in the model’s present location but this will add overhead to the model and render. If you can work closer to 0 that would be my suggestion in the meantime.

Update… looks like this doesn’t always prevent the artifacts. Sorry, I will need the developers to look at this one. @Jussi_Aaltonen @andy

Thanks for the report and model @Thomas_Moran. That bug seems to be related to stuff that is on my Rhino 8 pile.
When your object still has the correct look you can run TestRenderMeshMapping. That resets the mapping object transform (shown as XYZ position on Texture Mapping properties). When the mapping object transform is identity the mapping is more likely to survive when you rotate/move object.

1 Like

@Thomas_Moran Hi, this bug is fixed in Rhino 8 WIP.