Artifacts

[3dboomerang]

Hi;

Has anyone seen artifacts like this in their renders yet? What's the source?

Grts

[romullus]

Looks like NANs in combination with bloom&glare. You can right click on those black pixels in VFB to make sure if it's indeed NANs. Solution - report as bug and provide scene.

[TomG]

If you are using Corona for 3ds Max, you can try disabling the New Light Solver (in C4D, the same thing can be achieved by choosing either Group or Scalable in the Solver section in the Development/Experimental stuff section of the render settings)

Also, the latest daily builds of both versions may correct the issue for you too.

If any of those do fix the problem for you, it would be helpful for us to hear about that too :)

[3dboomerang]

Hmz, if I can fix it bny turning of the new light solver or bloom I'd go for that one.

Any idea when the new corona official update is coming?

grts

[TomG]

Bloom and Glare won't stop the NANs - if a NAN is present, Bloom and Glare will amplify it, but it will never cause them to appear in the first place (they always come from an error in the Corona core, as they are "not a number" results of rendering calculations, for instance if something tried to divide by zero).

Not fully sure what you mean by "next official version" - if you mean final releases, they are a ways off yet. You can watch the plans for both on the roadmaps:
https://trello.com/b/EfPE4kPx/corona-road-map-3ds-max
https://trello.com/b/dgI8vjDb/corona-road-map-cinema-4d

[3dboomerang]

Alright thanks, I'll keep an eye out. So for now no more new light solver then ;)

Grts

[maru]

Which exact version of Corona is this? It should not happen any more with 3 Hotfix 1, even if new light solver is enabled.
If it's happening in 3 HF1, can you send us this scene? The uploader is in my signature.

[3dboomerang]

K, uploaded

[TomG]

First thing to try would be to update to the latest Hotfix in that case, as Hotfix 1 corrected issues with NANs in the New Light Solver (https://forum.corona-renderer.com/index.php?topic=22859.0)

[maru]

Yup, that's Corona 3. Please try with Corona 3 Hotfix 1, and let us know if the issue persists. https://corona-renderer.com/download/

[3dboomerang]

I upgraded. Now I'm getting this....

[TomG]

Can try the steps on https://coronarenderer.freshdesk.com/support/solutions/articles/12000048205-nvidia-gpu-ai-denoiser-errors

Also, can swap to using a different denoiser for finals (and turn off NVIDIA during IR) in the meantime, to allow rendering your current project without NANs and without this error.

[3dboomerang]

Also, can swap to using a different denoiser for finals.

I was counting on the Nvidia one since I have a Geforce 1050 Ti, but yeh... ok.

(I don't understand why this is happening with an official release tbh... I'm doing high-end viz and I'm spending to much time on this erroneous, bugged state)

I'm not going to rant. Just unhappy with the outcome.

[romullus]

I don't understand why this is happening with an official release tbh...

I think it's mostly because of strange file naming decision by Nvidia, rather than Corona's fault. You're frustration is understandable, but you might be pointing to the wrong direction.