Hans K

OK John, that's clear. The problem is that support for EFB2 stopped some months ago although a lot of flightsimmers still use the program. I am aware that a combination of EFB2 and MSFS2024 will not be possible but as long as I use MSFS2020 as my main simulator I like to use EFB2. With your info I did a test with version 7.5.0 and MSFS2020 and when I start EFB 2 after MSFS2020/FSUIPC is established there is no problem. SOLVED. Hans

Hi, I detected something with version 7.5.0 that's probably the same. I am using a program (EFB2) that is uses FSUIPC to interface with MSFS2020. I installed two separate versions of FSUIPC but since then I am getting messages from EFB2 that a wrong simulator is running (so not MSFS2020). However the program is working fine, only these messages (every 5 minutes) are annoying. Today I installed the version 7.4.18 for MSFS2020 and the messages are gone. The only thing now is that I am getting a message that a new version is available. Hans

I see the reason why there was an adjustment. No problem, and with the extra line in the .ini there is a acceptable solution. But from a technical point of view it is interesting what the reason is. Today I did two additional tests:. One was online flying so the traffic was injected by the network. That network is not as big as the two major ones but the technology is in principle the same as VATSIM and the pilot client is also the same. The behaviour of the AI traffic in my EFB2 application was the same as by the two test former test with external AI sources: Without the fix no en-route traffic visible, with the fix all traffic was visible. The other test today was flying in a environment where the AI traffic was generated by MSFS2020. In this situation the fix was not necessary: all trafic was visible with the default 7.4.18 version so without the fix. So it seems that there is a difference in the way AI traffic is injected by external sources (or handled by MSFS) compared to the internal traffic of MSFS2020. Regards, Hans

For your information: In the meantime I did a test with traffic generated by FSLTL and a second test with traffic generated by Beyond ATC. The behaviour of traffic in EFB2 is the same. Without the extra setting only visible traffic on the ground, with the extra setting all traffic is visible. Next week I will fly together with friends on a network but I expect the same results. Regards, Hans

The installed version of FSUIPC I had was indeed the correct version (3 nov). So I added the mentioned setting in the General section of the FSUIPC.ini file and made a short test flight. It seems that this is the solution because after takeoff I saw all AI traffic on my EFB2 screen. Thanks for your support. I will inform a handful of other flightsimmers here who had the same problem. Regards, Hans

Hi John, Thanks for the very quick response. I am pretty sure I have the correct version but I will check that tomorrow and will add the line in the .ini. I will report the results. The sim is working so I can live with it for the moment and am not in a hurry. Regards, Hans K

For many years I have been using Electronic Flightbag (EFB2) from Aivlasoft. One of the functions is that I can see my fellow pilots and AI traffic on a map. That has always worked fine but after the update to FSUIPC7 version 7.4.18 I still can see the traffic when I am on the ground but as soon as I have taken off I see no surrounding traffic in EFB2. I do see that traffic on my ND in the cockpit and also "physical" when it is not too far away through my cockpit window so it is in the sim. I then rolled back to version 7.4.17 and everything worked again as it always did. So it apparently has something to do with a change in FSUIPC. Can someone give me a hint how to solve this? Regards Hans K