I’ve noted that, there is “Remove EEVEE-Legacy.” point in EEVEE-Next #93220
Is that good idea? Wouldn’t be better to leave eevee as is in daily build but renamed to “EEVEE (depricated)” or “Legacy EEVEE”. Just leave it as is, only fix critical if any show up.
I mean eevee-next is cool and fun, but it definetly have some deficiencies in comparison to legacy eevee. Maybe not huge, but they do exist:
Eg. lack of solo AO (HBAO, or GTAO in legacy) eg. for lookdev modeling and stylized purposes,
I guess that there are not a lot of those, but i’;m only playing around and testing and not doing actual work, but people will definitely find more in release.
And since 4.2 is LTS it won’t be updated for another year.
Also removing features without warning is always perceived negatively if new system is not seamless like CyclesX was. So at least one version with feature market as “depricated” is imo way better solution of removing old renderer.