Hrm – it seems to me that ATC callsign should:
– Not be in the ACF
– Not be in the livery
In that I could take a United gray & white livery of B738 and go fly and take on the callsigns UAL2828 an then UAL301 in two consecutive flights.
In particular, tail number is only callsign for GA…hence the tail number decal on the panel to help forgetful pilots (at least, I guess that's what it's for) which is how liveries leak into the ACF file.
To me, the callsign would be picked when you file a FP or call in for flight following.
]]>Hrm – it seems to me that ATC callsign should:
– Not be in the ACF
– Not be in the livery
In that I could take a United gray & white livery of B738 and go fly and take on the callsigns UAL2828 an then UAL301 in two consecutive flights.
In particular, tail number is only callsign for GA…hence the tail number decal on the panel to help forgetful pilots (at least, I guess that's what it's for) which is how liveries leak into the ACF file.
To me, the callsign would be picked when you file a FP or call in for flight following.
]]>First…time to move this to the Wiki. 🙂
http://wiki.x-plane.com/Next-Gen_Liveries_RFC
Second…yes – we are indeed missing the ability for plugins to be livery aware. I was thinking of solving this problem with a very simple mechanism: a dataref that indicates (by name or number or both) the current livery. 🙂 That this dataref is not in 921 is actually an omission on my part.
]]>as you mentioned the tail number issue I would like to expand it to livery specific configurations files for plugins, this would allow to have different options for your acf when loading another livery, like tail number or loading configuration. Only problem here is for the plugin to find out which livery is used, or even better, which livery folder is currently used. Any solutions for this in the future ?
Regards
Jan
(twinpropflyer)