OTOY Forums

Integration with the main 3D app is very important for work flow.
I can see Octane will speed up rendering, but now switches the bottleneck to exporting and importing, making model changes, exporting/importing. etc.. gets tiring and slow.
As long as Octane and the slow work flow is faster than a 3d app with an integrated renderer, I'll put up with the slow workflow.
I'll be happy
But the day I see this inside 3dsmax's active shade will be truly an awesome day

cheers

You probably never gonna see Octane in active shade
But Octane workflow gonna evolve with dynamic loading of scenes and objects
That mean loading the file when a change is detected. That will speed up a lot of things

Let's wait for the beta

I'm not too concerned about comprehensive integrations myself, specially if octane will have some basic scripting. It would be quite laborious to do it in multiple apps.

But it just occurred to me that none of the videos I've seen so far show any object or light translations happening. Does octane have basic move/rotate/scale controls yet? I don't mind doing reimport after geometry changes, but having static lights would kind of defeat the whole point of the renderer. For me anyway.

Well the environment lighting is obviously dynamically manipulable, but we will have to wait and see about mesh lighting. Since these light sources are intimately connected to scene objects I would assume that they would be static. Would be fabulous if I was wrong.

Sam wrote:You probably never gonna see Octane in active shade
But Octane workflow gonna evolve with dynamic loading of scenes and objects
That mean loading the file when a change is detected. That will speed up a lot of things

Let's wait for the beta

I like the sounds of dynamic scene loading !! Thats all I needed to hear.

Sam wrote:Let's wait for the beta

Me want some!

If the scripting is done right for the host app the importing and exporting can be done somewhat easily using the command line version of Octane (when its available). The biggest thing will be tweaking of the materials and such to work properly across from the host app to Octane. That might take a little more work.

i think just like mradfo21.

This rendering engine is so good that i think it can become an industry pro standard, but for that, the software has te be not only for blender hobbists and co. but also for studio workflows. How make that ? make octane more professional, or make an "octane professionnal edition", you choose, but this would be damage making just an easy to manipulate render engine.

But i don't worry so much, octane is renderman compliant, so the devellopers have certainly some pro ambition for it

bye.

i think octane has what it takes...

its simple to use (fast, efficient)
Doesnt cost the earth (no bank loan required)
Results are pretty fast considering its still in alpha the output is excellent.
Intuitive design... I love the node approach. (reminds me of unreal engine 3)

V1 release will have most of the features required. Batch rendering with animation support would be welcomed.
Network distribution would also be welcomed.

Remember this is a small company they haven't the luxery of the bigger companies and to be direct most of the big companies suck at support and over charge (unless you pay a silly fee). Small companies are managed more effeciently and also their coding tends to follow suit... how many big packages require big hardware investment to use them well.. just not financially practical for most of us..

Cost vs performance - octane wins hands down

A little more dev and it will mature into something wonderful.
Just using the alpha has impressed people and my own potential clients.... imagine what release v1 will offer.

No stress, no hassle, easy quick and to the point.
Once its here it will help millions of CGI artists and students without the burden of huge financial debt.. So give it a chance to grow...

My 99 euros.. (best investment ever)

That's the key thing here. Octane is just entering beta/v1. So many people are expecting them to come out of the gate with all the tricks and features of existing bi brand software. Give them time and things will work out. It is not like they are working on a well established system, like a standard PC program. Cuda is still fairly new and a more complex and tricky system to work with. Hence why we are only just starting to see viable applications using it, or other gpgpu options. Again, just give it time. Once I am able to get a license going I will start working on trying to write some scripts for specific applications (max/maya/blender) to see if I can get some decent integration with the CLI version of Octane and the host app.