FSX Development team,There's an issue I'd like to bring to your attention, that is causing a big problem for online controlling, in FS9.As a VATSIM Controller in Seattle, there's a big problem for us.Since Seattle (Runway 34R) is the DEFAULT for FS9, we have a huge problem when people connect to the VATSIM Network. When a person connects to VATSIM, and has not selected their starting location, they logon and appear on KSEA Runway 34R. As controllers, this causes a big problem for us, when that runway is in use. a good part of the time, someone is connected onto the runway, and we have to direct traffic around them.Can the Default position in FSX be selected somewhere out of the way, perhaps 0N 0W?? In that case, if they connect, they'd be at ground level, in the ocean. If you wish to make Seattle the default Field again, that's great, but PLEASE don't have it, so when people connect right away, they will be on the runway.Thanks for reading, and I know you guys do.

>FSX Development team,>>There's an issue I'd like to bring to your attention, that is>causing a big problem for online controlling, in FS9.>>As a VATSIM Controller in Seattle, there's a big problem for>us.>>Since Seattle (Runway 34R) is the DEFAULT for FS9, we have a>huge problem when people connect to the VATSIM Network. When>a person connects to VATSIM, and has not selected their>starting location, they logon and appear on KSEA Runway 34R. >As controllers, this causes a big problem for us, when that>runway is in use. a good part of the time, someone is>connected onto the runway, and we have to direct traffic>around them.>>Can the Default position in FSX be selected somewhere out of>the way, perhaps 0N 0W?? In that case, if they connect,>they'd be at ground level, in the ocean. If you wish to make>Seattle the default Field again, that's great, but PLEASE>don't have it, so when people connect right away, they will be>on the runway.>>Thanks for reading, and I know you guys do.>The multiplayer needs a major overhaul, but this specific item could be fixed by VATSIM if they were willing to. Upon the VATSIM server receiving a new connection have it check if the user's X&Y coordinates are within a few meters of that spot and if so then just reject the connection. Not very hard to do. Have you petitioned VATSIM?

Didn't the FS devs already say that the multiplayer system received a major overhaul?

That's really a VATSIM issue . If the users don't read the VATSIM 102 - Pilot Etiquette Guide they deserve to be yelled at or better yet kicked off the network with a 5 minute ban.Kicking the user with an explanation sorts out the problem nicely.1. The user gets to know they screwed up and why they were kicked.2. The conflicting aircraft is removed immediately.Alternatively it would be relatively simple to check if a user tried to connect to the network while on the end of a runway and deny the connection.Paul

I think an F-16 scramble/intercept system built-in to flash warning beams into the cockpits of offending craft is a keen compromise.Andrew

This should not be a problem in FSX.

Excellent! Thanks tdragger