Page 1 of 1

Quixel bridge megascans workflow into Rhino Octane material.

Posted: Thu Jun 06, 2024 6:08 am
by splittmatt
Hi.

I am trying to find the best way to import downloaded Quixel Bridge textures into a Rhino octane material. I can import the files into Rhino's Physically based material slot easily using a zipped file of all the downloaded files, but when converting to Octane material it loses all the textures.
Is there another way rather than make an Octane material and manually point each section to the relevant texture?
It's been a while since I've used Octane so I may have missed something.

Thanks.


Matt

Rhino Version 8 SR7
(8.7.24138.15431, 2024-05-17)
Octane 2023.1.3.139

Re: Quixel bridge megascans workflow into Rhino Octane material.

Posted: Thu Jun 06, 2024 9:45 am
by face_off
I haven't used the Quixel Bridge textures, so I don't know the answer to your question.
I can import the files into Rhino's Physically based material slot easily using a zipped file of all the downloaded files
Are you able to see me a .3dm file of this so I can see why it is not converting the textures to the Octane material?

Thanks

Paul

Re: Quixel bridge megascans workflow into Rhino Octane material.

Posted: Mon Jun 10, 2024 1:49 am
by splittmatt
Hi Paul

I've found that if I convert the Rhino Physically based material to a custom and then to an Octane material it keeps the base map and bump/normal at least. If you convert it straight from Physical to Octane none of the textures stay connected.
The reason for starting with a Physically based material is that I can create new material instantly from a zipped file of all the textures. Is it possible to have this option when creating a new Octane material?

Thanks


Matt
rhino_PBM_Octane.jpg
Rhino_create new material.jpg
Rhino_create new material 2.jpg