Wise87 Posted March 22, 2023 Share Posted March 22, 2023 Looks like the recent update to Sim Update 12 for MSFS2020 has caused AvlaSoft EFB to read AI aircraft with a strange text instead of by the aircraft type. Is anyone else seeing this? Quote Link to comment Share on other sites More sharing options...
aivlasoft Posted March 23, 2023 Share Posted March 23, 2023 I can't reproduce it here. AI traffic, generated by MSFS, appears with correct aircraft types (EFB v2.3.136, MSFS v1.31.22.0). Are you running a third-party-tool which generates traffic? Are you running the latest version of EFB Server and Client? Have you already looked at the Server's traffic monitor? Maybe you could assign another field number for the type? Quote Link to comment Share on other sites More sharing options...
Wise87 Posted March 23, 2023 Author Share Posted March 23, 2023 52 minutes ago, aivlasoft said: I can't reproduce it here. AI traffic, generated by MSFS, appears with correct aircraft types (EFB v2.3.136, MSFS v1.31.22.0). Are you running a third-party-tool which generates traffic? Are you running the latest version of EFB Server and Client? Have you already looked at the Server's traffic monitor? Maybe you could assign another field number for the type? I am currently using FSLTL and AIG for model matching while on Vatsim. Yes I am running the latest version of the client and server. Good idea, I will check on my next flight and report back. Quote Link to comment Share on other sites More sharing options...
Wise87 Posted March 24, 2023 Author Share Posted March 24, 2023 Support I wanted to add a few more findings. I decided to fly the Fenix A320. Before the SU12 update Aivlasoft EFB read the profile without an issue. Now it reads it as default. I have also provided a screen grab of the Server's traffic monitor. My setup isa clean install. I'm suprised no one else has mentioned this. Quote Link to comment Share on other sites More sharing options...
Avgo404 Posted March 24, 2023 Share Posted March 24, 2023 I have the same problem. Before SU12 the Fenix A320 was recognized and now it becomes the default profile. Quote Link to comment Share on other sites More sharing options...
aivlasoft Posted March 24, 2023 Share Posted March 24, 2023 Thanks for the screenshots. It seems that this is a Fenix issue, not EFB. All other aircraft provide a meaningful text in the model column. Quote Link to comment Share on other sites More sharing options...
Wise87 Posted March 24, 2023 Author Share Posted March 24, 2023 On my photo attached the 3 model down is not correct. I am also seeing more aircraft display the long model text over the last few days. As far as the Fenix, they have made no change to the model and it worked the day prior to SU12 being released. I’ll post this issue on other sites to see if other users are seeing this and have them report here with their findings. Also the Maddog shows as default and it worked before SU12 also. Quote Link to comment Share on other sites More sharing options...
Berzerker Posted March 25, 2023 Share Posted March 25, 2023 I'm also experiencing the same thing, using FSLTL and FS Traffic too. I'm not so sure this is a plane issue to be honest. Quote Link to comment Share on other sites More sharing options...
aivlasoft Posted March 25, 2023 Share Posted March 25, 2023 I will try to implement a fix with next EFB update. To be honest, slowly I'm getting upset because of these ongoing inconsistencies with each update of MSFS. Quote Link to comment Share on other sites More sharing options...
savery Posted March 25, 2023 Share Posted March 25, 2023 I have the same issue, I can see your frustration... Quote Link to comment Share on other sites More sharing options...
zacks16 Posted March 26, 2023 Share Posted March 26, 2023 Same for me with Fenix... Quote Link to comment Share on other sites More sharing options...
bullo82 Posted March 26, 2023 Share Posted March 26, 2023 Happening the same here since SU12. Apparently EFB is taking the value "ATC_TYPE" instead of ICAO value from the aircraft cfg, or apparently is the simulator who is publishing the different field. If you check in the aircraft.cfg for Fenix for example fnx-aircraft-320 location at SimObjects\Airplanes\FNX320 aircraft.cfg atc_type ="TT:ATCCOM.ATC_NAME AIRBUS.0.text" atc_model ="TT:ATCCOM.AC_MODEL_A320.0.text" While the values for icao_model are not "text" between "" and they have these values icao_type_designator =A320 icao_manufacturer =AIRBUS icao_model =A-320 Something seems to be different since SU12 and we need to do more testing here. Quote Link to comment Share on other sites More sharing options...
aivlasoft Posted March 27, 2023 Share Posted March 27, 2023 11 hours ago, bullo82 said: Apparently EFB is taking the value "ATC_TYPE" instead of ICAO value from the aircraft cfg Negativ. As you might have overseen in the screenshots above, the cryptic names do not start with "TT:". @all: Could you please let us know the versions of the FENIX-Airbus, and also from FSUIPC7. Thanks. Quote Link to comment Share on other sites More sharing options...
zacks16 Posted March 27, 2023 Share Posted March 27, 2023 1 hour ago, aivlasoft said: Negativ. As you might have overseen in the screenshots above, the cryptic names do not start with "TT:". @all: Could you please let us know the versions of the FENIX-Airbus, and also from FSUIPC7. Thanks. Hi, for me, Fenix Version is 1.0.6.146 and FSUIPC7 V7.3.19 (not register). Thank you. Quote Link to comment Share on other sites More sharing options...
dawgfan58 Posted March 27, 2023 Share Posted March 27, 2023 I'm having the same issue. All types of aircraft. I use fsltl model matching on vatsim only. Quote Link to comment Share on other sites More sharing options...
aivlasoft Posted March 28, 2023 Share Posted March 28, 2023 @dawgfan58 Did you read my post above, regarding file versions? Quote Link to comment Share on other sites More sharing options...
Wise87 Posted March 31, 2023 Author Share Posted March 31, 2023 Fenix Version is 1.0.6.146 (latest) and FSUIPC7 V7.3.19 (register). Maddog, 1.2b152 Quote Link to comment Share on other sites More sharing options...
lonewulf47 Posted March 31, 2023 Share Posted March 31, 2023 Well, it seems to me that only users with additional 3rd party software (FSLTL, FS Traffic) are affected. I do not use either and do not have any such issues. I use Fenix v1.0.6.146 and FSUIPC 7.3.19. So go figure... Quote Link to comment Share on other sites More sharing options...
dawgfan58 Posted April 1, 2023 Share Posted April 1, 2023 Fenix Version is 1.0.6.146 fsuipc 7.3.19 Quote Link to comment Share on other sites More sharing options...
Berzerker Posted April 2, 2023 Share Posted April 2, 2023 Is there a workaround for now where we can add the malformed module name to the profile and get it working? I tried adding ATCCOM.AC_MODEL_A320.0 to the list of acceptable airframes but it's still not recognizing it. Or is there a way to disable the automatic profile selector? Quote Link to comment Share on other sites More sharing options...
aivlasoft Posted April 2, 2023 Share Posted April 2, 2023 Obviously there are two different issues discussed in this thread. First, the name of the currently loaded aircraft in MSFS, and second, the names of AI aircraft provided by MSFS. Regarding issue #1, I have the latest version of Fenix' A320 running (v1.0.6.146) and FSUIPC7 v7.3.19 is installed. On the next screenshots you can see that the ICAO type designator is properly detected by EFB: Regarding issue #2 I can only say that the malformed names are the names of AI traffic and not the name of the own ship. Although these names are created beyond the scope of EFB, I have implemented some 'filtering code' which is trying to extract the ICAO type designator from these malformed names. It will be available with next update which is planned to be released soon. Until then I don't see a workaround except to pause the AI generation by the aforementioned third party tools. Quote Link to comment Share on other sites More sharing options...
Berzerker Posted April 3, 2023 Share Posted April 3, 2023 21 hours ago, aivlasoft said: Obviously there are two different issues discussed in this thread. First, the name of the currently loaded aircraft in MSFS, and second, the names of AI aircraft provided by MSFS. Regarding issue #1, I have the latest version of Fenix' A320 running (v1.0.6.146) and FSUIPC7 v7.3.19 is installed. On the next screenshots you can see that the ICAO type designator is properly detected by EFB: Regarding issue #2 I can only say that the malformed names are the names of AI traffic and not the name of the own ship. Although these names are created beyond the scope of EFB, I have implemented some 'filtering code' which is trying to extract the ICAO type designator from these malformed names. It will be available with next update which is planned to be released soon. Until then I don't see a workaround except to pause the AI generation by the aforementioned third party tools. So for issue #1, will the workaround implemented for issue #2 alleviate this as well? Those of us also on the same Fenix and FSUIPC version are seeing a different identifier in the EFB, so clearly there's some issue here (though I agree probably not with the EFB). Either figuring out the proper addition to add for the A320 profile or having a way to disable the automatic profile selector would be a more-than-good-enough workaround for now. Quote Link to comment Share on other sites More sharing options...
aivlasoft Posted April 3, 2023 Share Posted April 3, 2023 Quote So for issue #1, will the workaround implemented for issue #2 alleviate this as well? Yes, it should. 2 hours ago, Berzerker said: Either figuring out the proper addition to add for the A320 profile or having a way to disable the automatic profile selector would be a more-than-good-enough workaround for now. You can find the required name in the Server's log file (see next screenshot as an example). Just add the name which is displayed to the already listed names in the respective profile. Quote Link to comment Share on other sites More sharing options...
va3fyc Posted April 7, 2023 Share Posted April 7, 2023 Thank you, Urs for working on the fix for #2. Much appreciated! Quote Link to comment Share on other sites More sharing options...
dualznz Posted April 16, 2023 Share Posted April 16, 2023 yup same for me on fstl traffic for fbw320 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.