Nan

Corona Corona for 3ds Max Issues
1

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

2

You can send in the scene :smiley: 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 :smiley: )

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.

3

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: Chaos

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

4

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

5

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

6

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/ Button Render selected on/off

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

7

Interesting thanks, will test it!

8

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.

9

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.

10

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

11

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.

12

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 :smiley:

13

@renorr… how did you find what was causing the NaN issue?

14

Hi, if you are getting a NaN error, please contact us at https://support.chaos.com/hc/en-us/requests/new
We will either find the root cause or forward the case to our developers for further investigation.

15

I’m also having problems with NaN since a few days, i updated to the latest corona version and sent the scene to the support right away, but they couldn’t help me so far. Is there a way to find de corrupt object by myself? im running out of time and the scene is to big to find it by chance.

Thanks a lot for any advice

Im Using
Corona Version • 12 Update 2
and
Cinema 4D 2025.0.1 (Student License) (Build 2025_0_5b173c7692f9_1454601850) OSX

my file is to big to attach

16

Files of any size can be attached to the ticket, there isn’t a limitation there.

The general way to find culprits is what you could call “bifurcation” I suppose - hide half of the scene, see if the problem continues. If yes, hide half of what was left. If no, unhide the hidden half and hide the unhidden half. And keep cutting in half until you have a manageable number of objects to check.

OFC it might not be so straightforward for a NAN, as it could be a couple of objects interacting with each other, but at least it’s a (relatively) quick way to test to see.

17

@Rigugegl - can you share your support ticket number?