Version: SU2 - 1.4.18.0
Frequency: Consistently
Severity: Blocker
Context: Sting S4 and Sirius TL3000
Bug description:
Any aircraft MSFS 2020 using avionics V1 are now unable to load the flight plan from the main menu as they used to be able to do it since MSFS 2024 release.
Repro steps:
Create a flight plan in the main map with the MSFS 2024 EFB, click send to avionics, load the flight.. you will see the G3X avionics are not getting the flight plan as they used.
I believe V1 only requires you send the Plan to ATC Raul. That emulates the Load Flight Plan behavior at World Map in FS2020. At least, that’s what I heard.
Send to Avionics only applies to V2 generation FMS.
This was working as I described from release, so, something changed now.. I am getting customers saying they are unable to get any flight plan in the G3X..
R.
No problem. We’re talking in your Discord, so I’ll try to help out there.
Hello. I would also like to expand on this issue that I have noticed similar problems with Aera.
Even being a simple system it has been crippled as of SU1.
It can’t get flight plans from tablet as well and many core functions stoped working:
There are some other issues, but this is related to this problem by the sounds of it.
It would certanly need to be investigated.
That’s an existing instrument that needs to be revamped by Asobo versus a base issue that’s SDK related. Please submit a Zendesk ticket.
Okey, so.. after a lot of testing (thanks to CasualClick for the heads up on my discord server) we were able to make this work as long as:
A) The user is using VFR (point to point) flight plans in the G3X
and
B) The user only uses “Send to ATC” in the main map.
This way the flight plan transfers. In order to support IFR, the user must use one of the liveries with GTN (an external navigator) and then it works. (All as per design, so we good here)
However, the problems starts when the user in the main menu clicks “Send to ATC” and then clicks also “Send to Avionics” this breaks everything, the second action seems to cause a reaction where the flight plan breaks.
This was not the case few months back, I tested this myself because I used TL3000 for a group flight via MS Twich official with seedy and the comunity managers, and at that time, I used the “send to avionics” from the main menu, and I had the flight plan perfeclty in the TL3000 G3X.
So it seems, something has changed recenlty, where if the user only uses “Send to ATC” it works, but if they use the Send to Avionics in the main menu for MSFS 2020 airplanes, stuff falls apart.
This is the bit I consider revieiwing, as a work around I am instructing people to only use “Send to ATC” but as you must understand, this is very confusing for them, causing problems, so any help on this would be apreciated.
Best,
Raul
Hi, I was redirected to this post as it seems to be a general issue affecting Avionics V1 and Legacy when trying to submit a flight plan created from the EFB and based on IFR rules (VFR still works, but only to create a simple flight plan with origin and destination, but without any procedures). While creating an entire FPLN and sending to avionics, originally worked with the previous interface, active in February if i’m not mistaken (using the “File Plan with ATC” button), it no longer works with the new interface (basically, that feature was removed, and now the bugs described here occur when trying to select one of the other functions).
I can still create flight plans with procedures directly from my avionics, and that’s what I’m telling my users to do. However, I’m writing in this post because I see it’s already August, and this post has been open since May 2nd, and it doesn’t seem like this issue has been resolved. I just wanted to know if a fix is being worked on.
I understand that the EFB is an interface you created to make it easier for users to create flight plans without having to do so directly from the avionics devices. I also understand that the EFB is not bidirectional, meaning any FPLN you create in your avionics won’t overwrite anything in the EFB. But this latest change you made further restricts the compatible devices that can receive a flight plan from the EFB.
Thanks.
Sorry for resuming this old topic… but we are having similar problems with all of our planes that use the map to show the flight plan in their avionics (F-35, M-346, Tornado…and the new Eurofighter).
The issue we are having is that:
in MSFS2020 everything is fine and the flight plan is displayed correctly
in MSFS2024 the flight plan is drawn as a “drop” which immediately takes you back to the departure/arrival airport
Here is an example in our F-35 - Flight plan is created in the world map as follows:
In MSFS2020 the flight plan appears on the map as expected (starts from KEDW, and takes you to KMHV and KPMD before taking you back to KEDW):
In MSFS2024 it is drawn as a “drop” which will immediately take you back to KEDW
Hello @Scimmia1974
Does it make any difference if the flight plan is VFR or IFR?
Other devs reported VFR flight plans are loaded correctly so I’m curious to see if this is the same for you.
Regards,
Sylvain
The general problem is that all avionics based on V1 avionics or legacy JavaScript since you updated the EFB are not compatible with IFR plans created from it, while the version you had in February works. This version seems to only be compatible with V2 (VFR works, but it doesn’t make any sense to use the EFB since it will only create a flight plan with origin and destination, without ENR waypoints or departure or arrival procedures). This is what we’re all reporting. The February EFB interface worked perfectly when clicking on “FILE PLAN WITH ATC,” but in the new interface, you’ve removed that option.
In other words, this isn’t an individual issue; it’s widespread. You’ve made changes to the EFB without testing whether you’re rendering V1 avionics inoperable. It’s that simple.
Those of us who can create and manage flight plans through our avionics (whether V1 or otherwise) have no problem, we can do without the EFB (but users will tell us that our avionics is not MSFS2024 compatible for this reason). They simply will never be able to receive an IFR flight plan created from the EFB, as the submission format will be incompatible.
If you could analyze what you’ve changed since the February EFB, or restore the “FILE PLAN WITH ATC” functionality, it would be fixed:
Apologies for the late reply (due to a much needed vacation). The case I described did not involve the EFB at all.
In MSFS2020, the flight plan was created on the world map as a VFR - GPS flight plan. Works as expected.
In MSFS2024, the flight plan was created on the world map (no EFB) and looked correct on the map. Once the plane loads:
The map on the EFB is correct.
The map on the F-35 avionics (from MSFS2020) is not, and shows the “drop” shape. Also waypoints do not match (like if they have been generated separately).
Nothing has actually changed in that regard. The FILE PLAN WITH ATC was simply moved to SEND TO ATC in the new layout; it is the same function and calls the exact same API as before.
However, there were changes to the code on the sim-side made by the other teams for career compatibility that no longer push the plan to the legacy FS player flight plan, but solely to ATC. Previously it went to both.
This was flagged as a potential issue during discussion of this change and we can surface it again to the other teams and discuss internally how this can be resolved in a future sim update.
Thanks,
Matt
This is causing some grief for 3rd party devs now, I am getting emails from customers asking how to send the flight plans to avionics to our MSFS 2020 products as they are getting confused why things don’t work anymore.
I imagine they need to press also send to avionics from the main menu to get it across to V1 avionics right?
All the best,
Raul
No, SEND TO AVIONICS requires listening to the 2024-only Coherent event for this purpose. It would not be used by V1 avionics.
Thanks,
Matt
So, what we saying is, now V1 avionics never receive the flight plan? that would explain support tickets and the emails I am getting recently.
R.
Saying that definitively will require investigation on the MSFS team end; that I’m not sure of right now.
Thanks,
Matt
@EPellissier can we check this? this is pretty bad if this is the case, as pretty much renders all MSFS 2020 products unable to interact with the core flight planning tools and there is nothing we can do as 3rd party developers to mitigate or corrects the situation apart from doing a full conversion to 2024 native, which of course will take a lot of work and time.
My support tickets are coming in hot, and I am not sure what to answer at this stage, so far my testers are indicating they cannot get any MSFS EFB Flight plan towards any 2020 aircraft (including ours) which are using V1 avionics.
Unless there is a step we missing? I am trying to advice to our users what to do, but I am running out of ideas.
Best,
Raul
Well today is working:
worldscreen - efb - plan route - sent to atc and avionics… then start flight, it gets to V1 avionics.. maybe the FP is sent when you click start flight? or a fix was pushed?
Best,
Raul
Just to clarify a couple of points of our particular problem (I am under the impression we have different situations here - although the core problem seems the same, and that communication problems between 2024 EFB and planning tools and older avionics).
For what concerns the F-35:
I have retested everything right now, as we DID NOT use the EFB for flight planning on the F-35 (as it did not appear to work) but only the “VFR” map drawn on the world map.
The situation is simply that in both cases the map drawn AND the A:GPS variable DO NOT MATCH what is shown in the world map.
This is not very clear in most flight plans, but it is if the departure and arrival airports are the same (which is the typical mission profile for many military flights)…
In particular, as per my previous message:
VFR flight plan created on the World map in MSFS2020 → OK
Same “Flight plan” created on the World map in MSFS2024 → OK on the map screen (and even OK on the EFB), but KO in the plane (“drop shape” flight plan - which takes you directly back to base).
A thing I did not tried until today was creating a VFR plan in the EFB in MSFS 2024… which produced mixed results, meaning you get “some” waypoints, but at a certain point the flight plan takes you back to base “abruptly” - and the flight plan “shape” in the plane looks different from the one on the map.
It is like the logic used to generate the flight plan and map view was different from the one on the EFB and V2 avionics.
Also, the A:GPS variables seem to follow what is displayed in the aircraft map (and not the EFB).
Here is an example done as follows:
In other cases, if the departure and arrival airports are different, the situation is much better - the flight plan in the map and A:GPS variables still does not match with the EFB, but it is “roughly” the same…
