ORBX proxies please!

[Seekerfinder]

Hi Fuzzy,
Could you add ORBX as an option for proxy imports?

Cheers,
Seeker

[resmas]

+1

[fuzzybro]

Ok. It's going to be a bit limited tho. No simplified geometry, just plain orbx geo. And no material import.

[resmas]

Ok. It's going to be a bit limited tho. No simplified geometry, just plain orbx geo. And no material import.

Perfec to me

Thanks

[Seekerfinder]

Ok. It's going to be a bit limited tho. No simplified geometry, just plain orbx geo. And no material import.

Hi Fuzzy,
Simplified geometry - like one mesh - I can understand. But we'd need materials Fuzzy! I mean, what's the point if we have to add materials in the plugin? Then we could just import an OBJ, no? My thoughts here is that we texture in Octane standalone and 'package' the file for the plugin. Your OCS proxies already does that job but we will probably see more usage of ORBX between users - that's the only reason why I think it would be useful. Perhaps some of the others have different needs. So to me it's not on the 'urgent' list - 64bit is waaay more important...

Seeker

[fuzzybro]

Hey Seeker,


No-no, sorry. Materials will be imported into the plugin and displayed in Octane viewport just fine.
I meant that materials from ORBX won't be imported to materials library(a.k.a editor) and you won't able to reuse them.
In the current implementation when you import .ocs proxy materials are being added to the material editor under the "imported" category. This won't happen with orbx.

[Seekerfinder]

Hey Seeker,


No-no, sorry. Materials will be imported into the plugin and displayed in Octane viewport just fine.
I meant that materials from ORBX won't be imported to materials library(a.k.a editor) and you won't able to reuse them.
In the current implementation when you import .ocs proxy materials are being added to the material editor under the "imported" category. This won't happen with orbx.

Ah, got you. That's great, thanks Fuzzy.

Best,
Seeker

[resmas]

Hey Seeker,


No-no, sorry. Materials will be imported into the plugin and displayed in Octane viewport just fine.
I meant that materials from ORBX won't be imported to materials library(a.k.a editor) and you won't able to reuse them.
In the current implementation when you import .ocs proxy materials are being added to the material editor under the "imported" category. This won't happen with orbx.

That was what i thought great

Cheers