So, I recently downloaded Blender 4.1 alpha just to try out the new version of EEVEE called EEVEE-Next… but it has been plainly UNUSABLE on my device.
While using the Viewport in render mode, the moment I switch the render engine from Cycles/Eevee to EEVEE-Next, the entire program would suddenly lag so badly that the entire program would effectively grind to a halt, until I switch back to one of the previous render engines.
and that’s just with the startup scene with the default cube and singular light! but the moment I try to do anything even slightly more complicated than that (for instance, adding a HDRI)… BOOM. The entire program would crash then and there.
I thought that disabling the realtime raytracing would sort of fix the problem… but that didn’t change a thing.
Does anyone have any hint on why these problems are happening? Is it that my system (Intel Core I5 8250U, 8GB RAM) is too weak to handle this? or is the current Alpha implementation of EEVEE-Next simply isn’t optimized for my kind of device yet?
if it’s the latter, then I hope that the devs fix it up in time for the final release.
Buit if it’s the former (my system being weak), then that could be bad, because if the devs go through with their promise of completely discarding the old EEVEE in favour of this one, then that could mean bye-bye realtime rendering for me. I hope this isn’t the case.