Using v8, when I turn off “Visible in reflections” the object is rendering white and this error message comes up:
===== 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.
It seems to only occur with certain materials. Furthermore, clicking on “Create bug report ticket” does nothing.
HDRI Sky - Confirming an issue, but w/ overexposed result & NaNs Error.
W10, R25 w/ v8 daily (Dec-16-2021)
Yes, overexposed is more like it. It’s not just plain white.
here also a NAN problem sadly,
also hdri (and sky) with different visibilities ( sun/sky/BG hdri / reflection hdri)
hope this can be fast fixed, otherwise 8 is great
AYN news on this?
this sadly makes many of my scenes fail in latest v8 version
Hmm, I am not able to reproduce this in V8. Would one of you be kind enough to record a short vid of this happening? Thanks in advance 
it renders with all objects totally blown out(white)
the usual Nan error message appears, , not sure what to record?
i have a sun, a sky, set to give gi, and a hdri in sky object that acts fro reflection/refraction and as BG,
the scene is big, but renders fine in r23 with corona 6
Hello Beanzvision
Here is the scene in which this error occurs. https://1drv.ms/u/s!AtQc0dCHh4Jfj6tqvFP2qNOPQ23RdQ?e=EKgbax
The problem disappears if you enable Visible in refractions on Corona Sky or reduce Roughness to 0 on material that has Refraction enabled.
Until version 7 Hotfix 2 everything is fine, since the first builds of 8 this problem appears.
For me this seems to have been fixed in the latest build. It’s been an issue since the start of V8 in most scenes but the 20th Dec build has fixed it.
i also have the same problem
Hello,
I confirm it too.
Hello,
we are working on this. As far as I know, the latest stable version (v7 hf2) does not produce this NaN, so that can definitely be used as a fallback
Thanks,
Jan
