Chaos Corona Forum
Chaos Corona for 3ds Max => [Max] Bug Reporting => [Max] Resolved Bugs => Topic started by: JoachimArt on 2019-10-26, 11:18:54
-
I had this problem since I started using Corona and thought I mention it. But if Corona Interactive is running and you overwrite/update a texture used in the scene, Max will crash. I have tried to make an habbit of stopping corona interactive whenever I work on the textures but sometime I forget. It would be great if Corona would rather stop rendering than crash, at least.
-
You don't even need to run IR for crash to occur on image rewrite or delete. Previously it was guaranteed crash on such occasions, then this issue was fixed, but lately i see it returned. Most interestingly, sometimes i remove image from a scene, make sure that it is no longer present in assets tracker, but when i delete it from HDD in windows explorer, max still crashes.
-
Does this happen to all bitmaps ? Not sure why I thought it only happens to me when I use CoronaBitmaps.
-
Hmm, not sure about that, but i rarely use CoronaBitmaps. What i did notice, that crashes are most likely occur, when PNG file is modified or deleted. Maybe that's just coincidence, since i use PNG quite often, never bothered to test it.
-
I have not tried to bugtest it, but from my experience any kind of image with coronabitmap or regular bitmap it will likely crash if you make an update while interactive rendering is on.
-
We will definitely look into this.
It *might* be related to some of the issues with IR that were re-introduced in V4 (I think), such as crashes when resetting the scene and merging thing while IR is running.
(Internal ID=415639564)
-
I happens also sometimes when not rendering, if you have material editor open. Probably because it updates the preview balls.
-
Hi,
Is this happening with CoronaBitmaps or Max Bitamps?
Secondly which versions of Corona and Max are being used?
Cheers,
Rowan
-
I was able to reproduce it with standard bitmap now, but I believe it happens with both corona bitmaps and regular bitmap - it doesn't matter I think. The corona message viewer pops up but 3ds max crashes before you can see any error listed. This is with corona interactive rendering on while updating a bitmap. I need to have a scene with multiple textures for it to happen, if I only apply one texture to a cube and try, it doesn't happen. So it's not something that happens with every try or scene.
If you can't find a scene that has the problem, I can send you one. Usually it happens when corona interactive is on, in a large scene and you update a texture while it's running.
I'm currently using the latest official release of corona 4 (hotfix 1) and 3ds Max 2020.2
But this problem has existed ever since I started using corona, through 3ds max 2018-2019 and now 2020. So that means in corona 2 and 3 as well I believe. and on all machines I've used.
-
Hi,
If you have a scene where this is happening and are able to send to over to me I would appreciate it.
Instructions on how to do this can be found in my signiture.
Thanks,
Rowan
(Internal ID=415639564)
-
Ok, I have uploaded a zip file. Just hit corona interactive and try to resave the textures with small changes in the bitmaps. I tried it again, it happens randomly, now it happened with the texture called background.tga. These are not corona bitmaps though, but I know for sure it happens with both - but since I was able to reproduce it here I didn't want to change it.
-
Hi,
Thank you very much.
Rowan
-
Hi,
So after quite a lot of testing we were unable to reproduce this behaviour. Both with Max and Corona bitmaps.
Do you have the scene stored on a network drive or is it stored locally? Could you also describe the specification of your computer?
Thanks,
Rowan
-
That's strange I've had this problem since day one. I made a habit of trying to close material view and stop interactive rendering when working with the textures. It's stored locally I'm a single user freelance individual. so no network drives.
I've had this problem on several computers. Starting with intel x99 6 core i7-6850x, windows 10,. Currently I have Rampage extreme IV motherboard, i9 9940x and Windows 10. Working from local SSD on all occasions.
I have not tried extensively with corona 5, since that was just released but I can.
-
Hi,
Would you be able to send over a minidump the next time this happens?
I believe this is the best way for us to investigate this as we aren't able to reproduce it so far. Instructions on how to generate a minidump are in my signiture.
Update: I was able to reproduce the crash when deleting the texture from the directory while the IR was running. But this only happens with the Max bitmap, doing this using the CoronaBitmap doesn't seem to cause this kind of crash. Can you try using the CoronaBitmap and seeing if the crashes still occur?
Thanks,
Rowan
-
I just bought a plugin (material texture loader) that had this as a warning for corona users. Doing what is said here might be a good place to starting hunting for this problem. I will test when I have time but thought you should know.
"The CoronaBitmap has trouble updating many different textures at the same time, 3ds Max might crash as a result.
Either turn off Rendering for the material editor, or don't instance too many CoronaBitmaps."
-
Hi,
I'm still not able to reproduce this one.
The next time you experience a crash with this please can you send over a minidump? Instructions on how to generate one are in my signiture.
Thanks,
Rowan
-
Hi, I just tried now, it took me 5 minutes to reproduce this, very strange it doesn't happen to you. I have just committed a big report with my minidump. I did get a message in corona one time when updating the image, saying it had to stop progressive rendering because the file had been changed and being reloaded, I never had that before, but it might be what's happening, that it sometimes doesn't stop rendering when image is being saved and crash instead. anyway, I hope you'll make something out of the minidump.
-
Hi,
Thanks, where did you send the bug report and minidump to?
Secondly I think that error message is to do with using Max Bitmaps. Would you be able to switch to CoronaBitmaps and see if the issue persists?
Cheers,
Rowan
-
ok I will give it a try.
I made a new ticket through bug report. Didnt it come through?
-
I've not been able to reproduce it through corona bitmap. Maybe its gotten better in latest Corona 5?
Dunno if you want to check out the minidump for regular bitmaps - did you find that one?
-
Hi,
In Corona 4 we redesigned the CoronaBitmap reloader which in turn fixed some issues like this.
I have the minidump now, thanks for sending it through. We will take a look at it and see if we able to fix this as it just seems to be happening with the Max bitmap.
I guess the workaround will be to use the CoronaBitmap for the time being.
Thanks,
Rowan
-
Yeah now that I know I can trust corona bitmap I will use that. thanks!