[CAN NOT REPRODUCE]WP SEQ insert bug

[Swift.]

When inserting a waypoint into the middle of a sequence, the inserted waypoint will always show as WP0 regardless of which number is entered.

 

Timestamped video showing the behaviour of the bug:

 

INS>7>8 should place wp8 just after wp7, but instead it puts wp0 after wp7

[Ziptie]

Is it because your alignment isn’t complete yet?

 

 

Cheers,

 

Ziptie

[Swift.]

Is it because your alignment isn’t complete yet?

 

 

Cheers,

 

Ziptie

 

It's never behaved like that before

[Ziptie]

 

It's never behaved like that before

 

Odd. I read in another thread (somewhere it's buried by now but it was regarding the new alignment process) - where the alignment has to be completed before manually entering any waypoints otherwise there can be an issue.

 

Regardless, I just flew today and input 10 manually entered coordinates and didn't experience the same issue your video showed - so not sure what was going on there for you.

 

Side note: I followed your advice for not disengaging the NWS for an airfield takeoff in the Hornet and it was just fine, so thank you for that.

 

 

 

Cheers,

 

Ziptie

[Swift.]

To reproduce:

Select a sequence without wp0 (eg seq with del0 or seq2/3)

Insert 2 WPs,

attempt to insert a WP between the two existing WPs (SEQUFC>INS>precedingWP>WPtobeinserted)

WP to be inserted will show as 0

 

 

To note:

Happened in Hotstart, INS in IFA

WPSEQbug.trk

[Swift.]

Track provided^

 

[BIGNEWY]

Seems ok to me swift, in the picture example I add a 5 after 1 in the sequence after doing number 4

 

[Swift.]

Hmm very strange, I was testing on Nevada. I will see if I can find out more about the failure conditions, as it was very reproducible for me.