Jump to content

Recommended Posts

Posted

Been a while since I flew the Harrier, thought I'd hop in yesterday. Lots to get back up to speed on, but one of the weirdest things I've encountered is that I can't seem to manually increment the waypoints. Pressing the waypoint increment button short does nothing, nor does pressing the up or down arrows on the EHSD.

The only way I seem to be able to change my currently selected waypoint is to press either the waypoint increment button or up arrow on the EHSD long enough to bring up the QA menu and then input the desired WP number on the UFC. Now, I know RAZBAM have changed a bunch, but I didn't see anything about this changing. Is this a bug? User error? Am I the only one who's experiencing this?

Thanks in advance!

To be clear, I am not talking about changing the type of waypoint (waypoint vs. target vs. mark). I'm literally just talking about changing W1 to W2 to W3, etc.

Posted
5 hours ago, FMBluecher said:

Pressing the waypoint increment button short does nothing, nor does pressing the up or down arrows on the EHSD.

Couldn't reproduce in OB dcs-mt, can you share a short track ?

Tested single player, Caucasus map, OB 2.8.3.37556 

  • Like 1

i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440

Posted
18 hours ago, Ramsay said:

Couldn't reproduce in OB dcs-mt, can you share a short track ?

Tested single player, Caucasus map, OB 2.8.3.37556 

Thanks for looking into it--knowing that you couldn't reproduce it, I ran a repair and then opened a fresh new map, made some waypoints, and everything worked properly. Guess it was either a problem with my DCS install or something specific wrong with the mission, but everything seems to be OK! 😄

Posted

This has been happening to me too, on every map, before and after the MT patch (and I did run a repair post-patch). Only way to cycle WPs is the WP increment bind. I assumed it was operator error, but still can't figure it out.

Posted
6 hours ago, xflyer said:

This has been happening to me too, on every map, before and after the MT patch (and I did run a repair post-patch). Only way to cycle WPs is the WP increment bind. I assumed it was operator error, but still can't figure it out.

Odd advice, but maybe try a second repair? I did one repair post-patch and then another after Ramsay posted. The first one didn't seem to fix it, but the second did.

To clarify--the WP increment bind does work but pressing the arrows in the EHSD doesn't? Or do you have to do what I did pre-second repair and pull up the QA menu in order to select any different waypoint at all?

Posted

Correction--this issue still doesn't seem fixed for me, either. If I make a brand-new mission, the waypoints work properly. However, if I load a mission that existed previously, incrementing the waypoints via any manner other than the QA menu still doesn't work. Did the update break older missions?

Posted
4 hours ago, FMBluecher said:

Odd advice, but maybe try a second repair? I did one repair post-patch and then another after Ramsay posted. The first one didn't seem to fix it, but the second did.

To clarify--the WP increment bind does work but pressing the arrows in the EHSD doesn't? Or do you have to do what I did pre-second repair and pull up the QA menu in order to select any different waypoint at all?

I'll try a repair again.

Yes, the WP increment HOTAS button works but clicking the arrows up and down on the EHSD will cycle the waypoints on the EHSD but will not update the selected waypoint in the HUD.

I will still allow that this may be user error on my part. On one of my last missions a single button push was the difference between successfully lasing the target and ballistically dropping my GBU-12 on a residential neighborhood!

Posted

I'll double check tonight. I had similar behavior for TPs , but skipped past it by using WInc Hotas button 

Come fly with us : https://discord.gg/tawdcs  TAW CJTF 13 - EU TZ MilSim Squadron

Ryzen 5 5600X | 32GB DDR4 3733| ASUS Radeon RX 6700 XT  | ASrock B550 Phantom Gaming 4 | HP Reverb G2 | Thrustmaster Warthog Throttle , F16 & F18 grips , TFRP Rudders |  Win 10

Posted (edited)

OK, so 100% operator error on my part. I didn't realize I had to take the EHSD out of "Data" mode. I was also wondering why waypoint designation wasn't working. 🤦‍♂️

Edited by xflyer
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...