Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
Yup. Sucks but at least there is a work around. I just upgraded my entire PC and got a 7900 XTX and I can only play on Medium settings, 1440p without crashing.
I saw people even saying "disable hyperthreading", and I was like "are you mad?"
I do wish the devs would seriously put some focus on the CPU side of things (especially the graphics settings, where most of them barely do anything when turned up much or down, save for shadows/SSGI/SSR, which are main culprits in most games).
Also I tried the DX 11 mode and got far worse hitching/overall perf, and I swear people forget that not every build on the planet can run both DX 11/12 eprfectly. Some games work better for me in 11 (usually the older games), whilst others in 12 work better (like the newer titles, DRG for example works way better for me in 12 than 11).
As neat and interesting as the simulations are in this game, I don't think us taking a massive sledgehammer to our CPU's was worth such a trade off, in a game that's always online-based and will eventually die by the dev's hands one day.
I also tested with CPU on default clock/no OC and OC and turbo boost, and I got way worse perf with the former over the latter.
The game is so CPU heavy rn, that having less speed on the clock is actually a net negative, not a positive.
I saw that and thought the same thing. It's always the general "Windows people" advice - run as admin, do some random bespoke thing, disable hyperthreading, sacrifice a small cupcake to Microsoft, blame the anticheat, reinstall nvidia, format your PC, ...
The only useful Windows related was someone recommending Process Lasso to try to control the threading.
I will never not question why they shoehorned Helldivers 2 into Stingray. Autodesk isn't going to help them out to tell them why the threading is bonk.
Im not sure if non rdna3 users have driver timeouts but i think this helps especially for the driver related issues that acording to AMD now only effects dualscreen setup users, so if you have 7900 XTX and single screen and frequently crash perhaps do a bug report via AMD Bug Report tool, also does help reporting back here as well.
Been wanting to re buy the game by the next driver now 24.3.1 which still has not fixed issues, i hope the devs find a way to optimize it.
What probably happens behind scenes is graphics pipeline being to small for what game is trying to do with shaders less optimized for AMD hardware, just imagine a big train trying to enter a to small tunnel it will crash.
AMD has probably the tools to optimize these shaders aka replace them, but devs can probably do this as well, AMD also has a nice tool for devs to analyze crashes and cause that helps adress these issues kind of like debug tool
https://gpuopen.com/learn/rgd_1_0_tutorial/
This is probably not useful for avg user
I even see it on youtube and it still irks me.
Like years ago, yeah it made sense to right click the exe and click "disable fullscreen optimisations" and the DPI scaling, but these days the FSO isn't a big factor in performance hampering anymore (MS eventually caught onto this).
Things like "game mode on" is placebo, because I've seen multiple games and setups tested and it just isn't what people think it's gonna be.
The run as Admin really takes the cake though, like that is ancient advice, and these days it actually makes things worse than any good.
Yeah I've no idea either. Like they knew 2 years in that they got dropped on engine support, yet they still went ahead and continued working on an end of life engine since 2018 till 2024 and thought "yeap, no one's gonna have issues by the time we're done with this".
So now we're stuck with an outdated and non supported engine, that likely won't get many important fixes made to it to lessen the load, so now everyone is just gonna have to brute force on the CPU side (which is funny, because for years we've always been brute forcing from the GPU side on PC).
You're softer than warm ice cream.
At this point if they disabled arc then there would be player riots claiming that Arrowhead intentionally sabotaged the arc thrower to remove meta because they intentionally released a videogame designed to traumatize players unless they pay more money.... which is a really @#$!ed conspiracy theory and anyone that has that mindset can go back to Overwatch.
Even if we, as players, solve the Arc problems on PC it's still pervasive on PS5 so we'll just be causing other PC players and PS5 players to crash. Still can't use the thing except in solo or with limited friends. I've mostly sorted arc crashes for myself but still can't use it.
Someone is going to jump in this thread and call me a fanboi or something for even suggesting that the game isn't a "pay2win cash grab in early access" or whatever. There's no "right" decision for Arrowhead at this point. On one hand, the playerbase is a complete poop show. On the other hand they sort of set themselves up for failure by not explaining some of the game mechanics, using the bonked game engine, and not tracking changes very well.
Anyway I'm still on the side of the threading being wonky. You can solve it with Process Lasso in Windows, gamemoderun limiters on linux, and nice/renice on linux. PS5 is a console so gl hf until next week.