Aces High Bulletin Board
General Forums => Aces High General Discussion => Topic started by: devious on July 01, 2003, 07:00:43 PM
-
Lag is normally no problem for me. But when there`s about 300+ people on I experience this strange phenomenon:
Any plane, press trigger when flying alone - immediately lead starts flying.
When I`m near someone, pull trigger - - screen freezes half second - pop pop some rounds come out - screen freezes half second - firing really starts.
This is quite annoying, and I just lost a 262 to it.
This makes it impossible to fight properly, and I have to log or smash something around the room. I narrowly evaded tossing the monitor out the window.
Turn into nme 262, pull trigger, LAAAAG, next pic in slideshow, lead flies - where is he ? BOOM.
I have tried everything, reducing sound accelleration, reducing graphics detail and resolution, no dice.
It doesn`t depend on my grahics card I think - I can normally fire, even in a massive furball, unless there are about 300 guys on.
System: Athlon 1.4 GHz, GF4200 128 MB DDR, 512 MB DDR RAM system, onboard sb, IBM DDRS SCSI HD, Board Epox K7A
Connection is single line ISDN (about 7kbit)
I`m running Win ME or WINE under Debian 3.0 for AH, makes no difference. Of course, nothing is running in the background.
Any hints save not flying during american prime time ?
-
I had that happen with my SB live when i turned the accellelration on it all the way off.
Might be some kind of sound card issue...
-
try turning your tracers off, I've had that happen on occasion when I had tracers turned on.
-
Originally posted by Innominate
I had that happen with my SB live when i turned the accellelration on it all the way off.
Might be some kind of sound card issue...
I noticed the same thing a while back when I turned the down the acceleration on my audigy. Didn't help with vox problem so I turned it back up. Sometimes I go for several hours without losing vox, others, mulitple times in an hour.
-
Ditch 'Multiple Errors'
Its got to be the WORST OS I've ever used. (95, 98SE, ME, 2000, XP Pro)
-
ME isn't an OS. It's a graphical front end for the program loader known as msdos.
-
Don't you mean a GUI?
-
It's a sound issue alright. Try fiddling with the sound accel settings as suggested by others.
The interesting thing is, this same phenomenon happens in IL2:FB also.
-
Yet in FB its not solvable at least for me with a gf4, sblive! on a via board...
SKurj
-
Fiddling with sound accelleration did nothing - even though dxdiag suggests the onboard sound doesn`t have hardware buffering (so i reckoned "stop DX from trying to use it").
Amazingly, turning tracers off did it. I don`t understand it, the graphics card is FAR from slideshow quality in any situation :confused: and it runs Navy Seals Quake 3 just fine with all the mist/particle FX...
CCVI, as for Win ME: Like all other Windozes, it`s ****. Ever programmed Visual Basic w/ handmade VC++ ATL DLLs ? Sickening !
But AH sadly doesn`t run under a real OS ;)
Thanks for the hints guys , hoping the no-tracers-improves-gunnery thing kicks in soon ;)
-
At different times I've noticed this... not always. But, I've always had a suspicion it had to do with sound or tracers or a combination of both.
Same thing used to happen in AW. The infrequency of the glitch has never caused me to investigate though.
-
Originally posted by devious
Thanks for the hints guys , hoping the no-tracers-improves-gunnery thing kicks in soon ;)
I usta fly with no tracers, for many months. Pretty much flew only planes with 50 cals and had no trouble hitting tgt. Then I started flying La7 and 109's. Couldn't hit the tgt even when it was flying straight and level at only d300, tracers back on, hitting resumed.
Stick with one plane 'till ya get the feel for the guns and be prepared to miss alot when you switch planes.
-
ya...got used to p51 and jumped into n1k just for kicks.....couldn't hit a damn thing WITH tracers:rolleyes: