In both cutscenes and gameplay my game has awful fps. It doesn't matter if the graphics are on high or low it's just terrible. It's making me really mad because I just got this computer in August and it fits all the spec perfectly. If anyone can help me I would really appreciate it.
I5 2300K,12GB RAM,GTX750TI 2G VRAM,344.75 driver，micro stutter（hitching） is everywhere when you are moving，im sad about the performance。
@ScorchingRage wrote:
@c3lix wrote:Performance fix for GTX690:
deactivate "tessellation", if you don't search for the effect in the world, you will not notice it, it also reduced SLI flicker for me -> my fps went from 40 to 60 in Hinterland, RedCliff is still in the 45's but before that it was in the 30's.
Force Vsync and tripple buffer in NVIDIA control panel removed microstutters/cutscene stutters.
Hope that helps.
No mate, let me tell you what happens:
I play everything at full, GPUs work at %70-75 at 1440p I get 40-80 FPS occasionally
I lowered settings GPUs work at %60-65 at 1440p and I get 40-80 FPS occasionally (that's happened when I lowered tesselation just like you said)
This unused power doesnt covert into extra FPS
There is clearly something wrong here
You've got it right there. The issue is that not only is the performance not scaling really at all, the GPUs (and CPU cores) are not being utlitised properly. It's a serious ****up, most likely at both the engine level and driver level.
@pillowthesleeper wrote:
@ScorchingRage wrote:
@c3lix wrote:Performance fix for GTX690:
deactivate "tessellation", if you don't search for the effect in the world, you will not notice it, it also reduced SLI flicker for me -> my fps went from 40 to 60 in Hinterland, RedCliff is still in the 45's but before that it was in the 30's.
Force Vsync and tripple buffer in NVIDIA control panel removed microstutters/cutscene stutters.
Hope that helps.
No mate, let me tell you what happens:
I play everything at full, GPUs work at %70-75 at 1440p I get 40-80 FPS occasionally
I lowered settings GPUs work at %60-65 at 1440p and I get 40-80 FPS occasionally (that's happened when I lowered tesselation just like you said)
This unused power doesnt covert into extra FPS
There is clearly something wrong here
You've got it right there. The issue is that not only is the performance not scaling really at all, the GPUs (and CPU cores) are not being utlitised properly. It's a serious ****up, most likely at both the engine level and driver level.
This is exactly the problem I'm having. DA:I is barely using my CPU, and GPU usage is not what I would expect at all for this game.
And I'm lucky if I'm getting 10 FPS on a system that meets almost all recommended (not minimum, recommended) specs. With all the settings turned down to low.
@IowaStExpat wrote:...and I tried reverting to the NVIDIA GeForce 344.65 driver
...still 10-11 FPS
...and then I dropped resultion scaling down to 50%, so it looked like King's Quest...
...still 10-11 FPS
Unfortunately there are no workarounds to these issues. We just have to accept that the developers at BioWare and at DICE (and Nvidia) have to fix it.
The shocking lack of testing/QA for this is amazing. They must have spent all their budget in testing on PS4/XB1 only.
Or they did do PC testing and the margin of Errors weren't high. It could be that many with NVIDIA do get good performance but there is a small percentage of us who don't.
I'm just trying to defend BioWare. Generally they do not make these mistakes.
If I was in the market of developing games, I would keep one PC around that was just a junker. Barely above minimum specs, not updated in the last 4 months. You know, Just to keep the spectrum broad. It may also show some nice little technicalities that should be fixed since it isn't an ideal testing rig
baffling
@Sabor wrote:If I was in the market of developing games, I would keep one PC around that was just a junker. Barely above minimum specs, not updated in the last 4 months. You know, Just to keep the spectrum broad. It may also show some nice little technicalities that should be fixed since it isn't an ideal testing rig
But would the issues in that junker prevent you from release? They might have encounted the engine error and just known that they'd have to patch it after release but there isn't much sense in this type of talk. Instead, lets keep each other up to date with updates on the patch we all so desperately need.
Probably. Testing things in the most ideal conditions isn't the best way to test anything. That's just giving something the best chance for success. You need to find the cracks
