OTOY Forums

Turntable rendering sequence within octane?....OK we have it beautiful
Sun position rendering sequence within octane.. OK we have it ...beautiful..
Rendering a heavy scene with waiting voxeling millions of polygons... opening closing octane..doable but so heart breaking..

Solution:

You already add camera shifting XY position and we have Zooming anyway..... why not making it working like "rendering a sequence"

.. a basic keyframe.. Position X ... keyframe 1...... keyframe 2... - you have beautiful PAN... or sliding effect..
You will save at least half of architectural visualization...

DOLLY IN OR OUT ... done

TILT UP or DOWN ...done

PAN LEFT or RIGHT...done...

come on just 2 keyframes... (no i dont need easy easing...i dont care envelopes..)

Please please please add this... if octane knows how to rotate around the object or object rotates itself whatever... this should be doable too..

Hi,

This is not a simple thing, to do animation we need to introduce the concept in time accross the whole application.
We have plans to add basic keyframes, but we already have a lot of important stuff we want to finish first for v1.0 final (multi-gpu, new render kernel, instancing, etc...)

I think this is a great feature to add after those.

Radiance

actually i am asking just out of curiosity Radiance...When octane is making turn table rotation and also sunrise -sunset animation it looks like completing some kind of time base stuff.

Because right now i am making some turntable animations in order to achieve fake panning.. Can we fake octane that it still think it is rotating but actually moving in X Y or Z (following path of a long disc shape) without introducing whole deal of keyframing etc..

And is there a way to "write to disk method for Voxeling" such as voxel caching.

"If only camera moves and no object moves" do we still need to wait for Octane re-voxel millions of polies? ... If you came up with a solution to that... Voxeling... keyframes can wait...

I have a file name for ya even OcV (voxelcache of octane:))

I think an ability to load camera position only with same mesh, would be a great time saver for those who are looking to animate a camera in a scene of static content. (flythroughs, etc...)

Not sure if there is a way to do this, or how complex it would be to implement, but if you could set up a camera only import, that would theoretically get rid of a lot of voxelizing time wouldn't it?

DayVids wrote:I think an ability to load camera position only with same mesh, would be a great time saver for those who are looking to animate a camera in a scene of static content. (flythroughs, etc...)

Not sure if there is a way to do this, or how complex it would be to implement, but if you could set up a camera only import, that would theoretically get rid of a lot of voxelizing time wouldn't it?

exactly and purely my feelings mate...

DayVids wrote:I think an ability to load camera position only with same mesh, would be a great time saver for those who are looking to animate a camera in a scene of static content. (flythroughs, etc...)

Not sure if there is a way to do this, or how complex it would be to implement, but if you could set up a camera only import, that would theoretically get rid of a lot of voxelizing time wouldn't it?

huge 1+

Can't we for example set a turn table animation of 600 frames or so and then Octane read the camera positions for this animation from a simple text file or something ?

you can add just a simple button "load path".

we don't mind copy pasting in a string grid or something

there are some utils that can output camera path in text file, or a plug-in can be made in no time.

just my idea... to help things out.

camera animation is a must for most of octane users