Hi, that would be very helful to avoid that framerange bug (unfortunately this keeps happening but I don't know why):

viewtopic.php?f=103&t=76399&p=398239#p398239


Thanks,
F

Hi, This is just to confirm, it's working without crash on my side.
thanks again.

Hello,
Currently when exporting ORBXs from Houdini, their framerange gets offset and starts at 0 when imported in other softs and Octane Standalone.
Would it be possible to have an option that keeps the same framerange as Houdini please?

Thanks,
F

Hi, This is great thanks Juanjo!

Hi Juanjo,
did you find the source of the crash by any chance?

thanks,
F.

Hi,
I'm not able to export that many frames to ORBX, I tried that on two different machines but no luck...
Please have a look at the attached screencapture.

Thanks,
F

edit:
0-1430 framerange never works, but 0-1431 works perfectly...

I'd like that, a robust ORBX export/import would be a really powerful tool.

Hi,
I'm not sure if it's the same issue, but I'm also unable to export ORBXs when the framerange goes in the 1400 ish frames.
the idialog shows as if it's exported, but the orbx isn't created in the folder.. I've tried many things but I'm out of ideas. I need the timing in the orbx to correspond to ...

Hi,
Yes I did, I actually have that issue across many if not all my Houdini scenes. It also happened on different machines in the past.
The crash happens every 2/4 export(from the most basic to more complex scenes).
Please find attached a different Houdini project and octane logs.

Thanks,
F

Hi,
I see thanks, I was trown out by the fact that merging in a single point didn't always fix the issue.
But merging a polygon of scale 0 with all necessary attributes seems to do the trick with more consistency!

Thanks,
F.