Possible Time on Station/Carrot Bug
-
Might be the issue about CAS lock being reversed (green locks is unlocked). Check leg distance and ensure proper timing on WPT based on your desired speed:
IE: Leg 35Nm … 420KTAS is 7Nm/min, so from WPT2 to WPT3 => 35/7 = 5min.
If your WTP2 is at 10:00:00, WTP3 must be 10:05:00
-
Link is not valid on my side.
Hi Dee-Jay,
I have now attached the mission files as a zipped attachment - link works (or at least it does on my side)-S
-
Hi Dee-Jay,
I have now attached the mission files as a zipped attachment - link works (or at least it does on my side)-S
On my side it points to my own Dropbox. Anyway, try what I suggested above.
-
On my side it points to my own Dropbox. Anyway, try what I suggested above.
Hi Dee-Jay, no i mean i have got rid of the drop box and added the files as a zip via the proprietary attachment for this forum - should work now?
-S
-
Might be the issue about CAS lock being reversed (green locks is unlocked). Check leg distance and ensure proper timing on WPT based on your desired speed:
IE: Leg 35Nm … 420KTAS is 7Nm/min, so from WPT2 to WPT3 => 35/7 = 5min.
If your WTP2 is at 10:00:00, WTP3 must be 10:05:00
Hi Dee-Jay,
I think this appears to have solved it (the CAS lock being reversed). Many thanks :bowd:[[B]Edit note: I think this worked because I had deleted steerpoint 2 and 3, replacing them with new steerpoint as well as taking off the green padlock for speed - better resolution posted below by Dee-Jay]
-
Ok, got it now.
Indeed , the time from 2 to 3 is inconsistent. 70Nm @420KTAS should takes about 10min …
Is your TE created from scratch or is it converted from an older version?
-
Something is corrupted in your TE.
Go in Mission Commander, load your TE then edit your WTP3 … just lock then unlock it (or simply double click on the WTP3 then close the window) … you will see that the timing will change from 12:22:48 to 12:16:48 (now it is correct … about 10min after WTP2!) … Redefine speed/timing for the first leg (unlock speed and timing in MC first) … save, and you’re good to go.
Please tell me if it was a TE build from scratch, if it is a conversion from an older version (4.33?) and/or if you have edited it with MC before … that could help me to reproduce/troubleshoot.
EDIT: … mmm … still some troubles with this WTP3! … looks really corrupted. Will have to dig more.
-
Something is corrupted in your TE.
Go in Mission Commander, load your TE then edit your WTP3 … just lock then unlock it (or simply double click on the WTP3 then close the window) … you will see that the timing will change from 12:22:48 to 12:16:48 (now it is correct … about 10min after WTP2!) … Redefine speed/timing for the first leg (unlock speed and timing in MC first) … save, and you’re good to go.
Please tell me if it was a TE build from scratch, if it is a conversion from an older version (4.33?) and/or if you have edited it with MC before … that could help me to reproduce/troubleshoot.
EDIT: … mmm … still some troubles with this WTP3! … looks really corrupted. Will have to dig more.
Hi Dee-Jay,
Yes this was a completely clean mission built from scratch in 3.34 (I only installed BMS last weekend).-S
-
Roger.
If you look at your WPT3, if you set it back as “Hold”, you will see 6min holding. Even if you set it 00:00, the 6min remains in the flight plan, and if you switch it to WTP2 then back to WTP3, you will see that the modification is not taken in account and still shows 6min. So my best advice for the time being is to keep is as Hold.
We will investigate on our side.
Thank you for report!
-
… ok, found how to solve.
If you look at your briefing page, you will see that the WTP2’s comment shows that it is and Holding! I don’t know why and will try to repro.
Simply delete the WTP2, and re-create it. It should be alright.
Another way to solve the issue, set the WPT2 as “Hold”, set holding time 00:00:00, then set it back to “Nav”.**EDIT:
Bug found.
If you change a “Hold” type point into “Nav” point, the holding duration is not nulled!!! … so either delete the point and create another one, or … set hold duration to zero prior to change it into “Nav” type.
I will open a bug-tracker for it!
Very good catch Sharpe!!!**