[BUG] Home base waypoint incorrect via Jester via F10 map

[earnil]

Hi Heatblur!

I think there's a problem with setting up Home Base waypoint via Jester via F10 map.

 

How to recreate:

1) Cold startup

2) No predefined waypoints

3) use F10 map to create waypoint

4) use Jester to set that mark as Home Base waypoint.

 

As shown from attached pictures, while Tunb Island, which is the intended Home Base is bearing 228 degs, HSI shows something over 130 degs. Range is correct.

 

Attached is track file and the pictures.

 

While I didn't do it in the track attached, same thing happens if I use manual input and just input the coordinates directly.

Also, WP1 and WP2 are being shown correctly, with correct bearing and range.

I think there's same issue with Defense point WP, but I haven't tested it extensively.

F14 INS Test 2.trk

Edited November 30, 2019 by IronMike

[bonesvf103]

I also noticed this and posted about it in another thread and several other people noted they have the issue as well:

 

 

Whatever is your current waypoint, the Jester menu shows it as being +1 that waypoint. ie, if you tell Jester to select WP1, and he says OK and does it, the next time you open the Jester menu, it will show Current Destination WP2.

 

So, is that a bug or am I missing something?

 

 

v6,

boNes

[earnil]

If anyone is struggling with this, I wanted to post a short update here with a workaround

 

First, there appear to be 2 distinct bugs

1) Under certain conditions, Jester seems to input desired waypoint coordinates as your plane's actual position, breaking the alignment

2) When selecting waypoint, the waypoint selection works ok, but then the wheel shows incorrect information as bonesvf103 mentioned.

 

Regarding the 1) this seems to work for me almost 100% of the time:

During startup, after your engines are both up but BEFORE you continue and before the INS alignment is past first stage, ask Jester to enter WP1.

Then follow through the startup, wait until alignment is complete, until Jester says 'ready to taxi' and then you can start to input other waypoints. When you go through the startup, once you power on HSD you should see correct distance an bearing to WP1

ALWAYS input just 1 at a time. Let Jester finish it, then input another.

Keep the HSD in NAV mode as you enter the waypoints

Don't change WP1

 

Following these steps, I can now use the waypoints freely without messing up the alignment. I cannot say if all of these are necessary or if the timing is bit more loose (like adding WP1 during INS alignment seems to work too) but this is what works for me.