OctaneRender™ Standalone v1.0 RC 1 [obsolete]

[suvakas]

for color balance use Nik effects, they are more efficient.
In the suite you get Dfine for noise reduction, Sharpner pro for enhance details, Viveza for local adjustments.
All my Octane renders are color corrected with Nik.

Glad you're happy with your workflow.
Using an external program is a workaround that has a price tag. Only to do things that a render engine should already do?
It's also not a good solution cause I need to adjust WB during rendering. My lighting and camera settings depend on it too.

Suv

[gabrielefx]

for color balance use Nik effects, they are more efficient.
In the suite you get Dfine for noise reduction, Sharpner pro for enhance details, Viveza for local adjustments.
All my Octane renders are color corrected with Nik.

Glad you're happy with your workflow.
Using an external program is a workaround that has a price tag. Only to do things that a render engine should already do?
It's also not a good solution cause I need to adjust WB during rendering. My lighting and camera settings depend on it too.

Suv

Probably Otoy could implement a frame buffer with more controls. The Vray frame buffer rocks, it's a good example.
Also I don't understand why is not possible to save tonemapped renders at 32 bit in exr or hdr format. Live does it...

[suvakas]

I'd like to get a comment from developers about the white balance feature.
Would it be possible to implement it for 1.0 ? Is it too much work? Do you need to change the engine to support this?

Suv

[mantra]

tangent vector direction pass what is it?

[matej]

Considering this one is called RC, I suppose we wont see a new scene format for the standalone version yet? How long will Octane rely on separate .obj/.mtl/.csv files and wont support a more powerful custom solution?

This info is important for Blender users and the future of the Blender exporter, so please share it.

[abstrax]

Hi all.

Now that the release candidate is out, I guess it's time to give a quick explanation, what that means. We are aiming to get to a stable final 1.0 very soon. That means that there will be a feature freeze and we try to iron out some more bugs until we have a final release 1.0. We may add 1 or 2 small things with the next release candidates, but we will try to minimize the number of release candidates and the time it takes to reach version 1.0.

That does not mean, that we will drop everything, go to the Bahamas and take a holiday for the next 10 years Of course, we are already working on new stuff. And there are also point updates planned with new features and improvements. I can't say how many and what they will include, but I can assure you that our aim is to continously improve Octane, which means we try to continue to release new versions as often as possible and reasonable.

The beta phase has been now almost 3 years and in my opinion a non-beta release is long overdue. Having a beta version gives you some freedom during development, but also has some negative side effects which will eventually harm the product and the company. Our hope is that with the end of the beta cycle, the awareness of Octane will rise.

I hope this clears up a few questions, but feel free to ask more.

Cheers,
Marcus

[abstrax]

Ha, nice update.
Is this the Release Candidate for stable 1.0?

Yes, that's correct.

There is something wrong with texture/materials in 1.0 if I open a file from 3.03.

Cheers, mib.

Ok, it seems that the try to reduce numerical issues has introduced other issues. Please play with the ray epsilon and make sure that the scene is centred around the origin. If that doesn't help, please send us an example scene and we will have a look.

Cheers,
Marcus

[abstrax]

RC already?
So it means there will be no way to adjust white balance in final version of Octane?
I was kind of hoping that there will be still some stuff implemented for final version. A bit dissapointing.
Adjusting color palance using only camera curves is very limiting.

Suv

A (non-beta) version 1.0 doesn't mean the end of the development. Which features will be implemented next, depends on the demand and their complexity.

[PolderAnimation]

That means that there will be a feature freeze and we try to iron out some more bugs until we have a final release 1.0.

Thanks for information. By 'Ironing the final release', could we expect more performance from the 'kepler' cards? Or is that something, that needs more then just ironing.

[suvakas]

A (non-beta) version 1.0 doesn't mean the end of the development. Which features will be implemented next, depends on the demand and their complexity.

The thing is, that I don't want to start paying extra for basic features like white balance.
When I got the license I was very sure this stuff is missing because it's beta. Cause come one, this stuff is trivial.

Suv