Hi Adrian,

In general, it looks like you're on the right track. I'll try and insert 
a few comments and answers in your post below:

Adrian Sprick wrote:
> Hi to all!
> I 've created some Traffic-Files to populate my airport. It should make some 
> a/c start from
> EDDG, land at some airports around the world, and then return.
> The schedules are weekly (747, Mo 7:16), daily (A320, Mo 8:00), and from 
> Mo-Thu and from Thu-Sun (737, Mo 7:30/ Thu 7:30).
> When I observe departures at EDDG, I get a little confused:
> 1. Sometimes no a/c appears at all
>   
This is most likely to happen when the FlightGear UTC clock has moved 
past your departure time. Looking at your schedule, the latest departure 
is set to 8:00, so if you start FlightGear at a later time, all aircraft 
have already departed. Note that all schedule times are in UTC. To 
ensure you don't miss the action, try starting FlightGear using the 
--start-date-gmt option (i.e., do something like 
--start-date-gmt=2007:03:17:07:15:00). Under windows, you can probably 
add this in your start-up file, or add this in the "advanced" options 
part of fgrun.
> 2. All 3 a/c pile up and dont move
>   
The piling-up is due to the fact that your airport doesn't have a ground 
network yet, which defines the parkings and taxiroutes. See 
http://wiki.flightgear.org/flightgear_wiki/index.php?title=Interactive_Traffic 
for additional documentation on ground networks. In effect, what you see 
is the backup mechanism, that ensures that flightgear keeps running, 
even in the absence of this ground network.
> 3. The 737 piles up with the A320 and 747 and then starts
>   

This is what should happen on a day, other than monday, at exactly 7:30 
UTC. If you were to wait for another 30 minutes, the A320 would probably 
also depart.
> 4. The 737 appears and starts
> 5. The 737 piles up with the 747 and both start
>   
There is a little bit of grace time build into FlightGear. Suppose your 
747 is supposed to take off at 7:16, and when you start FlightGear at 
the time the internal clock hits, say, 7:20, the 747 will still perform 
it's complete departure sequence. The idea is that flights can be 
delayed, as in real time. Off the top of my head, the maximun grace time 
would be about 5 to 10 minutes, but because your airport doesn't have a 
ground net yet, it's probably longer, because there is no position on 
the taxiway to place the aircraft on. So that being the case, it would 
be possible for the 737 and 747 to depart at the same time. Not sure why 
you wouldn't see the A320 through, without having looked at your 
specific setup.
> I ve had these effects when tried using systime, time match real, etc.
> FGFS is running on a Win98Se OS.
>   
As mentioned, try --start-date-gmt, to get precise control over the timing.
> My questions are:
> 1. Does FGFS consider weekdays (Mo, Tue, We and so on), and how?
>   
Yes, weekdays are supported, just prepend the  weekday to the departure 
/ arrival time, separated by a forward slash (for example: (0/21:00:00), 
where 0 means sunday, and 6 means saturday. Note that the weekday only 
makes sense in combination with <repeat>WEEK</week>. If you do a 
(multiple) hourly update, results may become unpredictable. Also note 
that for your daily flights you should probably set repeat to 24Hr. And 
finally, make sure you use the same repeat value for each flight that is 
assigned to one particular aircraft.
> 2. What time triggers the departure?
>   
That should be the simulated UTC value.
> 3. What effect does CTRL+T has on time concerning Ai-Traffic?
>   

The CTRL+T is not quite fully integrated yet. The AI models system 
doesn't honour it at the moment, so even when you hit CTRL-T, it doesn't 
have any effect on AIAircraft in the scene. The traffic manager itself 
is more or less sensitive to CTRL-T, and in a few circumstances this has 
an effect on the animations. Aircraft in parked position compare their 
schedule time with FlightGear's internal clock, so when you accelerate 
time, they should start moving when the accelerated simulated UTC hits 
the scheduled departure time. Note that this only holds for forward 
acceleration. Once you start moving backward in time, there is currently 
no way for the system to catch up with that.
> Regards,
> Adrian
>
>   

Hope this helps. Please let me know if you have further questions.

Cheers,
Durk

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Flightgear-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-users

Reply via email to