Hello,
it may sound strange but i find some bug when submitting camera using consolo_vantage.exe with a start frame different from 0.
Description:
When rendering an animated camera via the Chaos Vantage CLI (vantage_console.exe), the camera animation fails to evaluate properly and the render unexpectedly switches to a static perspective view if the -frames range starts at frame 25 or higher.
Steps to Reproduce / Detailed Behavior:
- Export a
.vrscene containing an animated camera from 3ds Max.
- Execute
vantage_console.exe via command line with a frame range starting at frame 25 or above (e.g., -frames=25-50).
→ Result: The sequence renders from a default static perspective view, completely ignoring the camera animation.
- Execute the CLI with a range starting before 25 and spanning across it (e.g.,
-frames=20-50).
→ Result: Frames 20 to 24 render correctly using the animated camera. However, precisely at frame 25, the view abruptly drops the camera and switches to a static perspective view for the rest of the sequence.
- Execute the CLI starting from frame 0 (e.g.,
-frames=0-50).
→ Result: The entire sequence renders correctly using the animated camera from start to finish without any issues.
Environment:
- Software: Chaos Vantage (v3.4.0) CLI
- DCC: 3ds Max 2026.3 (.vrscene export)
Also in a different scene the camera and the rendered framerange are offset by 100 frame.
Frome command line using: -frames=100-800
The rendering animation start form frame 200 to 900 but save the images as .00100.png
Best regards,
Federico
Hi Federico,
While the steps and the setup is not something complicated, I’m not able to replicate exactly the same behavior here. Is it possible to attach a 3dsMax file to use your scene to export ? Is the active camera/view selected when exporting ?
Also do you specify the camera name when running the command in CMD for Vantage rendering ?
Hi,
thanks for the respons.
Here the link withe the files:
Include the 3dsmax scene (simple setup), the .vrscene exportet, 2 .bat files i used to test the console command and olso the full script for camera manager in vantage.
When exporting a `.vrscene` from 3ds Max with a restricted frame range starting at frame 25 or higher (e.g., `startFrame:25 endFrame:50`), animated cameras fail to evaluate and render as a static perspective view in Chaos Vantage.
When exporting the same `.vrscene` from 3ds Max with framrange 0-100 the console command works fine even with different framerange from console.
I hope this is clear enough. If you need any further details or a screen recording reproducing the behavior, please let me know and I can record and provide a video.
Cheers.
Thank you! I can replicate it now and will try to find what is happening.
The .vrscene is exported with frame range from 3dsMax 25 > 50, but when loaded by Vantage this is remapped to 0 and this is the reason why you don’t get the correct animation output for the frames after 25.
You need to export the entire frame range from 3dsMax 0 > 50 in this case.
Maybe we should think about how to improve this workflow in the future.
this mean that if i have a scen that start at frame 41000 to 41500 i have to export the scene from 0 to 41500 and then render only the selected framerange?
it’s not very practical 
Also if you change the frame range to 100-800 the vantage render start from frame 200 and save the images name as _100.png causing obvious error in frame handling.
I need to test if it was the same behavior in version 3.3
Best regards,
Federico
The render animation doesn’t work good with this specific workflow and we have to improve that. I will discuss the case with the team as there is a very similar issue report recently. Will provide updates here.
Thank you once again for preparing the samples and reports.
Also if you change the frame range to 100-800 the vantage render start from frame 200 and save the images name as _100.png causing obvious error in frame handling.<
Yep, unfortunately the same limitation. Moving the 100 frame at Zero - and the frame number 200 becomes at 100. Or I’m missing something ?
I need to test if it was the same behavior in version 3.3 <
Should be the same for the older version.
Hi,
Okay, thank you for the clarification. It feels a bit unusual to be the only one trying to use this CLI workflow to manage and batch-render multiple cameras via a script.
For the time being, I’ll stick to exporting directly from 3ds Max, but having this fully operational via script would be extremely helpful for faster and more precise render management.
Thank you for your time and assistance.
I’m not sure if this can be a temporary solution for the automation you use, but to avoid exporting big vrscene for ranges like 0 > 41500 , set the range to 41000 > 41500 and then from Vantage console use the -frames= 0 - 500 instead. Placing all ranges to zero.