- User Since
- Aug 13 2019, 6:16 AM (9 w, 2 d)
Fri, Oct 4
@Charlie Jolly (charlie) yeah, maybe but to be honest, personally I wouldn't change its default behaviour. It works as people expect. The only issue I think people have, is with the performance. That's my opinion at least.
Nodes selection is very common to be stored in the undo and it is very useful in many cases, especially on huge scenes where they will be very slow to navigate and you may have had to manually select many objects and you might accidentally click somewhere that will lose your current selection.
Aug 30 2019
A single undo in my scene, was at least a couple of minutes. My scene was an imported FBX data from a car manufacturer (and under NDA so I can't share I'm afraid).
Aug 23 2019
Hi @Bastien Montagne (mont29),
That's great. If you have a build that you want us to test, can you please give us some instructions of how to download and I can compare with the existing version.
Aug 22 2019
Oh, that's amazing. Can't wait for this to be addressed!!
Aug 16 2019
Aug 15 2019
hi @Brecht Van Lommel (brecht) , with version 2.8, we decided to give another go to Blender and overall it is great release and we were considering switching, but this undo issue is a the biggest show stopper we found so far. I'm surprised to be honest with the fact that this is considered "normal" priority. I have never worked in a production that doesn't have a few thousand objects per scene with a few million polys. If undoing a move takes a couple of minutes, this makes blender unusable for most productions I think. I decided to add this comment with the hope to bump this up a bit. I hope that's OK.