Blender 2.8 Viewport Performance

(English is not my native language) #171

@pitiwazou, when you have some time available to translate, Clément has answered some questions.
I also wrote the new question number 24.

(Pitiwazou) #172

Ok I’ll do that :wink:

(so3Datel) #173

50k polys character and simple idle animation.
2.79 - 37 fps
2.8 - 16 fps

How can I speed up my viewport? I starting animate character in 2.8 and understand I cant continue working because 2.8 is dramatically slower than 2.7.
sorry for my english

(zanzio) #174

It seems like 2.8 needs a lot of optimization before it will perform better than 2.79. The spring team has to work with 2.8, so I imagine performance improvements will roll in over time.

(Bernardo) #175

has anyone tried if in scenes with a lot of objects, constraints and stuff like that blender stays fluid? In 2.79 heavy scenes start to be extremely sluggish, not necessarly for viewport issues but more because of all the stuff going on in the scene.

in theory the new depgraph should help with this… any one tested such situation?

(lacilaci86) #176

i did recently work with a scene filled with ton of heavy meshes and linked collections and particles. In 2.8 it was a very smooth experience. when i tried the same in 2.79 it was pain to look at and navigate. No animations etc. though. But I’m way more confident with 2.8 even in it’s current state than I was with 2.79

(staughost) #177

I am constantly testing blender 2.8 viewport performance. I can say that the performance on lager scenes with large polycounts have significantly higher fps in viewport than 2.79 (but 2.8 must be in opengl mode). In edit mode 2.8 is horrid, absolutely. Editing meshes above 100k is just pain.

(Bernardo) #178

thanks for the answers! That’s good to hear!

(Bernardo) #179

today I tried to open a huge scene in 2.8. We are talking thousands of objects, linked and in scene. many of these objects use constraints and modifiers. In 2.79 is becoming hardly manageable. The problem is not really the (huge) amount of polys in the viewport, but the fact that blender freeze every few operations I do. Sometimes it takes 10-15 seconds to select, move or delete an object.

2.8 works super smooth! Just an instant to do anything I want, no random freezes! I guess this is the result of the new depgraph! Maybe raw viewport performance is still not there, but I am sure it will be when they start optimizing.Nonetheless what I saw today I was great, kudos to the developers! The experiment went honestly beyond my expectations! :slight_smile:

(Pitiwazou) #180

2.8 must support this scene!


Dreams :smiley: Ptex support first

(m9105826) #182

Really? PTex is all but a dead technology everywhere outside of Disney’s offices. UDIM has long surpassed it as the “detail where you want/need it” solution that the industry latched on to for ease-of-transition and performance reasons.

(Pitiwazou) #183

Yes, only Disney use Ptex.

(• I don't speak English "by default", so... ) #184

Some people are having fun with ptex in 3dcoat tho. :wink:

(Ace Dragon) #185

Has Disney figured out how to multithread Ptex though when a scene using it is being rendered (as that was a major pitfall of the tech. initially)?

I would imagine they have made progress by now if they continue to use it.

(• I don't speak English "by default", so... ) #186

Not sure…

(Thornydre) #187

Don’t know if it has already been told, but I got really slow ctrl+Z, especially when it has to change the mode, for example from edit mode to object mode, well the devs are probably aware of that, but sometimes it is 5 seconds for a really simple object :confused:

(oaschwab) #188

What is the reason that 2.8 seems to be as good or better than 2.79 except in Edit mode?

(cekuhnen) #189

yeah this is very concerning …

(Rimasson) #190

I noticed that sculpting was 10 times faster with the april 2018 2.80 build and the clay engine than with the actual build