Model Mathcing Issue (A319)

[Samuel Magalhaes 0]

Hello everybody, i have a issue with the a319 model. I just had installed the liveries from altitude software and from the megapack and i am using the "airlines.vmr".
My vpilot creates the models without errors but in the case of the a319 it creates all 319 on my range with the first model loaded. 
Example: i have 1 austiran (319) and 2 ezy (319) the first loading of the model was the austrian and the other 2 ezy will be a austrian 319.
I just did the command ".aircraft" and everything are correct with the names.
Anyone could help me?

[Samuel Magalhaes 0]

There is a pic of ".aircraft"

[Ross Carlson 170]

I've seen this happen with other models and liveries. It appears to be a bug in MSFS.

[Samuel Magalhaes 0]

5 hours ago, Ross Carlson said:

I've seen this happen with other models and liveries. It appears to be a bug in MSFS.

I will wait for the next Sim Update. Thanks a lot for your answer.

[Robert Shearman Jr 167]

The next sim update may not address it.  Does anyone here know whether it has been reported to MS / Asobo via Zendesk?

[Matthias Roschk 821976 0]

On 4/4/2021 at 11:56 AM, Samuel Magalhaes said:

There is a pic of ".aircraft"

Hello,

i also have Problems understanding the vPilot MOdel Math´ching.

First i am searching for the VMRGenerator and what is that Picture from ? What programm is that ?

Maybe anyone can help me understanding some Matchings that i can not understand...as example a C208 is matched as C152 ???

Matthias

 

ahh, i found the screenshot, but still searching the VMRGenerator

Edited April 5 by Matthias Roschk 821976
info added

[Samuel Magalhaes 0]

4 hours ago, Matthias Roschk 821976 said:

Hello,

i also have Problems understanding the vPilot MOdel Math´ching.

First i am searching for the VMRGenerator and what is that Picture from ? What programm is that ?

Maybe anyone can help me understanding some Matchings that i can not understand...as example a C208 is matched as C152 ???

Matthias

 

ahh, i found the screenshot, but still searching the VMRGenerator

The pic is a command in the vpilot just write ".aircraft" and this show all the models variables.

[Matthias Roschk 821976 0]

Just now, Samuel Magalhaes said:

The pic is a command in the vpilot just write ".aircraft" and this show all the models variables.

Yes, thanks...i found it. ( i am still new there )

What i am still searching is the VMRGenerator.
All links i found seams to be down 😞

 

Matthias

[Samuel Magalhaes 0]

5 minutes ago, Matthias Roschk 821976 said:

Yes, thanks...i found it. ( i am still new there )

What i am still searching is the VMRGenerator.
All links i found seams to be down 😞

 

Matthias

Well, i use this one https://drive.google.com/drive/folders/1bd7P8PI26vpweIOqGmhJqJh8EuYBddNO?usp=sharing

[Matthias Roschk 821976 0]

ok, but thats the vmr files, thanks for that, and the VMRGenerator itself is not available anywhere ?

[Ross Carlson 170]

VMRGenerator is no longer relevant. That was for version 1 of vPilot. Version 2 generates its own model matching rules by scanning your installed aircraft. However, because the model data folder structure for MSFS has changed significantly, vPilot does not currently generate model matching rules for MSFS. It only uses a set of basic rules that make use of the default models that come with the sim. So if you want to use third party models with MSFS, then you need to have a vmr file that someone created specifically for the model set you are using, such as the ones Samuel linked to above.

[Samuel Magalhaes 0]

3 minutes ago, Ross Carlson said:

VMRGenerator is no longer relevant. That was for version 1 of vPilot. Version 2 generates its own model matching rules by scanning your installed aircraft. However, because the model data folder structure for MSFS has changed significantly, vPilot does not currently generate model matching rules for MSFS. It only uses a set of basic rules that make use of the default models that come with the sim. So if you want to use third party models with MSFS, then you need to have a vmr file that someone created specifically for the model set you are using, such as the ones Samuel linked to above.

Will there be a new version entirely dedicated to MSFS?

[Matthias Roschk 821976 0]

hmm...i am on P3D v4 and have a Folder with all my AI Models inside the folder <prepar3d>/SimObjects\AI_Models.

In the Simobjects.cfg i have entered the path to it:

[Entry.10]
PATH=SimObjects\AI_Models
TITLE=AI_Models
ACTIVE=true
REQUIRED=true

 

If i understand correctly, i dont need a vmr file ??

 

but what means that? ( 127 identified )

Edited April 5 by Matthias Roschk 821976

[Ross Carlson 170]

59 minutes ago, Samuel Magalhaes said:

Will there be a new version entirely dedicated to MSFS?

Of vPilot? No, there is no need to have a dedicated version.

[Ross Carlson 170]

43 minutes ago, Matthias Roschk 821976 said:

hmm...i am on P3D v4 and have a Folder with all my AI Models inside the folder <prepar3d>/SimObjects\AI_Models.

In the Simobjects.cfg i have entered the path to it:

[Entry.10]
PATH=SimObjects\AI_Models
TITLE=AI_Models
ACTIVE=true
REQUIRED=true

 

If i understand correctly, i dont need a vmr file ??

 

but what means that? ( 127 identified )

Identified means vPilot was able to determine the aircraft type code and airline code by scanning the data in the aircraft.cfg file. It will only automatically use models that it could identify. In order to use other models, you need a VMR file.

[Matthias Roschk 821976 0]

44 minutes ago, Ross Carlson said:

Identified means vPilot was able to determine the aircraft type code and airline code by scanning the data in the aircraft.cfg file. It will only automatically use models that it could identify. In order to use other models, you need a VMR file.

Ahh, ok.

And what could be wrong ( mainly ) that vPilot can not determine the other Aircrafts?
Can i , anyhow, see a list oft the Aircrafts which are wrong?

[Ross Carlson 170]

Have a look at the documentation, it's pretty-well spelled out there.

[Matthias Roschk 821976 0]

https://vpilot.rosscarlson.dev/Documentation#model-matching

 

this one ?

 

It seams you mean that site, but i can not find out how i can get a list of the Aircrafts which are NOT found or are wrong anyhow?

Edited April 5 by Matthias Roschk 821976

[Ross Carlson 170]

Expand the "advanced" section of the model matching settings, and you'll be able to see which aircraft are identified. You won't be able to see it on an individual texture level, but you will at the model level.

[Matthias Roschk 821976 0]

Ahhh....over there...never seen i can expand this ...
Thanks a lot ....

[Matthias Roschk 821976 0]

Hello again,

i have tried to find out why one of my AI is identified and the other not.
So i take one, which is identified and one which is not identified and compare then to find out the difference.
But i can't find ... both have a aircraft.cfg, a sim= entrie which have a *.air file entrie, the *.air file is also available, a texture entrie, which is also available.

So how can i find out what is wrong with the one who is not identified ?
Is there a List what is vPilot looking for , like in the vmr file ?

Or is there maybe a initial pack of AI Aircrafts which are working ?

Matthias

[Ross Carlson 170]

It is looking for a valid type code in the atc_model line and for airliners, it looks for a valid airline code in the atc_parking_codes line.

[Matthias Roschk 821976 0]

Ahh, thanks, that helps ...

 

I had a test, and it seams the atc_model must match the Typecode and the atc_parking_codes must match the Callsign ( like DLH or RYR )?

Right?

Are there any Restrictions for the Callsign matching? ( minimum 3 letters or something) ?
As Example for RYR can it be RYR, FR ? Like atc_parking_codes=RYR,FR ?

 

Edited Tuesday at 06:12 PM by Matthias Roschk 821976

[Haojun Wang 0]

FOR MSFS2020 MODEL MATCHING, try this one:

 https://flightsim.to/file/12414/msfs2020-vatsim-modelmatching