It will display Saving when it actually does the save. The first save is after you complete the first full mission (about 30-60 minutes depending on play style). When it says Checkpoint Reached that just means that if you die you will restart from that point, but that is not a proper save. But, I watched a play thru of the first mission on youtube. I gave up after twice thinking I had gotten to a save point and will pick it back up soon.
Thank you so much, i have played fc3 1 year ago on w7, now i have w8.This definitely has driven me nuts too. Just for the record, I'm doing this on a Windows 10 machine.Ĭan't thank you enough for this, it did indeed fix it for me Originally posted by God of Pie:I know that this is a year-old thread, but nobody's ever replied to it, and I had the same bug but managed to fix it, so I figure I should pass on this info in case anyone else ever boots up this old game and finds the same problem. If FC3 doesn't have administrator privileges, it can't save the game, so it just keeps bouncing save requests off Windows and having them rejected. Random theorising I suspect that this bug is caused because whatever location FC3 uses for its save files is locked by Windows so only administrators can edit it. If you aren't already running Steam as an administrator, exit Steam, then right-click on its icon and click "Run as administrator" After you've set FC3 to administrator mode, Steam can't run it unless Steam is also in administrator mode. Do the same for the "farcr圓_d3d11" application (you may only have to do this for one of the two applications, but let's just cover our bases here)ħ. Go to the "Compatibility" tab and check the "Run this program as administrator" boxĦ.
Right-click on the "farcr圓" application and click on "Properties"ĥ.
Go to the "Local Files" tab and click "Browse Local Files"Ĥ. Right-click on FC3 in your Steam library and click on "Properties"Ģ. Short version you have to run both FC3 *and* Steam in Administrator mode.ġ. Just for the record, I'm doing this on a Windows 10 machine. I know that this is a year-old thread, but nobody's ever replied to it, and I had the same bug but managed to fix it, so I figure I should pass on this info in case anyone else ever boots up this old game and finds the same problem.
0 kommentar(er)
