Thread title. Every patch or so for years on end now the game client goes off the deep end and starts randomly crashing to desktop with no error message. This has been going on since the game was in freaking beta and it's a common problem among the player base. It's ridiculous at this point. Beyond. On top of that annoyance, this last crash crashed my entire PC and when I came back it has reset EVERY single solitary game setting to defaults upon installation... Years of finely tweaked settings from every different sensitivity from vehicles, to zoom ins, etc... Every volume setting, every solitary graphic setting which every ONE was custom, including rendering, sound channels and draw distances... You get the point, it's all gone. I came back from a long hiatus from the game because I had grown annoyed with it, and this month back since I've enjoyed the sudden new direction the game has taken. But these constant CTDs and crap like this setting reset had REALLY put me off. I'm ready to cancel a six year subscription at this point... Let's get the basic stupid questions out of the way... 1. Yes, I've run the repair tool, through Steam and DBG launcher standalone, it finds no errors on either and fixes nothing. 2. No it's not the PC or it's hardware. This is a custom built very high end gaming rig that runs every other game or program on highest settings, some games much more demanding than PS2, with zero issues, ever. 3. The CTDs always seem to spike in frequency after patches. I've seen hundreds of posts about this and occurring at the same time from hundreds of other players over the years and it never seems to get fixed or even addressed by the dev team. 4. Typically the game tends to "stutter", sometimes just sound, sometimes just graphically, typically both... For a second or two before the CTD occurs. 5. There seems to be no rhyme to reason when, where, and why they happen. It occurs on every continent, any base or location, in small or large battles, sometimes just a 1v1 on foot in the middle of nowhere, in vehicles or not, in any seat, driving or gunning or just a passenger, and wether or not I've got people with me, be they friends, squad or platoon mates, or guild mates. 6. It also can occur literally any time of day, real life time. Also, sometimes I'll be mid battle, other times I'll be outside smoking a cigarette and come back to a desktop screen with the game gone. 7. If anyone can think of any more relevant, helpful towards solving this year's long problem, feel free to ask. As I said, this is a six year old problem and it's beyond RIDICULOUS at this point, I'm finally posting about it because support tickets NEVER get answered about it and the whole making me spend the next few hours attempting to get my very finely tuned game settings close to what they were, in between dodging more CTDs, has infuriated me to the point of about to cancel my subscription for good. Please DBG, finally freaking resolve this...
I keep a UserOptions.bkp file that's the same as the ini but with the extension changed. Always back your important stuff up. I'll say, "Congratulations." PS2 doesn't care. My experience with the game crashing to desktop without error and with a collapse of the audio subsystem were due to the game running out of memory. I used to have only 4Gb on a 32-bit architecture (yes, I'm talking way back in the day) and the sound system crash would happen when I was topping 2Gbs for just PlanetSide 2. Also, there used to be a bug with flak that could cause the same issue. There are probably other difficulties that would lead to the same result as well. You can't fix something you don't understand. I never did check the Windows logs for information about my version of the sound system crash issue but, since it bypassed the standard Windows crash handler somehow, I doubt any entry about it would be helpful.
Game isn't running out of memory with 16GB of RAM standalone not to mention all the memory on the card itself, that's why I didn't even bother mentioning specifics about hardware because that isn't the problem, like I stated, and this same issue has been happening to hundreds, probably more, players for years on end now, with obviously, multitudes of different hardware setups, better and worse... And you can't ever understand a problem to correct it if you don't put a concentrated effort into FINDING IT to begin with...
Gotta tell you and you've probably heard this before...sounds like a hardware problem or an issue specific to the computer you've been running it on since back in beta. Simply stating that this is the only game that exposes that weakness is not as beneficial to hardware/software troubleshooting as you might think. It's basically a means to an end.
I don't know if you didn't read, can't read, or are just plain stupid, but if you understood ANYTHING that's been said here, you'd have seen it's been happening to hundreds if not thousands of players on, obviously, different PCs, throughout the entirety of the game's existence. And no, I've been on different PCs throughout it's existence as well and it still occurs. Last time I'm saying this and last time I'm wasting my and everyone else's time replying to straight up ignorant replies to this thread... IT IS NOT A HARDWARE ISSUE OR SPECIFIC TO ME. GOOGLE THIS THREAD TITLE AND YOU'LL FIND PEOPLE POSTING ABOUT THE SAME PROBLEM FOR THE BETTER PART OF THE DECADE. Jesus room temperature IQ Christ...
No game is worth this dude. You are describing a pretty generic error under generic circumstances. The details you give seem consequential to you but then there are some very consequential variables that we can carry from machine to machine that only someone with experience would identify as the cause. Have you considered the problem is following you? Something that you're doing? Something that you're plugging in...a common action? Either way anyone that might actually have the patience to help you would need all your specs. The devil is in the details even if they aren't details you are willing to share or consider.
The amount of RAM you have is meaningless to a run-away memory leak, unless you can confirm that the application really isn't allocating more of it than the computer is willing to give up. Despite your hyperbole, this game is only pushing five years old, with a great number of days few and far between no-report crash to desktop threads. The fact that it doesn't happen to everyone all the time suggests the underlying issue ("issues" if more than one) is sensitive to the configuration of the computer or the client in some way and is not just in a certain file and certain line number of code or in the logic of a specific routine that would run for everyone in the same instances.
Not really convinced that you can totally rule out hardware problems. PSUs can wear out quite quickly and failures show up very often in PC gaming. You can't even say that expensive custom PCs are immune since if anything it's more of a problem for them. And you can't say that it was running other games fine earlier in the year so the system is fine because stuff breaks.
