#I think i found something about Low FPS/Crashes based on the processor

1 messages · Page 1 of 1 (latest)

signal warren
#

Hello, everyone! I'm experiencing the same issue that others in this thread are reporting. Like them, I tried launching the game with Steam parameters to force OpenGL 3.

Steam parameters: --rendering-driver opengl3

I noticed two things with this: first, the low FPS (around 40 on my PC) immediately jumped to a stable 60 FPS. I'm not sure if I can remove this cap through parameters to see how high the FPS can go. Second, like others here, the game now looks a bit “funky.” I don’t know if anyone has found another solution yet, but I stumbled upon something interesting today.

I’m using an IdeaPad 5 with an Intel i5-1135G7 processor and have found a strange connection between performance drops/crashes and CPU/driver compatibility. I bought this game to play with my girlfriend, who has had no FPS or crash issues at all. She’s using an IdeaPad 3 Slim with an AMD Ryzen 5 processor. I initially thought it was due to her having up-to-date drivers, so I updated everything on my end, but the problem persisted. So, I’ve been playing with the OpenGL 3 configuration for about two days now.

Today, I was at university with some friends, and we decided to test the game on a few computers in the lab and on a friend’s laptop. That’s when I noticed the same inconsistencies again. Here are the details of the devices we used:

Two Asus Zen AiO PCs (I didn’t check the generation, only the processors and hard drives) and my friend's HP laptop with a 7th-gen Intel i5 processor (I remember it was Intel). The Asus Zen PCs had different processors and memory configurations—one with a Ryzen 5 and the other with an Intel i7-10700T, if I recall correctly. What stood out was that the Asus with the Intel processor and my friend’s laptop had the exact same issues described here—low FPS, random crashes. When I applied the Steam launch parameter, it fixed the performance issues, but again, the visuals looked “funky.”

(waiting for the cooldown to send the 2nd part)

#

Currently, I’m using these parameters as I’ve been testing different settings to see what might work:

-useallavailablecores --rendering-driver opengl3 -high

I’ve already tried various DirectX versions and explored the possibility of testing with different versions of Vulkan (though I’m not even sure if that’s possible). So far, I haven’t found any correlation between hard drive or RAM and the issue, but maybe I’m overlooking something there. Right now, the only consistent pattern I’ve noticed is between the type of processor and the bugs.

thks for reading and sorry if my eng is weir its not my 1st language