Tweet
So I'm playing more with using the scene translator to then kick off a distributed render for an image sequence.
Could I request to replace the "frames" field in teh standalone tab with Nuke's standard frame range dialog (see attached)?
This would make it way more intuitive for Nuke users.
Also, if frame padding is used in the imgFile field it would be nice if VRay treated this the same as Nuke, i.e. replace any "%04d" or "#" notation with the respective frame number rather than use it literally as part of the file name. I understand that VRay does thing differently on this level, but maybe a bit of code can take care of the discrepancy when creating the standalone command line, so the user doesn't have to think about the difference between VRay and Nuke when it comes to frame padding.
It's just about making this part of the VRay experience more consistent with the rest of Nuke rendering.
Cheers,
frank
Could I request to replace the "frames" field in teh standalone tab with Nuke's standard frame range dialog (see attached)?
This would make it way more intuitive for Nuke users.
Also, if frame padding is used in the imgFile field it would be nice if VRay treated this the same as Nuke, i.e. replace any "%04d" or "#" notation with the respective frame number rather than use it literally as part of the file name. I understand that VRay does thing differently on this level, but maybe a bit of code can take care of the discrepancy when creating the standalone command line, so the user doesn't have to think about the difference between VRay and Nuke when it comes to frame padding.
It's just about making this part of the VRay experience more consistent with the rest of Nuke rendering.
Cheers,
frank
