Codemasters F1 2010 – Save Game Crashes, Problems & Glitches
Not to be outdone by this past years most buggy games — which Obsidian seems to have a firm grip over with both Alpha Protocol & Fallout: New Vegas clocking in some game breaking glitches — Codemasters F1 2010 provided users with a litany of problems during the initial release month of the game. With this torrent of problems, players awaited the first set of patched updates from Codemasters, which finally arrived by the end of 2010. This article will outline some of the problems & glitches, like the synonymous Codemasters F1 2010 save game crash, as well as providing a viable fix for them if possible.
As previously stated, a patch was released for all platform versions of the game late in 2010. These addressed the Codemasters F1 2010 save game crash that had been plaguing a reasonable number of players. If you have the latest F1 2010 patch installed, whether that is through Xbox LIVE or via downloading it on the internet, then the major save game crash problem will most likely be fixed. Unfortunately there is still a cache of other problems with F1 2010 — aside from the no engine sound or other audio problems — which this article will look into.
Codemasters F1 2010 Frame-rate Issues
The PC version of F1 2010 is designed for multi-core processors, therefore having a single CPU core will indelibly make the game run poorly or even not at all. Furthermore, in Vista, the game requires more RAM than when it is run in other Windows OS’. Turning settings off — although undesirable, both the wind & mirroring effects are good choices for not gimping your graphical experience — is the only known solution to this extra RAM usage problem. Also, on PC, turning the “shadow mask quality” to 0 in the “harware_settings_config.xml” file increases performance and frame-rate.
Codemasters F1 2010 Save Game Crash Fix
There is a method to fix a corrupted save game on the PC version — although console players are out of luck if the newer official patches don’t solve the problem — and the steps are outlined below.
- Copy the corrupt save file (located in the My Games\F1 2010 folder) somewhere, like the desktop or “My Documents”.
- Start the game and create a new profile.
- Copy the new save somewhere else, having both a corrupt and clean save on your desktop for example.
- Begin to copy each “corrupt” file into the new clean save folder that was created.
- Run the game to check if any corruption error is thrown back at you. If so, then one of the files you just copied is the culprit.
- Root out the corrupt file/s by process of elimination and the save game should be fine once that file is deleted.
Final Words on F1 2010 Glitches
With the resplendent wealth of problems in F1 2010, especially on PC, the game still provides an enjoyable and often rewarding racing experience. It is a shame that so many bugs or glitches slipped through the hands of Codemasters quality assurance testing. As one final piece of advice, mixing and matching between different graphical or audio settings can lead to at least some playability, with solutions being the case of turning off a setting here or there. Also, get to know the “hardware_settings_config.xml” file, as it can be tweaked to solve numerous problems also.
This post is part of the series: F1 2010 – Guide & Information
- Codemasters F1 2010 – Game Controls Explanation & Guide
- Codemasters F1 2010 – Save Game Crashes, Problems & Glitches
- Codemasters F1 2010 – R&D Guide