Forum Discussion

7 years ago

[Fix] Crash Stabilization config files

This isn't going to 100% fix your crashes but should decrease them significantly. The game is basically gutted of specialfx and runs are incredibly low settings. This config is modeled after Mendo's...

videoconfig.txt1 KB

ApecksChampion

7 years ago

Or don't do this. No, seriously. I don't understand why everybody thinks it's a good idea to just copy and paste what everyone else puts in their config files and launch options. Do you even understand what any of them do? Take this for example

"setting.defaultres"		"1920"  
"setting.defaultresheight"		"1080"

Not everybody uses 1920x1080? Did you even read it or consider whether the contents are universal? Or this

"setting.dvs_gpuframetime_min"		"15000"  
"setting.dvs_gpuframetime_max"		"16500"

This is setting the min and max frametime, which is the time in microseconds that it takes to render one frame. 15000 microseconds is 15 milliseconds. You're locking your framerate at between about 60 and 66 frames per second. +fps_max 141? Not even 144? 141 only makes sense if you're using a form of adaptive sync, and i'm sure most people aren't and would be only negatively affected by that.

Oh and your autoexec file? 99% of those commands are doing absolutely nothing. Most are locked behind sv_cheats and are not accessible to non-developers. The rest will do *nothing* to fix a crash. The crash has nothing to do with any of this. Stop repeating this easily disprovable myth that any of these settings will fix a crash, let alone do anything. Bloated frankenstein autoexecs with random stuff pasted into them cause crashes, not fix them. You should only ever advise anyone to add a command to their autoexec if you know firsthand what it does, that it actually works, and that it's relevant to them.

LethalDF
7 years ago
Which commands don't work btw? Because i tested a vast majority of them and did research from source engine and they do work and no they aren't behind sv_cheats.

It's not random "stuff" pasted into a file and posted here for no reason, it's actually settings that reduce gpu load and have worked for dozens of people to 'lessen crashes' which i clearly said that's why i was posting them.

If people are crashing and desperate enough to be here why not let them try something else instead of coming on here like an * thinking you know everything?

I'm just here trying to help people and causing no harm while doing so. You're just here being cocky offering nothing.

Edit: use them or don't use them, me posting settings in a cfg file (that have worked for others) is no different than EA themselves posting a list of random BS as long as my arm in the troubleshooting guide.
- ApecksChampion
  7 years ago
  The stuff that EA has posted is not random BS. It’s what they need from the people experiencing the crash to help them. The keyword is them. The exception that most people are encountering with this crash is “EXCEPTION_ACCESS_VIOLATION”. That means that the client attempted to read from a memory that it doesn’t have access to. Basically it tried to read something that it doesn’t have permission to, or that doesn’t exist/has been deallocated. This is beyond the scope of changing your video settings and it’s a job for the developers. Just because people are “desperate enough to be here” doesn’t mean that they need to be fed misinformation and a list of irrelevant commands with no explanations.
  
  I’m not being cocky and I’m not trying to insult you. I’m trying to help stop the spread of misinformation that has become so common. I’m sure you did research, but you can’t trust sources not pertaining directly to apex. Since they forked the engine, it has become heavily modified, and I know for a fact that a ton of the commands which are unprotected in nearly all other source engine games have been locked, or changed. And trust me, if all of those commands worked, your game would be completely flat and gray, and you would have a huge advantage. At the very least you should put a disclaimer and tell people to back up their config folder first, as well as remove the commands that are not universally applicable.