On Thu, 20 Mar 2008, LeeE wrote:

> I think this is a valid issue.
>
> As a final bit of testing I do some flying on mp, to check for mp
> specific problems, but doing that under instruction from ATC isn't
> really viable.  While I try to not cause problems for other users I
> can see that having someone else randomly whizzing about while
> you're trying to do serious stuff is going to be a little
> distracting at the very least.

Hi,

One observation is that maybe you don't have to do your tests at KSFO :)
I often use my local airport ESGP or KNUQ for testing (but admittedly 
this is mostly because the heavy traffic at KSFO tends to slow my box to a 
crawl).

> At one time there were separate mp systems for users and development
> (using port 5002 instead of 5000) and I could do my testing using
> the development mp system and populating it, if necessary, using
> some of my other systems here at home to run mp drones.  The
> trouble is though, running another mp system needs more resources,
> not only in server bandwidth but also maintenance etc, so I can
> understand why it was dropped.

We still have the port 5002 network up, though with less mpservers than 
the port 5000 one. Currently mpserver02 and mpserver06 seems to be the 
only ones on the 5002 network. mpserver01 is probably also there but it's 
port 5002 fgms seems unresponsive.

> I could use a different airport, somewhere away from KSFO, and
> populate that area with a few mp drones, but as well as adding an
> extra three or four aircraft to the current mp system, instead of
> just one, I'd not be able to test the effects of the KSFO scenery,
> which is a big factor just in itself.

Remember, MP data isn't forwarded to clients out of sight (well, 50nm out 
of sight to be precise), so moving to a less populated area saves server 
bandwidth (your data isn't forwarded to the other clients and theirs 
isn't forwarded to you).

Cheers,

Anders
-- 
---------------------------------------------------------------------------
Anders Gidenstam
mail: anders(at)gidenstam.org
WWW: http://www.gidenstam.org/FlightGear/

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to