1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Dismiss Notice
Like RaceDepartment on Facebook.

FPS cut in half

Discussion in 'F1 2016 - The Game' started by dan020288, Sep 17, 2016.

  1. Hi Guys,

    I recently purchased f1 2016. The game was running great. Started a quick race in australia ran a handful of laps. all seemed well. Getting frames around 55fps - 70 Fps on my GTX970.

    However i closed the game came back to play a few hours later and now my FPS is 28- 33FPS.

    My settings have not change. I have been running 1440P with no Anti aliasing. all maxed out. nothing has changed on my PC. but the performance has basically been cut in half.

    Benchmark Result original 1 avg_fps="63.698608" max_fps="71.455086" min_fps="51.502041"

    Benchmark results slow avg_fps="30.592386" max_fps="37.963013" min_fps="19.953676"

    has anyone reported any problem like this.

    SPECS
    i7 4770k
    GTX970 G1
    16GB RAM
    WIN10
     
  2. Graham Laing

    Graham Laing
    ...... mostly harmless Staff

    Off the top of my head I don't know why it's happening, but I would try deleting the hardware settings files, and let the game detect your system again.

    Once the game is running you can then set up your graphics options to your preference again

    Path:-

    Documents > My Games > F1 2016

    Delete the hardwaresettings folder

    The folder and the two XML files in that folder will be replaced on game boot, the info xml contains your graphic card/cpu details, and the config xml contains the video settings that you set in-game

    It's worth a try ....... :)
     
    • Like Like x 1
  3. Hey, thanks for the reply. I did delete the xmls originally to no effect. However i did solve my problem. Oddly it was my dual monitor setup. Plugged hdmi out of my secondary display. Imediately fixed the problem and plugged back in. Seems like typical 9 series nvidia display issues.
     
    • Like Like x 1
  4. Graham Laing

    Graham Laing
    ...... mostly harmless Staff

    Ok, glad that you fixed it, and at least others may see this fix if they have a similar problem :)
     
    • Agree Agree x 1