This might or might not be related but a tip anyway: double check your max settings for bitmap loading resolution. + menu, configure viewports, then check that the textures resolutions are more or less default like 1024 pixels, 2048 pixels for viewport backgrounds. If you crank these up for any reason it can seriously mess up max file loading times.
Again, shouldn’t be anything related to corona but best checked anyway to rule out as your issue.
+1 here. 3Ds Max 2023, Corona 10 Hotfix 1
Extremely long loading times, stuck at “loading Corona assets”. 10 m+ and counting, a 1.23 Gb scene that was quite zippy before. What gives?
A quick update - the only workaround in my case was to revert to Corona 9, no issues whatsoever afterwards with the exact same scene
Something’s not right with the 10-build in terms of loading assets - my experience was that the scene would not load at all (so not that there was a long wait, but the whole thing actually froze)
Loading times are our worst nightmare in Max+Corona scenes. They are already pretty high in our most complex files in v9, but they always have been in previous versions too.
But cannot imagine having to wait for file to load even longer.
Thanks for the reports guys, won’t be updating to v10 until this is fixed I think.
+1 for this, glad I’m not the only one. Working on a few large files and they can take an hour to open. The current one is a particularly big 6GB file. Interesting that the Max log says the scene is loaded within 3 mins. Task manager is running at single thread speed and the RAM usage is idling around 20GB, so its slowly working on something but not building any RAM, there is zero disk activity, its been in this state for about 35mins and counting now. Eventually it usually opens after approx an hour. In other scenes I have put it down to lots of forestpack but only a few bits in this scene. I can try and archive it but I am guessing its going to be huge with all textures and assets.
I think we notice this loading corona assets more in Max 2024 with the loading bar feature which is useful.
EDIT: OK after 35-40 mins of idling around at 20GB ram and no disk activity, it bursts to life with loads of disk and cpu, ram quickly builds to 55GB and the viewport gets generated. Not sure what its chewing on. My guess would be material generating related. We were trouble shooting some crashes in another large scene and uninstalled corona to test and the scene geometry generated very quickly, just with all black materials.
Just installed v11, the daily build. The scene that I had problems with initially still gets stuck at 98%, loading Corona assets.
As stated before, the workaround for me was downgrade to 9 but also merge the problematic scene into a new max-file. Same scene content, same assets - loading times quite alright this time, given the size of the file. Both 9 and 11 work fine with the merged file.
Not done a closely compared time test but the latest one I’m sure is faster. Also the disk or RAM or CPU is always moving, unlike before where it was just hanging without activity for ages. Will keep an eye on load times next times with these large scenes. Good job!
OK Loading an other scene and unfortunately, still getting the long wait on the loading corona assets phase with the CPU running one thread and very little RAM / Disk / Network activity. The scene will eventually load but not sure what corona is thinking about during this phase. Not a particuarly heavy forestpack scene.
Can you please tell if Corona 11 daily build is slower or just as slow as Corona 10? And Corona 9 still loads faster than both?
Sharing the scene to test it on our end will be better of course.
I recently updated to Corona 10 HF2 for a project that required the implementation of some new features.
Today, I needed to perform a simple task: extract measurements from a basic Google Maps model, but it’s nearly impossible due to the lags in Corona 10.
I have attached the scene for your reference, and you can experiment with it to measure the time it takes for opening and merging materials.
Currently, I don’t have the time to test it with Corona 11 daily build.
Here are my “scores”:
[3ds max 2022]-Corona 10 HF2
Scene loading time: 9 minutes and 50 seconds
Picking multisub material: 10 minutes
After selecting the materials, I have to wait an additional 10 minutes due to 3ds Max freezing.
I have tested this on:
3ds Max 2022 and 2024
AMD Ryzen 9 5950X
64GB of RAM
SSD
Scene Information:
450,000 polygons
1 object
1 multisub material with 694 3ds Max Physical materials
I would suggest the following as the first troubleshooting steps:
1 - Click on the name of your viewport mode (e.g. “standard”, in your case: “standard-faster”) > viewports configuration > set all the “pixels” resolutions in that window to a low value like 256, then restart 3ds Max and try again
Sometimes the textures are loading extremely slowly when the texture resolutions are set to high values.
2 - Disable your antivirus/firewall (just to check if it has any effect).
Thank you very much for your video and advice. There is definitely something wrong with my machine.
However, before going through these steps, I reverted to Corona 9, and I also have some interesting time scores:
[3ds max 2022]- old settings (display performance - all 4096)
Scene loading time: 10 minutes (Corona 9 HF3) VS 9 minutes and 50 seconds (Corona 10 HF2)
Picking multisub material: 1 minute and 5 seconds (Corona 9 HF3) VS 10 minutes (Corona 10 HF2)
[3ds max 2022] - fresh ENU folder (display performance default)
Scene loading time: 40 seconds (Corona 9 HF3) VS 1 minute and 20 seconds (Corona 10 HF2)
Picking multisub material: 1 minute and 15 seconds (Corona 9 HF3) VS 1 minute and 45 seconds (Corona 10 HF2)
[3ds max 2024] - fresh ENU folder (display performance default)
Scene loading time: 45 seconds (Corona 9 HF3) VS 47 seconds (Corona 10 HF2)
Picking multisub material: 1 minute and 30 seconds (Corona 9 HF3) VS 45 seconds (Corona 10 HF2)
[3ds max 2022] - fresh ENU folder (display performance lowered all to 256)