OTOY Forums

I am wondering if Octane 3 or 2.X will offer (at least some simple) keyframing system.
Currently I am trying to use Octane for professional automotive visualisation but missing animation feature and the geometry limit make things hard...

I only need simple rotation key frames to have motion blur on the wheels or some translation keys to have a directional blurred background.
Any suggestions without using a plugin?

anybody?

It's doable with lua scripting - you have access to the entire animation and key frame generation pipeline. It would require development of course but it is not anything that is missing in the core standalone itself.

- - -
Update/Edit:
Removed parts to focus on the main issue.
I edited my original post because I do not want to artificially bump this.
Other users need to add their voice.
- - -

Original Question:

Does this mean the Otoy development team has NOT been developing a fully functional timeline and keyframe system for the standalone that is ready at launch of OctaneRender 3?

- - -
Updated:

The issue in practice:

Even if the host application of the plugins have a timeline and keyframe system users needs to be able to adjust keyframes in the standalone if the goal is to combine scenes from different plugins in the standalone.

How does Otoy want to deliver on the promise that in the future it will be possible to send any scene from one plugin to any other plugin or the standalone without a common timeline system that is shared?

- - -

Not only the standalone users could have benefited from an OctaneRender timeline system.
But each plugin developer could have benefited by being able to integrate the same timeline system in their plugin versions.
Especially if the host applications do not offer a timeline system that grants the ability to animate all OctaneRender features...

- - -

I guess goldorak means that Octane already has the nessecary technology under the hood.
But lets hope the gui will allow some keyframing in the upcoming version.
In the meantime i hope that some lua gurus will help out with scripts comparable to the existing camera animation script.

There won't be a timeline in version 3.0. And probably not in in 3.x, but I can't say for sure. It depends on many things. In case you wonder why: It's a lot of work (I mean a lot) for only a small amount of users. Most users use Octane integrated in the 3D applications they use for everything else and those usually come with animation capabilities.

But yes, in the longer term we have some interesting things planned for Octane and a timeline would be quite handy then, too.

The geometry limit is currently there because of performance reasons. The current planning for version 3 will allow us to work around this without a too bad drop in performance. But right now it's too early to tell for sure what the outcome will be.

“(at least some simple) keyframing system.”

A simple system is very unlikely to be useful for many users. Usually users don't need most of the features of any program, so a simple version of that program would be sufficient. But unfortunately this small subset of needed features is different for any user. As a consequence the simple version is useless for most users, since it almost always lacks one or another feature which is critical for him.

For now we consider editing animations to be beyond the scope of what Octane supports. We have a generic system for animation under the hood, and in theory someone can develop a timeline with keyframes on top of that. But as abstrax said, that's a lot of work.

The workflow we support for getting a camera animation in Standalone is creating the animation in a 3D modelling application and export/import it to Octane using Alembic or using an integrated plug-in.

--
Roeland

I now have to inform them that it is not a reasonable use of their time to learn how to work with a software that cannot be used to create animated VR scenes in the future.

Use one of the OctaneRender plugins. They all support keyframe animation.

Linvanchene, please calm down. Octane is a render engine and not an modeling, animation, UV mapping, whatever package. And please stop yelling at us with bold letters all the time.

Of course, we have plans to extend the functionality of Octane in the future, but for now we are 100% focused on rendering. A timeline/key framing system is not rendering. We have announced what Octane will have in version 3. There is no word about a timeline. And you should never buy a license based on what you think the application should have in the next version, because then you might set yourself up for a big disappointment. But that should be common sense, shouldn't it?