
I'd like to know how hard would be to have animation support?
I'm talking about camera animations so without need to re-export the obj file each time.
Thanks for your work.
Moderator: face_off
Which animation tool are you using? Bongo or something else like setFlyThroughAnimation? I'll have a look at the Bongo SDK to see what is in there, but no promisesALTO wrote:Hi Sam, your plugin is working really good here![]()
I'd like to know how hard would be to have animation support?
I'm talking about camera animations so without need to re-export the obj file each time.
Thanks for your work.
Hi ... Your plugin is working good.SamPage wrote:Which animation tool are you using? Bongo or something else like setFlyThroughAnimation? I'll have a look at the Bongo SDK to see what is in there, but no promisesALTO wrote:Hi Sam, your plugin is working really good here![]()
I'd like to know how hard would be to have animation support?
I'm talking about camera animations so without need to re-export the obj file each time.
Thanks for your work.
Sam
newske wrote:I realise this thread is a bit outdated, but for reference I have been using IronPython in Rhino 5 to output batch files which reasonably closely mirror the FlythroughAnimation and PathAnimation which are in Rhino. Ie. You set up your scene, and then export the batch from Rhino and it will open octane, render a frame, close octane and repeat. To make this faster I am hoping that the OTOY team will include the possibility of reading .txt files to render from batch files, or just generally re-visit this.
Current version can deal with:
Flythough Animation
Path Animation
Motion Blur
Number of Frames (override)
Number of Samples (override)
Resolution (override)
Shutdown on finish
Rendertarget (containing all details)
*.exe octane location
*.ocs location
*.png out location
Everything else is determined by the rendertarget set up in the octane scene -- though it would be easy to make it do anything that is currently available in the command line options for octane (--help).
Currently speed is linear (whereas in Rhino it is based on control points I believe) though that would also not be hard to include.
If anyone is interested in this let me know -- maybe SamPage can find a better way to do it with the exporter.