>>>>> "Ron" == Ron Jensen writes:
>> 81:: Consider the case where FlightGear is run with the
>> --disable-ai-models command line option.
>>
>> It appears that some of the ai-related code continues to
>> run. You can easily verify by turning on log-level=info, in
>> which case you will see screen after screen of ?scheduling?
>> messages. The messages refer to ?scheduling? events many days
>> in the future. I reckon they shouldn't be scheduled at all when
>> the ai-models feature is turned off.
Ron> This is not a bug. ai-models refers explicitly to the 3D
Ron> models, which are used by scenarios, multiplayer and AI
Ron> traffic. AI traffic scheduling is done by the
Ron> traffic-manager. You want
Ron> --prop:/sim/traffic-manager/enabled=0
I've noticed that with AI traffic turned on, there is a constant
setting and resetting of the time accessed by
globals->get_time_params(), presumably as a result of events scheduled
"many days in the future" that John mentioned in his post. This
doesn't seem to cause any obvious problems in FlightGear, but this
does cause Atlas to get horribly confused when connected to FlightGear
- the time-stamped messages it receives jump all over the place. With
AI traffic turned off, the problem goes away.
Assuming that AI traffic is indeed the source of the problem, is there
any way to tell the AI aircraft not to reset the clock? Or,
alternatively, is there a pristine time source that the atlas.cxx code
can use, instead of globals->get_time_params()?
Brian
--
Brian Schack
19 Xǔchāng Street 2F phone: 2381 4727
Taipei 100 fax: 2381 2145
TAIWAN
------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
