4.0+ Destroyed Eevee

[Nirvash]

I've searched around and found a few cases of this talked about, but zero answers. But all versions of blender 4.0 and on Eevee is completely unusable performance wise. If I set the viewport to "material preview" so that it uses eevee, it takes about 30 seconds to initialize, and then once that is done, simply turning the camera runs at about 1 frame every 3 seconds, whereas in 3.6 and back eevee has always run instantaneously for me.

This happens regardless of driver versions (newest or rollbacks), and it has nothing to do with the scene itself since even if I load a very basic scene, the issue persists. If I take the same scenes in older versions, they run smooth, but 4.0 the performance has decreased by several orders of magnitude. Meanwhile "rendered" views and cycles run like 25% faster than old versions.

My specs are GTX 1080ti, Intel Core i7-7700k @4.20ghz. And of course everything else like brand new games, cycles, or other 3d programs run the same or better than they ever have previously. The issue exists exclusively and solely with the eevee render engine. And it's really frustrating since eevee is the ideal viewport for tweaking animations, but I've already updated my shaders and materials to use the newer nodes.

[butcho]

Cannot confirm this. I opened several projects in Blender 4.0.2 to test this but they all work like they supposed to work in Eevee, on both my 2070 Super and my 4070 TI. No lags in the viewport or while rendering or other odd behaviour.

Weird. I dunno but maybe it's related to different hardware combinations.

[KilometerHarris]

from what I can get out of blender, with the eevee render engine, it depends on the model and background, that's if you are using free models and maps, which I use. Some models I have don't export with Blender 4.3.2 on eevee, and some that do. My computer can't really do cycles so I have to use eevee. Hope this helps! :)

[Mittens]

Originally posted by KilometerHarris:

from what I can get out of blender, with the eevee render engine, it depends on the model and background, that's if you are using free models and maps, which I use. Some models I have don't export with Blender 4.3.2 on eevee, and some that do. My computer can't really do cycles so I have to use eevee. Hope this helps! :)

just disable compositor in the viewport settings

[Nirvash]

Since people started replying to this again randomly, I will just say that my original post is still correct in a sense, but I figured out why. First of all I'm sure since it's launch, Eevee Next has had some improvements. But the main issue for me specifically is I was building a massive shader for a character model that controls everything. Skin, eyes, lips and mouth, nails, everything. Not just the colors but also the details like bump nodes and procedural pores and the various intricate details of the iris, even having the material linked between multiple objects and combining all of their separate UV maps.

The original version of this shader used approximately 1 trillion color ramps. This made the shader very CPU intensive, and Eevee Next seems primarily CPU based. So that's why I could run it much faster in cycles than Eevee. I have since learned that if you just plug a Math node into a Mix Color node, then dragging the "From Min" and "From Max" between 0 and 1 does the same thing as a color ramp but seemingly for much less CPU usage. So that combined with other changes to efficiency have made it usable in Eevee again.

[DukeyNukey]

even my boyfriend with an rtx and however many cored cpu still has performance issues in blender when he didn't before 4.0. whatever they did is ruining blender.