32FPS at character select w/ no gears

18FPS w/ 3 gears

6~8FPS in town

Windows 10 w/ Anniversary Update

Intel i5 4590

GTX780

16GB RAM

I've tried as much as I can think of, and the only thing I can tell that is probably happening is that the game game is refusing to use my GPU, since it's usage goes completely untouched when the game is running. And of course since this game uses a .atm file instead of a .exe, I can't force it to use GPU through drivers.

Any ideas?

I would like some help with this as well, having pretty much same issues you're having.

Win10

i7 4790k

GTX 1080

16GB RAM

I just quote my post from the other thread:

As far as i remember, it's not a bug caused by any Windows updates. It's more of a problem with Win 10 itself. There are some drivers or settings, that are not properly restarted, when you restart your computer, which causes some wierd FPS caps. I'm playing with 60 FPS normally (at least when there is no other person on the map. lel) and my FPS cap was set to 32 and later on it was at 16 FPS. Even in the Gear select menu. 

There was a way to fix it by opening the CMD line of Windows and executing some specific commands. The problem is, that i don't remember them anymore. I try to find them and post them asap. 

its this game, not windows. this game since it launched in 2006, has ALWAYS, run like shit, on every pc out there & still to this day. its always taken masangsoft years to update (and half assed at that) anything with the game to do with compatibility with hardware, drivers, os, etc.

anyone remember the nvidia "bug" that lasted so many years? lol...

I have the same problem, it's unplayable. Also 2 friends of mine have low fps like me. It seems also that the better hardware you have the worst it is. Any fix?

i7 2600 3.4 GHz

RAM 8 Gb

R9 390

Here's the fix guys:

Open your Windows command prompt (Windows search for cmd.exe) and navigate to your System32 folder by using this command: "cd  c:\Windows\system32" (Without the " of course). Then you type in "Shutdown /r /t 0" (Again without ") 

This will cause your PC to restart and your FPS should be normal again. I actually had the same issue yesterday and about a year ago on another server. I have now idea what causes the game to set a lower FPS cap but i can confirm that it's not related to any Windows Update. And no this won't do any damage to your system. it's just another way to reboot your system. You can Google it if you don't trust me ;)

EDIT: Some screenshots. Command line, FPS befor using the fix and one with normal FPS again.

It didn't work for me.

Well that's awkward. Are you sure you did everything right? That's the only fix for the FPS that i know, besides the usual stuff like disble Vsync, update your drivers and stuff like that.

I think i tried everything. I updated every driver, restarting the pc everytime. I tried with game booster. I tried with compatibility. I tried reducing the resolution. I tried with your method, but restarting the pc from the cmd it's not different from restarting from the windows button.

but restarting the pc from the cmd it's not different from restarting from the windows button.

That's not true. The person that told me to try that CMD trick, actual hosted a private Ace server and he knew quiet a bit about the game. He told me that Win 10 doesn' t kill all programs and processes entirely when you shut down your PC. That's the reason why Win 10 is booting up much faster than Win 7. Using that command line will force your system to kill every process, programm etc. and restart your system. That actually fixed my FPS like i said before. Even though i had to repeat it every once in a while. (Ace/AR was the only game that had any perfomance issues btw.). Since your problem sounds exactly the same, i thought it would help you too. It looks like something is setting a lower FPS cap as usual to the game. The normal cap is 60/62. That bug causes the game to limit your FPS to 30/32. Mine were even set to glorious 16 FPS once. But it was fixed by using that command every single time. If that doesn't fix your problem, i have actually no other idea right now. Sorry :/

EDIT: I just noticed i posted the same screenshot twice in my previous post. Now you should be able to see the difference. In the first SS my FPS were capped at 32. In the secnond one it's at 62 like it should be.

Btw i don't think it's a cap thing, because when i go in the first map and i look toward the outside of the map the frames go up, like it's a hardware problem, but it's obviuos it's not.

I get 17-18 fps in the gear selection.

In the first map i get from 7 fps to 35, 35 when i am at the edge looking outside where there is nothing to load.

Sadly Stormy, the issue is that the game is not using the GPU at all, not some awkward FPS capping. 

what we found out over the years; game doesn't like intels. or hyperthreading. a fast single core CPU can show better results than any of the 'new age' multicore ones.

then, the original graphics are (sadly)  uncompressed big chunks, processed by the CPU, on the same one core running the game. there used to be performance mods around, we will see if masang would allow such. if you happen to have some of the old ones, they're designed for AR, might not work here.

also, game has a hard time rendering anything written. chat, speakers, ments and so on. if you hide names, you get more fps.. true on a low spec machine.

finally, there's the windows 10 issue. namely, you're using windows 10 which is imo still a beta and leaves you no control over what is installed behind your back and what no matter if you need it. makes you "kindofalabrat" there.

try it on a old single core OC'd XP box, you might have more fps.

*edited* cuzican

The problem is the anniversary update (ver. 1607) of windows 10. Before that, airrivals runs fine on windows 10. The fps cap of 32 or 16 fps, stormy mentioned before, also exist and the real reboot helps there, but doesnt't fix the new problem. Unfortunately, I didn't find any fix for that problem beside going back to the last windows 10 build (ver. 1511). I hope that the next update from masangsoft, or the next windows 10 version, will fix the problem because going back can't be the solution for long term.

So far

~Space

well, 2 days passed, still no fix? im having hard struggles with that aswell