OctaneRender™ Standalone v1.0 RC 1 [obsolete]

[Jaberwocky]

Thanks for the update Roeland.

Suvakas

I'm Pretty sure that V1.0 - through to V1.99 will still be free.That's what was stated in the past.
V2.0 upwards will cost more....so there is always a chance that white balance adjustment may be included in a future release.

If you want to adjust Post processing of the image.Try Raw Therapee

http://rawtherapee.com/blog/list/13

Regards

Jaba

[abstrax]

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...

That's because the camera response curves are limited to a certain brightness, they have no meaning for a brightness > 1. Vignette is already applied and gamma doesn't make sense for HDR either. The only thing we could apply additionally would be saturation (I think).

And we could do something what Suv asked for: Having additional controls for color corrections and white balance. In theory we could probably implement a fully fledged image development module like Lightroom... There wasn't just any time for it yet and at the moment Octane is a render engine and not a post-production tool. We hope to improve that area in the future, but for now it is what it is.

Cheers,
Marcus

[abstrax]

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.

It's highly unlikely that there will be any further performance improvements for Keplers without algorithmic changes. We have been looking into this matter over the last 2 months and the current version is the result of a rewritten CUDA framework and lots of small tweaking to have good performance Teslas, Fermis and Keplers. Unless we have missed something or NVIDIA releases a magic build-fast-Kepler-code toolkit there won't be any important performance improvements. I tried to explain my personal view here and here.

Cheers,
Marcus

[mib2berlin]

Hi abstrax, change rayepsilon does nothingm try diferent camera angle and fov.
Problem scene is attached.

Cheers, mib.

[face]

For a stable release, you should also accept a "," as "." for numerical inputs.
It´s a paint to type numbers on the numpad and can´t use the decimal point from it.

face

[matej]

When we could expect an improved scene sharing format that would allow additional data to be passed to Octane? I would like to know how long will .obj/.mtl/.cvs stick around as the way to export data to Octane standalone. (there was some info your were working / thinking about a custom format)

[abstrax]

When we could expect an improved scene sharing format that would allow additional data to be passed to Octane? I would like to know how long will .obj/.mtl/.cvs stick around as the way to export data to Octane standalone. (there was some info your were working / thinking about a custom format)

Sorry, forgot to answer...

Fact is, we need a new file format for many reasons. A route forward would be either an already existing format or a home-grown format perhaps with a import/export library provided by us. We haven't decided that yet, so I can't give any specific time frames, but we will let you know as soon as possible, so that exporter devs can update their plugins. These things are currently moving up on the to-do list.

Cheers,
Marcus

[matej]

Thanks, Marcus. Glad to know that a new format it's indeed seriously planned. With Octane new possibilities like instances, the .obj workflow is starting to get obsolete and hard to work with.

[pixelrush]

Considering how reasonably priced an Octane v1 license is/has been and the beta phase has been going on for 3 years - quite a long time to support development staff/offices/hardware/website etc - I think its fair enough to move on to a final soon. The promised to do list is pretty well complete anyway. IMO v2 should be the time to move on to a new format. .obj has been very useful being widely available in many apps. Really though its too much work and liable to introduce bugs to redo it at stage. We are trying to get to a stable state not have ongoing chaos.
Anyway I guess its time to really test out the beta to the max and find those last issues.
Probably there are some that have been reported that have been overlooked too so I might read back through the old posts to remind myself where we have been over the past 3 years...

[Aenima]

A bit offtopic but why Otoy not send mails about the releases? Or i miss something?