On Wednesday 29 December 2004 00:33, Dave Martin wrote:
> I was thinking more about callsigns; if each AI aircraft is given a
> callsign, they could then take a registration from a pool (simple list) of
> correct registrations for their 'type' (ie: SqueezyJet 737) If a
> registration is taken by an AI traffic, the aircraft is given another from
> the same list.
For those op you interested: Some rudimentary support for this is already in
the traffic manager: Have a look at one of the traffic files in
${FG_ROOT}/data/Traffic for an idea. I'm not using most of these tags yet,
but they're there for future purposes.
>
> For airline fanatics, they could even help by providing 'flag-name' details
> for real-world registrations which would mean that:
>
> callsign: Speedbird 6
>
> Recieves: Reg: G-CIVW and flag-name: City of Lichfield.
:-).
The traffic manager actually organizes this the other way around:
<aircraft>
<model>Aircraft/MD11/Models/KLMmd11.xml</model>
<livery>KLM</livery>
<registration>PH-KCA</registration>
<heavy>true</heavy>
<!-- Day one: Amsterdam to San Fransisco, CA, USA -->
<flight>
<callsign>KLM0605</callsign>
<fltrules>IFR</fltrules>
<departure>
<port>EHAM</port>
<time>0/09:45:00</time>
</departure>
<cruise-alt>330</cruise-alt>
<arrival>
<port>KSFO</port>
<time>0/20:55:00</time>
</arrival>
<repeat>WEEK</repeat>
</flight>
</aircraft>
>
> Of course, this is both extreme and probably pointless when it comes to
> flag-names but it is the sort of thing that you could apply to textures
> using Imagemagick if the flag-names were pre-made.
>
I did keep a flag name as a comment in my xml files.
However, while I hate to spoil the party: This approach would require several
copies of each aircraft type (each with a slightly modified registration
texture) to be loaded. I recently changed the system so that we use multiple
instances of the same copy of each aircraft model, because the original code
that loaded separate copies of each model was taking up way too much
resources. I don't think we want to go back to the original situation, just
to display a registration number on an AI craft, which we wouldn't be able to
read 99% of all times.
Cheers,
Durk
_______________________________________________
Flightgear-devel mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
