The JukiModelMatcher Tool generates VMR files that are necessary to get custom model matching for your liveries with vPilot.
The creation of your VMR file can be as easy as hitting three buttons, but you can also customize and manage your model matching if you want to.
If you are tired of downloading VMR files and seeing default aircraft spawn instead of your beautiful liveries, this is the tool for you.
Feedback/Bug reports are appreciated.
Requirements:
- Windows 10 (10.0.17763.0) or later or Windows 11. "Windows 10 S" may be unable to run the app.
- Windows sideloading has to be enabled. This is enabled by default, but if not follow these steps:
- 1. Open the Settings app > Update & Security or Privacy & Security > For developers.
- 2. Select Sideload apps.
What are my risks?
Worst case: The Model Matcher program may crash :(
How to install:
- 1. Unzip file
- 2. Open JukiModelMatcher (Package) folder
(Steps 3-10 only required on first install)
- 3. Double click on JukiModelMatcher (Package) certificate file (*.cer)
- 4. On the opening window click Install Certificate...
- 5. Select Local Machine
- 6. Select Place all certificates in the following store
- 7. Click Browse
- 8. Select Trusted Root Certification Authorities (its the 2nd option from the top if you have a different language).
- 9. Click finish and then hit ok.
- 10. Go back to the JukiModelMatcher (Package) folder
- 11. Launch JukiModelMatcher (Package).msixbundle and install the app
- 11.2 If there are issues when installing, go to the dependencies folder and install the dependencies for your computer.
- E.g. go to x64 and x86 and install the dependencies by clicking on the individual files one after another.
- 12. You have successfully installed the JukiModelMatcher.
Why is the install process so annoying/Where is my .exe?
The install process (missing .exe) can be seen as the successor of the .exe, which would be very simple to use especially if I would not upload this program here, but via the Microsoft Store. So why is the successor install process so unhandy when installing for the first time? Its because I did not pay money for a certificate, as I wanted to bring you the program for free.
How to update:
- 1. Backup your Documents > JukiModelMatcher directory in case something goes wrong!!!
- 2. Unzip file preferably to last installer location
- 3. Launch JukiModelMatcher (Package).msixbundle and install the app
How to use:
- Launch JukiModelMatcher.
- Go to Settings and select your MSFS community folder.
- Go to Liveries and click on refresh and wait until the pop up completes.
- Click on Generate and wait until the pop up completes.
- You can find your generated VMR file in your windows users documents folder in a directory named JukiModelMatcher.
- Don't forget to point vPilot to your new custom .vmr files.
How to use for advanced model matching users:
General:
On the Settings page you can not only select yout MSFS Community folder but also a light or dark theme :).
All entries like Airline and Type etc. should be ICAO codes.
Manual entries should save automatically if Auto is deselected.
Liveries Page:
On the Liveries page you can see nothing unless you hit Refresh.
Livery is the name of your community folder livery.
Airline is the Airline ICAO code associated with the livery.
Type is the Aircraft ICAO code associated with the livery.
Type2 is an alternative Aircraft ICAO code associated with the livery.
If either Type or Type2 matches the users aircraft, the corresponding livery will show.
You can leave the Airline field blank if you don't want to associate an airline with that livery.
For the livery to work, at least Type or Type2 has to be filled out.
If you don't have a certain airline installed, but the correct aircraft type (or type2), worst case, one of your matching livery types is picked at random.
So it is recommended to not leave the Aircraft field blank, as the livery will spawn anyway when no matching airline is found, but the type fits. Note, this only applies if the perfect match option is deselected in the settings menu. If it is selected, leaving the airline field blank, means that the livery cannot spawn.
Select Auto if you want the JukiModelMatcher to handle the livery automatically.
E.g. it will use the Aircraft page to determine Type2 automatically for your livery.
Select Exclude and deselect Auto if you don't want to use the livery for model matching.
If you want to manually set any field for your livery, like Type, make sure Auto is deselected.
If you want to revert manual changes back to automatic handling, select auto. The values will update when you click refresh, so don't forget to hit refresh before clicking generate to ensure your manual changes are overwritten.
Aircrafts page:
Determines Type2 on the Liveries page, by checking if the Livery name matches the given Regex.
Default entries are already provided. You can add or remove further types if necessary by entering the type and clicking add or remove.
Default types should not be removed. Rather deselect Auto and enable Exclude to disable the type.
Remember this does only effect Type2 and not Type, on the Liveries page.
To manually change entries, deslect auto and enter your custom values.
To enable the default values again, confirm the correct Type is entered and select auto.
If the perfect match option is selected in the settings menu, Manufacturer, Engine Class and Size are unused for VMR generation and therefore only serve for user friendly sorting purposes. So for a livery to spawn, airline synonyms from the Airlines page in combination with the Airline code on the Liveries page has to match, together with the aircraft type informaton given. So if someone uses "DLH" "A320" as airline and aircraft type, but you don't have a livery with exacty these entries on the Liveries page, no match is found and a default aircraft may spawn. If you entered a synonym to "DLH" like "LH" and you have an livery with "LH" and "A320", this will still match, even with the perfect match open enabled.
If the perfect match option is deselected in the settings menu, nothing different will happen compared to the option being selected, if you have a livery matching the airline(incl. synonyms) and aircraft type of a user. The difference occures if no perfect match is found. If you don't have a matching airline, but a matching aircraft type, a random livery matching the aircraft type may spawn. If you don't have a matching aircraft type, liveries with similar aircraft types will spawn. If the similar aircraft types contain a matching airline livery, an aircraft from the same airline will spawn using a similar aircraft type. If there is no matching airline code for the similar aircraft types, any random livery for the similar aircraft type will spawn. Only if you do not have a livery for the aircraft type and no livery for any similar aircraft type, the default generic aircraft determined by vPilot will spawn. Which aircraft types are similar to one another is based on the Manufacturer, Engine Class and Size. Additionally vPilot also has a fixed set of aircraft types that are deemed similar. If Manufacturer, Engine Class and Size are the same for two aircraft types, then they are similar. If no similar aircraft types exist for an aircraft type using all three characteristics, it suffices if another aircraft type has the same Engine Class and Size in order to be similar. If still no similar aircraft types exist, it suffices if another aircraft type has the same Size in order to be similar. Otherwise there are no similar aircraft types. E.g. if someone uses an DLH A380, but you don't have any A380 livery and no other Airbus jet with that size, but you do have a B747 jet livery with the same aircraft type size entered in the Aircrafts page, a B747 jet livery will spawn instead of the A380. In that case, if you have a DLH(or a synonym for DLH) B747 livery, this will be used, otherwise a B747 of another airline may spawn, if there is no other similar aircraft type that has a DLH livery. This will hopefully almost completely prevent the spawning of the default generic aircraft. If they still spawn, check what aircraft type it was supposed to be and add it to the Aircraft page, so that similar installed liveries can be found. E.g. a user used a Concorde and I did not have a livery for a Concorde, so I added an entry to the livery page for the aircraft type CONC with a size, where I knew that I had Liveries installed for aircraft types with the same size, so that they would spawn instead.
Airlines page:
On the Airlines page you can add Airline ICAOs that should be seen as synonyms.
E.g. if you want all liveries with "DLH" airline ICAO codes to also spawn when "BER" is used as Airline code, just add a row that contains "DLH" and "BER".
It does not matter which column is used at all.
What if you want to see "DLH" airline liveries and "EZY" liveries when someone uses "BER", but you don't want to see "EZY" liveries when "DLH" is used and the other way round?
Just add another row, so that "DLH" and "EZY" are in different rows. It is not an issue that an airline ICAO like "BER" exists in multiple rows.
If you don't specify any synonym airlines, only the airline given on the liveries page will be used for a particular livery.
Remember, if someone uses "BER", but you do not have any "BER" livery or a synonym of it on the liveries page, another airline livery may spawn like "EZY", only if the perfect match option is deselected.
This should cover the most important details.
You can also always check the generated VMR file to see, if it looks like you would expect.
What if you have spent countless hours using ModelMatchingMagic?
You can import your settings from the ModelMatchingMagic.json into the JukiModelMatcher.
I would recommend running JukiModelMatcher once and generate a vmr with it, so that your Documents > JukiModelMatcher folder contains all necessary .json files.
Make a backup of all files that you are going to change, before editing them.
You then can copy your manual changes for the Liveries page from the ModelMatchingMagic.json into unusedOverrides.json.
You can do the same for manualAircraftTypes.json for the Aircrafts page.
Feedback
If you have any feedback or experience issues/bugs with this, please don't hestitate to comment below.
If the program suddenly exits, it is probably because it encountered an issue.
You may find a crash log in your Documents > JukiModelMatcher folder describing the issue.
The last error that occured can be found at the bottom of the file.
If there is a clear error given, like "failed to process liveries at path xy", you may be able to solve the issue yourself.
Otherwise provide me with the last errorLog entries if available, so that I can potentially identify/resolve issues.
How to completely uninstall the program?
- 1. Uninstal JukiModelMatcher like any other program via the App&Features Windows Settings.
- 2. Remove JukiModelMatcher folder from your Documents folder (You will lose your JukiModelMatcher settings!).
- 3. Remove the community folder link from the drive where your community folder is located. E.g. C:\community (not the actual MSFS community folder).
- 4. Remove the installed JJR certificate from Windows via Windows "Manage computer certificates".
Why is a link to the MSFS community created on my drive?
Because I do not have a better solution yet, to ensure that the users community folder does not exceed the maximum Windows path length.
Huge thanks to the creator of ModelMatchingMagic for the design inspiration.
Hope you have a good time with the Tool :)
3 months ago
RideroftheMark
5 months ago
Xstasus
8 months ago
nickvdruit
Unfortunately, the certificate is not valid anymore (expired) and with the dependences, it doesn't work. Is it possible to fix that ?
1 years ago
I got a fix:
Go to your System -> Settings -> Time and Date
Set it to 01.01.2023
execute the bundle
Rexet it to auto
Programm should work thereafter.
11 months ago
MasterKill95
HulkSea
can you add an option to select folder and not the community folder,becouse if i want to deactivate(exlude)all the aigmoci group to do a first vmr with perfect match anable for the fsltl pacages is a very long process.
i mustt exclude thr livery cliching one on one.
1 years ago
Hello Lorenzo,
yes I can look into adding such a feature,
but I won't be able to do it before the end of november due to a deadline coming up, which is taking my time away.
For the time being, I recommend to temporarily remove the folder (that should be excluded) from the community folder before launching JUKIModelMatcher, or create a new directory with symbolic links to the folders that you want to generate the vmr for and point JUKIModelMatcher to that folder.
1 years ago
BlackFantasy
Lorenzo.D
Path exceed the length the system can handle when I hit refresh, I moved the community folder and it just crashes everytime I select it from settings 😞 really crap experience using this tool
2 years ago
Hello Bossmoney69.
Sorry to hear that you are having issues.
Sounds like you have a mod in your community folder that has so many subfolders that Windows path character limit is exceeded. I will try to find a way reading from paths that exceed the limit and if this is not doable, i will let it ignore the folders that exceed the path limit. Will try to get it done this week. If you are willing to try it after the improvement, I would be glad to hear from you if the problem has been resolved.
2 years ago
BlackFantasy
Bossmoney69
Great tool!
But would it be possible to add simple type code synonyms without having to use regex matching on the name?
Like map "P28A" to the same models as "P28R"?
2 years ago
Glad to hear.
I think that is a good idea.
It would be basically the same as the airlines synonym page, but for aircraft types.
There are plans to update vPilot this year, making VMR files for most users obsolete. Keeping this in mind, if they make good progress, it may unfortunately not be worth it to implement larger features, if the current tool is sufficient for most users.
If more users would request it, I will certainly implement it anyway.
So more feedback would be nice.
2 years ago
BlackFantasy
Laurinius
Im gettin Error in parsing the app package. when trying to open the package
2 years ago
That is unfortunate to hear. Would you mind contacting me via Discord, so that I can look at the problem in more detail? Username: BlackFantasy#7956
2 years ago
BlackFantasy
wille19991
Neat little tool! Glad there are devs working on better model matching utilities for the sim. 😊
2 years ago
superb program thank you very mach.
2 years ago
Lorenzo.D
mykrode