Aces High Bulletin Board
General Forums => Aces High General Discussion => Topic started by: SteveBailey on November 07, 2007, 11:51:29 AM
-
I was vulch busting last night and ran into Jamusta(he wasn't vulching he was trying to take town down) In the first shot you can see where I get the kill message but the f6f in the picture is Jamusta. I know this is just netlag but I thin it's kind of interesting. In the second shot he blows up as a result of multiple canopy sprites that hit his plane right before the first screenie. It wasn't much of a delay in real time but clearly there was a bit of time lapse.
(http://i35.photobucket.com/albums/d191/AZC4guy/jamusta1.jpg)
(http://i35.photobucket.com/albums/d191/AZC4guy/jamusta2.jpg)
-
Last night I saw a LOT of this. I hit a Tiger at 2.2k in a shootout where we both fired twice and it started rolling again before it blew up. I hit it and then it started moving and went a good 100 feet before it exploded.
I shot a 234 in the canopy from 400 yards and it pitched up into a loop but not hard enough to rip wings or anything. Half way around it exploded.
I shot a Lanc in the cockpit from above and behind. When I got to 800 in front of the Lanc it exploded.
-
I noticed this last night also. my 1 real "pop" kill was on a 38, killed the pilot on a deflection, and I watched him go past to my left then start to reverse before he blew up. he did start smoking on my FE right away, but the pop was a good 2-3 seconds later.
-
ive been getting alot of that.
-
Question: Can packets somehow arrive out of order?
-
Basically when a packet is sent the receiving end sends an ok as confirmation to send next.... if it is not received ok then it asks the sender to resend.
I think you just have slow bullets... :p
There are so many things that can affect your connection to the servers that it is actually amazing a game can be played online and be so enjoyable.
Things always have a way of evening out in the end..... have fun!
-
Yes and no bronk.
It is possible for packets to arrive out of order to your computer. But the software accounts for this and will always process them in the order they were sent.
There really is no order in what you are seeing. The piece of software that sends the kill message and the piece that sends the explode plane message are not the same thread/process. Hence they will occur at close to the same time but can very.
-
Somehow I think this may also be related, I was on the Knight cruiser in the 5 inch guns attacking 43 in late war (orange) arena last night. I was watching planes take off from out in front of the cruiser not from the carrier which was behind. When my squadie and I decided to up from carrier, he was floating 700 ft ahead over the water next to cruiser and I was on the carrier we both took off at the same time (him from his invisible carrier although it was visible to him). the same happened when we landed together, he landed on (to me) an invisble carrier 700 ft in front.
Now he also was seeing this only in reverse. He was seeing me lifting off from behind him. How weird was that?
-
Thanks hitech.
-
Originally posted by hitech
Yes and no bronk.
It is possible for packets to arrive out of order to your computer. But the software accounts for this and will always process them in the order they were sent.
There really is no order in what you are seeing. The piece of software that sends the kill message and the piece that sends the explode plane message are not the same thread/process. Hence they will occur at close to the same time but can very.
This makes sense.
As I said though, in real time the delay was nominal, I just found it interesting. It certainly didn't impact playability.
-
I had some serious lag some time back. More than once I shot a panzer, shot him again and got two kills on the same panzer.
-
Let us think about this a min.
Say both players have a ping time of 100 ms.
You shoot a guy it takes 100 ms to got to the server. Then another 100 to get to your opponent. So now we are up to 200 ms. Now his front end has to sen back the "ok ya killed me" thats another 200 ms.
So my next question is how far can an AC go at say 250 mph in 400 ms?
This is not factoring in software processing time
-
Nice skin choice Steve.
:D
Oh, and Nomak says Hi
-
More and more now I have to shoot.... pause for a second or two to see if they die, shoot again, pause, rinse repeat.
I can't count how many times recently I have shot a plane, saw ZERO damage, thought hmm... I know I hit 'em, lined up for a second shot and had 'em explode from the 1st shot's damage finally registering as I was pulling the trigger.
And this is on a 40ms ping w/ flat var.
Something is really "messed up" with ATT in Dallas. I have gone from a 13ms ping to 40 ish. Granted, that's still low, but why would my ping time triple? After a month ish it went to 20ms, then a month or 2 later 30ms, then here recently it's @ 40ms.
Steadily climbing up there.
-
all you did was watch the kill, get the kill message, rewind film and watch again. screws with the text buffer.
happened to me before.
-
There was definately some delay last night in a few kills that I had also. One of them I was 200 off of a pony feeding him some tators from a 109K and although I'm not a great shot I would have to say that at least 10 to 15 tators hit that pony before it went down. :rofl
A few minutes later I got a lucky shot on a pony from about 600 out with only 1 tator from the 109K and it was about a 2 second (maybe a bit less) delay and he blew up.
I also noticed alot of small warps last night. :(
However...It is quit obvious that Steve was cheating and I think he should be banned.:D
-
so thaaaat's what a kill message looks like :)
-
Every time I see Steve in his Pony..... I go in the corner and cry.....:noid
Gives me the hibbie-jibbies!! :D
-
its this f ing VOIP crap clogging us up...
-
its this VOIP crap clogging us up...
-
speaking of VOIP, each time I key, it freezes my screen for anywhere between 10 - 30 seconds. So I only type nowadays.
-
you have to use wax coated string on your "string and can " connection