Ok, not strictly a corona issue but driving me a bit crazy nevertheless.
For some unknown reason my scene is super smooth while orbiting camera, selecting and in the material editor etc. but as soon as I transform an object (move, rotate, scale) then max locks up for around 15 seconds.
During the actual transform it’s incredibly smooth, the issue only arises after I let go of the left-mouse button.
Has anyone experience something similar?
I don’t think I have ever experienced something similar, but can you share some more details? Is it happening with any object, even very simple? Or only with some specific object(s)? High or low-poly?
Hey guys, sorry for the slow reply. I ended up trying some stuff from a 3ds max facebook group but so far the biggest help was to remove all animation keyframes from the scene - this alleviated the issue by reducing the “lag” a little bit but didn’t eliminate it entirely.
I’ve narrowed it down to two foliage objects, one is 1.2m faces, the other is 1.8m which is mostly made up of leaves.
Each object has around 10-20 other instances in the scene.
I deleted all other objects in the scene and removed materials but the issue persisted.
Merging the objects into a fresh scene didn’t help - the “lag” followed it across.
Selecting a set of instances (i.e. all of bush A) and isolating them seems to solve it, but the problem comes back after ending isolate
Hiding the other objects does not have the same performance effect as isolating, even though the same number of objects are still visible.
CPU is a AMD 3990X (64 core, 128 threads).
Unsure about SMT but may be able to check later.
no, some of the objects did have a forest scatter using them as an exclude, but the problem persists even after all other objects are deleted.
removing all scene materials also doesn’t solve the problem
When removing materials - make sure all scene materials are also deleted from material editors (standard and Slate). If they are displayed in there, there might still be an update happening since the map forcing the update is still present in the scene (but not applied to an object).
Sometimes there’s some dependency that is present which will trigger a global scene re-initalization which than can take seconds. These can be all sorts of things, like volume select modifiers using it as a subselection object, maps like Distance, wired parameters, objects used as particle generators etc. If you try to merge that object into a new scene, enable ‘Display dependencies’ in the Merge dialog and see if it highlights another object (it’ll highlight depending objects in the list in a blue color) when you select that object in question.
Other than that all I can think of are animation tracks but you already checked that. There were some older max version that would excessively add animation tracks needlessly but if you checked it’s probably not that.
If you find the cause, please report back, there’s always new things to learn