No, not really. In the past they were meant to be used with a gamma of 1.0 and now it's 2.2 (or the gamma of your display).bepeg4d wrote:mmm, but now the Kodachrome or Ektachrome, for example, response curves needs to have the gamma @ 4,84abstrax wrote: [*] 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.
Ciao Beppe
OctaneRender™ Standalone 2.05.2
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
I am uploading the orbx. You'll get it within 10-15 minutes, Marcus.abstrax wrote:Please send us a scene that lets us reproduce the problem. We weren't aware of any issues until 30min ago. Thank you.
3090, Titan, Quadro, Xeon Scalable Supermicro, 768GB RAM; Sketchup Pro, Classical Architecture.
Custom alloy powder coated laser cut cases, Autodesk metal-sheet 3D modelling.
build-log http://render.otoy.com/forum/viewtopic.php?f=9&t=42540
Custom alloy powder coated laser cut cases, Autodesk metal-sheet 3D modelling.
build-log http://render.otoy.com/forum/viewtopic.php?f=9&t=42540
PM sent.smicha wrote:I am uploading the orbx. You'll get it within 10-15 minutes, Marcus.abstrax wrote:Please send us a scene that lets us reproduce the problem. We weren't aware of any issues until 30min ago. Thank you.
3090, Titan, Quadro, Xeon Scalable Supermicro, 768GB RAM; Sketchup Pro, Classical Architecture.
Custom alloy powder coated laser cut cases, Autodesk metal-sheet 3D modelling.
build-log http://render.otoy.com/forum/viewtopic.php?f=9&t=42540
Custom alloy powder coated laser cut cases, Autodesk metal-sheet 3D modelling.
build-log http://render.otoy.com/forum/viewtopic.php?f=9&t=42540
Unfortunately the Kodachrome or Ektachrome response curves needs to have the gamma @ 2.2 like for Linear/Off in previous version of Octane.
it seems that the Linear/Off value has been correctly translated but the other curves with Gamma 2.2 seems not. Here is an example: Ciao Beppe
Edit- Here is a PDF version:
it seems that the Linear/Off value has been correctly translated but the other curves with Gamma 2.2 seems not. Here is an example: Ciao Beppe
Edit- Here is a PDF version:
You do not have the required permissions to view the files attached to this post.
I noticed the crash problem yesterday with 2.04 as well when using for the first time a very large displacement surface.
I am currently rendering with success a displaced ground, but had to disable two surfaces with displacement that were not in the field of the camera.
It looks like several object with displacement at the same time or displacement outside the camera field leads to crash... just some clues.
On the image below, I also notice that displacement looks much better in shadows than in lit areas. I assume that the reason why is because the light bounces between the stacked micro faces of the displacement stucture and leaks...
I am currently rendering with success a displaced ground, but had to disable two surfaces with displacement that were not in the field of the camera.
It looks like several object with displacement at the same time or displacement outside the camera field leads to crash... just some clues.
On the image below, I also notice that displacement looks much better in shadows than in lit areas. I assume that the reason why is because the light bounces between the stacked micro faces of the displacement stucture and leaks...You do not have the required permissions to view the files attached to this post.
French Blender user - CPU : intel Quad QX9650 at 3GHz - 8GB of RAM - Windows 7 Pro 64 bits. Display GPU : GeForce GTX 480 (2 Samsung 2443BW-1920x1600 monitors). External GPUs : two EVGA GTX 580 3GB in a Cubix GPU-Xpander Pro 2. NVidia Driver : 368.22.
With versions < 2.05 all camera response curves had to be used with a gamma setting of 1, to be correct. Kodachrome 25CD was a 25 ISO emulsion with a very hard tone curve. If you applied a gamma of 2.2 you made it a soft curve again, which is ok, but not Kodachrome 25CD. The gamma of ~2.2 is already included in the measured tone curves we use, which was completely hidden in the past and caused a lot of confusion, because gamma meant something different if you were using a camera response curve or no curve.bepeg4d wrote:Unfortunately the Kodachrome or Ektachrome response curves needs to have the gamma @ 2.2 like for Linear/Off in previous version of Octane.
it seems that the Linear/Off value has been correctly translated but the other curves with Gamma 2.2 seems not. Here is an example: Ciao Beppe
Edit- Here is a PDF version:
Older scenes will be converted to exactly match the output in previous versions. So you don't have to fiddle around with them. For now, it should be set to 2.2 by default.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
I think I like the new gamma default. In the MODO plugin, I often switch between a camera curve and setting it off to closer match MODOs render output. Part of that was manually changing from 1.0 to 2.2. Now I don't have to? If so, thanks!
No, that's not what is happening. If you set a gamma to 2.2 in 2.05 you get the same tonemapped result as with a gamma of 1.0 in 2.04.riggles wrote:I think I like the new gamma default. In the MODO plugin, I often switch between a camera curve and setting it off to closer match MODOs render output. Part of that was manually changing from 1.0 to 2.2. Now I don't have to? If so, thanks!
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra