OctaneRender™ Standalone 2.05.2

[abstrax]

Hi all,

This is a maintenance update for version 2, fixing bugs and issues reported on the forum.

Changes since version 2.04:

• Exposure is now independent of the gamma. I.e. changing gamma does not change the whitepoint anymore.
• Fixed shading artifacts on objects with a lot of deformation motion blur with heavily rotating triangles, like waving flags.
• Fixed a rounded edges issue with the vertex order of triangles.
• Fixed incorrect update of emitter data, causing the kernels to crash in some cases.
• Disabled implicit enabling of all devices when all devices got disabled. Which also means that you can disable all devices now (of course it doesn't render then anymore).
• Lua produces an error when you try to change a read-only property.

We made a small hot-fix release to change two things compared to 2.05:

• Reverted the change in the gamma behavior of the imager node, because there has been too much critic and confusion about the change. I.e. the default gamma is 1.0, which means gamma of ~2.2 when a response curve is used and gamma 1.0 if no response curve is used. As in 2.04 and before.
• Fixed a crash bug in the displacement compilation (see http://render.otoy.com/forum/viewtopic. ... 32#p197032).

And another small hot-fix release to fix two more things of 2.05.1:

• Fixed incorrect gamma in material preview.
• Fixed binding of properties to a table (see octane.gui.bind()).

Download

Windows
- 32-bit installer
- 64-bit installer

Mac OS X
- 64-bit installer image

Linux
- 64-bit archive

Happy rendering,
Your OTOY NZ Team

[BorisGoreta]

I would like to report GPU crashes with heavier scenes ( GPU popup notification on Windows in bottom right corner, not a complete system halt but you need to restart software and reload the scene ) WHEN some other GPU using application is opened ( like Photoshop or AutoCAD ). I didn't have this before. I am currently using 2.2.1.

So if I quit all other applications then it renders fine.

Please could you write again how to edit that registry GPU wait value or disable it completely. My heavy foliage scenes are causing this I believe.

[BorisGoreta]

I have this strange material behaviour. The pool is specular material with scatttering and emission. If the emission is enabled trees in the reflection look wierd, they are too bright I think.

EDIT: It's the PMC kernel ! Pathtracing renders this correctly. Trees in reflection are not brighter then they are when not in reflection.

[ROUBAL]

I am also experiencing frequent GPU crashes on heavy scenes with foliages, but the problem is not due to the foliages in my cases. The crashes occurs as soon as I apply Displacement to a large area, even at very low value. I have larges surfaces of ground with Peebles and grass (100m x 100m of Peebles, 500m x500m of grass). Curiously, I rendered fine some shots with Displacement at 0.1 on 500mx500m of grass, but if I disable that and enable displacement on the 100x100m of Peebles at only 0.01 I get a crash.

[smicha]

I am also experiencing frequent GPU crashes on heavy scenes with foliages, but the problem is not due to the foliages in my cases. The crashes occurs as soon as I apply Displacement to a large area, even at very low value. I have larges surfaces of ground with Peebles and grass (100m x 100m of Peebles, 500m x500m of grass). Curiously, I rendered fine some shots with Displacement at 0.1 on 500mx500m of grass, but if I disable that and enable displacement on the 100x100m of Peebles at only 0.01 I get a crash.

same here

[abstrax]

I am also experiencing frequent GPU crashes on heavy scenes with foliages, but the problem is not due to the foliages in my cases. The crashes occurs as soon as I apply Displacement to a large area, even at very low value. I have larges surfaces of ground with Peebles and grass (100m x 100m of Peebles, 500m x500m of grass). Curiously, I rendered fine some shots with Displacement at 0.1 on 500mx500m of grass, but if I disable that and enable displacement on the 100x100m of Peebles at only 0.01 I get a crash.

Is this specific to this release? Because we didn't change anything in displacement since 2.04...
Could you send us a scene that reproduces the problem? Thanks.

[smicha]

Is this specific to this release? Because we didn't change anything in displacement since 2.04...
Could you send us a scene that reproduces the problem? Thanks.

I have this problem since 2.03

[abstrax]

Is this specific to this release? Because we didn't change anything in displacement since 2.04...
Could you send us a scene that reproduces the problem? Thanks.

I have this problem since 2.03

Please send us a scene that lets us reproduce the problem. We weren't aware of any issues until 30min ago. Thank you.

[smicha]

Is this specific to this release? Because we didn't change anything in displacement since 2.04...
Could you send us a scene that reproduces the problem? Thanks.

I have this problem since 2.03

Please send us a scene that lets us reproduce the problem. We weren't aware of any issues until 30min ago. Thank you.

I'll pack it and PM Marcus.

[bepeg4d]

[*] The default gamma in the imager is now 2.2 (changed from 1.0), which is now the actual gamma that gets applied. In the past, even if it was set to 1.0 and a response curve was selected, there was a gamma of 2.2 applied. Now, this gamma of the response curve is taken into account. In other words: The gamma you select in the imager node is the gamma that is actually applied.

mmm, but now the Kodachrome or Ektachrome, for example, response curves needs to have the gamma @ 4,84

Ciao Beppe