Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: APEP on March 20, 2008, 07:27:29 AM
-
First great updates.
I have an issue now with my frame rate. It started as son as you changed hosts after the new update. My rate has alwas been between 53, and 67 frames. And is now between 5, and 10. Ive chked mu cable connection 400bps, nothing running in the back ground. Below is my ping, and trace to the I.P addresses you have listed in the forum. Help! Cant play when its this slow
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Michael>ping 206.16.60.39
Pinging 206.16.60.39 with 32 bytes of data:
Reply from 206.16.60.39: bytes=32 time=59ms TTL=234
Reply from 206.16.60.39: bytes=32 time=56ms TTL=234
Reply from 206.16.60.39: bytes=32 time=56ms TTL=234
Reply from 206.16.60.39: bytes=32 time=59ms TTL=234
Ping statistics for 206.16.60.39:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 59ms, Average = 57ms
C:\Documents and Settings\Michael>ping 206.16.60.41
Pinging 206.16.60.41 with 32 bytes of data:
Reply from 206.16.60.41: bytes=32 time=50ms TTL=233
Reply from 206.16.60.41: bytes=32 time=50ms TTL=233
Reply from 206.16.60.41: bytes=32 time=50ms TTL=233
Reply from 206.16.60.41: bytes=32 time=50ms TTL=233
Ping statistics for 206.16.60.41:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 50ms, Average = 50ms
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Michael>ping 206.16.60.39
Pinging 206.16.60.39 with 32 bytes of data:
Reply from 206.16.60.39: bytes=32 time=59ms TTL=234
Reply from 206.16.60.39: bytes=32 time=56ms TTL=234
Reply from 206.16.60.39: bytes=32 time=56ms TTL=234
Reply from 206.16.60.39: bytes=32 time=59ms TTL=234
Ping statistics for 206.16.60.39:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 59ms, Average = 57ms
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Michael>tracert 206.16.60.39
Tracing route to 206.16.60.39 over a maximum of 30 hops
1 6 ms 5 ms 5 ms 73.158.112.1
2 6 ms 5 ms 5 ms GE-2-38-ur01.nstonington.ct.hartford.comcast.net
[68.87.183.201]
3 7 ms 7 ms 7 ms te-9-1-ur01.norwich.ct.hartford.comcast.net [68.
86.231.166]
4 7 ms 7 ms 7 ms te-9-1-ur01.easthampton.ct.hartford.comcast.net
[68.86.231.161]
5 8 ms 7 ms 7 ms te-8-3-ur01.middletown.ct.hartford.comcast.net [
68.87.182.33]
6 9 ms 7 ms 7 ms te-9-3-ar01.berlin.ct.hartford.comcast.net [68.8
7.182.49]
7 12 ms 11 ms 11 ms 12.116.169.5
8 54 ms 59 ms 54 ms tbr2.n54ny.ip.att.net [12.123.0.38]
9 54 ms 53 ms 53 ms cr2.n54ny.ip.att.net [12.122.16.205]
10 54 ms 52 ms 51 ms cr2.wswdc.ip.att.net [12.122.3.38]
11 55 ms 56 ms 54 ms tbr1.wswdc.ip.att.net [12.122.16.62]
12 54 ms 54 ms 55 ms tbr1.sl9mo.ip.att.net [12.122.10.30]
13 54 ms 53 ms 54 ms tbr2.dlstx.ip.att.net [12.122.10.90]
14 52 ms 55 ms 54 ms br2.dlstx.ip.att.net [12.123.16.213]
15 54 ms 53 ms 53 ms mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255
.82]
16 209 ms 54 ms 54 ms mdf1-bi8k-1-eth-1-3.dal1.attens.net [63.241.192.
206]
17 53 ms 53 ms 54 ms 206.16.60.39
Trace complete.
C:\Documents and Settings\Michael>
-
I am having frame rate issues also, since the patch went in. Normal FR 45-70, now 5-30.
-
Dropped from locked at monitor refresh nearly all the time to ~27 when near any kind of smoke...other times too I think, I just noticed it might be the smoke on fields.
XP Home SP2
nVidia 6800 (unlocked pipelines)
Sound Blaster Audigy 2 ZS
4x512 MB DDR400
Full in-game sliders, 4x FSAA, Vert Sync on, HiRes pack downloaded/selected, all preloading enabled
SATA drive for the page file (remember, this setup has worked fine in the past. I say that because Skuzzy's stated that you can't fit the HiRes in RAM)
-
And what happens when you roll back to 512 texture sizes and disabled AA? Just asking, as I have not experienced any frame rate loss at all. Still pegged at 75FPS (monitor referesh).
-
My frame rate also dropped. Last dog-fight I died in it was at 7. So I cut my details to low, set the models to 256, and turned off every special thing possible and still only got up to 27. I was averaging a not so whopping 50 fps before, but that was flyable. This is a death in dog-fights, most of the time from hitting that tree as my plan flops through the air. Combine this with the fact that vehicle de-spawning re-boots my comp (even with the graphic details at ultra low) and I am currently stuck in bombers. I have an NVIDIA 256 1600X, and am connected with an N-class router. If anyone can figure this out it would be a big help.
Thank you,
LT Rouy (pronounced Roy)
-
Yes big FR hit here also, befor patch I got around 40 to 50 and now I'm lucky to get 30, even if I lower the in game vidio settings all the way down still sits at 30 and if I see smoke it dips to 15... If it gets any worse It will be unplayable.
I'm running at 512 and could even run high res and never had an issue befor, so what changed?
-
I to have had problems since the patch.It nows seems I'm being shown pictures of a plane in a dog fight . No more flow of video.Its to chopy to fight. Please help.
-
More game resources now. Performance remained the same on my computer. Have you tried disabling AA and AF and see what effect it has? Have you tried reducing the maximum texture size to see what effect it has?
I am asking you guys to try it and see what effect it has.
-
Im running an OLD pc on the game and this new patch has put me just about out of play.
I cant GV cause my FR drop to 2 and 3
and furballs are out of the question
I have all the settings as low as they can go
Is there anything i can do to help my FR any?
-
I do not know. Shoot me a DXDIAG output.
On machines that are marginal, make sure you have them running as cleanly as possible. Check the CPU usage in the Task Manager. It should be at zero most of the time.
-
Now that is funny.. my frame rates actually went UP by about 20% (Used to see 55-65FPS, now pegged at 75FPS almost all of the time)
-
Try going to the clipboard menu-options-graphics, and move the top two sliders all the way right. It helped me a bit. Don't worry about the gui slider.
-
Skuzz I just Emailed my DxDiag to you. Hope it helps.
B2B changing the in game settings does not help, I already tried that. Befor the patch I could run fine with them 2/3 of the way up but now weather I have them there or all the way down it doesn't matter I get the same FR hit.
-
I got the same kind of frame rate hit. Low teens and 20's near the ground when before it was 50-60 near the ground. I'm running an Intel 3.06 Nortwood CPU with HT turned on and 1G RAMBUS. When I minimised the game and looked at my performance for the cpu(s), the virtual 2nd cpu was pegged 85-100%. This new patch was requiring much more cpu time. Processes in Task Manager showed the AH executable using 50% cpu time which is the same as before the new patch.
I have a Radeon x1650 Pro 512 vid card. I turned all of the 3D texture processes to the far end of performance rather than quality. AA is off. Vsync is on. AF and Smooth Vision are app preference. Before this patch I could crank everything up to quality with Vsync on and get 60-120 FPS in the game.
I was looking through my XP Pro services and found I had the (SSDP Discovery service) enabled. When I disabled it two things resulted. 1. My IE would launch 5x faster. 2. My game frame rates went up. Not as good as befor this version release, but not nearly unplayable when in a furball in the bushs. That effect of seeing other planes as a jerking slide show rather than a video.
Some of my squad mates with older systems than mine are finding this patch to be almost unplayable.
Skuzzy is it time for a general question to the troops about this subject to poll for performance responses?
-
As far as performance goes, I would expect a drop for some. I have seen what some players have thier settings at and I am not surprised there is some suffering performance degradation. The more we add and make look better in the game, the higher the load. It's just logical.
If you suffer frame rate issues, then crank down the setting you think you can live with until the performance is where you think it needs to be in order for you to have fun.
The single biggest issue I run into is CPU usage and that is where I typically start when I start thinking about how I can improve the performance of the game.
-
Just wondering what all changed that would have this big of a hit? There is nothing I can see that was added to the game that would hit this hard. The biggest thing that bugs me is that no matter where I move the in game sliders betweeen 2/3 to the left and all the way to the right with no FR change, it just sits at 28 to 30. in tower and down into teens in combat.
I have tried changing to the lowest texture size with no difference between it and 512. You would think that if I turned the sliders down and changed to the low texture size I would see some increase in FR but there isn't.
I'm running a 2ghz comp 512 ram and a 256 meg vid card and run it as clean as I can when playing AH. While it's not the most high end computer anymore it's not a total dinosaur yet. I could add more ram but I somehow doubt that would fix the current issue. Skuzz I'm thinking like you seem to be that it may be CPU related but being that I'm running double the CPU of the minimum requierments it would seem to me that something in this patch is eating the hell out of CPU power on some comps. Just a guess mind you. :)
-
just a suggestion for yall to try before moving your sliders..
google FS AutoStart. download it. i have a few of my squadies on this that where having FR issues and this has helped them ALOT. most of the time people have to many processes running in the back ground. do what Skuzzy said and ALT+CTRL+DELETE and it will pop up a window showing what programs are running click the tap at the top marked Processes and on the bottom of that window it will show the total. FS AutoStart helps you shut down the Processes that are not needed SAFELY. hope this helps yall out.
BTW Skuzzy the new computer is a blast. thanks for the advise on the PhysicX card.
-
I'm running a 2ghz comp 512 ram and a 256 meg vid
I'm hoping thats a typo! 512 ram :O That not enough to run windows reliably ! I would think thats your problem. That would make a big bottle neck.
-
512 ram has run all aps I have reliably for well, as long as I've had this comp (just after AH1 was changed to AH2) and AH has run perfectly up to this patch. I can and will test 1G ram in a min (wife has an extra 512 I can grab for test) but I'll bet it doesn't do any good..
EDIT: Just added another 512 ram and tested with the same results I have at 512 ram, so ram is not the issue. I have in game screen shots with the the ram info up if that would help..
I uped a wirble and had a fr of 24 looking out over the terrain and when I fired it droped to 12, then 4.. Looking directly up at the sky its better but not all atacking planes fly right over head so thats no good.
So now that I have tried with 512 ram and 1G ram and had the same results I'm again thinking that AH has suddenly hit my CPU hard or my particular vid card.
So far I have.
Dropped sliders all the way down in game and had little change.
Updated vid drivers with little change.
Droped texture resolution down to min and had no change from 512.
Added another 512 ram for a total of 1G and had no change.
Skuzz if there is anything you would like me to do just ask and it will be done OH great master of technical issues! I will do all that I can. :)
EDIT again: Has the way sound is played changed at all? Just a thought in case it is somehow using more resourses then it did befor.. Again just a thought.
Oh and if you would like I'll call you if you have some things you would like me to try. Monday ok or if your willing to work over the weekend I can call then also:P .... Now stop thinking dirty. :D
-
The game can run in 512MB of RAM, but that is if the computer is a really lean machine.
Everytime we ad more things to the game, the game will require more resources. Computers that ran fine , but happen to be on the edge of the fence can be pushed over.
Try removeing the 'cache' folders and 'skins' folders, the disable skins and allow the cache to regenerate. Disable any anti-aliasing next.
-
I was going to report the same thing. The first night with the update my FPS dropped from it's normal 15-25 to 5-15. Now I realize I have what's likely the oldest machine running the game and I was flying around large hoar... furballs ;) so I didn't bother reporting it. Last night I upped on the big island map and had the same issues, but when I switched arenas to one of the newer smaller maps all was well again. In the end it won't matter to me as I'm building a new machine today but if I were'nt I'd be concerned. Gotta go... time to start building.
-
google FS AutoStart. download it. i have a few of my squadies on this that where having FR issues and this has helped them ALOT. most of the time people have to many processes running in the back ground. do what Skuzzy said and ALT+CTRL+DELETE and it will pop up a window showing what programs are running click the tap at the top marked Processes and on the bottom of that window it will show the total. FS AutoStart helps you shut down the Processes that are not needed SAFELY. hope this helps yall out.
Been using that for years. It doesn't have much to stop, though. :D
-
Flayed1, running 1024 textures and 512 textures is the same exact thing, unless you have the hi-res pack downloaded (separate download.. I wouldn't recommend it for you based on your performance report, and only 512mb of RAM).
Don't let them fool you, Windows can run plenty reliably at 512mb... just not as fast is all.
Assuming the computer is lean, and you're virus/malware free, and the computer is running at 100%, then you can try two things:
Try dropping your resolution a notch (if you're at 1280X1024, try 1024X768.. if you're at 1024X768, try 800X600).
Try dropping down to 256 textures. This is likely going to make the biggest difference of the two.
Also go to your video card settings and make sure all of the fancy stuff is turned off (set it to 'performance' settings).
-
My frame rate totally sucks since this new download. I have 1gb ram and a new nividia video card, run fs autostart, and shut off my anitvirus software prior to running game. Any suggestions???? :confused:
-
Flayed1, running 1024 textures and 512 textures is the same exact thing, unless you have the hi-res pack downloaded (separate download.. I wouldn't recommend it for you based on your performance report, and only 512mb of RAM).
Don't let them fool you, Windows can run plenty reliably at 512mb... just not as fast is all.
Assuming the computer is lean, and you're virus/malware free, and the computer is running at 100%, then you can try two things:
Try dropping your resolution a notch (if you're at 1280X1024, try 1024X768.. if you're at 1024X768, try 800X600).
Try dropping down to 256 textures. This is likely going to make the biggest difference of the two.
Also go to your video card settings and make sure all of the fancy stuff is turned off (set it to 'performance' settings).
Read my other poasts.. I have tried turning down the textures to the minimum and get no change from 512... EDIT: On the resolution I havn't tried changing that due to the fact I just bought this 22" wide screen monitor and other resolutions on AH stretch funny on it not to mention whats the use of having a wide screen if ya can't use it being that AH was one of the big reasons I got it and looks so nice on it lol. (will see what I can do though) Have added another 512 or ram for a total of 1 gig and have no change.. I shut down all processes so I am only running 25 when I play AH.. No antivirus or mailware enabled, vidio card is set for preformance with all extras turned off. As stated erlier 2Ghz comp while not real fast by todays standard, I don't feel is real slow. The only thing I use it for is to play AH, EVE Online and other offline games with a lil web surfing on the side usually to the AH forum. So I try to run it as clean as possible.
Skuzz I removed the cache and skins folders with the same result.. And are you saying that a 2Ghz cpu with now 1Gig ram and a 256 meg vid card and trying to run as clean (not being a real computer geak it could probabbly be cleaner) as I can is now a marginal computer for AH? Not bashing mind you just asking. ;) I can still play but if there are any more of these updates it will put this system out of service for AH
As I said befor the thing bugging me the most is that I can set the resolution and in game sliders all the way down and see very little difference in preformance from 2/3 of the way up, where befor if I turned the sliders down all the way frame rates would jump up a great deal....
Hmm another thing I can try... My wifes comp is very similar to mine (I built them) but running a lil different 256 meg vid card. I'll copy AH over to it and see if I get a different result, might help show if its my vid card thats taking the hit. Will keep you updated. :)
-
Problem might be in the fact I am running a 22" wide screen monitor that needs to have an extreamly high resolution to make the game look in proportion. I turned the resolution down and got a big jump in FR and the sliders are now giving me the old FR bump I used to get if I turned them down but now everything looks squashed and stretched on my screen...
So problem might be vid card/monitor issues.
Skuzz if ya don't mind me asking what size monitor and resolution are you running? I am almost certain that this is my issue now but it still sucks that AH looks crappy on this monitor in any other resolution but the biggest. :) Also if this is the issue I can get used to the stretched look but I'll ask if there is a way to tell the wide screen to act like a standard square monitor so that the other resolutions don't stretch across it and look strange?
-
Any time you run a large LCD monitor you almost have to run it in it's native resolution to make it look good. Native resolution for most 22" widescreen monitors is 1600 x 1024 (IIRC). Thay means you have to render over 1.6 million pixels per frame, vs just over 786,000 pixels per frame at 1024 x 768 resolution on a regular aspect monitor (over 2x as many). Obviously, it takes a lot more machine to do this, or it takes a lower frame rate.
To give you the extremes, I just updated today from:
PIII 600 MHz
512K PC 100/133 SDRAM
64 MHz GeForce MX-440
Win98
Soundblaster Live Value
19" CRT @ 1024x768
Clean configuration running 512 textures and graphic details minimized @ 15-25 FPS under most circumstanses.
To:
Core2Duo 2.66 GHz
2G DDR2 800 DDRAM
512M NVIDEA 8800 GTS
WinXP Pro
Soundblaster X-Fi Gamer Fatality
22" 2ms/3000 contrast LCD @ 1600x1024
Background updaters were running as I tested the game. Running 512 textures @ 1024 settings and graphic details maxed @ 59 FPS solid (refresh rate set @ 60 and anti-aliasing maxed).
The FPS drop, in my opinion, is due to the additional rendering (trees, etc. that you never saw before). The best ways to reduce the impact (in order) is to reduce your resolution (not recommended for LCD monitors), reduce your texture size or reduce your graphics detail settings (object detail first then ground detail). These setting tweaks kept me in the game for years with a sub-standard system (but I wasn't trying to push 1.6MM pixels per frame).
-
Yeah I did find a resolution that isn't to horible, a little stretched but not extreamly horible and get 50 to 60 FR now down to 40 in real hevy smoke, with in game sliders back at my usuall 2/3 to the left. Now when I slide the sliders all the way to the right I start banging out 70 to 80 FR not that I'll be playing on low detail, just nice to see the sliders working again :)
-
my main issue is Bullet hit sprites...
... as soon as i hit someone the screen pauses for a few micro seconds. Makes my sucky aim even worse because its constantly pausing.
still does it offline.
i upgraded Monitor a few days after patch and had to reduce some settings but it hasnt removed the stutter on bullet hits.
1280x1024x32 @75hz 75fps fixed
512 textures
FSAAx4
AFx8
Detail Slider max, range a few clicks off max
1680x1050x32 @ 65hz 65fps fixed
512 textures
FSAAx2
AFx8
Detail slider a few clicks from max, range alittle less than before also.
I tweak settings so it stays near max fps (hz rate) as much as possible, but the stutter on hits is still pausing the game.
AMD 4400x2
7800GTX
1gig ram (single channel, 1 memory stick failed from 2gig setup :()
150gig Raptor for windows and game installs
-
I may have jumped the gun on thinking I have solved my issues by lowering the resolution...
While I get a better FR it is wildy unstable and nothing in particular seems to be screwing with it, just bobs up and down like a mad man.
Last night I took an F4U up and flew over to bomb some GV's at a Vbase and all was fine on the flight over. FR at 40 on CV and into the 60's in flight. FR stay around the 45 to 50 range when I entered the combat area and through the dive in from 10 K down right up to where I droped my bombs and the Wirble started firing at me and BOOM FR of 10.. I was cussing a bit but figured maybe the (seeing more tree's) issue was still the problem because I was diving in and of course you get closer to ground, see more tree detail.
Then I jump into a tiger for base defence at an airfield. Roll out of the VH and get between the base and town with only a few burned out buildings and several enemy and friendly cons up and my FR stayed at a constant 15 to 16 with no trees and few other objects in view.. Most of the cons were 110G and spit's. Nothing has changed with graphics for modles in general has it? This instance just seemed odd to have such terrible FR with almost nothing in view other than a good grouping of planes.
The rest of the night was just constant FR going from 25 to 40 to 30 to 60 to 15.... well ya get the idea. A lower fr wouldn't bug me as much as long as it was stable but this jumping all over hell is really messing with game play.. It's not possible that the graphics fix did't fix things to good and I'm loading stuff up off in the distance that I shouldn't/can't see.. In other words dumping stuff onto my CPU load at cirtain points that is not needed to load at those points. Like when I was looking over at town in my tiger, could my comp have been loading a bunch of trees beyond the hills and burned out buildings in my field of view that I had no way of seeing? Thus slamming my comp with a bunch of work that it didn't need to be doing?
Sorry if I'm wasting time here, I'm no programmer but I keep having this feeling that something is just off with this patch, gut feeling type of thing. If I'm having FR hits like this I don't see how anyone running the minimum system requierments posted on the home page can even play at all.
Just throwing out thoughts here.. I will continue to tinker and see if I can solv it on this end :)
-
What is the in-game Variance line doing?
-
What is the in-game Variance line doing?
mine used to be a solid line but now its a alittle bit bumpy (im talking like 1 or 2 pixels dif from a flat line, not massive jumps). this is in a bomber at 20k with nothing going on around me.
ill take some pics in stable flight and when hitting objects.
-
I am sorry. I was not clear. When the stutters happen, what is the Variance line doing?
-
I am sorry. I was not clear. When the stutters happen, what is the Variance line doing?
yeah ill post pics when i get the chance... busy at mo so flying bombers while afk (come hunt me down lol)
-
Just a small thing I noticed: The hit-sprite-freeze only happens with smaller guns: Wirbelwind, Ostwind, most aircraft cannons.
But for example NOT with B-25H's 75mm. I can shoot it without freeze, only if I use it's .50cals it happens.
-
Just a small thing I noticed: The hit-sprite-freeze only happens with smaller guns: Wirbelwind, Ostwind, most aircraft cannons.
But for example NOT with B-25H's 75mm. I can shoot it without freeze, only if I use it's .50cals it happens.
ive noticed it with 50s, 20mms, 30mms. Aint tested 303s/7mm.
Tanks and B25H 75mm are fine.
once the sprites are in the cache it seems ok, its almost as if they aint getting preloaded like everything else is
-
my main issue is Bullet hit sprites...
... as soon as i hit someone the screen pauses for a few micro seconds. Makes my sucky aim even worse because its constantly pausing.
still does it offline.
i upgraded Monitor a few days after patch and had to reduce some settings but it hasnt removed the stutter on bullet hits.
im getting the same thing i think the bug is not from the sprites ,but the actual muzzle flash graphic loading
-
Skuzzy's suggestions have been pretty helpful for me so far. Like he has said, there are areas where performance is gonna suffer (paraphrased). I saw some improvement in performance when I updated video driver. Note, after updating either the drivers or the patches for the game itself, there was much trial and error (and mostly error).
This is what has worked for my POS:
Turned Antialiasing and Anistrophic Filtering off or very low (offset stairstep by trying the highest resolution with desired performance possible - trial and error) Result framerate boost back to normal except when @ 400 away from contact (frustrating stutters).
Next, Turned off custom skins, weapons effects, and vehicles effects (do this by checking the appropriate disable boxes under Graphics Detail from clipboard). Also, turned both detail sliders to performance unless bombing where long range visability of target is needed. Result was good framerate and stutters disappear.
This is where Skuzzy and I don't totally agree. When detail sliders are higher, as needed in bombing, "Rubber Bullets" appear or should I say disappear. I believe Skuzzy explains this as packet loss. It is best to keep all sliders to the right unless you aim is good enough to hit something farther than .5 miles away.
I forgot to mention, that I turn all the background processes off using FSAutoStart before running AH2.
-
im getting the same thing i think the bug is not from the sprites ,but the actual muzzle flash graphic loading
Not here, because I only get the freze when I hit. I can shoot for minutes, but if my rounds actually reach the target: FREEZE!
-
Not here, because I only get the freze when I hit. I can shoot for minutes, but if my rounds actually reach the target: FREEZE!
yup... defo not muzzle flashes... its only hits.
i suppose it isnt much of a problem as i dont hit much so it doesnt happen that often. :p :lol
-
Itrs gotten to the point of where its not even enjoyable anymore in certain situations. I have everything dealing with the graphics card down and now running in 128, to the point my first PONG game in 1975 looked better. I even am trying the "Omega" drivers instead of the regular ATI drivers for my Radeon 9200.
I am running the replacement to FS Autostart and that only picked up 4-5fps at best. Smoke/fire kills me and I have the ground distance so far down I cant see anything anyway. The machine is very clean.
Its not my ISP as my wifes machine (she plays to) stays at 50-60fps but, she is a Vista versus my XP.
Maybe its something with DirectX 10 since the Vista uses this?
-
Something else to check for in the cpu bottlenecking department is unneseccary extra processes installed by your video card install, sound card install and other hardware/software device installs.
My ATI video card setup installed 3 unnecessary processes that I removed after researching them on the internet. My sound card installed a service to run a CDRom and media player installed a service that is nonessential. After removing these my FPS improved by alot in the game.
If you are runing XP pro, not all of the network detection services installed in service manager are needed to play AH on the internet. SSDP Discovery Service comes to mind.
If you are having frame rate hits after the newest version of AH has been installed try the following to gain back cpu cycles.
1. Go into your video card 3D setup and change any sliders from quality to performance. Do this a littel at a time to see if your FPS improve.
2. Open task manager and identify any processes that are nonessential to playing the game or running your computer and remove them or disable them during game play.
3. Go into service manager and look for unnecessary services and disable them(at least during game play).
This new version of the game seems to require more cpu processing cycles. In the previous version players with older systems got away with not cleaning up the processes and services running during game play while not doing any tuneing to their vid card. I know I did and thats what caused the performance hit on my FPS.
I'm running at 512 for textures and the amount of memory being used for textures when I hit <ctrl-I> in the game went from 54 up to 101 in this version of AH. Thats a give away that more is being required of your cpu to run the game.
-
First great updates.
I have an issue now with my frame rate. It started as son as you changed hosts after the new update. My rate has alwas been between 53, and 67 frames. And is now between 5, and 10. Ive chked mu cable connection 400bps, nothing running in the back ground. Below is my ping, and trace to the I.P addresses you have listed in the forum. Help! Cant play when its this slow
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Michael>ping 206.16.60.39
Pinging 206.16.60.39 with 32 bytes of data:
Reply from 206.16.60.39: bytes=32 time=59ms TTL=234
Reply from 206.16.60.39: bytes=32 time=56ms TTL=234
Reply from 206.16.60.39: bytes=32 time=56ms TTL=234
Reply from 206.16.60.39: bytes=32 time=59ms TTL=234
Ping statistics for 206.16.60.39:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 59ms, Average = 57ms
C:\Documents and Settings\Michael>ping 206.16.60.41
Pinging 206.16.60.41 with 32 bytes of data:
Reply from 206.16.60.41: bytes=32 time=50ms TTL=233
Reply from 206.16.60.41: bytes=32 time=50ms TTL=233
Reply from 206.16.60.41: bytes=32 time=50ms TTL=233
Reply from 206.16.60.41: bytes=32 time=50ms TTL=233
Ping statistics for 206.16.60.41:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 50ms, Average = 50ms
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Michael>ping 206.16.60.39
Pinging 206.16.60.39 with 32 bytes of data:
Reply from 206.16.60.39: bytes=32 time=59ms TTL=234
Reply from 206.16.60.39: bytes=32 time=56ms TTL=234
Reply from 206.16.60.39: bytes=32 time=56ms TTL=234
Reply from 206.16.60.39: bytes=32 time=59ms TTL=234
Ping statistics for 206.16.60.39:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 59ms, Average = 57ms
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Michael>tracert 206.16.60.39
Tracing route to 206.16.60.39 over a maximum of 30 hops
1 6 ms 5 ms 5 ms 73.158.112.1
2 6 ms 5 ms 5 ms GE-2-38-ur01.nstonington.ct.hartford.comcast.net
[68.87.183.201]
3 7 ms 7 ms 7 ms te-9-1-ur01.norwich.ct.hartford.comcast.net [68.
86.231.166]
4 7 ms 7 ms 7 ms te-9-1-ur01.easthampton.ct.hartford.comcast.net
[68.86.231.161]
5 8 ms 7 ms 7 ms te-8-3-ur01.middletown.ct.hartford.comcast.net [
68.87.182.33]
6 9 ms 7 ms 7 ms te-9-3-ar01.berlin.ct.hartford.comcast.net [68.8
7.182.49]
7 12 ms 11 ms 11 ms 12.116.169.5
8 54 ms 59 ms 54 ms tbr2.n54ny.ip.att.net [12.123.0.38]
9 54 ms 53 ms 53 ms cr2.n54ny.ip.att.net [12.122.16.205]
10 54 ms 52 ms 51 ms cr2.wswdc.ip.att.net [12.122.3.38]
11 55 ms 56 ms 54 ms tbr1.wswdc.ip.att.net [12.122.16.62]
12 54 ms 54 ms 55 ms tbr1.sl9mo.ip.att.net [12.122.10.30]
13 54 ms 53 ms 54 ms tbr2.dlstx.ip.att.net [12.122.10.90]
14 52 ms 55 ms 54 ms br2.dlstx.ip.att.net [12.123.16.213]
15 54 ms 53 ms 53 ms mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255
.82]
16 209 ms 54 ms 54 ms mdf1-bi8k-1-eth-1-3.dal1.attens.net [63.241.192.
206]
17 53 ms 53 ms 54 ms 206.16.60.39
Trace complete.
C:\Documents and Settings\Michael>
-
And what happens when you roll back to 512 texture sizes and disabled AA? Just asking, as I have not experienced any frame rate loss at all. Still pegged at 75FPS (monitor referesh).
Me too! 75fps pegged.
-
this is pretty strange,about 3 weeks ago i all of a sudden started getting a good FR as well,i used to never even be able to get 20,now im getting hi 30s to 60s