OTOY Forums

i spent hours on this and am hoping the mistake is on my end.

i have a simple particle system baked in c4d and want to bring it to daz.

i exported the orbx and it works in other dcc but cant figure it out in daz.
in system tab i imort the "whole scene" and i can see the material being imported (unused) but cant find the geometry.

how do i make this work?

I have never tried to import an ORBX into the plugin, however my guess is that this function would not work, as there would be not way for the plugin to generate DAZStudio geometry assets from the ORBX Mesh nodes.

Paul

i will skip the snark and just ask:

so how do i work with particles or vdb sequences?

so how do i work with particles or vdb sequences?

The plugin does not currently support these - sorry. You would need to export the scene from DAZStudio as ORBX and import into Octane Standalone and add the particles there.

Paul

thanks paul, appreciate the clarification.

i´ve tried that standalone. infact i´ve been going in circles with c4d/blender/ue4 and now daz, with every version having one issue or the other. i was fed up and thought lets try standalone. here is the thing though:

1. there is a longer windup with particles, until they reach certain amount.
when i ported it over to standalone i realized there is no frame offset to the sequence. it renders from the beginning and only from beginning.

that means i have to line up all of the animated assets and cameras/light.
frame offset has been requested for years now and otoy didnt see fit to implement this most basic feature.

2. the second issue is beyond ridiculous and a disgrace.
as i said previously- i am working with tablets. the node editor zoom function is only accessed via mousewheel, which does not exist on intuos or cintiq.
and there is no way to rebind the keys. this is so absurd i am thinking it has to be a way i am not seeing here.
this software cannot possibly be this badly concieved can it?

besides that, there is no playback it seems and no way to even keyframe the most basic functions. but this is more a want than a need. the first two issues are showstoppers.

i found posts here mentioning these problems for years.
again cant fathom how these problems exist at this point in octane development.
i hope i am missing something here...

I suggest you forward these issues to the Octane dev team - either in the Octane Standalone thread, or via the Support button at the top of this screen.

Thanks

Paul