Blender 2.8 Viewport Performance

these issues are known, and should be resolved in blender 2.82

They will not be resolved in blender 2.81 because they need a technical rewrite of some parts of blender, and then they will have to be tested for the right time in alpha and beta mode.

A branch already exists for the UNDO system, it should probably be made more solid and then implemented.

As you will have read on the previous posts, for the openSubdiv accelerate on GPU, first changes have already started


Happy to hear that! :slight_smile:

I’ve heard nothing about this being ‘resolved’ in 2.82, where did you read this?
They’re working on it, but it’s not an easy fix, so I’d be very surprised to hear that.

2.82 release is like halfway into next year I think so I’d be super bummed if they weren’t fixed by then. I don’t want to see them kick that can down the road another release.

Well, hopefully for the next 3-4 months they will make real progress on this … obviously nothing is absolute, I thought it was obvious by itself, but I believe that if these 3 problems are known, undo, slow heayy poly mesh editing, and slow opensubdiv perpetuate even after blender 2.82 will not be fruitful in terms of reputation, competition will fossilize these issues in the collective consciousness …
You can already imagine, “blender is a fun toy, but for serious productions it cannot be used”

So blender foundation has every interest in breaking down small dragons before they grow too much and take flight.
So even before adding new features, they have all interest in resolving once and for all these known problems in this release.

1 Like

Please don’t spread misinformation. There is absolutely no such commitment from the devs.

If I’m wrong, by all means, link it, I’d love to hear that too.


hey I’m not spreading misinformation, these issues are tagged for blender 2.82

As long term projects.

And even if that weren’t the case, a tag is hardly binding.

1 Like

Wow. There’s no need to be rude, I had no intention of angering you. I just stated fact.

Just because some stuff is tagged 2.82 that doesn’t mean it’s getting into 2.82, only that there’s not enough time to deal with it in 2.81. There is no 2.83 tag yet. This is not some remote possibility like sudden death, stuff gets moved along to the next release all the time. First they meant to fix all that before 2.8, then there was talk of fixing it in 2.81, and now the plan is 2.82. In two months the plan might be 2.83.

All the devs ever said about performance boils down to ‘we’re aware of it’ and ‘it’s hard’.


And it is for this reason that I responded to Micheal_Knudden that nothing is absolute and obvious, but that it would be interest of the blender foundation that these inconveniences are closed once and for all.

But instead of seeing this, to which you yourself came later, you thought I didn’t give you the right information …

This is ridiculous. I guess some people just want to be angry.


Man i believe that we are eclipsing on irrelevant details, maybe induced by misunderstanding.
So peace and go over.

3-4 months time is a long time. They need to show significant progress by then, or be ready to. Just today, a game company posted a bug report about how they’ve made the transition to Blender for production and are finding themselves dealing with performance issues.
There is a huge interest from the industry in Blender due to things like UX/UI changes and Eevee, but if big companies get burned by performance and it ends up costing them money, they’re not easily coming back to Blender.

That said, with performance being so fundamental to a DCC, and with companies like Ubisoft being now heavily invested in Blender, I think it’s only likely we’ll see progress soon. If not by the main development team, I should think/hope that now invested companies will find and contribute their solutions to Blender.

1 Like

They at least have things like edit-mode performance being todo items, so they recognize that it is a problem for many users. Some devs. also have done profiling on things like OpenSubDiv to identify performance issues.

The situation already is a little better in the current builds compared to 2.8, but many companies have administrators who install the software and will often stick to release builds.

Blender 2.81 in many parts is on a new planet in terms of performance compared to blender 2.80 …
The fact remains that the known problems remain, but it is normal, I know that they have made a preparation of a series of optimizations before facing them directly, also because they were more complex technical problems that require more time, and this is why we will see concrete results (we hope) in Blender 2.82

All I want for blender 2.82 it’s the GPU opensubdive implementation we are waiting to long for this !


My best guess is there will be incremental changes in the interim, which won’t be nearly enough, and some big rewrite will be necessary but will be punted down the line until there’s obviously a crisis. My money is on a 5 year wait.

1 Like

Anyone knows if there are any steps taken already to improve performance and if so how to find progress on that? At which stage devs are to solve that big issue? I tried to find that in raports, but it’s mostly silent.

I also think that this topic should be pinned because its a huge issue that most of the time doesn’t allow towork freely on high dense objects in edit mode. This topic shouldnt die in hundreds of other topics.

Right now no ,first we get blender 2.81 this week and after that they will starting push features and performance more aggressively

Perhaps this video will light a fire beneath the developers’ bottoms:

To be fair, though, in 2.81 I can perform the same operations using the new sculpt tools and butter smooth at that. And basic selections work a little slower on my aging system compared to Max in that video - not bad at all.

Just the raw edit mode performance needs a kick in the bottom. I am confident the devs will get there by 2.82 or 2.83/4. Matter of time. They seem to be aware of the bottlenecks.

PS I also tested the same model in Cinema4D 20 and Lightwave 2019 Modeler.

C4D does marginally better than Blender in raw performance, with selections slower, and transform operations about twice as fast as Blender in Edit mode. Sculpt mode in C4D was pointless and unusable: far too slow. Utterly unusable.

While Lightwave Modeler did keep up with basic selections, transforming large swathes of geometry was WAY slower than either Blender or C4D. But what can you expect from software which did not get any major updates in the past 15 years, or so.