Bring back the EEVEE Legacy option
It is very good that the render is developing, but is it possible to leave a choice for those whose main workflow was built on the previous version of the render like in 4.1 alpha? The fact is that in the old render, I was able to achieve an image similar to Cycles, as much as possible, but in the new one it does not work. The new render is slower and one of the main features is missing, due to which it was possible to create an atmospheric picture and smooth out inaccuracies - Bloom. Yes, it is possible to add a similar effect in postprocessing (Glare), but this is not quite the case. In the meantime, I have to use the old version 4.1 for my projects and this makes me very upset.
RTX4090 renders:
-
Blender 4.1 Cycles 1024 samples 30 sec render:
-
Blender 4.1 EEVEE Legacy 64 samples 1.66 sec render:
3.1. Blender 4.3 EEVEE New 64 samples 2.07 sec render:
3.2. Compositing fake bloom:
13 Comments
This question is asked many times. But won’t happed due to technical and it management reasons. Reasons why this would not happen: Development time is split to maintain two different engines. Less time can be spent on fixing issues the new engine has. Including How to bring bloom option back. This is being discussed how to do that.
It also removes the reason for artist to learn how to use the new engine. Keeping us in this state and there will never be a good time to remove it. Making any development slower.
Additional optimizations cannot be done due the existence of both engines.
If someone is attempting to fork and bring Legacy back, fix it to a usable build, any advice or resources for them? Like maybe load orco attribute part? 😳
Advice to get in contact with us at chat.blender.org so we provide what is needed. Most stuff is in the git repository. Unsure what you mean with the orco attribute part specifically as that isn't related to the render engine, but modelling
The old engine looked finished and a working tool that did not require support. The presence of two (three) engines inside one product was demonstrated in version 4.1 alpha. It seems to me that the whole point is that developers perceive EEVEE as a prevision tool, while artists like me have learned how to use it in big production. Well, I realized, it looks like I'm stuck on version 4.1 forever, or I need to completely go to Unreal with projects from a gigabyte or more.
I miss the way old EEVEE performed and some of the features (AO/Bloom/SSR) but also understand that Blender needs to move forward. Better parity between EEVEE and Cycles is a great thing to have but unfortunately it will create some discomfort as features evolve. Jeroenbakker put it very succinctly, it's just not worth the resources to maintain legacy rendering options and you'd be better served by sticking with 4.1 for whichever projects require that. 4.1 is by no means outdated!
yes, but what about Geometric Nodes that go further and further from version to version? That's the sadness. Should I use 4.1 only as a rendering engine?
Yes, there's a reason that LTS releases exist. The software will change (sometimes drastically) from version-to-version, but users/studios tend to depend on a single version throughout extended projects. A regression between versions is a different story, but it sounds like you simply prefer the way a feature performed in a previous version. You should stay on that version if your project requires it.
I take back my words. I found that compositing mode can be enabled in the viewport. Recently, this was the only complaint - that the Bloom effect was not visible in realtime.
Well Blender 4.3 is now out but unfortunately EEVEE NEXT is still delivering poor performance compared to EEVEE Legacy blenderartists.org/t/blender-4-3-released/1558823/3
you may feel i am biased but in comparison the newer looks closer to reality than the style you are looking for... so i stand with the newer version for the sake of future optimization, bcoz only blender devs. has the patience and passion and a strong gut feeling to bring VULCAN for their users for the price you can't even imagine
I am literally currently working on an urgent Motion Design project with glass, lights, reflections, and in 4.1 I get an acceptable picture very quickly, but in 4.2 I did not succeed... when the project is over, I will try to set up the final image in 4.2 and throw off the result. But something tells me that the result will not be good enough. And I'm not against the new version. I just want to be able to continue using the old EEVEE in new versions of the Blender, so that I can use the Blender as a full-cycle production solution.
You might want to read this topic: devtalk.blender.org/t/blender-4-2-eevee-next-feedback/31813
but also: devtalk.blender.org/t/2024-08-13-blender-admins-meeting/36228
This proposal should be coalesced into a single thread: blender.community/c/rightclickselect/B8AN/