My usual workflow is to map images in Rhino with custom materials and then live link to Keyshot. Previously, the images would transfer over to the Keyshot file mapped on the object as it was in Rhino, but lately this has not been working. The part in Keyshot reads as a custom material, but the image is not there.
Is there any fix for this? Would an older Rhino installation fix my problem in the meantime?
Hi @Lucas27 ,
Just saw this one if you still need help…
I don’t use KS myself but have students that do with success. I’d check first if the version of KS you are using supports the version of Rhino you are using. There may be an update for KS you can try. You might also experiment with alternate workflows to see if you can determine where the issue is. For instance, try saving a 3dm file and opening that in KS versus the live link.
Hi Brian,
Thanks for the reply. I found that a different material setting works. If I use a “physically based” material, the images once again pass through to Keyshot.
Ah perfect, thanks for letting me know. PBR is the better material choice anyways.
Hi Brian,
I am running into a new issue with images mapped onto objects and linking to keyshot. Objects are losing their mapping as they are linked from Rhino to Keyshot. The label is still there, but not mapped as it was in Rhino. Not all objects lose their mapping and not every time. Images UV mapped onto an object seem to work just fine, but planar mapping is where I am running into the most issues. I noticed this issue last Friday and it has persisted.
Thank you for your attention to this issue. This is a process I use all the time for work and would love for it to work more consistently like it was before last Friday 4/10.