This forum is no longer active. Reference only.

Peter, with MFS (2020) the new v1.7.4 version of JoinFS scanning seems to wipe out and replace the previous "models - Microsoft Flight Simulator 2020.txt" rather than augmenting it. This has at least one drawback. Our group has developed the practice of introducing models of other aircraft-livery combinations by loading those planes into MFS while JoinFS was running. This seems to work. We can thus assign our fellow non-MFS Multi-Player pilots with a wide range of liveries that more-or-less match their aircraft. However, when you simply replace the "models - Microsoft Flight Simulator 2020.txt", we lose our previous entries. Would there be any way to retain those after you scan? Is there any way that we can help you?

Thanks for all your efforts. Magic!

Quick answer.... if you can get someone to save their models - Microsoft Flight Simulator.txt file, so that you have the data before they update to the latest version. Will get back shortly.

Peter

Just a couple of queries. You mention that you assign Non-MSF pilots with the liveries. How exactly were you doing that, by sending the raw models.txt data? If they were Non-MSF pilots then didn't the scan just wipe out the existing data because the retaining of models was only active for MSF pilots so I would have thought they would lose the data if they did a manual scan?

The retaining of models in MSF was only really a stopgap, as some people mentioned that it's a little bit cumbersome to have to load models into MSF just to add them to the list.

Is your set of liveries specific to anything in particular? The idea was to add a new group to the Add-On section of the scan window in order to populate the models with a specific set of models for example the Caranado ones. Would your particular set benefit other JoinFS users or do you think you need something a bit more customized? Having to load different models into MSF doesn't really seem like the best approach.

Peter

Peter. Quickly and back with more. The inquiry was to see if we could maintain the current work-around. I shall return in a bit after thinking some more. (Dangerous, that.) Mike