Aces High Bulletin Board
General Forums => Axis vs Allies => Topic started by: Grits on August 26, 2004, 03:15:20 PM
-
Here is a post in the general forum about not getting hits and or not doing damage because of v-synch.
Had similar problem.
For me the problem was V-Sync!!!
Was getting good hits on cons but little or no damage.
As per Skuzzy turned V-Sync to always on rather then program preferences and now when I hit parts come off etc.
I agree the Zeke is a bit too tough, but maybe some of your problems are with v-synch? Are you still running with v-synch off or did you turn it on?
With v-synch off you can light a target up like a christmas tree and not actually get hits.
-
I turned V sync on but now the planes seem much more sluggish. Is that a possibility? I'm a computer imbecile. :D
-
You know I'm not really sure Storch. I dont know that much about it either, all I know is I've see both HT and Skuzzy say it should be on for AH or strange things happen with gunnery.
-
I turned it back on but havent really had a chance to test it.
-
Flew in the MA last night for a few sorties. I had several no damage hits just for someone else to finish off the kill. I did get credit but not untill it almost cost me my life. I dont see any difference as of now with sync on or off.
-
Originally posted by CurtissP-6EHawk
Flew in the MA last night for a few sorties. I had several no damage hits just for someone else to finish off the kill. I did get credit but not untill it almost cost me my life. I dont see any difference as of now with sync on or off.
because you fly 50cal dweeb planes. your hit power has been drasticly reduced.
-
Originally posted by B17Skull12
because you fly 50cal dweeb planes. your hit power has been drasticly reduced.
HIt power has only been reduced on armor.
-
Originally posted by B17Skull12
because you fly 50cal dweeb planes. your hit power has been drasticly reduced.
so now anything that is not cannon equipped is a dweeb plane, huh? I think you gots your planes crossed.......the cannon equipped planes are dweeb planes including the P38 and the F4U1C:D
especially if they head on you....no wait it isn't the plane it is the pilot that is the dweeb!:lol
-
hawk if you wanna do some more test do it on a plane that doesn't have amour at all like the A6M. Have you and a buddy go fly to a a6m to some place with grass and you do the same test to see how many hits it takes ot do damage.
i'd be willing to help you with this if needed. Me thinks it is the Amour. but i know how you feel, anytime i hit something with my 20mm it never seems to do damage anymore.
-
My first suggestion would be to double check your convergence.
and of course, having v-sync enabled. your monitor only puts out the max refresh rate it is capable of, which is why the "higher" fps with v-sync disabled is both misleading and can result in certain unseen frames where damage was done being "tossed out" and not sent to the server.
-
I have my frame rate set at 60 max. It normaly stays a steady 62. At the god-al-mighty fleets, it stays at 45. My convergence settings depend on what I am fighting and how they evade.
-
not the overall convergence (altho it can have an effect of "wtf, no dmg" if you hit outside of that optimal range) but rather the actual convergence of various guns on the platform ur using.
The p-51 is notorious for having it's 6-gun covergence revert back to default 300-350-400 (not mid-flight, no) due to the fact its .cfg file is read-only, so when you lougout then log in later, it's been changed and you may be unaware of this. ergo, you may be thinking ur pounding away, when only 2 guns are hitting hard and the other 4 just peppering - or missing.
I manually opened the .cfg file, unchecked read-only for the pony and set all guns to 400 yds then made it read-only again, so it never reverts back to the original default settings.
-
Originally posted by Shane
not the overall convergence (altho it can have an effect of "wtf, no dmg" if you hit outside of that optimal range) but rather the actual convergence of various guns on the platform ur using.
The p-51 is notorious for having it's 6-gun covergence revert back to default 300-350-400 (not mid-flight, no) due to the fact its .cfg file is read-only, so when you lougout then log in later, it's been changed and you may be unaware of this. ergo, you may be thinking ur pounding away, when only 2 guns are hitting hard and the other 4 just peppering - or missing.
I manually opened the .cfg file, unchecked read-only for the pony and set all guns to 400 yds then made it read-only again, so it never reverts back to the original default settings.
Hmmm, I will have to check on that!
-
Originally posted by Shane
The p-51 is notorious for having it's 6-gun covergence revert back to default 300-350-400 (not mid-flight, no) due to the fact its .cfg file is read-only, so when you lougout then log in later, it's been changed and you may be unaware of this. ergo, you may be thinking ur pounding away, when only 2 guns are hitting hard and the other 4 just peppering - or missing.
I manually opened the .cfg file, unchecked read-only for the pony and set all guns to 400 yds then made it read-only again, so it never reverts back to the original default settings.
Thanks Shane. Is this a known bug and is it applicable to all other planes as far as the .cfg files?
All the Best...
Jay
AWDoc1
-
it varies... some planes never seem to change, even if you made them different... i'd say there are a handful of planes this applies to, beats me if i can name them all... i recall the spit9 being one to change now and then... and probably one of the 109's iirc. there's almost no consistency or pattern behind it. never hurts to check ur 1st ride(s) in a plane(s) of the day after u log in.
easiest way to totally prevent this from happening is to go thru all the cfg files (planetype.cfg) and manually set your convergences - making sure to uncheck the read-only attribute before editing it. then setting your convergences (in feet) then saving and then re-checking the read-only. the only difficult thing can be determining which lin ein teh cfg file applies to which set of guns. I always have all guns on a plane set to converge the same distance so it's no big for me to have done that. some people, however, like to vary their convergence settings, i.e. many fweenies like to do that, apparently, and that would require more effort in editing the files.
then, you can still change convergence in game, but next time you open AH it'll default back to the saved .cfg file settings.
it's been a long time since i've been hit by that, so i'm unsure if in fact perhaps HT had fixed it whenever. which is why i was suggesting to check, just in case it's still present.
-
I have noticed that the 51D also refverts back to the default skin, but I never checked the convergence.
-
Originally posted by Shane
can result in certain unseen frames where damage was done being "tossed out" and not sent to the server.
This is a false statment.
And the convergance changing bug was fixed long ago.
HiTech
-
Originally posted by hitech
This is a false statment.
And the convergance changing bug was fixed long ago.
HiTech
re: vsync...
care to put this in layman's terms then?
quoting skuzzy from this thread (along with what siaf__csf said)
http://www.hitechcreations.com/forums/showthread.php?s=&threadid=99176 (my italics added)
Now it gets complicated. When vsync is enabled, you are assured that every frame rendered is displayed, as long as the video subsystem properly honors vsync. So what is a game doing when it cannot shove data to the video card during a frame draw?
Well, it depends on how many frame buffers a game allocates and if the frame buffers are full or not when the game wants to render a frame. It also depends on how the video subsystem (hardware/driver) decides it wants to handle it.
Sometimes a video card can stall the data delivery so a frame will not be missed, sometimes it might throw away a frame buffer to allow the game to continue. Really hard to know as it is dependent on the video subsystem.
Most of the time a video subsystem will make the best attempt to make sure the video frames are rendered so they do not miss any data, which keeps the video smooth and accurate.
Without vsync, a video subsystem has several options available. It can overwrite the video frame, which will typically cause 'tearing' in the video display due to mismatched frames being partially overlayed.
The video susbsystem may opt to finish a current frame buffer and overwrite previous buffers, which can cause some jerkiness in the motion of objects, but this method eliminates the 'tearing' effect.
A game could also send the same frame over and over again, if the update information is not available for the next frame. This last item can lead to some intersting visuals. For instance, in an online game, the object in your view needs a packet update from a server to be placed accurately in its environment. If you are running insane frame rates, your player/object could get updatred many times while game code simply extrapolates the remote object position. Suddenly a packet update arrives and the extrapolation may not have been accurate and the remote object jumps.
Your position, which the remote player has not gotten yet coupld also jump as while you are running insane frame rates and your object has been moving around, the remote player does not see it until he gets a packet update.
Now, both of you are out of sync, which can cause perception of lag, when in fact, it is a video synchronization problem and may not have a thing to do with lag. This can be more exaggerated with very high CPU speeds as well.
Keep in mind, I am not specifically talking about Aces High. Just the overall effect running without vsync can have on a multi-player game.
nopoop had this to say in http://www.hitechcreations.com/forums/showthread.php?s=&threadid=117118
Vsync on is important for another problem that comes with having it off. Rubber bullets. If your not sync'd that hit sprite might be a "tweener" and gets lost. If you lose it, your cons FE isn't notified. [/i]
seems to me what i said was more or less accurate in that what you're seeing on your monitor, with vsync disabled, isn't getting sent to the server, hence, rubber bullets. only thing i see i could be wrong was originally using the term "unseen" frames, even then you can only see the amount of frames your monitor refresh is at. and lag itself can play a role in the matter. vsync disabled can magnify it from what i understand.
care to clarify?