4 replies to this topic

[Jelan]

Looking for some trouble shooting or technical suggestions.

Every game at some point, usually early on I'll get quite a long freeze, it feels like at least a second and my mech carries on moving in the same direction etc before coming back to normal quite often wandering into the open like some kind of lemming. It feels like a lag spike every game, but only once near the start of engagement.

I'm playing on my old potato laptop with dual 1080 GTX cards, 64gb ram and an Intel i5 7600

Edited by Jelan, 28 May 2025 - 01:47 PM.

[Drenzul]

Interesting, I see the same and I'm running a 4090. Normally happens within a few seconds of dropping but
resolves in a fraction of a second for me.

[LordNothing]

you can try full window or flushing the shader cache in the repair tool. sometimes an update to drivers breaks your shaders and you need to have the game recompile them. full window is strongly recommended if you frequently alt tab out of your game and prevents tripping an unhanded exception (something to do with gpu power states). that one usually crashes to an error rather than freezing.

Edited by LordNothing, 28 May 2025 - 04:39 PM.

[Jelan]

LordNothing, on 28 May 2025 - 04:36 PM, said:

you can try full window or flushing the shader cache in the repair tool. sometimes an update to drivers breaks your shaders and you need to have the game recompile them. full window is strongly recommended if you frequently alt tab out of your game and prevents tripping an unhanded exception (something to do with gpu power states). that one usually crashes to an error rather than freezing.

Interesting I do alt tab out whilst waiting for a match and that does occasionally bork the match and I cant get back into it even with restarts, but I do run it in full window mode. I'll look into the shader cache thank you

[Jelan]

Drenzul, on 28 May 2025 - 02:19 PM, said:

Interesting, I see the same and I'm running a 4090. Normally happens within a few seconds of dropping but
resolves in a fraction of a second for me.

As a follow up it seems to have been fixed by reinstalling onto the SSD drive