VRSCENE export broken

[Dubbie99]

Houdini 19.5.368 - Py3.9
vray_adv_52024_houdini19.5.368_3de6c1d_22151

When I export a VRSCENE sequence in this build, the first frame has geo and nodes in it, but then any subsequent frames have nothing, so they render black.

you can see from my screenshot that there is nothing in the scene past the first frame:

[tsvetomira.girginova]

Dear Dubbie99, hello.

I've tested the same build and the export was successful in a simple scene with animated objects.
As far as I see the main .vrscene files (including everything = _test_v001.000#) are 15KB. Please confirm that rendering them results in black images.
If you untick Separate Files is the issue visible through the main export (one .vrscene file per frame only)?
Bitmaps, RE and textures are always 0 in your case as shown, so if we focus on geometry - it may be connected to the exact way of creating or animating it.
Let's find out why it couldn't be exported in _geometry.

Please, either share screenshots of the geo creation or upload a simple scene where the issue is reproducible.
If the .zip is too large to be added at the forum, please use our contact form and mention this thread at the description.

Best regards,
TS

[Dubbie99]

Hi, yes the frames past frame 1, render completely black.

I tried a simple scene with a plane and a sphere and with seperate files on and off. Same problem.

I only screen shot the separate files mode, to make it clear that it was just nodes and geo that are missing.

rolling back to 19.0, the scene exports as expected.

if I remove the frame number from the vrscene name to force a single vrscene file for the whole sequence, it renders the other frames fine. This doesn’t work for us though as it kills performance on the renderfarm.

I will send the test scene.

[tsvetomira.girginova]

Okay, thanks for the details.

Our dev team has made some improvements.
Could you please test your scene with the fresh uploaded latest nightly builds and confirm is it working as expected?

Waiting for your feedback.

[Dubbie99]

Sorry I missed this message.

the latest builds indeed seem to have fixed the problem. Thankyou!

[tsvetomira.girginova]

No worries.

Thanks for the confirmation.