We’ve been finding lately that saving, xreffing and opening files in 3ds max 2021 is taking ages. Of course it’s relative, but as an example, I’m currently saving a building file, 344MB in size, on the server it saves up to 338MB in no time (what you would expect) and then it just stays there for minutes. 6min. in total just now.
My colleague saved a landscape file earlier, 3.8GB, again got to 3.75GB in no time, then stayed there for about 7-8 minutes. So we both end up waiting 10min or so for a save even thought the big difference in file size.
I’m not really sure where the issue is tbh, but its so inconsistent at times that it’s hard to nail down an issue. At other moments its fine, even with big files. It’s like max is trying to sort itself out or that there are too many railclones of Forestpacks…We’ve been cleaning up the files aswell (even moreso than usual) but it isn’t fixing it.
Last week it was taking 24min to send a render in BB, yet a week earlier a project with bigger files and more xrefs was taking a couple of minutes…
Check your scenes for animation layers and tracknotes (remove if you don’t use it), they can really slow down saving. Also check this thread I started:
I opened a ticket at ADSK and they have now reported it as a bug, it has something to do with the SMT (hyperthreading) of the Threadrippers, they say, but I tested it with off and I experienced some lag still (only tested a little while though).
Just wanted to say that Autodesk fixed a lot of the file saving and loading issues and performance in Max 2023. So it might be good to upgrade to 2023.
Ah ok…and yes of course now when I read it again without the effects of a night out, I can see the OP said it was with Max 21
Silly me.
However I seem to think it’s still a bit slower with 23…at least it appears so but it’s hard to check.
Maybe the fact that it has the progress bar and that it still hangs a bit at around 73% (which I know was an issue at some point initially) is giving a false impression.
I’ve been testing some stuff and it seems like max isn’t cleaning out the ram when moving to a different file. Currently in a testing file and ram was at 55GB, from previous file, and slow to IPR. Restarted max and the same file works instantly in IPR, with ram at 2,5GB.
We’ve noticed that the slowing down (ipr, saves, xrefs) is more noticable at the end of the day so I think it might be a build up somewhere that is creating issues. Anyone else notice anything similar?
It is funny you mentioned that. I posted on the AD forum and asked why MAX hates me and starts acting up more often at the end of the workday. The later I work, the more clumpy MAX gets. I run the Prune script often, which helps.
Yeah we recently bought that after reading similar issues in an older thread. It does help, but there still seems to be something slowing it down.
Railclone might also be an issue for us, the more railclone heavy the file the slower it seems to get. For example a 300mb building file with lots of railclones can take longer to xref than a 3gb file with just regular geometry. Same with saving and opening them.
This week I’m working on a project that was a nightmare to xref a couple of weeks ago so will do some cleaning and testing. Might just collapse all the railclones in the building file as a tester to see if it speeds it up. Last time it was taking 25min for backburner to submit a job, which was great when I had about 15 more jobs to go…ended up being quicker just rendering them on my ws for 15min in ipr and then saving the image as they were only 2k testshots.
I have a Railclone roof, which might be the issue I currently have with a project. I’ll delete it and see if that helps. Right now, everything is painfully slow.
Railclones/Forests have to be read and built each time you do stuff with them, so it does slow stuff down and it can be extremely painfully long.
I always collapse them as soon as I can, even if it means rebuilding them if they change. You can always have a backup.
Bobby, I’d put money on your roof being the culprit.
When I did the foliage growing thing in the desert recently, all those forest items were incredibly tedious to work with at times.
I had to really work on optimising things just to get some sort of interactability and then still, as you said in another post, it can be slow to cancel out.
check if you have multiple modifiers applied on any geometry? I was facing similar issue with one of my max file. I realized that i have used multiple modifiers like edit mesh over edit mesh ..and many others and same geometry was repeated as instance at atleast 50 places.. and that file was taking really long time to save or autosave.. i merged them at issue sorted!
Maybe you have turned ON Compress when saving files? It takes 2-5 times more to save if compressed, which is understandable. Same as with PS file as well
Just a quick update. Having done a number of new projects, both with and without railclones, it very much is railclone that causes the excessive load times. We recently did a huge project, zero railclones, loaded in no time. Both in max with the xrefs and sending them to backburner. A small project, but a lot of railclones, far slower. Everything else is essentially the same between the projects,
I’ve also gotten into the habit of collapsing RC’s so that’s helping a lot aswell.
