OTOY Forums

VVG wrote:

aoktar wrote: I'll add a proxy node for orbx in next releases. But import and convert to geometry in to c4d scene is useless and big task. No need.

no need?

ORBX ecosystem between plug-ins is not needed?

maybe this needs to be asked from users?

what then is the ORBX format?

only export to standalone?

The ORBX package format was initially developed for packaging projects in the Standalone and for the export from plugin to Standalone and for the transmission to ORC.

Of course, it would be great to be able to load ORBX packages back into your 3D application, and it has been done for some plugins like Sketchup, but it's very complicated (and often impossible) to exactly convert the geometry from Alembic/FBX back into native geometry objects, which is why the current solutions all load ORBX packages as "black box", i.e. you can't change it - at least not via the C4D object/attribute managers. That should be fairly straight-forward to implement by Ahmet, but everything more advanced will quickly escalate in a huge amount of work and is probably not feasible.

abstrax wrote:

VVG wrote:

aoktar wrote: I'll add a proxy node for orbx in next releases. But import and convert to geometry in to c4d scene is useless and big task. No need.

no need?

ORBX ecosystem between plug-ins is not needed?

maybe this needs to be asked from users?

what then is the ORBX format?

only export to standalone?

The ORBX package format was initially developed for packaging projects in the Standalone and for the export from plugin to Standalone and for the transmission to ORC.

Of course, it would be great to be able to load ORBX packages back into your 3D application, and it has been done for some plugins like Sketchup, but it's very complicated (and often impossible) to exactly convert the geometry from Alembic/FBX back into native geometry objects, which is why the current solutions all load ORBX packages as "black box", i.e. you can't change it - at least not via the C4D object/attribute managers. That should be fairly straight-forward to implement by Ahmet, but everything more advanced will quickly escalate in a huge amount of work and is probably not feasible.

I did not even think about it converting everything back into native geometry. I understand that this is a difficult task and does not make sense.

don't need to native geometry.
enough FBX / Alembic geom + camera+mat+light

with ORBX packages then there will be an opportunity to exchange scenes between 3dmax / cinema / maya, etc.

The Published manual says about the orbx import in the live view menu:

"Used to load materials in Octane Orbx format. This optionc an be used to import scenes created in the Octane Standalone software"

Well, I tried to import a scene that I saved in orbx after exporting from MODO and no luck.

The scene opened just fine in the standalone.

Is the manual wrong or am I missing something?

Or at least how to get materials in the orbx to use in C4d Octane?

Well, Did figure it out but requires some manual labor.

1. Exporting the whole scene from standalone will only give you one material.

2. You have to right click and save each material individually as orbx in the standalone and then import
by selecting "Import Orbx" from the File drop down in the Live Viewer (could be other places I guess).

3. Could not get lights and Environment but those are easy enough to do manually

Hope this helps!

It's very old command just for importing one material from orbx.

Hi,
I bump this thread up. I imported an orbx file into C4D and I only see the container but not the material. How do I convert the orbx loader into an octane Material in C4D? Is this possible? In standalone the file is still working.

Thx

ceen wrote:Hi,
I bump this thread up. I imported an orbx file into C4D and I only see the container but not the material. How do I convert the orbx loader into an octane Material in C4D? Is this possible?

Thx

localdb is for importing materials.

Ahh ok. Thank you! It works.