given that the other excuses to complain have been resolved, it is obvious that the stakes have grown and now that of performance has become the hottest topic to chat us up right now
So it is likely that this becomes a priority to resolve for release 2.81 … but I’m not so sure it’s a simple thing to solve …
Perhaps a team will want a couple releases (time) of parallel work to study and do a nice project to solve the root problem?
I don’t know if it’s difficult to get something like I imagine:
I wish that any geometry object was being edited, this geometry-matrix of points selected and edited, behaved as if it were the only existing one, and the gpu and the cpu devoted all the resources exclusively to them in those moments of editing .
why do i say this?
Because I noticed that even though I have a super slow geometry very slow to edit, if I select a decent number of points and split them into a new object, this becomes superfast to edit …
So, according to logic, the road to solution is hidden around the corner in this sense …
logic wants that if a problem is too big to deal with, this must be split into many smaller and lighter pieces