I’ve played a handful of games that precompile shaders at boot up without it taking 15 minutes, and they try to hide at least some of it behind the splash screens and such. This is absurd. If pre-compilation or caching is needed, just fucking do it.
On top of what you said, that any company with the funds of Gearbox has no excuse for not being able to optimize it to happen during runtime without tanking FPS.
Steam basically does this right, imo.
When you launch a game, and… your drivers have changed, or there’s been a substantial update to the game… it just tells you its compiling shaders before properly launching the game.
15 full minutes is pretty terrible though.
I think my worst ever is around 5 to 10, and that is when I am intentionally fucking about with mods and different versions of Proton.
echodot@feddit.uk 17 hours ago
I don’t understand exactly why but they’re not storing the computed shaders so you constantly have to redo it. But it also shouldn’t be taking that long anyway. It takes the new battlefield maybe 30 seconds to do this, so something weird is going on in the background.
sp3ctr4l@lemmy.dbzer0.com 8 hours ago
Here, pick from various amounts of these 3 options, these have been the explanations for basically every ass tier AAA game in the past couple of years:
UE5 is very flashy, ‘developer friendly’ garbage that explodes in complexity when you try to do any serious modification/customization of the engine or render pipeline
None of these AAA devs that are supposed to be experts in UE5 actually are
Management is beyond incompetent and tells devs to do things that are actively bad/harmful/destructive/broken.