Michael Hatutian 1073781 Posted April 11, 2015 at 08:00 PM Posted April 11, 2015 at 08:00 PM Will we see this reflected in vPilot/IVAO MTL model matching? Right now apparently say someone files an AAL flightplan with an A319 or 320, I'll just get a default A321. I'm not sure if this is an IVAO MTL issue to sort out, or just a vPilot matching one. Link to comment Share on other sites More sharing options...
Ross Carlson Posted April 11, 2015 at 08:24 PM Posted April 11, 2015 at 08:24 PM It's an issue with the model set in that there is no A320 model painted in AAL colors. I imagine they'll be updating it at some point. Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Steven Caffey Posted April 22, 2015 at 02:49 AM Posted April 22, 2015 at 02:49 AM There is actually an AAL 319 model referenced in the rule set, so it should be showing the AA A319 for you. What you can do for others is open the model matching rule file in a text editor, and find the section for the types operated by the former US side but not AA (A320, A330, E190 off the top of my head) and copy the line that has the AWE, paste it and change the callsign to AAL. I'd leave the AWE references as I've seen people still filing AWE online (in fact I've seen a USA recently too ) for example: <ModelMatchRule CallsignPrefix="AWE" TypeCode="A320" ModelName="A320AWE" /> add: <ModelMatchRule CallsignPrefix="AAL" TypeCode="A320" ModelName="A320AWE" /> This tells vPilot to show the US Airways model instead of the generic at least. Steven Caffey (SY) ZLA Controller "A mile of highway gets you one mile, but a mile of runway can take you anywhere." Link to comment Share on other sites More sharing options...
Recommended Posts