That's a good idea. Currently I have slaved the Traffic manager to the AIManager. So if the AI manager is disabled, the traffic manager also doesn't run.
Adding in a separate option to disable the traffic manager independently from the AIManager is probably a good idea. I can image that there are situation where one wants AI traffic, but only from scenario. In this case the traffic manager has to be able to be disabled independantly. I'll see if I can add that in tomorrow. Cheers, Durk On Saturday 17 July 2004 19:08, David Culp wrote: > > Actually, fine tuning the AI traffic systems should be high on our > > priority list before the next version comes out. Even when the AI is > > disabled by default in the new version, as Curt suggested, we should > > still make a minimal effort to ensure it's working reasonably well when a > > user decides to enable it. > > I do think that preferences.xml should control whether or not the traffic > manager runs. Something like: > > <sim> > ... > <traffic-manager> > <enabled>true</enabled> > </traffic-manager> > ... > </sim> > > > I don't think it's good for something as new and complicated as the Traffic > Manager to run by default without an off switch. > > > Dave _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
