Aces High Bulletin Board
General Forums => Open Beta Test => Topic started by: Hajo on August 16, 2016, 03:15:23 PM
-
This is so obvious that I'm afraid to post this.
Here goes. I have a Nvidia 970 GTX graphics card. On the first clipboard are graphic settings, FOV, antialiasing etc. I tried running the game
in 4096 resolution and it cut my frame rate in half. I dialed the resolution back to 2048 and got max frame rates. My FOV is 100 (player selected).
Adjusting up or down on either of these controls before entering the game is a good idea.
Hope this is helpful. I know most here knew this already. Hopefully this helps someone new to the game.
-
GTX970
GDDR5 - 4G last 512 slower than GDDR5
Data Paths - 256bit last 32 used for last 512
Band Width - 224Gbyte\sec last 28Gbyte used with last 512
Shaders - 1664
If last 512M not reached.
GDDR5 - 3584M
Data Paths - 196bit
Band Width - 192Gbyte\sec <---sorry didn't reduce 224 by 28 first post
Shaders - 1664
You should be able to play at 4096 default settings and get 60 fps. Or are you selecting 2048 so you can push all sliders to max?
-
GTX970
GDDR5 - 4G last 512 slower than GDDR5
Data Paths - 256bit last 32 used for last 512
Band Width - 224Gbyte\sec last 28Gbyte used with last 512
Shaders - 1664
If last 512M not reached.
GDDR5 - 3584M
Data Paths - 196bit
Band Width - 192Gbyte\sec <---sorry didn't reduce 224 by 28 first post
Shaders - 1664
You should be able to play at 4096 default settings and get 60 fps. Or are you selecting 2048 so you can push all sliders to max?
A few adjustments are at 80%. I don't need tree detail etc. I have shadows off. Everything else full bore. Maintains 59 to 60 FR unless low over large airfield where FR
can decrease to a low of 15.
-
This is so obvious that I'm afraid to post this.
Here goes. I have a Nvidia 970 GTX graphics card. On the first clipboard are graphic settings, FOV, antialiasing etc. I tried running the game
in 4096 resolution and it cut my frame rate in half. I dialed the resolution back to 2048 and got max frame rates. My FOV is 100 (player selected).
Adjusting up or down on either of these controls before entering the game is a good idea.
Hope this is helpful. I know most here knew this already. Hopefully this helps someone new to the game.
I have the same card. I run fr 75 with everything on.
-
What are your pre-game and in-game settings at flat? :headscratch:
With 4k textures, 1920x1080 resolution pre-game, everything enabled and all sliders (environmental included) set to max in-game, I get 29-30 frames just looking at things in the hanger. I get 28 FPS when flying over a town with a drop to 24 when flying over certain cluster of trees. I'll get 60 when flying up high, but down low in general I roam around 24-30 FPS with occasional jumps to 45 briefly.
I have the GTX 970 Windforce.
-
Weird the results we see from some players using the same graphics card name. Wonder if you are running different 3rd party boards?
-
What are your pre-game and in-game settings at flat? :headscratch:
With 4k textures, 1920x1080 resolution pre-game, everything enabled and all sliders (environmental included) set to max in-game, I get 29-30 frames just looking at things in the hanger. I get 28 FPS when flying over a town with a drop to 24 when flying over certain cluster of trees. I'll get 60 when flying up high, but down low in general I roam around 24-30 FPS with occasional jumps to 45 briefly.
I have the GTX 970 Windforce.
all in game max, pregame 1280/1024, fov 106, max tex 4096. I stay steady at 75 fps best I can tell so far.
-
Weird the results we see from some players using the same graphics card name. Wonder if you are running different 3rd party boards?
GIGABYTE GeForce GTX 970 4GB WINDFORCE 3X OC EDITION
That is what I am using.
all in game max, pregame 1280/1024, fov 106, max tex 4096. I stay steady at 75 fps best I can tell so far.
My FoV is set to Auto (which appears to default to 80? :headscratch:). That's the one bit I didn't mention, and missed. :o
I set the FoV to custom at 80 (default), and my FPS improved a little. Having it set to Auto seems to eat my FPS. I now get 29 over town AND over large amounts of trees, with the once in a blue moon drop to 24. I'm seeing 60 FPS stick longer as I get closer to the ground, but still hovers around 29-30 while flying low (under 200ft). Still a 29-30 when viewing in the hanger, but it sits at 30 longer with occasional drops to 29.
-
Weird the results we see from some players using the same graphics card name. Wonder if you are running different 3rd party boards?
Bustr I'm running an ASUS PC with a new power supply 650 watts and of course the 970. Intel i73770 at 3.4 speed and 16 memory. Win8.1
I am sure it's an ASUS MB.
As I said I set the FOV to 100. I can't recall what the game set my FOV to. Also I am running 1920 X 1200 screen resolution. Native monitor resolution.
-
The spread on the results amazes me.
-
Just changed to my new 29 inch ultra wide monitor 2560 X 1080. will post results.
Ok 2560 X 1080 resolution. Set that resolution in game. Everything looks larger! I'm closer to the gauges and have to look down to read them. Resolution in windows set also. It's native to monitor.
The 970 GTX supports the resolution. Ok......I thought the look out of and in the canopy would be smaller, further back from instrument panel but I'm right on it. I did install the LG software.
everything appears larger!
I set the game resolution resolution to 4096 with antialiasing and vert sync on.
My frame rate holds a solid 59 to 60 all the time
Please. Tell me I'm not crazy. Thanks! I was using a 24inch monitor before at 1920 X 1200. I am guessing that from going from 1200 height to 1080 is the reason.
Thanks for any explanation that saves my sanity. And to add I let the game set my fov. It went from the 100 I set to 96 auto game set. Rock solid frame rate 59 to 60 2048 resolution.
-
Hajo, one explanation might be your system recognizing the wider monitor correctly because you have the LG software installed. The software itself may not do any difference, the drivers within do. Did you have your 24" monitor drivers installed or was it a "standard monitor"?
-
Hajo, one explanation might be your system recognizing the wider monitor correctly because you have the LG software installed. The software itself may not do any difference, the drivers within do. Did you have your 24" monitor drivers installed or was it a "standard monitor"?
I didn't install software for the 24 inch monitor. Windows picked it up. Windows also picked up my new 29in. LG monitor. Ran from the get go. I reset everything in game on the first clipboard video setting. Installed LG drivers.
At 2048 resolution it was close to the instrument panel also. I went back and set the resolution to 4096, FOV automatically set itself to 96. Restarted the PC and still everything in cockpit looks larger then when I used
the 24 inch monitor at 1920 X 1200. :headscratch: As I said earlier maybe going from 1200 height to 1080 is making the difference as well as being an ultra wide monitor. Out side the cockpit aircraft and fields look normal???
Monitor is 2560 X 1080 so maybe the change in size has something to do with it. :headscratch: My vid card is an Nvidia 970GTX.
-
The pixel count is what affects the frame rate the most. 2560x1080=2764800 is more than 1920x1200=2304000 so there's 460800 pixels more to draw. That's 20% more work to do.
The drivers may explain something, another possibility is the connector. VGA, DVI or HDMI? Did you use the same cable/connector in both monitors?
-
The pixel count is what affects the frame rate the most. 2560x1080=2764800 is more than 1920x1200=2304000 so there's 460800 pixels more to draw. That's 20% more work to do.
The drivers may explain something, another possibility is the connector. VGA, DVI or HDMI? Did you use the same cable/connector in both monitors?
HDMI on both.
I just did a benchmark on the card. The card is running hotter 81 C then it did on 1920 X 1200. At 1920 X 1200 it ran 10 degrees cooler
98C I guess is the max temp for the card to run on NVidias web site. The card is working harder to fill the display at the 2560 X 1080 level. Maybe it's correct. Everything looks larger. Can see only half the instruments
and can not see the stick in the cockpit unless I look down. Maybe it's normal for a ultra wide monitor and 1080 as opposed to 1200 which would make it shorter in height and wider in width at 2560 <shrugz.>
Something to ponder. I guess a pilot would have to look down somewhat to look at the stick and some of his instruments??
Anyway it is 4:35AM here. I'm going to bed. Working and looking for answers to long. Maybe I'm trying to fix a problem that isn't there. Who knows?
Thanks for your help Bizman!
-
Alright... Now this is just advanced guessing, but: If your new monitor worked faster right out of the box, it may have installed the drivers automatically through the HDMI cable. That's a more and more common feature in USB so why not in HDMI as well. If not, the LG software certainly has installed the monitor drivers. Your old monitor may not have had any automatic driver installing feature and if you haven't installed the dedicated drivers for it manually it might not have given the full power. Generic Windows monitor drivers have been known to cause issues. Actually all generic Windows drivers cause issues sooner or later.
As for your card getting hotter it's perfectly normal given the fact of the card having to do 20% more work.
For viewing the instruments better, start with the automatic FOV setting and play with it until you find what pleases you. Your old monitor was relatively much higher, you're actually missing 120 pixels vertically. That's 10%. On my monitor 10% of the screen height equals the diameter of a gauge. If your FOV settings have been adjusted according to a 16/10 (width/height) monitor, they're way off with a 21/9 one.
-
Got it Bizman! Had to set FOV to 122. All is well again. Thanks for brainstorming with me. It's a long way from the auto set FOV of 96 the game set me at.
-
Glad you got it sorted. :salute