Kenz CHERIEF Posted December 12, 2016 at 08:50 PM Posted December 12, 2016 at 08:50 PM hi ! just installed v2, thanks for the hard work your doing for the community ! i was wondering, as i'm also a ivao member, i have MTL installed, of 6805 models, vpilot identify only 29, is that a normal behaviour ? I added a rule created with VMR, is that okay and should work ? thanks ! Link to comment Share on other sites More sharing options...
Ross Carlson Posted December 12, 2016 at 09:05 PM Posted December 12, 2016 at 09:05 PM The IVAO models were removed from the model database since they are only for use on IVAO. It is still able to recognize some of them by looking for valid ICAO airline and aircraft codes in the aircraft.cfg files. Evidently, 29 of the IVAO models have valid ICAO airline and aircraft codes, the rest do not. I thought that VMRGenerator also removed support for the IVAO models, but I guess not. So, yes, using your VMRGenerator file should work, as long as you don't mind going against IVAO's prohibition of the use of their models on other networks: https://www.ivao.aero/softdev/IvAp/IvAp_downl.asp Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Mike Blackburn Posted December 13, 2016 at 06:36 AM Posted December 13, 2016 at 06:36 AM VMR generator didn't fix this particular problem for me either. Thinking about downgrading back to ver 1 Link to comment Share on other sites More sharing options...
Board of Governors Don Desfosse Posted December 13, 2016 at 07:42 AM Board of Governors Posted December 13, 2016 at 07:42 AM No need to downgrade. Just use v2 "out of the box", and don't use vmrgenerator to create a custom model matching ruleset. Or if you already have, simply don't the custom ruleset. Don Desfosse Vice President, Operations Link to comment Share on other sites More sharing options...
Ross Carlson Posted December 13, 2016 at 02:41 PM Posted December 13, 2016 at 02:41 PM VMR generator didn't fix this particular problem for me either. Thinking about downgrading back to ver 1 If you use VMRGenerator to create a rule set, then load that rule set into vPilot 2.0 as a custom rule set, it will still show the IVAO MTL models as unidentified on "Model Matching -> Advanced" tab in the settings. That just means vPilot could not automatically identify the models. Your custom rule set will still allow the models to be used for model matching IF VMRGenerator still generates rules for IVAO's model set. And if VMRGenerator does *not* generate rules for the IVAO model set, downgrading to 1.0 won't change that fact. VMRGenerator is a third party tool developed by Nico Kaan and it is in no way affected by the version of vPilot that you're running. Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Nico Kaan Posted December 14, 2016 at 05:56 PM Posted December 14, 2016 at 05:56 PM Hi guys, From the FAQ of VMRGenerator: 4.2 Is IVAO_MTL supported? Yes IVAO_MTL support is available because VMRGenerator is also used by PSXseeconTraffic users of Aerowinx PSX in a FlightSimulator with IVAO on-line traffic. However, vPilot users are kindly requested to refrain from using the IVAO_MTL. Regards, Nico Kaan Developer: PSXseeconTraffic, ParkPosGenerator and AILGenerator Link to comment Share on other sites More sharing options...
Recommended Posts