Установить Steam
войти
|
язык
简体中文 (упрощенный китайский)
繁體中文 (традиционный китайский)
日本語 (японский)
한국어 (корейский)
ไทย (тайский)
Български (болгарский)
Čeština (чешский)
Dansk (датский)
Deutsch (немецкий)
English (английский)
Español - España (испанский)
Español - Latinoamérica (латиноам. испанский)
Ελληνικά (греческий)
Français (французский)
Italiano (итальянский)
Bahasa Indonesia (индонезийский)
Magyar (венгерский)
Nederlands (нидерландский)
Norsk (норвежский)
Polski (польский)
Português (португальский)
Português-Brasil (бразильский португальский)
Română (румынский)
Suomi (финский)
Svenska (шведский)
Türkçe (турецкий)
Tiếng Việt (вьетнамский)
Українська (украинский)
Сообщить о проблеме с переводом
Тема закрыта 
Правила обсуждений
Пожаловаться
If you're running a DDR5 bleeding edge, make sure to check every month for a new bios and motherboard driver (chipset) updates until it's actually a stable platform. Early adopters get hammered by crap bios and limited testing drivers all the time.
My game ran fine for days without any issues, over 80 hrs. Then an hot fix broke it. Shuts down PC after a few min of play. Everyone looks to hardware issues. This method works if the game never work from installation. This is why it is important to have minimum hardware requirements listed.
I am running a almost 10 year old pc with a gtx 970 and I have never crashed. It's your pc.
Check your windows Reliability Monitor history under reliability details select the last Critical event copy past info and inside the game select F8 send feedback to developers.
(there's no TL:DR here, you'll stop reading exactly when you stop caring)
not when you look at how the thread title implies it is the game's fault, when there are so many other things that can be wrong between a work-in-progress game and a PC that is made of good parts but not set up correctly otherwise. It would be fine if they said "My PC is high end because specs, but game isn't running right, what might be wrong?". At least then you know you aren't going to have to unravel someone's assumptions and cognitive dissonance just to get to a point where maybe you can convince them that there are things they can do to help themselves. When the tone of a thread starts by blaming the game, anyone who has to do any real troubleshooting that wasn't conveniently fixed by "the big 5" just rolls their eyes and has to decide whether or not to invest in the thread because the OP already has too many assumptions happening with very little DEMONSTRATED competence. Sure, maybe it will be easy to help them, but the whole "I spent money and blame game, no other opinions will be tolerated, I just want to hear what I want to hear to validate my pain" is just all too common and all too impossible to help. Again, not saying THIS THREADS OP falls into that category, but anyone who goes out of their way OFTEN to try and help people even when they start with assumptions knows the odds are...not great, and anything we say may fall on deaf ears, but we keep trying in hopes that someone else who was about to make a similar thread will see it and stop, and maybe...juuuust maybe think.....oh, yeah! I haven't tried XYZ that they mentioned, I'll do that before broadcasting my assumptions in a way that would make it embarrassing to go back and admit I was wrong to jump to conclusions, and maybe I CAN help myself.
I'm not saying you, (HK that I am quoting) should have imagined that scenario before you called someone out, if you haven't been there then no amount of empathy would have led you in that directio9n, but it is a widespread phenomenon of un-helpable people(I know that's not a word, it's a colloquial, but again, if you haven't been there....) who are in that boat of cognitive dissonance where they BELIEVE they know enough about computers to say with certainty it MUST be the game's (devs) fault, yet the slightest bit of prodding and they will quickly demonstrate that they not only do NOT have the necessary competence to reasonably present such an assumption, but aren't even close to that competence, don't even have fundamental knowledge. They just read a couple google or quora top articles/responses, and occasionally watch some LTT so they think they know what they're talking about. I'm not accusing anyone of dishonesty mind you, just of being incredibly wrong IN COMBINATION with severe stubborness that makes them (again) un-helpable.
The funny thing is, so many of these people leave their own threads cold turkey in such a way that you KNOW some of them actually went back and tried the things suggested and they fixed the issue, but they never came back here and admitted it, not because their Steam reputation matters to them, but because they are entirely incapable of admitting they were wrong in ANY scenario (we all have that one family member, friend of a friend, acquaintance, if you don't then it's you JK haha not really it's actually you, again not "you" as in HK that I am quoting, but "you" as in anyone reading this) so they go back to happily playing the game without ever acknowledging that they started a whole big deal out of something that was based on their initial assumption being incorrect. I usually write it off as an age issue, but honestly I know a lot of adults who STILL do this IRL so I KNOW it is a real phenomenon.
But again, I'm not saying ANYTHING of that is what is happening with THIS OP, just that when Arty said something smelled fishy, I agree that there is LIKELY some disconnect, and while OP is probably having a legitimate issue, and may very well be open to non-dev-blaming assistance, the original post speaks volumes about how....well, helpable they are. One of the biggest tells in fact is "this doesn't happen with other games, so it must be because of this game" which is entirely false, but an understandable assumption because in legitimately trying to track down the issue, it REALLY DOES MATTER if it happens in other games or not, it helps narrow down the problem, but it does NOT indicate that it is the fault of THAT ONE GAME. People just assume that because in tech sup-port, we always ask "is it happening in other programs or just the one?" but that just helps narrow things down a bit, it does not imply that it is the one program at fault. DX version, resolution, CPU vs GPU usage, RAM usage, all kinds of other things exist between "is it happening in the one program or others as well" and "well it must be that program at fault" but because tech support takes in that information and doesn't spell out every possible implication to the user (because laymen won't get those implications, it requires a lot more education) many users assume it means things that it does not actually mean. This is a severely common misconception in tech support, that "only happens with XYZ program, so it must be that programs fault" which is a false logical connection more than 90% of the time. Just an example, again not saying anyone in this thread, including OP, falls into any of the described situations, just backing up Arty on why they were skeptical. I'm actually not even saying they were right to be skeptical, just that it's understandable. My one accusation here is that calling it a stupid rely is the result of inexperience, not knowledge, but if you want to argue against THAT point, I am totally open to it, and my replies would likely be much, much shorter.
- X570 AORUS ELITE
- AMD Ryzen 5 5600X 6-core 3701 MHz
- NVIDIA GeForce RTX 3070Ti
- 32GB RAM
Edit: Also forgot to mention. There is no obvious in-game action that triggers this. I thought it happened when removing a storage block, but tested it and it even happened when doing literally nothing after loading the game. Also tried "running away" as far as possible right after loading the game, no effects. Didn't try with a fresh start though.
I personally suspect a ♥♥♥♥♥♥ network card that might be ♥♥♥♥♥♥♥ with my motherboard, it's
ASUS PCE-AX1800 using MT7921 chipset. Just intuition at this point, I've read some bad stuff about it and was already considering replacing it for other unrelated reasons (quite stable on ubuntu, but not on Windows lol).
(Use the 'eventviewer' to look for errors)
That 10-20 seconds in is when there is a sudden CPU load on game objects. This usually manifests as 2-3 seconds lag spike for most.
Some AMD owners have reported instability when they have overclocked their CPU and/or RAM. Disable such OC and try again.
Also try and toggle VSync and limit the game to 60 fps via the game or driver.
Also monitored game EXE with procmon and Process Explorer to see if that gives any insights but no joy there either.
Have tried fixing frame rate and forcing DX12 but no luck. Hopefully it is solved when it leaves EA. Tis a great game :)
Specs are:
i5-11500
32GB RAM
RTX 3060
Games runs from NVME drive.