Author Topic: TOD is awesome.... (Read 1097 times)

Sancho · « **Reply #15 on:** July 13, 2002, 04:03:22 PM »

I'm convinced the problem is the SEA connection itself. The mass takeoffs don't help, but several minutes after everyone had taken off from the CVs, I was still seeing this:

--- beta.hitechcreations.com ping statistics ---
50 packets transmitted, 49 packets received, 2% packet loss
round-trip min/avg/max/std-dev = 130.156/713.067/2889.394/695.884 ms

As a result, the 56th FG went and flew in the MA, where despite having almost 3 times the players, I still managed a steady 35ms ping. Maybe HTC should host the SEA on the same server as the MA.

keeler · « **Reply #16 on:** July 14, 2002, 10:31:12 AM »

I think That it is Bandwith causing all the problems

Why dont we shut down Da or CA and pump that extra bandwith to Sea ?? If it is possibl

I agree that something needs to be done soon all that prep for lag ... How is this gonna play out in BOB ??

plumbob · « **Reply #17 on:** July 14, 2002, 03:53:46 PM »

Poorly, BOB will most likly be bigger than your average weekly TOD

jordi · « **Reply #18 on:** July 14, 2002, 04:06:32 PM »

Well they have a MONTH to find and fix the problems !

Vulcan · « **Reply #19 on:** July 14, 2002, 07:46:30 PM »

I tend to side with Ghostdancer in thinking that the problem is the new netcode.

HTC have said they've changed the netcode in several ways to favour things like nearby enemies. I've seen the SEA full before and I doubt they've actually dialled back the bandwidth, yet nothing like this has ever happened before.

My ping times tripled or quadrupled during the problems. When I went and checked the SEA later in the event (40 ppl left) ping times were back to normal.

Heres my 'guess':

The beginning of each ToD has always been riddled with warps, as squads launch, the text channels fill, and the voice channels fill too. After a few minutes this calms down and the ToD goes on normally. Because its the beginning of the frame and no one has engaged yet the warps only screw up formations initially.

So we all roll... whammo, 200 plays suddenly get 'warpy'.

Next, the new netcode steps up, sees the 'warps' and decides everyone is lagging. It decides to switch all 200 players over to TCP mode from UDP mode.

200 players switching from TCP to UDP mode screws over the server something chronic. Some of us log, and eventually relog in. Those that stayed end up with TCP connections that are ok, but slightly laggy/warpy.

It was interesting to note that voice comms stayed ok during the whole fiasco, albeit a little choppy. Which would tend to indicate the bandwidth was ok.

Aub · « **Reply #20 on:** July 15, 2002, 12:37:46 AM »

Quote

Originally posted by Sikboy
*These statements have not be verified by the FDA

Mr. SikBoy, this is the FBI... are you there?

TracerX · « **Reply #21 on:** July 15, 2002, 02:34:57 PM »

Ghostdancer, I like your ideas for dealing with the lag in the SEA. Our squad was new to the TOD (sorry for any etiquette/protocol violations) and thought that the lag might be normal. The biggest mystery was knowing when to launch even though we knew to launch at T+2 min. At about +9 min, we still had not seen any other AK's launch (I believe they were to launch before us) so we launched anyway. We were a small group and cleared the area quickly, but it would be nice to have a verbal launch command to eliminate the confusion. Also, separate Launch CV's would be a great idea.

viking73 · « **Reply #22 on:** July 15, 2002, 07:14:12 PM »

Biggest problem I saw was everyone trying to launch at the same time. We learned from that long ago and set the mission planner so that there are 3-4 separate flights a min or 2 apart. Just a suggestion for next time. Otherwise we all enjoyed the TOD. The TBM's made it all the way to the cv's and dropped but I think we had a bad angle and not all of our torps made it in. We did however have the opportunity to take out several zekes. I was surprised at how well the TBM's could mix it up with them.