Ahmed Zeineldin 1450113 Posted February 7, 2020 at 11:32 AM Posted February 7, 2020 at 11:32 AM Hello! I just recently logged back onto the VATSIM Network and found out that my vPilot is not finding FLAI Models and it's just showing me the A321. I'm on FSX:SE and I fully reinstalled almost everything. Please help! Link to comment Share on other sites More sharing options...
Deon Mathews Posted February 7, 2020 at 11:39 AM Posted February 7, 2020 at 11:39 AM I recommend you restart your system, run the FLAI operations centre and do an update. This worked for me a while ago. Hope this helps. Deon Mathews VATSIM Marketing & Communications Team Link to comment Share on other sites More sharing options...
Ahmed Zeineldin 1450113 Posted February 7, 2020 at 02:11 PM Author Posted February 7, 2020 at 02:11 PM Just tried that. Unfortunately, it didn't work! Link to comment Share on other sites More sharing options...
Ross Carlson Posted February 7, 2020 at 05:12 PM Posted February 7, 2020 at 05:12 PM When you say it's not finding FLAI, what do you mean? Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Ahmed Zeineldin 1450113 Posted February 7, 2020 at 06:51 PM Author Posted February 7, 2020 at 06:51 PM Means that when I connect to VATSIM the FLAI Models are identified but not shown in game, its just default FSX A321s. Link to comment Share on other sites More sharing options...
Ross Carlson Posted February 7, 2020 at 10:43 PM Posted February 7, 2020 at 10:43 PM Can you give an example of an aircraft that you encountered that showed as an A321 but should have shown as one of the FLAI models? Provide the type code and callsign for the aircraft, and the FLAI model that you think it should have matched to. Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Ahmed Zeineldin 1450113 Posted February 8, 2020 at 04:41 AM Author Posted February 8, 2020 at 04:41 AM Okay! Call sign: BOX85W Showed as: A321 Should’ve showed as: B777F Link to comment Share on other sites More sharing options...
Ross Carlson Posted February 8, 2020 at 05:01 AM Posted February 8, 2020 at 05:01 AM Which FLAI model should it have been? It would help if you could show me a screenshot of the specific model in the tree in your model matching settings. And what was BOX85W's type code? Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Ahmed Zeineldin 1450113 Posted February 8, 2020 at 08:22 AM Author Posted February 8, 2020 at 08:22 AM https://ibb.co/RYKSvr4 https://ibb.co/ncG2Nt4 also here: https://ibb.co/HH43rDR no custom rules set Link to comment Share on other sites More sharing options...
Ahmed Zeineldin 1450113 Posted February 8, 2020 at 08:28 AM Author Posted February 8, 2020 at 08:28 AM Also tried putting the .vmr file into custom rules and it didn't work. Link to comment Share on other sites More sharing options...
Ross Carlson Posted February 8, 2020 at 03:37 PM Posted February 8, 2020 at 03:37 PM You didn't post a screenshot showing the specific model in the tree that you expected would be used for BOX85W, nor did you specify what BOX85W's type code was. Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Ahmed Zeineldin 1450113 Posted February 8, 2020 at 05:44 PM Author Posted February 8, 2020 at 05:44 PM I can’t post a picture but for BOX85W I expected the model to be a B77F Aerologic but it showed as an A321. This problem started when copilot decided to remove the FSX:SE Model Matching Bar. Link to comment Share on other sites More sharing options...
Ross Carlson Posted February 8, 2020 at 11:42 PM Posted February 8, 2020 at 11:42 PM I can’t post a picture but for BOX85W I expected the model to be a B77F Aerologic but it showed as an A321. In your advanced model matching settings, please expand the tree to show the actual model that you expected to see for BOX85W. Take a screenshot of what it shows there, including the status (identified or not). This problem started when copilot decided to remove the FSX:SE Model Matching Bar. What is "copilot"? And I'm not sure what you mean by "FSX:SE Model Matching Bar". What is that? Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Ahmed Zeineldin 1450113 Posted February 9, 2020 at 04:52 AM Author Posted February 9, 2020 at 04:52 AM The copilot was an autocorrect of vPilot sorry. When I clicked the vPilot settings menu there was a section that said Model Matching FSX and there was another that said Model Matching FSX:SE. Since the Model Matching FSX:SE part disappeared this whole chaos started! I'll send a pic of the tree when I'm back from school. Link to comment Share on other sites More sharing options...
Ahmed Zeineldin 1450113 Posted February 9, 2020 at 04:26 PM Author Posted February 9, 2020 at 04:26 PM SOLVED! Just had to reinstall vPilot again and got that working! Thanks for your help. Link to comment Share on other sites More sharing options...
Andrew Ingram Posted March 4, 2020 at 11:37 PM Posted March 4, 2020 at 11:37 PM i am having the same issue with FSX:SE and vpilot not recognising FSX:SE and only FSX, any solutions? Link to comment Share on other sites More sharing options...
Recommended Posts