Author Topic: NaN Problem after crash, cannot find a fix.  (Read 1806 times)

2021-05-19, 18:23:39

alletect

  • Users
  • *
  • Posts: 1
    • View Profile
Everything was working fine until I accidentally subdivided an object that made my 3Ds Max crash.
I opened a backup file but with no luck, after trying some interactive rendering it just showed an overexposed photo with clipped objects and a streak of a random object in the middle.

An error message pops up that says "An internal error has occurred causing your image to contain NaN (Not a Number) value"

I've tried restarting Max a lot of times now, I've also tried to reinstall corona but had no result.
Please help!

**FIXED**

An object with a proboolean modifier was the cause of the problem

« Last Edit: 2021-05-19, 19:09:14 by alletect »

2021-05-20, 12:07:40
Reply #1

GeorgeK

  • Corona Team
  • Active Users
  • ****
  • Posts: 838
  • George
    • View Profile
Everything was working fine until I accidentally subdivided an object that made my 3Ds Max crash.
I opened a backup file but with no luck, after trying some interactive rendering it just showed an overexposed photo with clipped objects and a streak of a random object in the middle.

An error message pops up that says "An internal error has occurred causing your image to contain NaN (Not a Number) value"

I've tried restarting Max a lot of times now, I've also tried to reinstall corona but had no result.
Please help!

**FIXED**

An object with a proboolean modifier was the cause of the problem

If possible we would like to investigate the scene and see if the NaN error is addressed in Corona v7. Could you please archive your scene and upload it using our private uploader?

Private uploader: https://corona-renderer.com/upload

George Karampelas | chaos-corona.com
Chaos Corona QA Specialist | contact us