vrscene export framepadding changed/broken?

[David_L]

I updated our VFH to the latest version, and now vrscene export seems broken, framepadding for image output used to get exported as #
$F4 (houdini) -> # (vrscene)
now it exports
$F4 (houdini) -> <frame04> (vrscene)

also this line is missing from the new export:
anim_frame_padding=4;

This results in framenumber missing in the filename from vray standalone. ie. what used to render as beauty.1001.exr now renders as beauty..exr

Is this a bug or intended workflow?

VFH is 4.12.03

[David_L]

To clarify here is a compare between old an new vrscene files output from VFH.

[David_L]

Nevermind. Worked around the issue with the guys from royalrender

[Gosho.Genchev]

Good to know! How did you guys work around it ?

Technically the issue is the official standalone build is a bit behind the V-Ray for Houdini nightlies. Andrei also works on the VRScene format so all the cool new things come to Houdini very fast. Once we update Standalone, everything should be smooth.

Cheers!

[David_L]

As far as I can tell the guys at RR just added these flags to vray standalone call:
-noFrameNumbers 0

Nothing changed on the VFH vrscene export side of things

[dougWilkinson]

Good to know! How did you guys work around it ?

Technically the issue is the official standalone build is a bit behind the V-Ray for Houdini nightlies. Andrei also works on the VRScene format so all the cool new things come to Houdini very fast. Once we update Standalone, everything should be smooth.

Cheers!

Hello,
Is there any info on when vray standalone will be updated to support that new frame padding format <frame04>?

Thankyou,
Doug

[Gosho.Genchev]

Hey,

the changes are available in the standalone nightlies - if you guys have access, starting tomorrow all builds should work for you.

If you'd rather wait for an official Standalone release, I'm not exactly at liberty to give you a specific date but it will be quite soon.

Cheers!