Forum Discussion

Circubeer's avatar
11 years ago

Sudden FPS drop after 1 hour of play or sometimes even less (PC).

So I saw plenty of topics of people who had low FPS and the like.

My case I think is rather unique and I haven't read about it yet.

I run almost everything on ultra and I normally get an FPS of around 40-50 in EVERY place.

The problem is that after an hour or sometimes even half an hour of play the FPS drops to like 18 and won't go up again no matter how low I put the graphic options. When I restart my PC and start DA:I again it's all ok again and I can play on 40-50 FPS again till it suddenly drops.

It's very weird to me, my PC can obviously handle the ultra on 40 FPS, I really can't explain the drop.

Oh it also happends when I play other games first and then play DA:I after, it will never run on 40-50 FPS when I for example played LoL or CS:GO.

Anyone else has this problem and is there some kind of fix?

Or just wait an eternity for a patch?

Regards!

7 Replies

  • Overheating, memory leak, nothing else comes to mind.

    You can do a RAM, CPU and GPU stress tests to see if hardware is an issue. [Need 3rd party programs to do those and some time]

    Also check if all CPU cores work on the process ( If you get 90% for the first hour and when FPS drops it's 75 or 50).

    Also disable origin in-game overlay. You don't need it, compared to Steam's it's un-usable anyway. People report up to 20 fps drops with it on.

  • Circubeer's avatar
    Circubeer
    11 years ago

    Specs:

    8 GB RAM

    Intel i7-2700K @ 3.50 GHz (8CPUs) ~3.9GHZ

    AMD Radeon HD 7870 3 GB

    I already disabled Origin in-game.


  • @Hazosuta wrote:

    Specs:

    8 GB RAM

    @Intel i7-2700K @ 3.50 GHz (8CPUs) ~3.9GHZ

    AMD Radeon HD 7870 3 GB

    I already disabled Origin in-game.


    Sorry, but seriously... 

    1 CPU

    4 Cores.

    8 threads (irrelevant really)

    A very solid build, not saying it's not 😉 Just... Yeah, the little things. :P

  • This game has a memory leak for sure....goes from 35 to 40% usage then ramps up to 90%.  That's a memory leak.

  • You don't fix memory leaks. Bad code. But I wouldn't be that sure of that, I didn't notice change over time at all.