Hi all, I am experiencing an issue with the GPS system in the IconA5 but this same GPS seems to be used in the Hawk T1 and a similar issue shows up in the m-346.
Keeping with the default MS planes to reproduce this. It happens when either I create a flight plan in the world map using custom dropped waypoints, or create a .pln file through Skyvector and export to .pln
In the Grand caravan my flightplan shows up perfectly fine, In order and with my magenta line all looking good:
If I load the same .pln file in the IconA5 it is all messed up. Out of order, no flightpath linking the points and will even jump between point randomly. It seems most error prone when I make my departure and arrival the same airport.
Has anyone else experienced this? Its a shame that this happens on my favourite planes and makes route following difficult.
It seems to be something with the htmlgauge00=NavSystems/Aera/Aera.html
Packages\Official\Steam\Asobo-aircraft-icon\SimObjects\Airplanes\Asobo_Icon\panel\panel.cfg
Thank you for including your flight plan. It helped!
The World Map created MSFS flight plan file (.pln) structure is different than .pln files created outside of MSFS. There are internal differences that may not be evident users. These differences may cause problems like you are having with different FMS/autopilots.
These differences are easy to fix. Take your flight plan created by SkyVector and load it into the World Map. Without making any changes, go to the Load/Save menu. Save the flight plan with a different name. Return to the World Map and Reset the flight plan. The airports and waypoints will be removed. Go to the Load/Save menu and load the new flight plan .pln file you just saved. You will then be returned to the World Map and can start the flight. When you saved the flight plan, the World Map flight planner added everything needed by MSFS.
I tested this with the C208 and the Icon A5. Both loaded the new flight plan correctly. I donāt have the other aircraft you mentioned so I could not test with them. Also, you mentioned that the SkyVector plan worked in the C208. The C208 has the new Garmin G1000Nxi that incorporates a new flight planner in the FMS. It probably made the same changes to make the flight plan work. Other aircraft that do not have the Garmin G1000Nxi do not yet have the same FMS flight planner.
I hope this explanation helps. Recently in the last few updates MSFS has been changing the internals of flight plan files to incorporate needed ATC updates. This has caused some problems with non-MSFS flight plans. The solution is the same as described above. Load the old flight plan into the World Map. Save it as a new flight plan. Reset or clear the currently displayed flight plan. Load the new flight plan file.
Let me know if you have any questions.
BTW, the scenery in your flight is incredible. You created a nice little tour. Well done!
I had a chance to get to the PC. Following your directions I still have the same messed up flight plan on the Icon A5.
The steps I took:
loaded my original .pln file I linked in world map
touched nothing except save plan
saved to a new .pln file with new name
pressed backspace then F12 to reset world map
Loaded my newly saved flight plan
Fly now.
This still gives me the same issue though.
I tried starting from scratch within the world map by setting my departure and arrival to the same LSZM strip; Added a few custom waypoints in the same area of my tour.
Saved as new .pln file and then fly now.
Same thing is happening.
I also removed everything from my Community folder but that didnāt help.
I do appreciate your help, so you were able to download my file and re-save then load and it all looked good in the IconA5? I must be missing a step or something key here.
Yes, the Icon A5 loaded and flew the first part correctly. I didnāt fly the entire flight because I was distracted by a beautiful lake and I had to land the A5. I donāt think my A5 is stock. I have one or two mods, one of them for the GPS. Iāll take another look at the flight plan. I think there were changes made to flight plans in SU10. I noticed in the flight plan for the C208 had inserted waypoint altitudes as if it was an IFR plan (maybe for VFR VNAV?). Your flight plan took the cruising altitude of 12,500 ft and added that altitude to all the waypoints which is what MSFS used to do. Obviously this doesnāt work for the last couple of waypoints in order to start descent to the airport I donāt recall seeing any flight plan changes in the release notes.
Do you know what the FMS/GPS is in the aircraft I donāt have? There might be a stock aircraft with the same FMS/GPS I can try.
I created the original flight plan in Skyvector and export to .fpl file. This file has to be converted again.
Open the .fpl file in Little NavMap
From there I export the file to MSFS .pln file
I tried a few settings here, changing it to VFR. I have updated LNM to have all the airports from MSFS. I even activated the first leg to Waypoint 1 if that makes a difference.
Then in MSFS I load the .pln and re-saved it as something else to see if it includes missing components. Then load the new file and fly in the ICON A5.
It still seems to point me toward WP11 first with a strange roundabout way for the rest of the route.
For a second test I did it all inside the world map. Departure and arrival to LSZM, and added waypoints by clicking the map and āAddā. test.PLN (3.0 KB)
Same for the other planes that use the Aera GPS in panel.cfg. Iām guessing this is just an issue with MSFS and the default Aera GPS. hopefully there is something they are working on. I did read that the underlying GPS and NAV code was being reworked so maybe it will help with this.
Thanks! Iāll try your test.pln. The Garmin G1000Nxi was added in SU10 replacing the stock G1000. The flight planner was updated for this change but there shouldnāt have been any impact for the other FMS/GPS in stock aircraft. Iāll let you know what I find.
I tried your test.pln file with interesting results. The G1000Nxi read the flight plan correctly. I tried it in the ICON A5 and had the same problem you mentioned. For some reason the flight plan map in the aircraft was pointing to the last waypoint as the first waypoint to fly to then land at the airport. The FMS had loaded the entire flight plan but broke in the FMS. I was able to quickly fix it by selecting the first waypoint and then activating the leg to fly to it. Then the FMS āreadā the rest of the flight plan correctly.
The only thing I can think of is the use of the same departing and arriving airport and user created waypoints. I looked at the test.pln and all the waypoints had the same name. There MIGHT be a problem with the FMS. The flight plan works correctly in the G1000Nxi so it SHOULD work the same in all the others. You might want to try using different names for each waypoint. If the World Map created the flight plan with the same waypoint names might not be a bug or it mightā¦ If it isnāt a bug, it is very confusing.
Interesting, I am glad you were able to reproduce this. Your work around sounds promising but I have not found a way to Activate Leg. Is there a button or series of buttons you pressed?
I can click flightplan on the A5 GPS side bar and see the waypoints in the proper order here but there is no obvious way to activate a specific leg.
In the flight plan menu I press the three bar button that is just to the right of the screen on the GPS device but only a few options show up when I either have a waypoint or none selected.
They replace the stock Garmin Aera with the G3X Touch which includes a working autopilot. The information in my previous post was using these mods.
I temporarily removed these mods and tried your flight plan again with stock Garmin Aera. I recreated your problem. The Aera is broken and has been broken for a long time. I donāt know if this problem has been sent to Asobo through ZenDesk. I think most users install the two mods as a āfixā instead of waiting for an official one to be delivered.
