Aces High Bulletin Board
General Forums => Open Beta Test => Topic started by: FESS67 on March 20, 2016, 01:34:43 AM
-
With all fruit turned on but with sliders in their default locations I get 70 FPS with 4 other players around me.
With things dialled down to get max frame rates I am able to maintain 143 FPS except when I buzzed town low. CPU load remained steady at 9 - 13% and memory use was steady at 15%.
Dxdiag attached. Note I have SLI disabled at the moment for testing purposes so this was with just 1 of the graphics cards working.
I found it very very hard to see tracers and hit sprites. Is that as designed or a video setting?
-
It seems that you have a very nice monitor (at least by my standards) {Native Mode: 2560 x 1440(p) (59.951Hz)}. It just may be that at that resolution, tracers and hit sprites are more difficult to see. Note they are significantly different than those from AH2, with a much more believable hit and debris sprite. Also, keep in mind that HiTech probably has such things scaled to the default field of view 80. If you are like most of us we use zoom to get that FOV and set the game setting far beyond that.
Between the two things mentioned above, lowering resolution or FOV (or using zoom) might give you what you had expected to see. Let me know if any of this rings true for you.
*Framerates for this patch have a shadow bug that affects machines with less than 2GB of dedicated video memory (this shouldn't affect your system, but for others that may compare, keep this in mind and disable shadows for now).
:salute - Always enjoy seeing folks looking into details. Since I am not much of a cartoon pilot, :airplane: this may explain my addiction with this sim.
-
With all the eye candy on I get a solid 50FPS, I'm not a big computer whiz but I believe it will be ok for me!!! :salute
-
In testing from 80 - 120 FoV, I found as your 100Mil gunsight reticle got smaller so did the tracer pixels unless you used zoom.
From my testing, a response in another post:
I tested 80, 100, 106, and 120 for the diameter on a 24inch monitor of a 100Mil diameter reticle. In a real cockpit, a 100Mil dia. reticle would be just about 2 inches at 18 inches from your face.
100Mil dia reticle ring at 18in(457.2mm) is 2in(50.8mm) in diameter.
80 FoV - 1.25 inch dia. 31.75mm
100 FoV - 1.00 inch dia. 25.4mm
106 FoV - 0.75 inch dia. 19.05mm
120 FoV - 0.625 inch dia. 15.875mm
As you lower your FoV towards 100, you gain back a few FPS and small yaw movements at 100 FoV for a 25.4mm 100Mil ring, are gigantic adjustments for a 120 or higher FoV 100Mil ring. Probably the foundational reason most gamers use only a dot reticle in this game.
-
When discussing frame rates it's important to say where you are and what you're looking at. With the same hardware and settings I can get pegged 60 fps flying over a forest and 5 fps when in a tank gunner's view inside that forest. When deciding on graphics card performance needs it's important to take into consideration what environment you'll spend most of your time in; air or ground.
-
He has a GTX 980 4G. All of this should be a moot point for him when he turns vsync back on.
-
I did not have vsynch turned on.
My gaming monitor is this one: Current Mode: 2560 x 1440 (32 bit) (144Hz)
I guess the dxdiag pics up my 4k monitor and reports the 59Hz as native
-
I did not have vsynch turned on.
My gaming monitor is this one: Current Mode: 2560 x 1440 (32 bit) (144Hz)
I guess the dxdiag pics up my 4k monitor and reports the 59Hz as native
No, DXDIAG shows what DirectX is using. If it says 59Hz, then that is what it is using. You did not load the INF file for the monitor so DirectX is assuming a generic monitor which is usually 60Hz.
You need to load the INF file for the monitor.
-
No, DXDIAG shows what DirectX is using. If it says 59Hz, then that is what it is using. You did not load the INF file for the monitor so DirectX is assuming a generic monitor which is usually 60Hz.
You need to load the INF file for the monitor.
Hmm. Thanks. Seems ACER do not as yet provide an official Win 10 driver for their XB270HU monitor.