Use FSX server IP 188.77.206.24 now

[ROBERT DUNN 2]

Please move your multiplayer flight operations to FSX host server IP 188.77.206.24 at your convenience. This FSX host server, Ryback's Flybox (aka Hot Dog Air Service) will serve as our main FSX host for one week, ending on 4 March. This FSX host TeamViewer ID starts with 261 xxx xxx. Thank you.

[Storm]

Thank you Bob. An observation (or a speculation), having taken part in the first group flight on the server where most if not all participants were US based...

I seem to be getting a fair amount of lag in the server, as are some others. Rather more lagging, dolphining and bouncing aircraft that usual observed!

Several people were unexpectedly kicked too for exceeding packet limits, although this may have been bona fide as I don't know the planes involved. However it may be a symptom of packet rollover that I have previously observed on flaky or laggy net connections to any fsopen-controlled server.

Moreover the TeamViewer interface is so laggy as to be almost (but not quite) unusable. I logged on to verify that the kick limit was indeed 1000.

However, I don't think it's the server so much as our trans-Atlantic connection to it. Checking out the link to the server with a simple tracert, I see there is a lot of delay in the cogentco.com network - which I guess is being used for the trans-Atlantic and EU hops - especially the last steps toward Spain.

No conclusions as yet. Just a heads-up about something to watch.

[ROBERT DUNN 2]

Copy Storm. I'll take remedial action, probably by way of again offering up BigBox as an FSX host group flight backup. The TeamViewer issue is noted and personally experienced by me. Be advised (did I just say that?) that any staff has the right and the duty to take down the rarely used BigBox from P3Dv2 configuration and bring BigBox back up either as an alternate (my FSOpen account ROBERT DUNN 2) or as the primary community FSX host (msFlights FSOpen paid account) as an immediate situation may call for. If I'm not immediately contactable, just do what makes sense server-wise.

[CaseyRyback53]

sorry, i wonder that i read this, because Faultheo and Krugar was with me in the Lobby Germany and they joint the groupflight and they was always telling me, how good the server runs. later i went into the groupflight room and ask, and nobody was complaining. later on Hawk came online and i ask him to check the TV conection and he said it was good, so on what server Storm was? so what is the problem?

[WarHawK]

Do we not have any North American Servers to host our session from?

[CaseyRyback53]

yeah right, Mister "I give you my Additude".. that's what i'm waiting for..

[Storm]

It's just a single observation based on one group flight with everyone using 188.77.206.24. The additional lag did make a noticeable difference to this one flight, particularly when observing other aircraft, and especially during landings. It may be tolerable for most people, and even unnoticed by some, but I was just comparing it to the many other group flights I have attended.

HOWEVER... It's too early to say whether it's a generalized case or just Atlantic traffic that was heavy that one time. I would need many more observations to comment more fully.

On the other hand, Bob's TeamViewer experience seems to match mine and that was a more serious problem. There was a very slow initial response time of many seconds to log on - which itself is OK if you're expecting it. However, there was also always several seconds delay when doing an action (like dragging a window) to seeing it actually happen on screen. Rather like multiple satellite hops both ways - and maybe that was indeed the problem. A TeamViewer user therefore has to be very patient and do a single simple action at a time and wait for confirmation that it has happened before doing the next. Also they have to be much more careful since laggy remote operation is far more error prone. By contrast, previous TeamViewer experience on US servers has given me more or less instant response.

[CaseyRyback53]

Well Storm, i will agree some of you complainings, because i had a cloud prog running and forgot to switch it of. now is nothing else running, just FSopen and FSX, so if u don't mind to try the Teamviewer again, please.....it's the first day, give it a chance..

[Mulderpilot13]

I will add, Mulder server will continue to be online not running FSX or FSOpen if we see any problems. If something's drastic happens, just TeamViewer Mulder server and put FSX online.

Thanks

[Storm]

Well Storm, i will agree some of you complainings, because i had a cloud prog running and forgot to switch it of. now is nothing else running, just FSopen and FSX, so if u don't mind to try the Teamviewer again, please.....it's the first day, give it a chance..

So... I tried all the tests again and I am happy to report that everything is now very good. Admittedly it is just one more experiment, but I can confirm (a) there is no apparent lag observing other aircraft, and (b) the TeamViewer response is as now quick as for US servers. (I will add that, like before, I monitor my own internet connection strength while doing these experiments and only do them while the connection is good.)

Whatever you did seemed to have a very good effect. Thank you! :eagerness:

[CaseyRyback53]

Hello Storm, i'm glad to read this, thanks for trying again....happy flying for all Simmer's :-)

[ak416]

Does anyone know what the current packet limit on our server is, and if it is the same across all servers?

[CaseyRyback53]

1000 packets..

[Mulderpilot13]

1000 packets if there are a lot of high packet flyers online and they aren't in TeamSpeak for lets say.. a group flight, and 1500 packets when the server is full of a bunch of 200-400 packet users. And when we have Lazer's flight, because so many people forget to turn their radios off (Myself included), it is set to never for the first leg so everyone can get settled.

Thanks