I had a small project recently with a really simple POP instance setup which I wanted to render on RNDR. When exporting the complete frame range, POP animations were completely missing from the ORBX file, single frames were saved correctly in ORBX though.
Started playing around and figured out if I use a frame range that starts 1 frame after the POP starts, the ORBX file is exported correctly. I had to slice up the complete frame range into 3-4 separate ranges to export the scene to ORBX.
Is this normal behavior or I'm missing a step with POPs?
Thanks,
Chris.
POP ORBX export
Moderator: juanjgon
- mirocreative
- Posts: 46
- Joined: Fri Jan 17, 2014 2:26 pm
- Location: New York
- Contact:
In order to render particles, they need to exist in the first rendered frame. If there are no particles in the first frame, it won't work. Just make sure there is at least 1 particle in the first frame and it will work.
Win 10 64bit // GTX 4090 + GTX 3090 // 5900x // 64GB // SideFX Houdini // C4D
- mirocreative
- Posts: 46
- Joined: Fri Jan 17, 2014 2:26 pm
- Location: New York
- Contact:
Got it, thanks for the help!galleon27 wrote:In order to render particles, they need to exist in the first rendered frame. If there are no particles in the first frame, it won't work. Just make sure there is at least 1 particle in the first frame and it will work.
Yes, sorry. This is a known issue. An empty object is excluded from the scene extraction, so if this happens in the first frame, later this object can't be updated in an animated sequence. At some point, I'll try to add a workaround in the extraction code to avoid this limitation.
Thanks,
-Juanjo
Thanks,
-Juanjo
- mirocreative
- Posts: 46
- Joined: Fri Jan 17, 2014 2:26 pm
- Location: New York
- Contact:
Now that I'm aware of the issue, it's more or less an easy fix, no big deal. Thanks!juanjgon wrote:Yes, sorry. This is a known issue. An empty object is excluded from the scene extraction, so if this happens in the first frame, later this object can't be updated in an animated sequence. At some point, I'll try to add a workaround in the extraction code to avoid this limitation.
Thanks,
-Juanjo