Shader Compiling Bug

[Leo]

I've seen quite a few other posts of this issue though just in case not everyone is up-to-date or properly informed on what people are actually trying to explain what is happening.

Both I and many others can have this issue with the shaders compiling at the launch of the game, a process that takes close to 2-3 minutes on the high end. I've got quite the beefy computer and I surpass system requirements. Now, for you reading this, it could take only a few seconds to load up the game, something I have experienced too, not having to wait long, though the long wait times have returned for me and I am still unsure of the inconsistencies of why the game might not see that the shaders have already been cached. Again, this is not to be confused with the shaders compiling after a driver update, but straight up, it is creating the shaders as if it was launched for the first time ever. Not to mention, the absurdly high RAM usage when this happens, no seriously go check it out its pretty funny, sounds like my computer has turned into an intercontinental ballistic missile.

For further context, a game should usually compile all their shaders at the start of a launch for a new application, and from there only compile when needed. It shouldn't compile everytime. I've seen similar issues with newer titles having this same issue, more often than not games using UE5. Pretty shoddy if you ask me, though here's hoping that they even notice this issue since I just want to play an not wait a few minutes when other games it takes seconds because the game can just read the cached shaders it previously made. Even worse is I see some malarkey about "this actually makes the game run better" which is simply not true nor will it ever be. It doesn't make sense as to why people believe that but oh well...

Worst case scenario, this is really an Unreal engine 5 bug, to which I don't have much hope of them ever fixing it, they simply aren't the same company anymore. Hmm

[Gyunter]

any solutions for this? I have it too.

[Jemudr]

i am pretty sure it is not an unreal engine bug, the game is just a software mess and should be destroyed

[Yaku]

Fun fact: the shader compiler uses the CPU to compile it into the RAM. Because it seems Unreal Engine doesn't have the compiling programming for GPU.
Which means that it can't make the graphical calculations with GPU speed, so it'll instead use 100% of the CPU to finish them asap. And depending on what graphics configurations you choose it can either go the fast way or the looooooong way.
So yea, the programmers have this resource limitation problem.

You can check all this by using the Task Manager

[crystalcastles]

Did you check gpu debug mode on the game launcher? if you did, it will always compile shaders from zero, so uncheck that.
As noted above, compiling shaders is always a cpu task, that's normal.

[Jammpig]

Apparently this is only an issue with some steam users, some people have switched to epic games and fixed the issue.

[MALEIX]

This fixed it for me: https://www.marvelrivals.com/guide/20241114/41348_1193660.html
I had 3-5 minute compiling shaders issue and follow the directions on that guide exactly and it works, now compiling shaders only takes 8-10 seconds.

[Milo Burik]

Originally posted by Jammpig:

Apparently this is only an issue with some steam users, some people have switched to epic games and fixed the issue.

Nope, I have two accounts for MR, one on Epic and the other one here on Steam, and it's hard to say which is the faster for shaders compiling.
And yes, it's a 100% CPU task, my i7 13700k is all around on 90%, while my GPU 3600 Ti is on 0%.

[Keira Lunar]

if you on a 13 -14th gen intel cpu i recomend trying to update the bios that solved my problem i used to have to wait 3-4 minuets and prey it did not crash mid loading after the update to the bios it only took 10 seconds to load in and not crashed since as well

[sanbait]

in stalker 2 same problem Fix 5 line code by Modders community )) UE5 bad engine!
and developers worst

[Izzy]

The funniest thing is people asking "have you tried to install the game on a ssd?" like, no man, no one has ever thought that before, we don't even know what a ssd is... this comment of yours is just brilliant, thank you

[IRISHANARCHY]

Any proper solutions to this yet?

[MOvingLIkeBernie]

all this is madness, it's the video card that causes problems. I'm sure of it.
With an "ancient" setup, with a 1070ti, I could keep everything at maximum and the game NEVER lagged, zero problems with the shaders.
But after I bought a 4070 super : there is no online trick that can prevent the CPU from running at 100% when I load Marvel.
I just told you that I changed the whole PC thinking it was a bottleneck problem. But obviously even when switching to a powerful and recent PC, the problem remains.

[Buttons]

The game definitely has serious performance issues, but this should explain the change in CPU usage you are seeing.

Your old graphics card was the bottleneck in your system. Since it had very limited capabilities compared to the new graphics card, your processor was essentially waiting on it for more instructions.

Now that you have a much faster graphics card, your CPU has plenty to do.

What resolution are you playing at? I am confused as to how you were able to max out the settings on a 1070 Ti.

[Toiletdiqdoe]

This is horrible. it takes me 10 minutes to load the F*&*& game.

[MEGACHAOS]

I turned off game mode and it's now 20 seconds