Exporting

[fuzzybro]

Also, this is how you create Proxies!

Create high-poly object in SU, apply all the Octane Materials and export in to an .ocs file.
After that reuse it as an Octane Proxy to get High-Poly object in OctaneViewport and Low-Poly object in Sketchup.
Hight-quality rendering and responsive Sketchup. Win-Win

[smicha]

Each instance will be exported as a separate object which would be hard to configure in standalone.

So it is not creating any scatter node data for exporting translation/rotation/scaling of instances?

[fuzzybro]

Each instance will be exported as a separate object which would be hard to configure in standalone.

So it is not creating any scatter node data for exporting translation/rotation/scaling of instances?

It is creating. Plugin creates an exact map of SU geometry, i.e. there is only one mesh for ComponentDefinitions and Instances and Groups are handled using scatter nodes saving a lot of memory. Creating thousands of instances is almost free.

[smicha]

Each instance will be exported as a separate object which would be hard to configure in standalone.

So it is not creating any scatter node data for exporting translation/rotation/scaling of instances?

It is creating. Plugin creates an exact map of SU geometry, i.e. there is only one mesh for ComponentDefinitions and Instances and Groups are handled using scatter nodes saving a lot of memory. Creating thousands of instances is almost free.

Sorry for so many questions So in exported ocs we have let's say a component as a single obj and a scatter node connected to it to replicate its copies?

[smicha]

Fuzzybro,

Could you please do me a favor and open the attached file and export it to .ocs using the new plugin and send it back? This will give me precise info of how the file looks like.

[fuzzybro]

Fuzzybro,

Could you please do me a favor and open the attached file and export it to .ocs using the new plugin and send it back? This will give me precise info of how the file looks like.

Sure, here you go.
The picture and the output scene data.

[smicha]

Fuzzybro,

Could you please do me a favor and open the attached file and export it to .ocs using the new plugin and send it back? This will give me precise info of how the file looks like.

Sure, here you go.
The picture and the output scene data.

Oh !!!! This is far beyond my expectations! Fantastic!

[smicha]

Fuzyybro,
Here is one more file with scenes and two components, one of which has its proxy (created by GOSU, Renderiza plugin). Additionally one group is placed on a different layer and one more is hidden (on the second scene).

Could you please again convert the file to ocs and upload it? I'd like to see how the plugin handles different component placements.

[fuzzybro]

Fuzyybro,
Here is one more file with scenes and two components, one of which has its proxy (created by GOSU, Renderiza plugin). Additionally one group is placed on a different layer and one more is hidden (on the second scene).

Could you please again convert the file to ocs and upload it? I'd like to see how the plugin handles different component placements.

Here you go

[smicha]

Fuzzybro,

Thank you! Question: is it possible to automatically name objs as SU components names. Not as mesh_number? It would ease finding proper objs.