I know this is probably a question for the Area forum, but this forum seems to be populated with the best and brightest. And sorry if I’m way behind the curve on this, but I finally started using 2011 in Dec 2010.
Has anyone else noticed how slow Max 2011 is when deleting objects? I’ve estimated it’s .5 seconds per object. Which isn’t too bad if you’re deleting 12 objects. If you’re cleaning up a Revit file and plan on deleting 1,500 objects you’ll have a lot of spare time on your hands. I have this condition two workstations. One Intel, one AMD. One fresh rebuild, the other a year old installation. I’ve poked around the innerweb but haven’t found a fix. Any suggestions?
Forgive me, I’ve had this problem before as well, and I don’t remember how I fixed it, but I will think hard about it. Does it occur when you copy an object as well? (Because mine did)
Hmmm… Well one file I was working in contained only editable polys. So that doesn’t seem to do the trick for me. I can even open up Max fresh. Clone a few hundred teapots or boxes and its still super slow to delete them.
i have exactly the same problem… scattered a proxy forest, then marquee select the ones i want to delete (about 6000) hit delete, went to make coffee… still going… after 3 hours i killed max and simply selected the ones i wanted to keep, and saved them to a new file.
ill try the undo thing, sounds like the kinda thing that might help.. never done a comparison with editable poly, but not really possible when its proxies youre deleting. tbh i think this has been a problem in max for years.. i certainly remember problems deleting in max 8 when i was doing the same sorta thing with forests back then. Its quite possible its worse now though.
Alright, I got a reply. It was with max 2009 that we were having this problem and it was the viewcube causing it. We disabled it on our machines and everything was back to normal (we had to rename AutoCam.grp or some file in the plugins directory to AutoCam.bak to disable it). Check it out.
I don’t know about all of you, but the viewcube, ribbon, and MR arch&design materials has sped up my workflow at _least_ 1%. Plus as an added bonus, the “File” button at the top is now 230% easier to click (because it’s 230% larger!)…
I have been having this issue and had been following this topic to hopefully get a solution. I had the viewcube disabled within max but had not renamed the AutoCamMax.gup file. Went ahead and did that and used a test scene with a couple thousand boxes to test differences…sadly, no difference for me.
I decided that I was going to get to the bottom of this and started pondering which major new features would have any need to track scene objects. First thing that popped into my head was PhysX, so I went and renamed “nvpxplugin.dlm” located in ‘Program Files/3dsmax2011/plugins’ to “nvpxplugin.dlm.bak” and got a few expected maxscript errors when loading the file. Not really a problem since I have only played with PhysX and never actually use it or have need of it in typical day to day work. Surprisingly, this fixed my “long time to delete” issue.
I hope this helps someone else.
EDIT: Found a more elegant solution…just move the file ‘px_start.ms’ from 3dsmax2011/scripts/startup to 3dsmax2011/scripts and it will fix the issue without breaking anything. Then if you do ever need to use PhysX, you can just run ‘px_start.ms’. Remember you will need to restart max for the change to take effect.
how the hell did you guess that!?! works like a charm!!! deleting takes about 1 second now. amazing there isnt more complaint about this “feature” of max.. i guess your typical user maybe isnt trying to delete 10,000 objects at a time..?
It seems that there is a specific number of per-scene objects that trips the ‘slow to delete’ switch. I am beginning to wonder if it is related to the quantity of RAM on the graphics card since it seems not all have this issue.
I have a GeForce 8800 GTX with 768 MB of onboard memory.
Well that settles it…it’s most likely not video card related.
EDIT: So when I get to about 350 objects per scene, I start to notice a little delay if I try deleting all 350 objects. It seems that for each object in the scene the delete time for each object in the selection is incrementally increased by the number of objects in the scene. By the time I get up to 10,000 objects in the scene, there is a noticable delay per object, probably about 1 second. If I were to select 20 objects and hit delete with 10,000 objects in the scene my rough estimated wait time would be 1 minute!
Oddly enough, poly count seems to have no impact on deletion time as far as I can tell.
EDIT2: That’s still not quite right since it only took about 7 seconds in that scenario…only 7 seconds :lol:
…all I know is that PhysX should be disabled by default and easily called on if needed. I’m done playing with it now.
I haven’t had this problem myself ( and have been using the PhysX plugin a lot lately ) but I’ve been using pretty small scenes with nowhere near 10,000 objects.
so ive managed to get this passed to the max dev. team. (its only a one-way pipe unfortunately so dont expect any feedback) but maybe the “beestee fix” will be incorporated in 2012
