OTOY Forums

Hello

Maybe there is that fantastic feature but I don't know where.

Backburner is in the 3ds max and this tool is for setup scenes to render one by one. In most time we render few renders one object/scenes in different camera view. For example like on the gallerys cars etc. Idea is simple but fatanstic. We setup few camera and save that each camera view in new file. Than we add it to backburner, and backburner is rendering them automaticly one by one opening them and use setup we save offcourse (like render size, how much samples and where should be save picture after rendering will be done)

how this can work:
1. we made scene or different scenes to render.
2. setup all info (like render size, how much samples and where should be save picture after rendering will be done) and save file or add it exactly to backburner to start render.
3. backburner is starting rendering and we can add in this time new scenes to render.

backburner:
1. we should have buttons to pause render, choose scene to render or deletet it if we want, or change the priority for rendering , save backburner list to open backburner later and start rendering scenes from moment we stop it.

Problems :
backburner rendering, so if he made big render scene need much memory . I was thinking about that and we can solved it like this. When we run backburner in octan our render max size should be blocked to 300/300 pix for example, less render little memory. This should be enought to setup next scenes (in the furure in octan can be oprion for region render but it's not important now).

Most important is the power of that when we can go sleep and next renderings are made automaticly in the night, we save MUCH time.
I hope this tool will be in new version.

If I'm wrong, and there is something like this PLEASE tell me where can I run it.

Regards

Yeah. So is there any plans on making batch render posible with Octane? Would be very helpful

I think Dr.Que can do this. It should be possible with anything being as Octane is so scriptable now, though some of those features you mentioned might not be scriptable yet. You'd just need a scipt in your app that loads each file and calls the Octane script. When each render is done, or crashes if that happens, it loads the next file. Possible? Maybe. Finding someone to do it, if it is not done yet, and getting them to spend time on it is another thing.

Your 3D app should do that.

Backburner in Octane make no sense.
Animate a cube, how should Octane know the next position?
Our exporter send not the new position from the cube to Octane, only a obj.
This obj has ever the position 0,0,0 only with other vertex, poly and normal positions.
When you load a exported obj back in your 3D app, you will see that the center is ever at 0,0,0.

Your 3D app is the transmitter, Octane the receiver.
Maybe it works with the collada export in which all information are written.

face

hey

Face - Backburner in Octane make no sense? - what are you talking about?

Working is simple and powerfull. You made obj and open it in Octan. Than you prepare all setups as light, materials, etc. as every time you do that. You have allready scene setuped now. You change camera view and save it as Octan file. After that you add each octan file to backburner and he render it automaticly one by one. Probably you never use it and it's normal for you to wake up in middle of the night to start next render:). For me that feature is very powerfull and now have big sense because Octan is fast not like maxwell where we wait much longer for good render so this is not needed.

regards

visaro wrote:hey

Face - Backburner in Octane make no sense? - what are you talking about?

Working is simple and powerfull. You made obj and open it in Octan. Than you prepare all setups as light, materials, etc. as every time you do that. You have allready scene setuped now. You change camera view and save it as Octan file. After that you add each octan file to backburner and he render it automaticly one by one. Probably you never use it and it's normal for you to wake up in middle of the night to start next render:). For me that feature is very powerfull and now have big sense because Octan is fast not like maxwell where we wait much longer for good render so this is not needed.

regards

And how you will becomes the data in Octane?
The obj is changed every frame you animate it, not the position, the topology.
That means, you must load every frame a other obj in Octane to become the animation.
For a animation with 1.000 frames you must have 1.000 meshes.
Or want you to render a animation with 1.000 stills?
Thats only for meshes, other things as light and camera must added too...

In you 3D app, the app animates the meshes. The transformed meshes will send to Octane.
Also must your 3D app change the scenes, which can existst and saved in Octane with materials and so on as preset, and send the new meshes on Octane to render.
Octane can´t animate meshes or change his topology, it´s a renderer.

Thats the same as vray or maxwell should have backburner.
But it should not be a problem to expand the scripts to send several scenes to Octane.
After finish a scene, the script must load a new scene and start the export again.

face

Edit:
I think you mean, we should have a backburner in our 3D app with the integration of Octane.
That would make sense...

you should add command line controls to start yoru 3d app in command line mode, then launch the octane plugin and tell it to render frame x to x.
this is on our guidelines document for beta 2.3.

Radiance

radiance wrote:you should add command line controls to start yoru 3d app in command line mode, then launch the octane plugin and tell it to render frame x to x.
this is on our guidelines document for beta 2.3.

Radiance

That would be funny to implement, i can´t it...

face