Chaos Corona Forum
Chaos Corona for 3ds Max => [Max] Bug Reporting => Topic started by: lupaz on 2024-01-19, 17:05:09
-
Hi all.
I get a NaN error window.
Just open the scene, and start IR (the viewport IR).
If you don't get the error try opening the material editor or moving the perspective view.
I'm not getting the error on the VFB IR.
3ds max 2023 - Corona 11 hotfix 1
-
I just downloaded your scene and no error here (corona10). Could be a corona11 issue? Not sure, thought id just share anyway.
-
Hi,
I have checked the scene, multiple times, with Corona 11 and 11 hotfix 1.
Nor the viewport IR, not the VFB IR, not production render lead to NaN.
Is there something specific you were doing which were causing the NaN, e.g. material changing (while rendering), render setting changing etc.?
-
Hi,
I was able to repro the same issue on my end with 3ds Max 2023 and 2024 + Corona 11 HF 1.
I have logged it further in our system to be further investigated by our devs. We will let you know if there are any updates on this.
(Internal ID=1287096377)
-
I am getting NaN issues much more often since Corona 11 HF1. It happens during IR while changing displacement values of Corona Displacement modifier. Of course if I save the scene it remains plagued by this problem :(
Is there any script or anything that might clean it?
Thank you
-
Hi Flavious, it would be best if you can start a ticket with us or if you want, I can also do it for you.
https://support.chaos.com/hc/en-us/requests/new (https://support.chaos.com/hc/en-us/requests/new)
-
NaNs are now happening to me on both my computers with Corona 11 - it happens mostly in denoising phase, but also in IR. I was testing many scenarios, material overide without any maps and it always appears. Only solution working is not to use Light mix......which is not pleasant thing
-
I have a similar problem sometimes. I noticed that this is after creating a chrome material. On the other hand, I can continue to work, I just have the error message that comes back when I restart an interactive rendering.
-
Yes when I imported some models with metal materials (from corona cosmos for example the white earphones without cable) then the NaN was there everytime either IR or denoise phase.
-
I confirm. With the transition to 11 Corona, I started getting random NaN errors. Moreover, they can be caught even on stage in gray material. And the more complex the scene, the longer you work in it, the more often you catch the NaN bug.
The same thing happens in 11.1 Corona. The error is present on all 3 of my computers.
For all those who are trying to catch this bug: I did not find any patterns that would help catch it. It's like random. Relatively speaking, I can work in a complex scene with a lot of suns and artificial light and everything will be ok, but I’ll catch NaN in some kind of closed corridor, which is essentially just a box. And vice versa.
-
I manage to reproduce the error. In an empty scene I apply a CoronaPhysicalMtl to a Teapot. I run the material in "Chrome" with the internal preset. I light the scene with a simple white color. If I move my point of view with the current interactive view, no problem.
But if I put an HDRI connected to a CoronaColorCorrect as a light source, there I can get the NaN message. And in this case, it appears at every change in the VFB, even if I remove the HDRI or if I change the material.