Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: Citabria on June 19, 2012, 09:47:42 PM
-
got new vid card and it blazes.. runs skyrim like a dream etc.
it runs aces high fine with everything maxed out for an hour or so then starts to microstutter like mad. unplayable and unenjoyable. gunnery near impossible.
suckfest.
i cleaned all drivers etc etc.
I am told other people experience this. AH runs fine then bam stutter central.
grrr.
-
Which drivers are you using and what settings?
-
301.42 drivers
default settings on vid card.
everything turned on on aces high.
Aces high runs solid 60fps for a long time then out of the blue... bam micro stutter 25fps.
its not consistent it just happens out of the blue.
-
Same experience here. The game runs fine with all the eye candy on, steady 60 FPS for like 20-30 minutes then it slowly decreases to 15-20. Alt+tabbing in and out usually solves this problem even though sometimes it causes game crashes. It can be annoying. Especially since this system runs everything else (mostly Napoleon Total War and Skyrim) very steadily.
Radeon HD-5830, the latest Catalist, PhenomII 955, 8GB Kingston DDR3-1600 ram, AH is on an OCZ Agility 3 SSD, 500W Chieftec PSU.
-
Im using the same drivers but with 690s and I dont have the problem but I also do not have all settings maxed or even on. I dont like the way shadows look on opposing aircraft (especially bombers) so I have them off. I also do not use building shadows or the grass. I can turn them on without having issues with the following settings (and as I already stated).
I use 2048 textures in the first settings window but when I use shadows (graphic details) I have them set to a maximum of 1024.
I am using FXAA with 8x antialiasing under Enhance the application and with 3 prerendered frames.
Anisotropic filtering is set to application controlled.
Multi-display is set to single display.
Negative LOD bias is set to allow.
Texture filtering is set to quality.
Vsync is on.
All that said if I use CSAA above 16x I will get something like what you describe but I only see fps drop to about 55.
Now I know you will wait for Skuzzy to see if there is any other issue at work but if this isnt clear for someone and they want more info I can also post a screenshot.
-
Sounds to me like the memory of the video card is filling up. Easy to fill up 2GB (or more) of video RAM with Aces High, depending on the settings. Get enough objects in view with enough anti-aliasing and large shadow texture size and that will do it.
Just drop the shadow texture size and see if that helps. Or drop the anti-aliasing a notch. Or both.
-
So... the GPU can run it maxed out as long as the VRAM isnt full, then i alt+tab, ergo reset the VRAM so my card can run AH again for 20 minutes?
Why the old (maybe unneeded) data isnt cleared from the VRAM? Is that even possible?
-
301.42 drivers
your problem is from the drivers, there is an inconsistent bug in them. the gpu will sporadically drop down to 50mhz, nvidia claims it only happens with overclocked video cards but, people with stock cards are having the same issue. either roll back to the previous drivers or try the beta drivers if you feel brave.
-
So... the GPU can run it maxed out as long as the VRAM isnt full, then i alt+tab, ergo reset the VRAM so my card can run AH again for 20 minutes?
Why the old (maybe unneeded) data isnt cleared from the VRAM? Is that even possible?
Aces High does release data it no longer needs for the draw, but caching is done, which can cause data to be left in video card RAM. The drivers will not clear it, if there is still system RAM it can use (the overflow) for storage. Unfortunately, any video card fetches from system RAM are going to cause stutters due to how slow that process is.
gyrene also brings up a good point.
-
removed the drivers and installed the old 266 drivers from the disk the card came with will see if that works.
-
I played for more than four hours tonight with no issues. I looked into the bug reports and its "some manufacturers" and the cards are dropping back "by 50Mhz" and not "to 50Mhz." Also the sporadic problem is "intermittent vsync stuttering" and again only by some manufacturers. No idea what that even looks like.
Doesnt seem to faze the 690s from what I can tell.
-
I played for more than four hours tonight with no issues. I looked into the bug reports and its "some manufacturers" and the cards are dropping back "by 50Mhz" and not "to 50Mhz." Also the sporadic problem is "intermittent vsync stuttering" and again only by some manufacturers. No idea what that even looks like.
Doesnt seem to faze the 690s from what I can tell.
uh ya...
not surprised the 690s aren't affected, not as many people are willing to shell out $1000 for a video card as there are people buying $200-$300 video cards. most of the complaints i've seen (outside of the nvidia propaganda) have been with 4xx and 5xx series.
-
Doesnt seem to faze the 690s from what I can tell.
I got a Ferrari. Im rarely being overtaken by Fiats.
:rolleyes:
-
Interesting... the bug reported was specifically for the 600s being affected but specific brands of factory overclocked models.
Apples/Oranges debrody.
-
Apples/Oranges debrody.
Not as much. If its a memory overload bug like Skuzzy said, how can you overload a card with 4/6GB vram?? My lord.
-
Not as much. If its a memory overload bug like Skuzzy said, how can you overload a card with 4/6GB vram?? My lord.
If you crank up the shadow texture size to max, use all the shadow and bump map options, and crank anti-alias to its max, you can chew through 4GB of video RAM pretty easily, if you get 64+ objects in your viewing area.
-
Not as much. If its a memory overload bug like Skuzzy said, how can you overload a card with 4/6GB vram?? My lord.
This is a 690. What can you tell about the 4GB model on this card from the photo here?
(http://i447.photobucket.com/albums/qq197/Chalenge08/StrippedDownGTX690.jpg)
-
??
the 680 came out with 2GB vram, the 690 got 2*2 by factory default. Its pretty unlikely that the manufacturers fit it with 2*1... The 6 i mentioned was only my slow brain, sorry.
-
Thats right each GPU has 2GB. I think you can see how 2GB would run out very quickly with the upper level of graphics settings in AH.
-
hmm turns out that AH maxed out requires a way better video card than the Crysis2 and the Metro2033 together... or an old 4870 with 8GB ram would be enough
:lol
-
If you say so.
-
hmm turns out that AH maxed out requires a way better video card than the Crysis2 and the Metro2033 together... or an old 4870 with 8GB ram would be enough
:lol
No it does not. The game can chew through a lot of video RAM, but that is just a resource. You want to be able to see 17 miles, have unlimited objects rendered in that 17 mile radius, and have good graphics then it takes a lot of resources.
Here is some simple math. Take an 8192 shadow texture size. That one texture, for each shadowed object, will use 256MB (8192*8192*4) of video RAM. Now, how many shadowed objects can you have in view before you run out of texture space for that one texture? This does not take into account the texture space for blurring the edges of the shadow, or the rest of the world and textures of the object itself.
I really think we should remove both the 4096 and 8192 options from the shadow texture size. Both those options are doing us more harm than good. Constantly having to explain the math and listen to people complain how their 512MB or 1GB video card runs badly as compared to some first person shooter or fantasy game which have view limits measured in feet rather than miles along with limited object counts in view is not good for us.
-
Look,
to be honest, my game isnt even maxed out.
-shadows were disabled (the HD5830 cant handle the 8192 shadows withouth an instant, large frame rate drop, also the 4096, what can be run smoothly, still look a bit "cube-ish" so i found it better to turn it down at all)
-object self-shadow disabled (practically invisible difference from the air)
-bump map other vehicle or plane disabled (invisible difference)
-grass is disabled during flight (if its one and i dive to the deck, the frame rate drops down to 5-6 for 10 seconds, then rises back) /guessing its the time til its get loaded into the memory, is it possible to keep it there?
-object detail slider is at "Faster" (i dont see any difference at all, is there any?)
everything else is on, ground object range slider is at 4 miles, hi-res texture pack installed. My system is able to run the game with a steady 55-60FPS with everything enabled, maxed excluding the self-shadow texture size, what has to be set back to 4096. Again, the problem named by Fester only comes through after 15-20 minutes, and can be solved by an alt+tab in and out - still annoying cause sometimes it makes the game crash. It makes me guess that the GPU/CPU itself would be able to run this game almost maxed. Is there any way to solve this without drastically reducing the graphics detail (the most performance gain with the least loss in the visible effects)?
-
It sounds to me like you are not running into the same issue that Fester had but you are running out of memory when you see the frame rate drop and decide to alt-tab.
-
Look,
to be honest, my game isnt even maxed out.
-shadows were disabled (the HD5830 cant handle the 8192 shadows withouth an instant, large frame rate drop, also the 4096, what can be run smoothly, still look a bit "cube-ish" so i found it better to turn it down at all)
-object self-shadow disabled (practically invisible difference from the air)
-bump map other vehicle or plane disabled (invisible difference)
-grass is disabled during flight (if its one and i dive to the deck, the frame rate drops down to 5-6 for 10 seconds, then rises back) /guessing its the time til its get loaded into the memory, is it possible to keep it there?
-object detail slider is at "Faster" (i dont see any difference at all, is there any?)
everything else is on, ground object range slider is at 4 miles, hi-res texture pack installed. My system is able to run the game with a steady 55-60FPS with everything enabled, maxed excluding the self-shadow texture size, what has to be set back to 4096. Again, the problem named by Fester only comes through after 15-20 minutes, and can be solved by an alt+tab in and out - still annoying cause sometimes it makes the game crash. It makes me guess that the GPU/CPU itself would be able to run this game almost maxed. Is there any way to solve this without drastically reducing the graphics detail (the most performance gain with the least loss in the visible effects)?
That video card is an okay performer as long as you do not use any, or very little, anti-aliasing.
-
That video card is an okay performer as long as you do not use any, or very little, anti-aliasing.
Ding ding ding.......... anti-aliasing is the culprit, I would heavily wager on it. Or for those folks who are stuck ON anti-aliasing that would be "d-d-d-d-d-ing-d-d-d-d-i-d-i-ding................d-din.....................................................................g"
Debrody, I have the 210 card and have no problems with any stutters, unless I do one of these things, increase anti-aliasing above one notch (currently non), shadow textures above 512 (currently off), ground clutter in flight (currently off). Then I trick my filmviewer to playback in whatever setting that I choose. I have the best of both worlds, I can film high quality film and have smooth gameplay.
HTC deserves an award for not boosting the profits of graphics card manufacturers that squeak out minimal advances in technology. Having said that, an upgrade in graphics card usually doesn't hurt (if your system and power supply can handle the change). Just don't expect it to be the end all of every graphics problem.
-
I had a problem where I was running at 60 fps, but every 8 minutes I would get 15 seconds of stuttering and a frame rate of 20-25 fps. It was driving me batty. I tried shutting down every process I didn't need, etc. No help. Finally, I downloaded the latest Nvidia driver and the problem disappeared. Now, I may still have to do a reinstall to get the film viewer to not crash on start-up..
-
I am running into similar problems with my GTX 550ti 2048 ddr5. I just installed yesterday and ran in to the same problems you guys are speaking of. I havent changed any of the game's settings and what i dont understand is that my 4yr old 9600 GSO 756mb card ran everything fine without so much of a hiccup. Like i said none of the settings were changed so im not sure where the issue is. Any help would be appreciated.
-
I have been having problems lately its been working fine and them it starts stuttering like fester said but when i go to the cockpit view in game it works fine what is up :huh