My game didnt save...

[Unbustable Nut]

I'm pretty pissed, I put a lot of time the other night into this game on Veteran only to find out the game never saved for some reason. Then I remembered this is why I stopped playing years ago... why is it not saving my game? I'm about to straight up skip this COD.

[lewosch]

it looks likely that you've manually set your config file as read-only, possibly for changing FOV or maybe tweaking some other options. other than that, I don't really know of any other reasons that could lead to this problem, as campaign progress in Black Ops 1 isn't even saved to steam cloud, unlike newer CoD titles.

[Unbustable Nut]

Originally posted by lewosch:

it looks likely that you've manually set your config file as read-only, possibly for changing FOV or maybe tweaking some other options. other than that, I don't really know of any other reasons that could lead to this problem, as campaign progress in Black Ops 1 isn't even saved to steam cloud, unlike newer CoD titles.

ahh crap, that's what i did...

[Jane Springfield]

You were using cheats on Veteran right?

[lewosch]

I think Black Ops 2 was the first CoD with steamworks integration where campaign progress was kept across different computers and even installing the game again later. before then, single-player saves were always stored locally on disk; either as separate files outside of configs, or being recorded as command lines inside a config. PC versions of CoD4 and WaW fall into former category, whereas the campaign of Black Ops 1 falls into the latter.

I believe setting the configs as read-only isn't actually required for the most part (for older CoD titles, at the very least), so it would be enough to save changes made to the file once and close it. if your intention was raising FOV value, you can find some community guides on steam explaining how it's done with command binds, by manually editing a config file.

[Unbustable Nut]

Originally posted by Big Daddy Z:

You were using cheats on Veteran right?

No I added in a command that binds a key to change FOV

[Unbustable Nut]

Originally posted by lewosch:

I think Black Ops 2 was the first CoD with steamworks integration where campaign progress was kept across different computers and even installing the game again later. before then, single-player saves were always stored locally on disk; either as separate files outside of configs, or being recorded as command lines inside a config. PC versions of CoD4 and WaW fall into former category, whereas the campaign of Black Ops 1 falls into the latter.

I believe setting the configs as read-only isn't actually required for the most part (for older CoD titles, at the very least), so it would be enough to save changes made to the file once and close it. if your intention was raising FOV value, you can find some community guides on steam explaining how it's done with command binds, by manually editing a config file.

Thanks! That's what I did, I think that is what caused my game to not save since I changed it to read only.

[PsyHaIceFire]

Originally posted by big swangin:

Originally posted by lewosch:

I think Black Ops 2 was the first CoD with steamworks integration where campaign progress was kept across different computers and even installing the game again later. before then, single-player saves were always stored locally on disk; either as separate files outside of configs, or being recorded as command lines inside a config. PC versions of CoD4 and WaW fall into former category, whereas the campaign of Black Ops 1 falls into the latter.

I believe setting the configs as read-only isn't actually required for the most part (for older CoD titles, at the very least), so it would be enough to save changes made to the file once and close it. if your intention was raising FOV value, you can find some community guides on steam explaining how it's done with command binds, by manually editing a config file.

Thanks! That's what I did, I think that is what caused my game to not save since I changed it to read only.

I bet you have save files! ^^
Go to \steamapps\common\Call of Duty Black Ops\players\save and you should see a few files.
Open your config.cfg and search for seta sv_lastSaveCommitedToDevice and seta sv_lastSaveGame
Edit These two lines to a save file you have and you should be good to go! :)
for example: save\kowloon-6.svg

[Unbustable Nut]

Originally posted by IceღFire:

Originally posted by big swangin:

Thanks! That's what I did, I think that is what caused my game to not save since I changed it to read only.

I bet you have save files! ^^
Go to \steamapps\common\Call of Duty Black Ops\players\save and you should see a few files.
Open your config.cfg and search for seta sv_lastSaveCommitedToDevice and seta sv_lastSaveGame
Edit These two lines to a save file you have and you should be good to go! :)
for example: save\kowloon-6.svg

Oh damn didnt see this, I just started last night and got to where I was but thanks anyways. Should have known setting that to read only would cause issues, feel like a straight n00b.

[PsyHaIceFire]

Originally posted by big swangin:

Originally posted by IceღFire:

I bet you have save files! ^^
Go to \steamapps\common\Call of Duty Black Ops\players\save and you should see a few files.
Open your config.cfg and search for seta sv_lastSaveCommitedToDevice and seta sv_lastSaveGame
Edit These two lines to a save file you have and you should be good to go! :)
for example: save\kowloon-6.svg

Oh damn didnt see this, I just started last night and got to where I was but thanks anyways. Should have known setting that to read only would cause issues, feel like a straight n00b.

DW :)
We all needed to find out the hard way at one point xD