OctaneRender V4 XB2.1

[vijay]

Now that I have denoising working on the 670, while the 1080ti renders, I decided to test a 4K (3840 x 2160) denoise.

It works, but it's not very fast.

Use multiple GPUs if you can( current requirement is around 450MB per device). it reduces the denoise time exponentially.

I also noticed that having "denoise on completion" disabled, makes switching passes very slow. If I try to switch between passes, it's like the UI gets stuck for a while (I see several pass buttons highlighted instead of just 1), until octane recovers

Thanks for the report. we will look into it. But current one should be much better than the XB1. Interval denoising is only needed when you use interactive render region, it doesn't make any difference to final output over denoising on completion instead it only increases the render time.

I have a feature request. Could we have a "denoise NOW" button, or a "denoise on PAUSE" feature?

Noted. But at this time I can't guarantee anything.

[vijay]

I just ran a quick test and denoising in now working on my system, BUT, I ran into a major problem.

If I disable the "denoise on completion" option, my pc is rebooting when it tries to denoise. I don't have time to troubleshoot this at the moment though

EDIT: Actually I'm getting random reboots when the denoiser runs, even if "denoise on completion" is enabled

EDIT 2: For now, I can denoise without crashing/rebooting if I set denoising to my GTX670, while the 1080ti does the rendering. I'm OK with that, but I'd like to figure out why the pc reboots if I denoise on the 1080ti.

Never happened before, What driver version you are using?. Could you please try updating it?.

[funk]

I just ran a quick test and denoising in now working on my system, BUT, I ran into a major problem.

If I disable the "denoise on completion" option, my pc is rebooting when it tries to denoise. I don't have time to troubleshoot this at the moment though

EDIT: Actually I'm getting random reboots when the denoiser runs, even if "denoise on completion" is enabled

EDIT 2: For now, I can denoise without crashing/rebooting if I set denoising to my GTX670, while the 1080ti does the rendering. I'm OK with that, but I'd like to figure out why the pc reboots if I denoise on the 1080ti.

Never happened before, What driver version you are using?. Could you please try updating it?.

I was using 397.64 (currently the latest). I also tried going back to 391.01(which came with the card).

I thought it might have something to do with my power supply, so I removed 1 card and and tried with the 1080ti alone. I still get a reboot. It's possible denoising just pushes the 1080ti harder and my PSU cant handle it.

[itou31]

Hi,
Thanks for this realease.
Speed improved and denoise works best with 1080ti. (if mix or add 980ti, it slows down).

[nuno1980]

Universal material but it doesn't have birefringence (double refraction - eg: calcite) support!?! But will birefringence support Uber material??

[Notiusweb]

Hmmm...
I am getting exactly the same speed and times as before. Nothing bad as far as crashes, but nothing different.
Win 7, Titan X main display (not in use at all with Octane), then 5 Titan X Pascal, and 1 Titan Xp.

Are we supposed to be able to dedicate a GPU as 'strictly' for Denoising? If I do that, I get no render movement, no freeze or crash, just doesn't render.
I can stop and adjust devices in preferences fine, just nothing happens with the render.
I tried 3 just for Denoising and had the other 3 for regular rendering. I always have at least one active rendering card for tonemapping.

[Notiusweb]

Okay, so I was able to also test on a Win 10 build.
And in this case, I was in fact yes able to render while having some other cards seemingly dedicated to just Denoising.

But 2 things:

(1) BLUE SCREEN FREEZE -
it ran a couple times, then froze, and crashed to a Win 10 Blue Screen of Death. It actually reminded me of what used to happen back in the early V3 days, on my Win 7 when a PCIE 1x card was connected and then you selected Post Processing, it would freeze the system. Abstrax later added tonemap option in the device panel to allow users to specifically unselect from tonemapping those cards that were attached PCIE 1x...
Anyway, but the crash itself looks exactly like that. Like it runs, then suddenly freezes, and goes to Blue Screen. Perhaps a similar phenomenon is occurring where a task is choking the PC upon being sent to the cards in some way.
But for some reason Win 7 is spared, and Win 10 not.

(2) CATCH 22 -
When I was able to just dedicate cards just to denoising, from the test runs I did see completed, the rendering is slowed down due to the fact that - you guessed it - there are then cards being allocated to just denoising.
Meaning, even if you *could* dedicate cards just for denoising, you, yes, do lose speed as they are not rendering....so there's no point!....

My mind summizes a workaround for the crashing is this:
1-Set all cards that you plan on using as ACTIVE for rendering
2-Set one as tonemapper, but not as denoisers
3-Set any, or all, of rest as denoisers, but not as tonemappers...maybe even set a lower render speed priority on those set as denoisers.

Maybe will avoid a criss-cross somewhere for those with crashes?...

[Goldorak]

Universal material but it doesn't have birefringence (double refraction - eg: calcite) support!?! But will birefringence support Uber material??

The longer term aim with the Universal Material system is to in fact support anything that can be rendered in physical world, while keeping things intuitive for artists - even simpler than what we have had before. We'll have to get to that final goal in stages, as we continue to work on UM system beyond V4 (i.e. 2018.1+).

With the final V4 release, our aim is for mix materials to hopefully be replicated or converted in most cases to Universal materials. UM's already render faster in V4 XB2.1 than mix materials they can fully replace. We have also made sure UM's support substance out of the box starting with XB2.1, and more artist friendly interchanges will be possible with by V4 RC1.

[coilbook]

Okay, so I was able to also test on a Win 10 build.
And in this case, I was in fact yes able to render while having some other cards seemingly dedicated to just Denoising.

But 2 things:

(1) BLUE SCREEN FREEZE -
it ran a couple times, then froze, and crashed to a Win 10 Blue Screen of Death. It actually reminded me of what used to happen back in the early V3 days, on my Win 7 when a PCIE 1x card was connected and then you selected Post Processing, it would freeze the system. Abstrax later added tonemap option in the device panel to allow users to specifically unselect from tonemapping those cards that were attached PCIE 1x...
Anyway, but the crash itself looks exactly like that. Like it runs, then suddenly freezes, and goes to Blue Screen. Perhaps a similar phenomenon is occurring where a task is choking the PC upon being sent to the cards in some way.
But for some reason Win 7 is spared, and Win 10 not.

(2) CATCH 22 -
When I was able to just dedicate cards just to denoising, from the test runs I did see completed, the rendering is slowed down due to the fact that - you guessed it - there are then cards being allocated to just denoising.
Meaning, even if you *could* dedicate cards just for denoising, you, yes, do lose speed as they are not rendering....so there's no point!....

My mind summizes a workaround for the crashing is this:
1-Set all cards that you plan on using as ACTIVE for rendering
2-Set one as tonemapper, but not as denoisers
3-Set any, or all, of rest as denoisers, but not as tonemappers...maybe even set a lower render speed priority on those set as denoisers.

Maybe will avoid a criss-cross somewhere for those with crashes?...

are you using 397.64 drivers They freeze my PC and I get watchdog BSOD with asus motherboard

[Notiusweb]

are you using 397.64 drivers They freeze my PC and I get watchdog BSOD with asus motherboard

Great question, I am using 391.01 on Win 7 and 388.13 on Win 10. For no other reason than it just was working for everything else so I hadn't updated.
Coilbook, is yours on Win7/Win10, do you have all of your cards connected to the motherboard (8x, or 16x), or have you tried my suggestions regarding assigning separately denoiser and tonemap?
Would be interesting to see whether the crashing is, or is not in your case, halted by separating assignments. If it isn't then I can say what I was suggesting to try does nothing, but I *only* got crashing when I tried to specifically set a card for denoising ONLY. Also, it was on Win 10, driver 388.13 (we can likely cross out driver as cause). If you are Win 7, we can cross out OS.