Forum Discussion
Hi, just an update on the testing I've done till now...
1. Removing the hardware config file didn't do any changes to the crashing. The game crashes my PC even after removing this file.
2. Removing the entire 'F1 23' folder which consists the hardware config file also didn't solve the issue.
3. Removed Steam download cache files. Need to login to Steam again once I've done this. The game still crashes my PC. After doing this, the game crashes on the 6th lap, not on the usual 1-2 laps.
I've tried all of these in F1 World -> Grand Prix -> F2 2022 as I have an ongoing race weekend in it. I'm now starting to wonder if it is a bug with the F2 2022 module itself. Will again have to test all of these in other modules like F1 2023, F2 2023, Career, Braking Point, etc...
@gkimiraikkonen7 wrote:Hi, just an update on the testing I've done till now...
1. Removing the hardware config file didn't do any changes to the crashing. The game crashes my PC even after removing this file.2. Removing the entire 'F1 23' folder which consists the hardware config file also didn't solve the issue.
3. Removed Steam download cache files. Need to login to Steam again once I've done this. The game still crashes my PC. After doing this, the game crashes on the 6th lap, not on the usual 1-2 laps.
I've tried all of these in F1 World -> Grand Prix -> F2 2022 as I have an ongoing race weekend in it. I'm now starting to wonder if it is a bug with the F2 2022 module itself. Will again have to test all of these in other modules like F1 2023, F2 2023, Career, Braking Point, etc...
I don't recommend any of the steps you've tried.
Simply deleting the hardware_settings_config.xml is sufficient - it effectively uses a "File exists? Use it. File does not exist? Re-create it." methodology. Starts the game in 'safe' mode', effectively re-probing the hardware.
Deleting random folders is never recommended or messing with Steam settings is only advised if there is anything in the release notes. Update the client and read the update history if there's an issue. People always ready to blame Steam; it's not the answer this time just because there may have been issues in the past. Rather a knee-* response.