I would be nice, if the undo performance (speed) would be better :)
Undo in big scenes is really frustrating. (Slow undo in scenes with over 100 obj and 10 mill polys)
Undo in big scenes is really frustrating. (Slow undo in scenes with over 100 obj and 10 mill polys)
7 Comments
I really don't understand Blender undo. It's messed me up many times.
It is different depending on the mode in which you are. In edit mode, going back will bring you back to the last editions of the mesh. In object mode, it will take you back to the last modifications of the object. So will delete all edits in edit mode at once. Remember that there is the shortcut Ctrl + Shift + Z to "undo" the undo. Sorry for translation..
@valentinwn: I've run many tests and find when jumping back and forth between modes that some of the history is lost.
* @valentinwn * Actually, for me it's not working like this anymore. Now undo changes between edit and object in the same order. I understand that's a more linear history action, but I had some struggle with it when working with heavy meshes. I'd love to see an option to use the 2.79 undo action.
This really isn't an actionable proposal. "Make it better" isn't particularly specific. The fact that you mention large scenes helps, but what's your metric for "large"? Where does performance fall off?
Even if you can't recommend suggestions for how to make an improvement, you can at least be very clear and specific about the nature of the problem you're having.
@Jason van Gumster: I did not say "make it better" is said "make performance better". I think every one who works with blender, knows the behavior of super slow undo, while working in scenes with over 100 obj and over 10 mill polys, so i just didnt mention the obvious so sorry for that. I just wanted to give this topic more attention, but if there is a better place to do this, than please tell me :)
Blender is not slower than other software. It only has very little integration of multithreading. The display interface is directly related to the actions. Thus we are always obliged to wait until the action ends before doing something else (including canceling). All would be to ask the developers to run all the operators in a different thread to not block the interface, and at the same time make a loading bar, and the possible cancellation.