Peter wrote:I have just updated the TEST version of JoinFS with some fixes for FS2020 support.
For details on installing the TEST version see this thread,
viewtopic.php?f=2&t=491
To get this working I just had to do a workaround for enumerating the aircraft titles that FS2020 needs to inject new aircraft. You should now be able to scan for the aircraft models by choosing the simulator folder as the folder where you have your packages installed. The old workaround of using the additional folders is no longer needed.
There are just a couple of minor annoyances. First, the substitute window doesn't combine the variations into each aircraft, so all variations are listed in the type option, and the variation option is just a duplicate of the type selected. Second, in FS2020 there are some aircraft that are locked down by DRM and so JoinFS is unable to enumerate these during a scan. However, I have done a workaround so that at any time JoinFS sees an aircraft in the simulator that it doesn't know about it will add the aircraft to the list. The effect of this is that when another network player connects with an aircraft that you have never loaded yourself, it will use the default substitution. All you need to do is load up yourself in that aircraft temporarily then you should find that it now appears in the JoinFS model list. Then just re-substitute. You should only need to do this once for each aircraft type that is DRM protected.
Hopefully this should all work fairly well. Keep an eye out for any other odd behaviour. I'm assuming that you no longer need to limit to 35 fps with FS2020. Please let me know your findings here.
Peter
Hi Peter (long time since we spoke last, hope you are well !),
Superb progression with MSFS 2020 support mate!
A small bunch from our group tried this version last evening.
I have a version of JoinFS running on a separate pc dedicated to acting as a server for the rest of us. Then I connect (same location on another pc with the same external IP address). After that, external users (our flying group members) connected. Then we all started our sims (MSFS2020 x 4 and ONE P3Dv3 member). Each had successful NETWORK and SIMULATOR green connections. Each had successful scans for models. We ALL could see each other in the sim in the correct aircraft and we had a stable connected flight, no issues.
There was NO NEED to create or use GROUPS within MSFS 2020 - EXCELLENT !!!!!
The P3D user could see labels of the other aircraft.
The MSFS 2020 users see no labels (understandable). However, a way of doing this would be useful.
We did not look at the MSFS 2020 map to see if we could see other users (I suspect that would not show up). Will do next time !!
We all use Plan-G and the latest Alpha Version 4.0.0.232. That was not showing any other users (but to be fair this version was not doing that anyway even in MSFS 2020 group flights as yet, as it also is in early stages of adaptive development too). Will there be anything from your side that would need to be done to allow Plan-G to "see" the local and remote users in the sim? I suspect not and that this is still a Plan-G issue?
To be fair..... this early version has functionality that does allow our group to all fly together (we only have P3D and MSFS 2020 users).
So, WELL DONE sir. Many thanks from us at MDA Flights
