Jakob Elaaidi Posted November 3, 2018 at 03:13 PM Posted November 3, 2018 at 03:13 PM So i have been getting a few errors lately with the Airbus model matching, people are logged in at A320 for the callsign but vPilot or FLAI seems to give them the model for the A321 and not be able to find the A320 correctly correctly. I have also been having the same issue with the Neo's I would write in BVA but i am not a member so i cant get in. Link to comment Share on other sites More sharing options...
Norman Blackburn Posted November 3, 2018 at 03:55 PM Posted November 3, 2018 at 03:55 PM Have you included the model matching rule set under custom? Norman Link to comment Share on other sites More sharing options...
Ross Carlson Posted November 3, 2018 at 04:35 PM Posted November 3, 2018 at 04:35 PM You can reach the FLAi team at the feedback form on their site: http://flai.bvartcc.com/ Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Jakob Elaaidi Posted November 3, 2018 at 05:55 PM Author Posted November 3, 2018 at 05:55 PM Have you included the model matching rule set under custom? affirm its there, its a little annoying it ruins the flight when there is a constant beep from vPilot because of it Link to comment Share on other sites More sharing options...
Evan Reiter Posted November 5, 2018 at 04:27 PM Posted November 5, 2018 at 04:27 PM Jakob, If you haven't already spoken with Matthew or Ryan to resolve this issue, we're aware there's an issue with the A320 file in our latest update. We've got a resolution available and a fix is supposed to be pushed for it shortly. If you're still having the issue, could you send me an email to [email protected]? I'll just send you the update directly so you don't have to put up with the error messages while you wait for the official update to be released. Evan ReiterBoston Virtual ARTCC/ZBW Community Manager Link to comment Share on other sites More sharing options...
Recommended Posts