Key Frame System in Octane 3 ?

[linvanchene]

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?

I showed patience for more than 5 months now.
I even tried to keep other users calm on the subforum and kept defending Otoy over and over the last five months.
This turned out to be a mistake if Otoy still does not understand the importance of the standalone for plugin users with limited options in the host application.
Octanerender standalone was the last hope I had to be able to work in a proper way.

- - -

There was an annoucement about a timeline at GTC 2015.

Slide 39.

Per Node timeline

You even have the slides in your official news post:

http://home.otoy.com/otoy-unveils-octan ... -renderer/

- - -

The plugin I am mainly using is in open beta since 2013.
The last stable version was released in Feburary 2014
The last unstable beta version was released in December 2014.
All the other plugins I am waiting for are still in an alpha or closed beta state.

The last five months I could only work because I was able to export to the standalone.

Can you even imagine how I now feel after having to read that someone deceided that users like me who are working with the standalone are a minority that is not worth supporting?

- - -

[abstrax]

I didn't write the slide show and didn't know of that bullet point. Must have been a mistake, since it's definitely not on the roadmap for version 3.x. Sorry about that. We may add some initial (small) version in version 3.x, but as I said, it's a lot of work and most users are working in the 3D application to do these things, so it's currently more important to implement missing render features.

If you want a solution now, you have to use a 3D application that supports animation and has an Octane integration. There is even a free 3D application that allows you to do these things: Blender

[Refracty]

Thank you for the detailed feedback regarding to the timeline and keyframe as well as geometry limit.
I know that some plugins work in a proper way and offer animation possibilities but a keyframe system in the stand alone is definately useful. Because the standalone is rock solid.
It would be also great to key the transformation values on an hdr background, so that we have a blured bg.
Lets hope for that.
These features are required for cgi still productions for automotives. This is my experience and compared to other tools llike VRED there is not much that Octane is missing, except feyframes and a timeline. The price tag of Octane is much cheaper so it could mean new customers for Otoy...

[Seekerfinder]

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.

Unfortunately not all, Paul... Even though SketchUp does support it, the Octane plugin for Sketchup does not. That's a real shame because so many use SU and it's a HUGE market for Octane in my view. And with OR coming, there's a whole world of 'non-pro' content creators that are left out of the VR animation sequences, which could easily be created in SU.

SU development has been real erratic, which is disappointing.

Best,
Seeker

[abstrax]

Just to be clear: We are not against a timeline. As I said, out plans with Octane go beyond a pure render engine and we have lots of ideas. It's just that right now, we can't commit to proper animation tools in version 3.x. And yes, I personally like working with the Standalone, too, and every now and then I really would like to have this or that feature. The stupid thing is, that the day has just 24 hours...

[Seekerfinder]

The stupid thing is, that the day has just 24 hours...

Please change that in Version 3...

[Buraq]

I use 3D Max but I realy love working on Stand Alone. Not only it is fast, it is comfortable and make me feel free to do everything. Timeline is just a request and you are the one, can make it real. ( you already did great things and you all increase our expectations )
Thank you all for hard working
Best

[Refracty]

Thank you for the good stuff and the hard work.
It just that Octane Standalone is a great tool and I often prefer to work with it.

[Goldorak]

A lot of us like the standalone (I am one of them). With the v3 C API, finalization of ORBX multi-script packages/nodes and some other APIs we are adding to enable more options in the SE layout, we have the foundation for powerful 1st and 3rd party extensions to Octane. Our goal is to get this part of the ecosystem on par with the integrated DCC plug-ins over time.