Chaos Corona Forum
Chaos Corona for 3ds Max => [Max] General Discussion => Topic started by: ProxyFuel on 2022-10-20, 09:09:36
-
I have some 30+ students that use Corona render and we´ve been teaching and useing corona for many years. Suddenly my students started complaining that they got this error and ther render got abortet.
"Render had to be aborted because a bitmap on disk changed and is being reloaded. Continuing the render could cause crash or undefined behavior"
I found this info on the support page that "solves" the problem but I still don´t understand why everyone suddenly was getting this issue? Is it a corona 8 problem? Only other this that has changed is they use google drive to store files but in ofline mode.
https://support.chaos.com/hc/en-us/articles/4528201114641-Render-had-to-be-aborted-because-a-bitmap-on-disk-changed-and-is-being-reloaded-Continuing-the-render-could-cause-crash-or-undefined-behavior-Bitmap-name-is-XXXX
-
Thanks for reporting this. We have at least one more similar report right now.
The issue seems to be related to the asynchronous textures feature which was introduced in Corona 7, but so far we were unable to reproduce it.
Could you please try moving the project and all of its assets including textures from gdrive to a local folder (e.g. simply C:\test\, you can use the 3ds Max "Archive" option). Does the issue also appear after doing this?
-
Yes it still happens. When it first happend I was sure it was an issue with google drive trying to backup somthing and that made Corona freak out so I told everyone when they doing overnight renders to place project on desktop and just render from there. Still happend.
Could it have anything to do with "relative to the project folder"
-
That's very strange. Could please submit a support ticket here and attach any scene where this happened at least once? https://support.chaos.com/hc/en-us/requests/new
Please also include the following information:
- which version of Corona you are using (including hotfix version)
- which version of 3ds Max
- which version of Windows
- what 3rd party plugins you are using in the problematic scene
- what is the CPU model of the computer where the issue appeared
Thank you in advance.
-
I'm experiencing this problem too, in basically every scene. I have turned off the new cache bitmap thing in the scene settings too.
Corona 9 (official release)
Max 2023.1
CPU: Threadripper 2990WX
Windows 10
Plug-ins I'm using; Pulze SM (and RM) and basically no other major plug-ins I can think of
-
I'm experiencing this problem too, in basically every scene. I have turned off the new cache bitmap thing in the scene settings too.
Corona 9 (official release)
Max 2023.1
CPU: Threadripper 2990WX
Windows 10
Plug-ins I'm using; Pulze SM (and RM) and basically no other major plug-ins I can think of
Could you please also submit a support ticket about this? https://support.chaos.com/hc/en-us/requests/new
-
This is logged and we are still investigating.
(Internal ID=988777520)
-
Unfortunately, so far we are still unable to reproduce this issue, even with user scenes and their reproduction steps.
If anyone is experiencing this, please contact us at https://support.chaos.com/hc/en-us/requests/new
-
I have exactly the same problem. I regularly but non-systemically get the same message. Textures are stored on a network drive //server/project/bla-bla-bla. There are no third-party plugins in the scene. Max 2023.3, Corona 9 hotfix 1, Win10, Ryzen 3950х.
The message appears more often if you take material from an object in the material editor.
Then rendering stops, but the Stop button is not pressed.
-
hello. any update?
corona 10 happens the same, even during IR
thx
-
Hi, sorry, but we were never able to reproduce this and users stopped reporting this at some point, so we assumed it was not happening any more and closed our internal report. This sometimes happens, for example if an issue is random or is caused by 3rd party things like Windows Updates.
If you are able to consistently reproduce this, please contact us about it at https://support.chaos.com/hc/en-us/requests/new
Thanks!
-
It's still happening to me, but to a lesser extent.
Usually happens in a scene that I've been working on for a while after I import/merge a purchased asset from 3dsky (for example). It's a persistent message until I do a restart of max then it seems to stop happening.
So although it's still annoying, it's far less annoying than it used to be...