OctaneRender™ Standalone 1.26

[stratified]

Hi All,

This release fixes some issues reported for the previous versions.

Changes since 1.25

Rendering

• Fixed box mapping in object space.
• Allow negative values for the object scale.
• Render targets are always renderable even if there's no geometry or camera connected.

Scene and Geometry Import

• Added packaging to save a scene together with all it's assets in a single file (Octane package - ocp file).
• Saving of the materials in the LiveDB and locally is enabled again.

Lua Scripting

• Improved the conveniece of the copy functions in Lua.
• Fixed a crash when an UI component had 0 width.
• Added a collapsible panel stack UI component.
• Recursive searching in nodegraphs.
• Daylight, turntable and generic animation scripts are now shipped with Octane.
• Added a button button to load scripts immediately in the editor.
• Windows created from a script don't disappear to the background anymore on Mac and Linux.

Other Changes

• Linux is built with Ubuntu 10.04 instead of CentOS 5.5. Technically, glibc 2.11 is now required to run Octane (formerly it was glibc 2.5). Roughly this means that Octane needs a distro more recent than end 2009 (formerly it was end 2006).

Download:

Windows
ZIP archives:
- 64-bit
- 32-bit

MacOS X
ZIP archive:
- 32-bit and 64-bit

Linux
ZIP archive:
- 64-bit

Happy rendering,
Your OTOY NZ Team

[grimm]

Yay! Thanks Octane team! Now I can finish up my turntable script.

[Elvissuperstar007]

http://render.otoy.com/forum/viewtopic.php?f=33&t=37821

Octane 1.0 = 9.93 ms/sec

Octane 1.1 = 6.19 ms/sec

Octane 1.2a = 6.33 ms/sec

Octane 1.25 = 6.40 ms/sec

Octane 1.26 = 3.57 ms/sec

[ephdot]

Thanks guys.

+1 for OCP. It's also nice to have Live DB/Local back.

[Elvissuperstar007]

fake shadow does not work

[Zay]

Trying to set black body lights without luck in this version. Works fine in 1.25 but not in 1.26.

[Elvissuperstar007]

texture emission and black body does not work

[abstrax]

Ok, thanks for the feedback. I hope we can find and fix the issues tomorrow and then release an update.

[voon]

http://render.otoy.com/forum/viewtopic.php?f=33&t=37821

Octane 1.0 = 9.93 ms/sec

Octane 1.1 = 6.19 ms/sec

Octane 1.2a = 6.33 ms/sec

Octane 1.25 = 6.40 ms/sec

Octane 1.26 = 3.57 ms/sec

What do these numbers mean? I mean I know where to see them, I know about the testrender scene and whatnot, but what is an "ms"? And is it even sensible, to compare this across versions or do recent releases achieve more work done per "ms", so despite smaller numbers, it may actually be faster?

[stratified]

http://render.otoy.com/forum/viewtopic.php?f=33&t=37821

Octane 1.0 = 9.93 ms/sec

Octane 1.1 = 6.19 ms/sec

Octane 1.2a = 6.33 ms/sec

Octane 1.25 = 6.40 ms/sec

Octane 1.26 = 3.57 ms/sec

What do these numbers mean? I mean I know where to see them, I know about the testrender scene and whatnot, but what is an "ms"? And is it even sensible, to compare this across versions or do recent releases achieve more work done per "ms", so despite smaller numbers, it may actually be faster?

It's megasamples/sec. It basically states how many ray paths Octane is tracing through the scene per unit of time. They will differ from release to release but if there are sudden jumps it migh indicate an issue. It's an indicator and the numbers should be considered on a per scene basis.

The only "real" measurement is to see how good the image quality (noise reduction) is after a certain amount of time. And indeed, some algorithms may actually take less samples (lower numbers) to achieve better results. Thats why we have for example path tracing vs PMC, you would use PMC for scenes with more "difficult" light paths. In theory if you take an infinite amount of samples, the result should be the same. In practice, your customers don't want to wait an infinite amount of time on what they paid for

cheers,
Thomas