The textures somehow are replaced by a mirroring surface. To cure this, I have to cut an affected block instance, and repaste it into the file. Then suddenly the correct textures reappear. I suspect something fishy in interaction with the graphics card (FirePro W9100)
I meanwhile did a system recovery back to the point before I installed the latest AMD driver (January 3rd) because I felt some of the texture problems occurred since then - and yes, obviously the latest AMD driver has problems with Rhino7:
This however does not cure the initial problem of erratic and messy textures mentioned above.
I gladly can upload parts of the project, but please be aware these are hundreds of files, the oldest stemming from 2010 and Rhino3/4 and now mixed versions of Rhino5/7.
Hi @Cyana, there appears to be flipped faces on the custom mapping meshes. One easy way to solve this problem is to run _UVEditor, select the UV texture mesh of the malicious face and _Flip it.
Are you only seeing this issue on models created with Rhino 5?
thank you for your reply. Yes, all textures were made with Rhino5, where they looked correct. I have not yet created textured objects with Rhino7, as the project is nearly finished.
How can I find out if a mesh is malicious? And how can become a face malicious?
Does this also explain inconsistent behavior like mentioned above?
More general, I experience an inconsistent erratic behavior with textures in Rhino7:
While textures are correct here
@Cyana, by malicious faces I mean those that show wrong texture mapping in Rhino 7. Those issues are caused by flipped faces in custom mapping meshes (the meshes attached to the custom texture mapping object). Like I described you can flip those manually using UVEditor and Flip commands. But it is also possible they are flipped because of a bug in Rhino 5. Anyhow I’m working on a fix for Rhino 7 based on an idea I got after my last reply.
Could you upload a model with that object you have selected in the screen shot? I’d like to fix that as well. Thanks!