I recently switched to Rhino 6 and am now experiencing problems with textures and pictures on surfaces. When I try to open a picture in Rhino, it only displays a blank surface. I can see the image name in the material properties, but it doesn’t show up in the viewport. I have updated my drivers, so that is not causing this problem.
All my rhino files and textures are on Google drive, which I access through Drive File Stream on my computer. I think this causes the issue, because when I save the texture file on my desktop, it works perfectly… Does anyone know how to fix this? Is there a setting in Google drive I should change? Or could my virus protection be blocking the image somehow?
Hi Anne - so far this works here - I can add a Picture from my Google Drive/Filestream and it looks correct.
Can you navigate to the image via the object’s Properties > Material ?
Hi Pascal,
Thanks for the quick reply. I can see the image and navigate to it through the properties, but it doesn’t show in the viewports. I tried rendered mode and shaded, neither works. However, I also tried it on a different computer and there it works fine with the same files from Google Drive, so maybe that’s not the problem after all… Very strange…
Hi Anne - nothing leaps out at me here - I think I’d expect it all to work.
@jeff - do you have an idea? Pictures on a Google Drive show the correct path but do not display correctly on this machine - others in the office OK with the same situation, is what I understand so far.
@anne2 When navigating your Google Drive using Rhino’s material editor, can you actually see the images in the preview, or are you just seeing the file names? In other words, once you select an image for a texture channel, can you then see it inside Rhino’s texture editor preview? (see pic)
If you can see the actual image, then it means Rhino is able to load the file…and there is some disconnect between the Material Editor (ME) and the display pipeline somewhere… But atm, I have no idea what that would be… still thinking…
Just today I have had this issue as well with images on a GoogleDrive stream folder. Regardless of the files being made available offline or not.
This was my conclusion as well. The image shows in the ME yet renders white in the viewports. If I copy the imagefile to my desktop and load it from there all is fine.
Let me know if I can run any tests to track this down.
Does the ME stores the image in memory and does the pipeline read that image, or does the pipeline pick up the imagepath and loads it from disk?
On my phone ATM so no systeminfo yet. GPU is a GTX1070 iirc.
I can see the image in the material editor preview, it looks fine there. If I select any of the default materials, it displays them correctly in the viewport, just the images from Drive that cause this issue.
I also tried opening the image file from Drive in Photoshop, this works fine, no problems there.
Hi Willem - thanks for the details - here, I’m using Drive Stream and drag-and-drop or the picture command both seem to work as expected. Hm - however, the image on the Google drive originates on this machine, I’ll test some other scenarios…
Any update on this topic?
Seems like the problem occurs when the path to the texture has to go through “shortcut” folder of the file stream.
Also, mirror UV temporarily fix the problem if you don’t mind weird decalcomania look.
this exactly seems to be the problem! I really would like to have this fixed, I am currently working on a clients project completely based on google stream… No texture shows up in the viewport!
Seems like checkboxing Clolor mask works great as a temporary solution!
Saving texture with rhino file won’t work as far as the rhino file is in the google drive. (it will work for a while and blank out on first autosave)
