As mentioned by Karu here this is currently a limitation which needs to be solved by adding support for 32-bit float HDR textures. Since this version is feature locked we won't be able to add this to 2020.2 but in a future build.funk wrote:BUG: HDR images with large dynamic range render incorrectly
This is another older one from this thread: viewtopic.php?p=377892#p377892
It still happens in 2020.2. Octane is clipping HDR images even when manually setting the texture import type to 32-bit:
You can see the "sun" in the HDR image is being clipped. The blue sky is becoming just as powerful as the sun, making the render look too blue.
OctaneRender™ 2020.2 RC1
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
Yeah I remember his reply, but since it was a while ago (7 months), I wanted to bring it up again in case it was forgotten. I feel this is kind of important.mojave wrote:As mentioned by Karu here this is currently a limitation which needs to be solved by adding support for 32-bit float HDR textures. Since this version is feature locked we won't be able to add this to 2020.2 but in a future build.
I also replied to his post here: viewtopic.php?p=380243#p380243
Win10 Pro / Ryzen 5950X / 128GB / RTX 4090 / MODO
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
+1, I also find it to be an important issue.funk wrote:Yeah I remember his reply, but since it was a while ago (7 months), I wanted to bring it up again in case it was forgotten. I feel this is kind of important.mojave wrote:As mentioned by Karu here this is currently a limitation which needs to be solved by adding support for 32-bit float HDR textures. Since this version is feature locked we won't be able to add this to 2020.2 but in a future build.
I also replied to his post here: viewtopic.php?p=380243#p380243

We are taking note of this. Thank you both for your feedback.nejck wrote:+1, I also find it to be an important issue.funk wrote:Yeah I remember his reply, but since it was a while ago (7 months), I wanted to bring it up again in case it was forgotten. I feel this is kind of important.mojave wrote:As mentioned by Karu here this is currently a limitation which needs to be solved by adding support for 32-bit float HDR textures. Since this version is feature locked we won't be able to add this to 2020.2 but in a future build.
I also replied to his post here: viewtopic.php?p=380243#p380243
- enricocerica
- Posts: 1012
- Joined: Wed Nov 25, 2009 7:32 pm
- Contact:
Hi,
Chaos Texture doesn't seem to work when used on normal pin, is it a expected limitation ?
Chaos Texture doesn't seem to work when used on normal pin, is it a expected limitation ?
Modeling system : I7 32GB Windows 10 & Fujitsu Celsius H720
GPU : 1x Gigabyte GTX580 3GB + 1x MSI GTX780 3GB + 1x PALIT GTX780 6GB +1x Asus Stix GTX1070 8GB
http://www.myline.be
GPU : 1x Gigabyte GTX580 3GB + 1x MSI GTX780 3GB + 1x PALIT GTX780 6GB +1x Asus Stix GTX1070 8GB
http://www.myline.be