OctaneRender™ 2019.2 XB2 [latest 2019.2.x]

[funk]

I have actually applied the same default values in 2019.1 and 2019.2, but we just haven't released the 2019.1 build with the updates that 2019.2 has in it.
It will definitely be changed to 0.0 in 2019.1.

Thanks Wallace. I still don't think this setting belongs in the kernel, but at least we'll have matching default behavior between the 2 versions.

Sorry, I was still digesting your post .

I do think you have made a valid point, and will move it to per layer instead.

OK thanks Wallace. I hate creating more work for you guys! I don't know exactly how this should be implemented. I just felt the kernel was the wrong place.

[wallace]

OK thanks Wallace. I hate creating more work for you guys! I don't know exactly how this should be implemented. I just felt the kernel was the wrong place.

No problem, that is the whole point of experimental versions/release candidates, we value your opinion because ultimately you guys are the ones who use it.

[Notiusweb]

OK thanks Wallace. I hate creating more work for you guys! I don't know exactly how this should be implemented. I just felt the kernel was the wrong place.

No problem, that is the whole point of experimental versions/release candidates, we value your opinion because ultimately you guys are the ones who use it.

@Funk - I see now, I misunderstood actually how it was working outside of the layer scenario, because it didn't say "affects layered roughness"...or something more explicit to layer...
Thanks for pointing out and illuminating with your example.

@Wallace - can we still have a master roughness, in concert with specific material-level, like how Rajib mentioned ? (steadily defaulted to "0")
THX!

[sieadr2]

lua octane.render.saveDeepImage() is saving non-deep exr
is this a known bug? Anyone else having this problem?
it used to work in v.4.x

[mojave]

lua octane.render.saveDeepImage() is saving non-deep exr
is this a known bug? Anyone else having this problem?
it used to work in v.4.x

Thank you for reporting this. This will be solved in all future releases.

[mojave]

In this update, my castle scene does not render at all. Including switched off rtx. As soon as I start the render, a crash occurs.
https://drive.google.com/open?id=1XVfLt ... EpCRSe06cB

Hi Divasoft,

We fixed an issue with this scene when RTX was disabled that was happening in scenes with AI light enabled. This will be fixed in the next release.

However we have not been able to find any issues with this specific scene when RTX mode is on, could you give us more details about how to reproduce it?

Thank you.

[divasoft]

Hi. Why turning on IES light makes scene darker? How it possible?
https://drive.google.com/open?id=1J2SVJ ... t-ph6Y-Ygs

[mojave]

Hi. Why turning on IES light makes scene darker? How it possible?
https://drive.google.com/open?id=1J2SVJ ... t-ph6Y-Ygs

Could you please post this in the relevant version of the plugin sub-forum and share a small scene to reproduce the issue? Thank you.

[Zay]

Is the massive use of VRAM in 2019.x.x compared to 2018.x something we have to get use to?

A scene I tested measured in GPU-Z.
With parallel sample set to 16 and max. title samples to 16:
2018.1.3 = 2869 MB
2019XB2 = 3800 MB

With parallel sample set to 1 and max. title samples to 1:
2018.1.3 = 2251 MB
2019XB2= 2804 MB

[PolderAnimation]

I have a bug regarding the Universal camera.
if I connect a float value to a universal camera and save my file and then re-open it, the connection is gone.
This is in all the 2019 versions.