In the TBM when I load a flight plan directly into the the G3000, go out of the flight plan and back in again I am getting a message as follows :
Any help appreciated
Happens to me sometimes too, not sure exactly what causes it.
1 Like
Yes I too would like to know exactly what it means, I suspect it may be indicating the current flight plan has a redundant or contradictory waypoint or other fly to point…ie. flight plan waypoints…A-B-C-‘C’-D.
I managed to solve the issue. I cleaned out my Community file and rebuilt it and the issue corrected.
Are you saying you removed all mods from your community folder?
Then you replaced them?
Yep, did it a few at a time and discovered an add on called Global Ships was causing issues but, I also re installed the G1000 and G3000 fresh.
If you work with a lot of mods you might like using OVGME…freeware.
v0.7.4
New Features
[**GTC] The Flight Plan page will now provide warnings when the system detects that the FMS active flight plan is desynchronized from the sim’s flight plan.
So what does this actually mean and how can it be corrected?
1 Like
It seems when you insert a WP incorrectly placed you need to delete it if you have more than 1 of them…this is just an example of what can cause the warning.
1 Like
Thanks for the suggestion, I will double check the plans when I put them in.
Did anyone figure out what causes this warning? I just acknowledge OK and continue! Not sure if this is the proper procedure?
No, I haven’t. Yesterday I entered a flight plan after only setting a departure point only.
Entered the flight plan and got the message, so I really don’t know what goes on.
If I discover anything I will post it here.
I think I have the solution to the issue with of the message relating to the G3000 flight plan.
when entering the flight plan and you have something like this : YMEN ESDAN ML H129 DOSEL
W569 AY YMAY, do the following.
Enter the origin and destination. After that enter waypoint, in this case ESDAN then ML, from here left click on ML ,the side window opens and add airway (H129) then select the exit point, in this case DOSEL and then click on ADD AIRWAY. At this point another airway needs to be added, so left click on DOSEL, side window opens and add airway (W569) and select exit AY then click ADSD AIRWAY.
So in short you need to add waypoints and airways as you go, don’t go back to add airways after adding waypoints
Hope this is clear enough for everybody. If you don’t understand some part of my explanation let me know and I will try to explain it a bit clearer for you.
I may suggest that you try this flight setting up at YMEN park position 9, fire up say the TBM and input the flight plan as it is shown.
Best of luck
I did a flight from LSZH to LOWI (Zurich to Insbruck) yesterday in the TBM 940 and got the message again. This flight plan did not contain any airways (LOWI - KOLUL - DEGES - GAMSA - MADEB - ELMEM - LOWI).
So I don’t know if you were saying that this issue only occurs with entering airways AND waypoints? But I will try your flight later
I performed the flight from YMEN to YMAY and loaded the flight plan as you recommended. I did NOT receive the message then. However, as soon as I entered the departure and arrival procedures, the warning message was re-appearing. So I just clicked OK.
1 Like
I will try the flight again and enter arrival and departure procedures after the plan is loaded. Wil get back to you.
I entered departures and arrivals after doing the flight plan with no issue.
When you load a flight just load to your departure airport, don’t put in your destination on the world map page. This may cause a conflict as it automatically loads a plan for GPS or whatever.
Can I also suggest maybe delete the G3000 mod and reinstall it in the community folder.
That’s exactly how I load a aircraft into the sim: World Map - Departure Airport - Stand - Weather Selection - Fly Now. This is also how I use it in the FBW A320Neo and load the FP via the MCDU and SimBrief.
I will try it with the G3000 mod re-installed.
Thanks for Info
Did re-installing the G3000 solve the problem for you?
No, still the same problem
Thanks for follow up
Maybe with next update?