Hi otoy,
I know you usually have no time to respond but can you look into light (mesh light, octane light) reflecting and creating a lot of noise that takes forever to clean. Plus we tried with ai on and off no difference.
Could you add an option to send more samples to these troubled parts. Light samples are already set at 1000
thanks
OctaneRender™ 2019.2 XB2 [latest 2019.2.x]
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.
Look at this glitch upon saving image 16-bit PNG with 4x4 Up-Sampling:
4x4 US @1080p
4x4 US @2160p
4x4 US @3240p
Glitch on saved PNG image gets worse as resolution increases, when 4x4 Up-sampling is used, and when saved as a 16-bit PNG.
3 findings of importance I want to relay:
1) Does NOT happen when 2x2 is used
2) Does not show on screen in viewport. ONLY shows on the saved 16-bit PNG
3) No glitch with 4xUS on 8-bit, ONLY when 4xUS on 16-bit
Thus, the glitch occurs when saving a 16-bit PNG image rendered using 4x4 Up-sampling.
THX
4x4 US @1080p
4x4 US @2160p
4x4 US @3240p
Glitch on saved PNG image gets worse as resolution increases, when 4x4 Up-sampling is used, and when saved as a 16-bit PNG.
3 findings of importance I want to relay:
1) Does NOT happen when 2x2 is used
2) Does not show on screen in viewport. ONLY shows on the saved 16-bit PNG
3) No glitch with 4xUS on 8-bit, ONLY when 4xUS on 16-bit
Thus, the glitch occurs when saving a 16-bit PNG image rendered using 4x4 Up-sampling.
THX
Win 10 Pro 64, Xeon E5-2687W v2 (8x 3.40GHz), G.Skill 64 GB DDR3-2400, ASRock X79 Extreme 11
Mobo: 1 Titan RTX, 1 Titan Xp
External: 6 Titan X Pascal, 2 GTX Titan X
Plugs: Enterprise
Mobo: 1 Titan RTX, 1 Titan Xp
External: 6 Titan X Pascal, 2 GTX Titan X
Plugs: Enterprise
There's something weird going on with scenes using Octane Daylight between V4 and 2019.2
I'm thinking the V4 output looks correct, the 2019.2 is way off.
Obviously it's the same scene that was rendered, no changes were made from one to the other.
I'm thinking the V4 output looks correct, the 2019.2 is way off.
Obviously it's the same scene that was rendered, no changes were made from one to the other.
I've identified what's causing an issue with the Daylight System.
Adding a visible environment causes a problem.
This only happens in 2019.2 XB1 and 2019.2 XB2
2019.1 RC5 is fine
I've attched a simple .orbx to demonstrate the issue, this only happens in 2019.2, both XB1 & XB2.
Adding a visible environment causes a problem.
This only happens in 2019.2 XB1 and 2019.2 XB2
2019.1 RC5 is fine
I've attched a simple .orbx to demonstrate the issue, this only happens in 2019.2, both XB1 & XB2.
Despot wrote:I've identified what's causing an issue with the Daylight System.
Adding a visible environment causes a problem.
This only happens in 2019.2 XB1 and 2019.2 XB2
2019.1 RC5 is fine
I've attched a simple .orbx to demonstrate the issue, this only happens in 2019.2, both XB1 & XB2.
Hi,
What does "Adding a visible environment causes a problem." mean? Like sky texture? Thanks
- BorisGoreta
- Posts: 1413
- Joined: Fri Dec 07, 2012 6:45 pm
- Contact:
Spectron light cone shouldn't affect Octane dirt node !
19 x NVIDIA GTX http://www.borisgoreta.com