Hi,
I have trouble with my workflow for animations after migrating to V-Ray Next.
With earlier versions I have used a simple C# component to trigger rendering with Rhinos Render command. The script would then wait until the render finished and save the frame, before incrementing the frame number and repeating the process.
This worked like a charm, while having the "Batch render" option ticked in V-Ray. As far as I can see this options has disappeared.
Thus, I tried to migrate to the official Grasshopper components.
This seems to work ok with one missing input: the camera up-vector / rotation/tilt around camera axis. (I'm trying to match the animation with a drone-shot)
If there is a way to enable the old method of setting up an animation render ("batch render" option) that is the easiest as I can change the camera from the script before triggering a render.
This would also make it possible to change material settings and/or textures frame by frame with the V-Ray Scrip Access.
In general I think moving the trigger render button in Grasshopper from the right-click menu to an input that can be triggered with a boolean toggle or button etc. would make it a lot more flexible.
I hope there is a solution that I have missed or hidden options accessible from the V-Ray Scrip Access.
I have trouble with my workflow for animations after migrating to V-Ray Next.
With earlier versions I have used a simple C# component to trigger rendering with Rhinos Render command. The script would then wait until the render finished and save the frame, before incrementing the frame number and repeating the process.
This worked like a charm, while having the "Batch render" option ticked in V-Ray. As far as I can see this options has disappeared.
Thus, I tried to migrate to the official Grasshopper components.
This seems to work ok with one missing input: the camera up-vector / rotation/tilt around camera axis. (I'm trying to match the animation with a drone-shot)
If there is a way to enable the old method of setting up an animation render ("batch render" option) that is the easiest as I can change the camera from the script before triggering a render.
This would also make it possible to change material settings and/or textures frame by frame with the V-Ray Scrip Access.
In general I think moving the trigger render button in Grasshopper from the right-click menu to an input that can be triggered with a boolean toggle or button etc. would make it a lot more flexible.
I hope there is a solution that I have missed or hidden options accessible from the V-Ray Scrip Access.
Comment