OctaneRender™ Standalone 2.05.2

[ROUBAL]

Hi Marcus,
No more GPU crash so far with the TdrDelay value at 20 following your advice. Thank you very much !

[prodviz]

Hi Abstrax,

cheers again for the update.

I'm not sure exactly what has been changed and then changed back, as far as the gamma.

The untonemapped .exr now looks much more like the render view, which is cool.

The only query I have now is which colour space should I assign to the .exr when I open in photoshop?
When I assign sRGB the colours do not match.
The Adobe RGB colour space is closer, but not always matching the render view.

cheers,

Steve

In Octane you have to set the camera response curve to "linear/off" and the gamma to 2.2 and in Photoshop you would have to set the color space to sRGB, then you should get a similar result. It wouldn't be 100% the same, since sRGB is actually not a simple gamma 2.2 curve, but a gamma 2.4 curve with some offset and a linear part for the shadows.

Cheers for the info.

The change in appearance is more in the colour that the tone.

Colours look less saturated in Photoshop.

cheers.

[mib2berlin]

Hi, testing a small alembic file exported from Linux Blender addon I got a crash at frame 18 from 25.
Render 100 samples.

BT is not really helpful but anyway:

Code: Select all

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffed7f9700 (LWP 21789)]
0x0000000000ebc696 in ?? ()
(gdb) bt
#0  0x0000000000ebc696 in ?? ()
#1  0x0000000000ed0442 in ?? ()
#2  0x0000000000e7b4a1 in ?? ()
#3  0x0000000000e8beba in ?? ()
#4  0x0000000000e5f7ec in ?? ()
#5  0x0000000000e63403 in ?? ()
#6  0x0000000000dda2ed in ?? ()
#7  0x0000000000ddef85 in ?? ()
#8  0x0000000000ddfc57 in ?? ()
#9  0x0000000000e0a809 in ?? ()
#10 0x0000000000e0c064 in ?? ()
#11 0x000000000069043b in ?? ()
#12 0x00000000006904b1 in ?? ()
#13 0x00007ffff50de0db in start_thread () from /lib64/libpthread.so.0
#14 0x00007ffff55df90d in clone () from /lib64/libc.so.6

Btw., render animation forget the sample and location setting every time and you have to set it again.

Attached file crashed, Cheers, mib

[Elvissuperstar007]

very slow viewport material, if you add the displacement (Glossy and specular )
impossible to work
1-2 FPS Nvidia 580 GTX 3gb + 460 Gtx 2 gb

[prodviz]

Just for info:

Looks like either no colour profile/not colour managed or Adobe RGB is the closest match to the render view,
with sRGB coming in last:

Render view (screen grab):


Untagged/not colour managed:


Adobe RGB:


sRGB:

[ROUBAL]

Hi, In my current big scene "Milton Manor", I encounter a weird behaviour of the AF picker : it doesn't work with Path Tracing : I have to switch to Direct Lighting kernel each time I want to focus a a peculiar Object/Distance. Right click as well doesn't provide the list of object to focus on when using Pathtracing. Not tested with PMC yet as it is an external scene. Central AF works properly if enabled on the camera, but I maily use the AF picker as the interesting focus point is rarely right in the middle.

[stratified]

Hi, testing a small alembic file exported from Linux Blender addon I got a crash at frame 18 from 25.
Render 100 samples.

BT is not really helpful but anyway:

Code: Select all

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffed7f9700 (LWP 21789)]
0x0000000000ebc696 in ?? ()
(gdb) bt
#0  0x0000000000ebc696 in ?? ()
#1  0x0000000000ed0442 in ?? ()
#2  0x0000000000e7b4a1 in ?? ()
#3  0x0000000000e8beba in ?? ()
#4  0x0000000000e5f7ec in ?? ()
#5  0x0000000000e63403 in ?? ()
#6  0x0000000000dda2ed in ?? ()
#7  0x0000000000ddef85 in ?? ()
#8  0x0000000000ddfc57 in ?? ()
#9  0x0000000000e0a809 in ?? ()
#10 0x0000000000e0c064 in ?? ()
#11 0x000000000069043b in ?? ()
#12 0x00000000006904b1 in ?? ()
#13 0x00007ffff50de0db in start_thread () from /lib64/libpthread.so.0
#14 0x00007ffff55df90d in clone () from /lib64/libc.so.6

Btw., render animation forget the sample and location setting every time and you have to set it again.

Attached file crashed, Cheers, mib

Hi Mib,

We tested it here on Linux but we couldn't reproduce the crash. Is it consistently reproducible on your machine?

cheers,
Thomas

[roeland]

Hi, In my current big scene "Milton Manor", I encounter a weird behaviour of the AF picker : it doesn't work with Path Tracing : I have to switch to Direct Lighting kernel each time I want to focus a a peculiar Object/Distance. Right click as well doesn't provide the list of object to focus on when using Pathtracing. Not tested with PMC yet as it is an external scene. Central AF works properly if enabled on the camera, but I maily use the AF picker as the interesting focus point is rarely right in the middle.

It doesn't seem to be reproducible in other scenes, do you only have this problem with this particular scene? Just to be sure, can you confirm it doesn't work, rather than just being slow?

--
Roeland

[roeland]

Just for info:

Looks like either no colour profile/not colour managed or Adobe RGB is the closest match to the render view,
with sRGB coming in last:

Render view (screen grab):
(img)

Untagged/not colour managed:
(img)

Adobe RGB:
(img)

sRGB:
(img)

Octane is indeed not colour managed. It always expects input textures and RGB values to be specified in sRGB, and the rendered image is also in sRGB.

Currently the Octane Standalone window is also not tagged as having a particular color space, so Windows won't do any color space correction on the displayed images. I can confirm that this is currently a problem if your monitor is different from sRGB. For instance some monitors can be set to use the Adobe RGB color space, in which case colors displayed in Octane will appear too saturated.

Another thing, the grid behind the material ball is not supposed to look like that, do you often see a background like this?

--
Roeland

[ROUBAL]

It doesn't seem to be reproducible in other scenes, do you only have this problem with this particular scene? Just to be sure, can you confirm it doesn't work, rather than just being slow?

Hi Roeland, It is not specific to this scene apparently. Just occurs on heavy scenes. Sometimes it works. It seems that the presence of large surface of displacement (ground peebles) could be a clue.