Just to make things a little easier to grasp:

The FShost does NOT generate a lot of traffic. It will also NOT be overloaded too quickly. This is because of how the protocoll over which the flightsims communicate with the server/each others is designed as follows:

When one connects, his position is transmitted to the server only every 256 ms right now. This means that is a hit every 1/4 of a second, which implies not very much traffic (about 1k/sec per client)...
If two players fly together and they are as close as max. 10nm then the server will inform both simulators that they are close to each other and they should start sending their data to the other client. This is called P2P or PeerToPeer communication. Because of this the server does not have heavy load on its cpu and it does not have to do complex calculations. Also it implies that if people are flying at different places in the world (for example when different events take place) they will only be limited by their local bandwidth to have the game run smoothly when many people are together and can see each others. (distance < 10nm).

I hope this makes things a little easier to understand.

Of course I still want to do some testing on how the server load reacts to MANY people.

So it would be really awesome if there were quite a couple 
of eager pilots trying to connect tomorrow for the stress test.

xaBBu

We had a longer downtime today.. maybe caused by
defect memory module. We´ll be looking into this the next days.

Did anyone allready succesfully connected with FS2002 ?

It´s now Sunday 20:15 GMT.. we are online to test the performance.. join us if you want !!

We allready talked about this problem... .At the moment it does not look like it´s a problem on our side. I will check
if maybe another port needs to be open on our side...
but it´s quite unlikely !! The FSHost is set to allow FS2002
connections !

I experienced similar problems in the past on different server (sometimes I
only find 1 wspilots server no-matter what port I use).
To make shure you have a correct setup on your side...
make shure the following ports are open !!!

23456 UDP
6073 UDP
23432 TCP+UDP

also make shure you are searching the session through the correct port (your flightsim multiplayer setup). It must be 23456 (I don´t know if this is the default for FS2002). If you previously visited
a wspilots server it might still be set to 23457 or 23458.
And this will not show a session !

If this is all done.. and you still can´t find our session,
I´m sorry there is probabely not much that can be done about it. As I said, I experienced the same problem on different servers. One time a friend opened a local Server.. and 3 people were able to find it.. 2 were not. After 15 minutes the 4th person suddenly found a session.. while
the other guy still was unable.  The routing itself seems to work.. cause you were able to find our website.
I have no idea what could be wrong here. But anyway.. check your port setup twice !!

I would also like to ask someone else who has FS2002 installed to connect to the server and check if this works.
Thank You,

sam


edit: Airshow Lover.. can you connect to the wspilots servers at all ?