Our pipeline uses the start frame as 1001, as do most studios that work with lots of simulations etc. When exporting the ORBX file as a frame range, for example 1001-1051 (50f), the ORBX offsets to 0-49, so when rendering the frame number does not match the original scene. What's the workaround for this? Or is it a bug?
Thanks
Orbx export changes frame range
Moderator: juanjgon
-
ricky_otoy
- Posts: 289
- Joined: Mon Jun 19, 2023 6:34 am
There isn't currently a workaround (as far as I know), but I have logged it into the system to get looked at for you. I know there are some studios that do use this as a start frame etc.
Sorry for the inconvenience right now!
Sorry for the inconvenience right now!
-
ricky_otoy
- Posts: 289
- Joined: Mon Jun 19, 2023 6:34 am
Hi, just an update.
We require a change to be done for us in the SDK, so unfortunately the upcoming release builds won't have the change you need just yet.
Although as far as I know, it may work with motionblur off.
We require a change to be done for us in the SDK, so unfortunately the upcoming release builds won't have the change you need just yet.
Although as far as I know, it may work with motionblur off.