Game crashes when I change video settings

[blindside32]

Whenever I change my video settings, the game freezes and stops responding as soon as I click apply. It also crashes when I click quit (it freezes instead of actually closing the game). I've been dealing with this issue for 6 years now (my current computer is about half that age), and I'm tired of hopelessly trying the same things over and over. Does anyone have an actual fix for this thing? If it helps, my specs are:

Graphics: Intel HD 520
RAM: 12GB
Processor: Core i7-6500u @ 2.5 GHz
OS: Windows 7 Professional 64-bit

HELP NEEDED

P.S. I prefer we keep comments like "I have the same problem" to a minimum, as that's not what I'm asking

[Ali.Z]

depends on your settings, you may want to provide more information about the settings you are changing; plus it wouldnt make much difference as your laptop wouldnt be able to handle the graphic properly.

[blindside32]

Resolution, V-Sync, and Anti-aliasing are the 3 main things I'm changing, and I at least figured out the resolution. As for the second part of that, I don't understand how my card can't handle it when it can handle more demanding games (MW3, Bad Company 2, Bioshock Infinite to name a few) with little to no issues.

[lewosch]

try changing those settings through config files. as default, config files are located; local disk (c:)/users/your windows username/AppData*/local/activision/CoDWaW/players/profiles/your in-game profile name

*if you can't find AppData folder, you need to enable visibility of hidden files on windows first. check this if you don't know how: https://support.microsoft.com/en-us/help/4028316/windows-view-hidden-files-and-folders-in-windows-10

config.cfg is for campaign/zombies
config_mp.cfg is for multiplayer

open the files with notepad and search (ctrl+f is convenient for this) for appropriate lines for the settings you wish to adjust.

seta r_mode "1920x1080" => edit the resolution at this line to your monitor's standard value
seta r_vsync "0" => "0" makes the vsync option disabled
seta r_aaSamples "4" => highest anti-aliasing is 4 as in-game option allows but you can try making it 8 or 16 just to see if it's better

after editing those command lines, exit the file when saving the changes made to it.

[blindside32]

Thank you so much! This didn't fix everything unfortunately, as it still won't properly quit the game (I have to close via task manager), but I can change my settings more easily now, and I figured out the game also crashes less if I play on lower settings. Sucks that I have to do that, but at least it's mostly playable.

[Ali.Z]

keep the V-sync on, the game engine that built this game is quite old and can not handle frames higher than 30 properly.

[lewosch]

Originally posted by Ali.A:

keep the V-sync on, the game engine that built this game is quite old and can not handle frames higher than 30 properly.

even the consoles could give 60 fps without difficulty back in the xbox360/ps3 days. implying 30 fps as something acceptable is an insult to the members of glorious PC gaming master race...

there are some engine-related issues in many older CoD games, with very high fps values like 200+; such as inaudible footstep sounds, increased jumping heights allowing easy out-of-map glitches etc. but still, enabling Vsync isn't a good idea as it creates some amount of input lag which can hamper aiming in multiplayer modes.

game has a default fps cap of 91 and that just does fine for average users. but if someone wants to utilize the potential of his 144 Hz (or higher) monitor; the default fps cap can be modified through in-game console (or through config files); by typing (or finding) com_maxfps 144

Gsync and FreeSync are both useful technologies (if monitor has these features) which prevent screen tearing while avoiding input lag. but Vsync is rather to be kept disabled; as the majority of fps (first person shooter, not frames per second ) players on PC think.