Nan

[renorr]

Hi,
I'm on a tight deadline and need help.
Corona suddenly returns a nan error:

===== Warning(-19) =====
An internal error has occurred causing your image to contain NaN (Not a Number) value.
Please report the bug with the scene attached. We can fix these problems promptly if we have the scene where it happens.

What can I do ?
Thanks

[TomG]

You can send in the scene :) And all the details (which version of Corona, which host software, which version of the host software, which OS). See https://coronarenderer.freshdesk.com/support/solutions/articles/5000524006-how-to-report-issues-3ds-max or https://help.c4d.corona-renderer.com/support/solutions/articles/12000033461-how-to-report-issues-c4d, depending. (That page has the private uploader on it, for sending in scenes direct to us, rather than to everyone on the forum :) )

And when I think about it, an example of what the render looks like would be useful too, to see where the NaNs may be.

[romullus]

Hi,
Please provide the scene as suggested. Without the scene, developers can't know what's causing NANs to appear. You can upload it to the private uploader: https://corona-renderer.com/upload

Also, it is highly recommended to update to latest Corona. Many NAN errors were fixed in recent versions.

[renorr]

Thanks for the reply, found it by myselft, it will be faster to redo thoses objects.
And this project is confidential so..
thanks for your help btw

[GeorgeK]

Thanks for the reply, found it by myselft, it will be faster to redo thoses objects.
And this project is confidential so..
thanks for your help btw

If you managed to pinpoint the NaN offender I would please like to know, we are currently into a NaN-hunting report mode :)

[Bormax]

If you managed to pinpoint the NaN offender I would please like to know, we are currently into a NaN-hunting report mode :)

I'm getting the same error message and in my case it's somehow connected with the script I've stared to use about week ago. You can check it here
https://forum.corona-renderer.com/index.php?topic=27143.0

I get this message when the button is pressed, but not every time I use it, and I didn't notice any actual problem in my renders if I just press ignore line in messenger window

[GeorgeK]

If you managed to pinpoint the NaN offender I would please like to know, we are currently into a NaN-hunting report mode :)

I'm getting the same error message and in my case it's somehow connected with the script I've stared to use about week ago. You can check it here
https://forum.corona-renderer.com/index.php?topic=27143.0

I get this message when the button is pressed, but not every time I use it, and I didn't notice any actual problem in my renders if I just press ignore line in messenger window

Interesting thanks, will test it!

[romullus]

Thanks for the reply, found it by myselft, it will be faster to redo thoses objects.
And this project is confidential so..
thanks for your help btw

It might be faster for you to fix the scene for yourself, but the issue will remain unsolved and you or someone else, eventually will stumble upon it again. If you could provide the scene, developers would fix the code, to ensure that the error won't happen again. Your scene would be handled confidentally and would only be used to fix the issue.

[gunarchi]

m getting the same error, it wasnt there before but when i was working on night time lighting it appeared twice, then i restarted 3ds max it worked again but after some time it appeared again....
m using  3ds max 2020 , corona renderer6 RC4

please solve my problem , m in middle of my project.

thanks.

[rowmanns]

m getting the same error, it wasnt there before but when i was working on night time lighting it appeared twice, then i restarted 3ds max it worked again but after some time it appeared again....
m using  3ds max 2020 , corona renderer6 RC4

please solve my problem , m in middle of my project.

thanks.

Hi,

We will need your scene in order to fix this issue. Please can you send your scene to us? Instructions on how to do this can be found in my signiture.

Cheers,

Rowan

[gunarchi]

hi all, i dont know how but its fixed now, i just re-started my 3ds max couple of times and it was gone, never came back.

[TomG]

Just as a note, NaNs are usually random, because raytracing has randomness in it. Sometimes, the exact rays that caused the NaN do not happen - but sometimes they do. If the scene ever gave a NaN, and nothing was fixed or changed, then chances are it will come back again at some point (and then go away again, and so on). So, as a better safe than sorry, still best to submit the scene so we can look into it :)