Support for MSFS 2024

[Zhavok92]

Hello and thank you very much for JoinFS. I am a really big FAN of the tool and wanted to ask if support for msfs2024 is planned?

Best regards!

[omx5o]

Hi. I'm afraid I no longer develop it but perhaps someone will extend the git source for the 2024 version. Best regards, Peter

…

On Thu, Nov 21, 2024 at 3:56 PM Zhavok92 ***@***.***> wrote: Hello and thank you very much for JoinFS. I am a really big FAN of the tool and wanted to ask if support for msfs2024 is planned? Best regards! — Reply to this email directly, view it on GitHub <#5>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BG3QSQVC7NCCCUGCBXEJ3N32BX7EDAVCNFSM6AAAAABSHK3UNCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGY4DAMBRHEYTEMQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Zhavok92]

Ahh ok. That is a pity to hear. But thanks for the quick reply anyway ;)

[neoxeo]

Hi,

I will add 2024 support (not before the end of the year) and ask your help @Zhavok92 to made tests, if you are agree.

[Zhavok92]

I'm not a JoinFS pro, I've only used it to host a session for two people. But yes, I can test it

[Mariopilot808]

I've been investigating MSFS-2024 support. Currently compiling a list of all Aviator's Edition aircraft for model matching tables.
Also, I have a modification to move MSFS marketplace add-ons to a text file, instead of them being hardcoded.
Will try to share these soon.

[neoxeo]

@Mariopilot808

Hi, I didn't understand your comment before I install MSFS2024. Now, I see that a lot of "objects" did not installed by default but streamed when you need them. So effectively, it is necessary to have a list of "standard" objects for each version of MSFS2024 and scan Community path to have a complete list of available object.

Perhaps, it is possible folder names present into :

• Steam: %APPDATA%\Microsoft Flight Simulator 2024\StreamedPackages
• MS Store: %LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\StreamedPackages
  to get first list even if models didn't downloaded.

Tell me if I can help you.

Thanks.

[Mariopilot808]

@neoxeo ,
As you say, MSFS-2024 only streams objects. Therefore the only way is to have a library of them. This is what I did.
Since I have Aviator's edition, I could see all. Sadly the only way now is to screenshot the DevMode's Aircraft Selector page, create a huge composite image and run this through OCR scanning. 1600+ aircraft variations!!
The good news is that Getting JoinFS to work with FS-2024 proved otherwise quite simple!!
The limitations are:

• Cannot use the new "Modular Simobject" format of FS-2024, hence only the base models for these can be called. This is a SimConnect limitation. MS may expand the functions in the future. Their liveries cannot be. This effectively reduced the number of available aircraft to 510.
• All streamed content must be in a static library. Cannot be scanned.
• If MS updates the FS-2020 aircraft to FS-2024 standard, the static library will need updating.
• Note: I hve placed this in a text file that JoinFS will read. Previously marketplace add-ons were hard-coded. This makes it exceedingly complicated to add new ones.
  The LocalState folder you mention populates if you enable VFS projection from the SDK. We cannot ask users to do this.
  Not sure how Steam will deal with it.

I was planning on creating a Fork and dropping my code there.
I also found out that I could log-in in FS-2024 (MS Store) on one PC and FS-2020 (Steam) in another (old laptop), and JoinFS with myself.

Regard,

Mario

[neoxeo]

@Mariopilot808

Thanks a lot for all these interesting informations !

Regard,
NeoXeo

[Mariopilot808]

@omx5o ,
Is your code signing still active?
In order to do my work I turned code signing OFF.
If we push an updated version for FS-2024 into your repository, will you kindly do the release work on your site?
Note that I am still working on stuff. This is just so to organize how to work on my fork.

Best Regards,

Mario N.

[Mariopilot808]

@tuduce
You seem to be better versed at C# than me.
Feel free to navigate my fork and take any conde snippet you like.
I had this feature where FS2020 add-ons were now residing in a text file.
This avoided re-compiling just to add more. I was also planning a feature for users to insert new ones, but put it on hold as I worked on the New FS/2024 EnumerateSimObjectsAndLiveries function.

[tuduce]

Thanks @Mariopilot808 ! I will take a look at your code and integrate it in my fork.
I just released the first MSFS2024 integration if you are interested.

https://github.com/tuduce/JoinFS/releases/tag/v3.2.20

[geobouimg07]

Thank you all.

Let me introduce myself, I am the administrator of a VA of 35 active pilots using JoinFS very regularly.

I don't really know to what extent this can help, maybe your approach is further along, but just in case.

Here, I have developed a small aircraft.cfg file base for JoinFS 2020 to be able to make valid substitutions in FS2024 considering that now FS2024 aircraft are "streamed".

To help me achieve this, I activated the virtual file system (VFS) and manually when possible I copied the aircrafts files. Because you must have noticed, for a large number of models, the file disappears as soon as you try to open it. I had to manually, inspired by examples for the models I was interested in, modify the "aircraft.cfg" files according to the FS2024 approach and at the same time make them readable correctly by JoinFS and substitutable by FS2024.

The substitutions have all been tested successfully in groups. FS2020 vs FS2024 vs FS2024.

However, in terms of limitation, I have not managed to have more than one livery (default) per aircraft model. I can't find a way to do it. My findings after several attempts, it seems that the aircraft.cfg file variable "Title=" is the major input to call the call of a FS2024 model. The other variables "ui_variation" and "ui_type" are more used to categorize in JoinFS. As there are cases where it is unique and repetitive, this causes a pitfall.

I see that you have really developed a good base, very exhaustive and very well categorized in the JoinFS FS2024 v3.2.20 version. Bravo! Very good work !

Now, the substitution seems to be a big challenge here (v3.2.20), but maybe you are on the way to achieving it.

Hoping very humbly that this can help in the progression of this development.

If you want to take a closer look, here is the download link.

https://imaginairvirtuel.qc.ca/download/AIRCRAFT-SUBSTITUTION-JOINFS.zip

There are 43 models divided into 27 aircraft. They are all in the standard version of FS2020/24, one or two in Deluxe.

I opted as much as possible for aircraft that are often used in my group and for all flight categories.

Ex. Tbm930, Kingair, Pipistrel, Beaver, 737, etc.

Here is the procedure to install, you have to extract the contents of the downloaded zip file and copy only the folder "JOINFS_modeles_FS2024" into the "Community" folder of FS2024.

1 - Then, start FS2024, once on the tarmac, launch JOINFS 2020 v3.2.17 (or v3.2.18) click on the "File" menu, then "Scan for models"

2- Click on the "browse" button to find the location of the FS2024 packages, which is exactly the following path.

Once the path is found, it must be copied into the "Other folders to scan" rectangle for the search to work (v3.2.17) and then you can click on "Search"

3- If in your FS2024 "community" folder, there are no other aircraft installed, you will have as result "43 models"

4- you will be able to make all possible substitutions with all these models in JOINFS 2020.

5 - In "Model Matching", to help JoinFS, we can categorize the substitutions with these aircraft.

If this can help you, I am willing to test any development with my group of JoinFS pilots if necessary.

Thank you very much for this involvement in the development of JoinFS.

geobouimg07
VA ImaginAirvirtuel
https://imaginairvirtuel.qc.ca/

PS. Sorry! If there are any errors in sentence construction, English is not my mother tongue.

[geobouimg07]

Sorry! My addition of information in the previous message is more or less relevant. When I wrote it, I had not seen and checked thoroughly version 3.2.18.

This one works very well, in the "Add-on" section, it allows to make adequate substitutions on all FS2024 aircraft even if it is only on the default livery in most cases.

Version 3.2.20, the aircraft substitution function now seems absent or non-functional with this new integration. This is probably coming soon.

I remain available if you need help to test new versions.

Thank you very much for your involvement. Keep up the excellent work.

Kind regards

geobouimg07
VA ImaginAirvirtuel
https://imaginairvirtuel.qc.ca/

[tuduce]

Hi all

@geobouimg07 : sorry for the substitution bug. I fixed it in the code. Fell free to clone, compile and test before I let out the next release.

If you find further problems, please feel free to report them at https://github.com/tuduce/JoinFS/issues

I am happy to collaborate with other developers to further the product. @Mariopilot808 if you want, you can integrate your changes in my repo. This way, they will be seen as you contributions and credit will go where credit is due.

[geobouimg07]

Thank you very much @tuduce for the quick intervention to fix the code. Unfortunately, I would like to but my skills in this area are limited, I am not able to compile or produce a new release.

Maybe @Mariopilot808 would be able to accomplish this part or maybe you, I do not know what would be best in this context of collaboration.

For my part, I remain available afterwards to carry out tests and do a thorough analysis (with several simmers) and come back to you with a reliable result.

[tuduce]

I released 3.2.21 to fix the substitution bug I introduced.

No problem if you can't compile. I didn't know that. Testing after the release is very much appreciated!!

[geobouimg07]

Thank you very much @tuduce.

I will give you an update as soon as I can under the circumstances. Until then, Merry Christmas.

[geobouimg07]

Hi @tuduce and all,

According to a lot of tests done with this latest patch (v3.2.21) the (manual) substitution works wonderfully well.

The 125 aircraft of FS2024 (Standard, Deluxe, Premium and Aviator Version) are ALL substitutable (with all simulators; FSX, P3D, FS2020, etc.) and in addition in all textures or "liveries". It is very impressive. The result is very conclusive. Really a beautiful work!

Only one small exception, coming from a bug in FS2024, is the FOKKER FVII COMMON, the Aircraft model being absent until now. If ever it is possible to remove this entry from the list of FS2024 aircraft.

Furthermore, on the "model matching" feature or section (automated substitution by aircraft category; SingProp, TwinProp, Airliner, Rotorcraft, Glider, etc. originally based on the "ui_typerole" variable of the "aircraft.cfg" file), we have observed that it no longer works quite the same way.

Sorry, if I give a lot of details here below, my only goal is to be as precise as possible to help you be able to see what can be corrected in order to promote this integration of the FS2024 substitution aircraft list to optimal operation.

1- For the case where the FS2024 "Community" folder is empty, the "model matching" window is also empty (if a scan just before) or (if we reconnect without a scan) it assigns to all categories the first in the FS2024 aircraft list, i.e. the Beechcraft D17S Staggerwing. If substitutions are made, they are not kept for the next use of JoinFS. Subsequently, the detection of aircraft (D) remains very random, does not correspond to the categories.

2- For the case where the FS2024 "Community" folder contains an aircraft (or two), then the latter occupies all the entries in the "model matching" window without distinction of category (SingProp, TwinProp, Airliner, etc.). If a substitution is made with an FS2024 aircraft, it is not kept for the next use of JoinFS.

3- For the case where the FS2024 "Community" folder contains several aircraft, a good variety, these are the only ones to occupy the entries in the "model matching" window, they are detected (D) correctly according to the categories (SingProp, TwinProp, Airliner, etc.). If a substitution is made with an aircraft from the "Community" folder then it is kept for the next use of JoinFS. If we make a substitution with an aircraft (S) from the FS2024 aircraft list, it is not kept the next time we use it.

However, an aircraft (A) is detected and assigned correctly from the FS2024 list especially when we are with other pilots who are also in FS2024 vs FS2024 or FS2020 (base aircraft) and the FS2024 community folder is relatively empty. We really see a priority (almost exclusive) of the aircraft in the "community" folder on the list of integrated FS2024 aircraft.

In summary, for detection, we observe an unequal treatment between the aircraft in the Community folder vs the integrated FS2024 aircraft list for model matching. The integrated FS2024 aircraft list does not contribute to its fair extent.

Another observation in the same vein, in the list of the file "models - Microsoft Flight Simulator 2024.txt" in the subfolder "AppData\Local\JoinFS-FS2024" all the FS20024 aircraft are categorized with the only variable "SingleProp" while the aircraft from the subfolder "community" are categorized correctly (SingProp, TwinProp, Airliner, etc). Maybe this gives you a clue to explain the observed behavior of the "Model Matching" feature.

We are continuing our tests, we will get back to you, if we ever observe other significant things.

If you have any questions or if there are points to clarify in this feedback, do not hesitate.

Thanks again for this last patch, considering the significant challenge it overcomes, it is really an excellent result, a big step forward that you have achieved.

Kind regards

geobouimg07
VA ImaginAirvirtuel

[tuduce]

Thanks @geobouimg07 for the extensive testing. I will split your feedback across a couple of issues. One of them is already solved, but not yet released (the default matches use only community models). For the proper classification of the MSFS24 aircraft I'm still thinking about a solution. Since the sim classification is not the same as the JoinFS classification, I need external matching. I'm thinking of a method where the community can contribute to this classification.

You'll hear from me in the next days. I really appreciate your help with testing!!

[Mariopilot808]

@tuduce , In my repo fork there is an excel file you may find very useful! Be advised that this was collected via aircraft selector +screenshot+ OCR and may contain mistakes. I suggest to log the output of GetSimObjectsAndLiveries, and then use a compare tool such as WinMerge.

[tuduce]

@Mariopilot808 it is useful, thanks!!

I opened an issue for this at tuduce#6

[tuduce]

Hi all

JoinFS-FS2024v3.2.22 is out, fixing the issues in your feedback.

https://github.com/tuduce/JoinFS/releases/tag/v3.2.22

Testing and feedback is appreciated!

[geobouimg07]

Great! Thank you so much @tuduce. I'm going back to the tests and will get back to you as soon as possible.

[geobouimg07]

Hi @tuduce @Mariopilot808 and all.

Following a large number of tests carried out with this latest patch (v3.2.22) focusing mainly on the "model matching" function

First of all, the banned model list is fully functional.

The type classification function works flawlessly and very efficiently when FS2024 aircraft are put in each of the types (SingProp, TwinProp, Airliner, Rotorcraft, etc.), I have not noticed any problem on this aspect in particular. Really very good. Efficient and very well done.

If we make changes to aircraft for each of the types, they are kept later without problem. If ever an aircraft is no longer available, a message and a replacement are made correctly.

We observed in the "model matching" window for the "default" that for FS2020 aircraft and others the "livery" are kept. For FS2024 aircraft, if you select a "Livery" there, it is not kept, and returns to a default "livery" at the next launch of JOINFS. As the way of classification is different in FS2024, maybe we can do otherwise. But this does not seem to cause any major problem.

If the user has an empty F2024 "community" folder, the classification of aircraft is done with FS2024 aircraft perfectly. A message displaying the number of models is done correctly. The only thing, a message "Model list is empty for this simulator. Would you like to scan for models now?" comes back in a loop even if "1674 models" MSF2024 were found.

If later, other aircraft are added in the FS2024 "community", everything continues to work perfectly with the initial "model matching" choices, if the user keeps "Scan at launch" checked.

Now for the case of a user who is just starting out with JoinFS2024 with a FS2024 "community" folder having a few aircraft (2 to 3) at the time of installation, if in the subfolders "..\AppData\Local\JoinFS-FS2024" and "..\AppData\Local\JoinFS" are non-existent and are created at this time, all the aircraft in "community" come to fill in not really respecting the newly established classification.

Here is an example (in "community", there were two planes; a comanche, an airbus 300-600):

Default SingleProp=A2A Piper PA-24-250 Comanche N6229P <-> community
Default TwinProp=A2A Piper PA-24-250 Comanche N6229P <-> community
Default Airliner=A300-600RF GE iniBuilds House Livery <-> community
Default Rotorcraft=A2A Piper PA-24-250 Comanche N6229P <-> community
Default Glider=A2A Piper PA-24-250 Comanche N6229P <-> community
Default Fighter=A2A Piper PA-24-250 Comanche N6229P <-> community
Default Bomber=A2A Piper PA-24-250 Comanche N6229P <-> community
Default FourProp=A2A Piper PA-24-250 Comanche N6229P <-> community

or place below which would be the correct and expected result:

Default SingleProp=A2A Piper PA-24-250 Comanche N6229P <-> community
Default TwinProp=Dornier DoJ Cabina Aviators Club Livery <-> MSFS2024 typeclassifiers
Default Airliner=A300-600RF GE iniBuilds House Livery <-> community
Default Rotorcraft=Magni M24 Plus White <-> MSFS2024 typeclassifiers
Default Glider=DG LS8 <-> MSFS2024 typeclassifiers
Default Fighter=North American T-6 Texan Reno <-> MSFS2024 typeclassifiers
Default Bomber=Dornier Do-31 E3 Experimental <-> MSFS2024 typeclassifiers
Default FourProp=Junkers Ju52/3m Modern <-> MSFS2024 typeclassifiers

It is really after multiple tests that we found this case, quite difficult to reproduce, it was from the desire to analyze more closely what happens with a brand new user who starts with JoinFS2024.

By the way, if this can give you a clue, if I close JoinFS2024, then if we delete the file "matching - Microsoft Flight Simulator 2024.txt", we restart JoinFS2024 having kept "Scan at launch" checked or in "settings/Model scan on connect" checked. I get the expected result!?

We can also very well manually restore everything according to what we want and afterwards it works very well.

Now, somewhat paradoxically, another observation, if we uncheck "MSFS2024" to know how many aircraft we have listed in "community", we do not get any message or count. On the other hand, if we check "MSFS2024, the count is displayed and correct (it includes aircraft from community and FS2024). As it is in a test context, there is little logical reason to make this choice, this without knowing the complexity and if it is worth finding a solution, it is up to you to see.

We also looked at the impact this has on aircraft detection (D) and assignment (A) and substitution (S) in the "View/Aircraft" window. The MSFS2024 classification system, works really well and has a very positive impact on aircraft autodetection by type and assignment on networked aircraft of other simulators.

As we have done a lot of testing, we have observed the same difficulty as in FS2020 concerning X-Plane and PMDG aircraft, (the latter seem to use more or less correct "livery" not having a "ui_typerole". Thus, these two cases do not seem to have a type classification and are seen as being by default "singleprop" and are classified as such by JoinFS2020 and JoinFS2024. On occasion some PMDGs with strange "livery" are not substitutable, but they are detectable (D), a lesser evil. Again, these cases are identical in JoinFS2020. I was just to inform you. It is not major, and we probably can't do much about it.

There you go! Hoping that this can help you as best as possible. Once again, thank you very much for the excellent work, really very well done. It is reassuring for the future of JoinFS.

We wish you a great 2025.

geobouimg07
ImaginairVirtuel.

[geobouimg07]

Oups! @tuduce, I forgot, just to let you know, (for users who are not computer savvy) the installation wizard does not create a shortcut on the Windows desktop during a first installation. You have to create it manually.

In addition, we have done tests with different versions of MSFS2024 (Standard, Deluxe, Premium, Aviator's . The list of aircraft is consistent with the version used. Which is completely logical and desirable. Which leads to the conclusion that the method used is on the right track.

I don't know if you plan to implement the languages ​​(de, es, fr, etc.), if so, I can also collaborate to check the French version.

Kind regards.

[tuduce]

Hi @geobouimg07

Thanks for the detailed test-report. I will split the feedback across a couple of issues to track them better. When I mention you in my issues, do you get notified? At the latest, when I will look into the X-Plane problem, I will have some questions.

Until then, as they say in my neck of the woods: have a good "slide" into 2025!

Best wishes!!

[geobouimg07]

Hi @tuduce,

Thank you very much for all these follow-ups. Yes, in answer to your question, if I am notified when you mention me in your issues.

Have a good slide in 2025 too! See you soon.