FSR500 never brought the SID or Stars from simbrief back via my EFB in msfs 2020, and will not in msfs 2024 since the code is the same.
SID and Stars are the pilot responsibility since they can change at any point depending on circumstances such as weather or ATC preferences and therefore I never sent those.
Now if some way points are not coming through it means i cannot find them in the msfs nav data, so perhaps you are not updating the nav 2024 databases via navigraph?
I suggest you try a different flight plan and test again, all my flights plans from SB worked fine fir me in msfs 2024 without any problems.
Regarding bringing in a flight plan from the Asobo EFB, I have the exact same problem in the G1000 172. It works fine in the GNS 530/430 though, so seems to be some G1000 specific bug.
In the case of FSR500, you cannot bring a flight plan from the msfs EFB dynamically, this is because it is a msfs 2020 aircraft working in compatibility mode.
Compatibility mode provides backwards compatibility not forward compatibility, this means it will works exactly as it did back in msfs 2020, where a msfs EFB didnât exist.
In order to use the msfs EFB flight plan, you need to do the plan in the main flight menu (just like back in msfs 2020) and then start the flight, then, the msfs EFB flight plan will automatically appear in the G1000, againg just like it used to work back in msfs 2020.
It is important to clarify this is the case with any msfs 2020 aircraft working in msfs 2024, which are using G1000 V1. Similarly, G3X V1 would exhibit the same behaviour, this means all my current offerings are going to be affected like this as well (Sting S4, TL3000).
It is also important to understand in order to sync dynamically with the msfs EFB we 3rd party developers will have to convert the products to msfs 2024 native.
However the previous post I believe was related to the FSR500 EFB simbrief import capabilities instead of the MSFS 2024 EFB, but I wanted to bring awareness about how V1 avionics would behave vs V2 avionics in msfs 2024 since is all by design of Working Title and Asobo.
As Raul stated above, I was trying to use the SimBrief import functionality within the FSR500âs bespoke EFB, not the simâs EFB.
I ended up just giving up and flying in 2020, again. The basics work there. Perhaps someday 2024 will be able to do the most basic of things right for me.
The challenge right now is that many 2020 aircraft, either deliberately upgraded to be forward compatible, or happen to work mostly without change, in FS24, arenât EFB âawareâ or compatible.
A backwards compatible aircraft from msfs 2020 would be using V1 of avionics and cannot be msfs EFB aware.
Is a limitation, but if you load the flight plan from the main menu, it will sync automatically when you load the flight.
There is nothing we can do, we need to fully convert, it is what it is, we cannot expect a code from msfs 2020 to be able to fully use the new technology of msfs 2024, the code needs to be upgraded for that.
If anyone would like to follow up my roadmap for conversions please join my discord as it is my official channel of communications and I can interact mive to answer questions and doubts.
With yours perhaps, but I have seen others where even that doesnât work, for G1000 powered planes. Not your concern, or responsibility, just explaining that a flight plan on the map screen does not always appear as it should in some G1000 planes.
I fly the FSR 500 and it works really well in MSFS 2024.
However, I noticed that when I lowered the landing gear, the view changed to show the belly of the plane and I watched the gear unfold. Once gear was fully extended it switched back to cockpit automatically.
