Rhino7: Unable to correct messy textures

Could you maybe share the object as the original v5 file? That will make it easier to investigate what the difference is between 5 and 7.

Thank you.

I will browse my backup archive to see if there is still a Rhino5 version there.

I’ve corrected some mappings meanwhile, however this one came up with the same broken texture as before:

I double clicked the block definition and got this error message:

It says that due to a failed memory allocation Rhino will close and I should restart the computer. The created emergency file looks correct:

More general, I experience an inconsistent erratic behavior with textures in Rhino7:
While textures are correct here

same block file is incorrect here. In both cases, the block file is linked to the main file.

Often, a file comes up like here:

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)

Here the system information:

Thanks
Cyana

The last two images, are they in Rendered mode?

In any case it would be useful for us to receive all necessary files to investigate. Probably easiest to put all files in a Zip archive, then upload it using https://rhino3d.com/upload?to=nathan@mcneel.com

This will keep your files further out of public, but allow us to investigate. If you do upload, please add a link to this discussion in the comment box of the upload form.

Thank you.

Yes, all images are in rendered mode. I’ve got the Rhino5 version of equ.073:

equ.073.PneuBulkheadPlt2_200.3dm (2.1 MB)

On my machine in Rhino5 it looks correct.

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:

Latest AMD driver:


AMD driver 2017

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.

thanks
Cyana

Thank you, I think for now the v5 version of the file will be a good starting point for investigation.

I do see correct Rendered mode in v5, and incorrect in v7. I think I’m going to ask @Jussi_Aaltonen to look into this since he’s better versed in the UV mapping code. We’ll let you know what we find.

Thanks Nathan for your patience and your help!
Have a nice Sunday.

Cyana

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?

Hi Jussi,

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?

Blockquote
More general, I experience an inconsistent erratic behavior with textures in Rhino7:
While textures are correct here
Blockquote

Blockquote
same block file is incorrect here. In both cases, the block file is linked to the main file.
Blockquote

thanks
Cyana

@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!

Filed as RH-62523 Flipped faces cause incorrect texture mapping

Hi Jussi,

thank you very much for your efforts to resolve the issue. Here is the file in question - however, all similar files (these vertical cable trays) are affected.
CTS24.3dm (5.0 MB)

I’m trying to understand the issue - I think, I did not intentionally flip any meshes, also, when I’m in the UV Editor, I cannot tell if the mesh is flipped or not.

Here is another example of a strange texture behavior:
cabtray24.90deg.3dm (224.5 KB)
The texture of the cables has a gray area. When you cut the whole object and repaste it, the texture shows up correct. This however is not persistent. When you store and reopen the file, the gray area is there again.

thanks
Cyana

Here an elaboration for the second texture problem, maybe it helps to find the underlying problem:


Here you see the messy texture of the Rhino object, and the result when you export it to SimLab Composer.


When you cut the object and repaste it, it comes up with a correct texture. Also the export to SimLab is correct.

Interestingly, when you link the object to another file as block definition, in most cases it shows up correct.

thanks
Cyana

Thanks @Cyana

The vertical tray model seems to work now with the fixes I made last week.

The 90 degree turn tray shows a problem with extrusion object and the Advanced texture preview. Filed that as: RH-62560 ATP wrong on extrusion

Hi Jussi,

thanks a lot for working on these issues. My project is in the final stage and a fix would be really appreciated!

Blockquote The 90 degree turn tray shows a problem with extrusion object

So a workaround would be to convert the object from extrusion to combined faces (hope this is the correct translation of German ‘Flächenverband’)? I’ll give it a try and let you know.

best greetings and thanks
Cyana

Here my tests:


I’ve converted the object from extrusion to combined faces, saved, closed and reopened the file. The cable tray looks correct, however export to Simlab is messy.


Cut & paste again cures the problem - the export to Simlab looks fine.

What do you use to export to SimLab?

And Flächenverband is polysurface in English :slight_smile:

Hi Jussi,

thanks for the correct translation :wink:
I’m using the SimLab integration plugin for Rhino 7:

The export worked fine with Rhino 5:

thanks
Cyana

Hi @Cyana, I’ve contacted SimLab and requested a minor change to their integration plug-in to solve that last issue.

Thanks Jussi - hope they will listen, I told them about the problem twice but there was no reaction.

Please let me know when your Rhino fix is available!

Hi @Cyana
Just browsed looking for a solution to a UV editor problem, and just wanted to say WOW, that’s an impressive model!!! Well done :+1:
-Jakob