Manual waypoint advance

[DmitriKozlowsky]

What is the recipe for manual waypoint advance, or selection out of order? I miss WP01 by 500 meter and there is no autoadvance. Selecting WP02 from ROute option on TSD, does not make WP02 the current waypoint. 

Point of order. Everything in AH-64D is much harder then it needs to be.

[Jef Costello]

When you missed Wpt1 did you tried to select Wpt2 by pressing "Rte" and "Dir" on the TSD? Because it works everytime!

[DmitriKozlowsky]

Got it! Thank you

But really. Three button presses to advance waypoint. Is there a HOTAS bind in controls to circumvent this?

Feature request. Navigation commands to AI George CPG.

In multiplayer, CPG can handle NAV, while pilot flies. But for single players we have to play both parts.Its too distracting, even with decent autopilot. At 50 GL, pilot can be pushing buttons on MFDs. Guess thats why most armed forces consider military helicoptering as two crew operation. Pilot flying, co-pilot/gunner monitoring(weapons and systems).

[336_TheAngryGamer]

34 minutes ago, DmitriKozlowsky said:

In multiplayer, CPG can handle NAV, while pilot flies. But for single players we have to play both parts.Its too distracting, even with decent autopilot.

I believe there are planned improvements to George. At the moment, his usefulness is more limited than his uselessness.  

[NeedzWD40]

54 minutes ago, DmitriKozlowsky said:

Is there a HOTAS bind in controls to circumvent this?

The only way around it is via the cursor, which can be used point n' click style to select a direct route.

[aaronwhite]

I'm looking forward to the day when the waypoint options to mark battlefield stuff like power lines and target areas/targets become something we can manually add in the Mission Editor. It'll make Apache missions so much more immersive, at least from a single player standpoint.

I would love to mark all of those types of things in the system now, but it's just brutal having to manually input all of that stuff yourself. It would be so cool to be able to designate the target areas and no-fire areas like in the demos for them, and then as extra icing on top of the cupcake, have it so you can tell your AI wingmen to engage in their designated areas. 

[Floyd1212]

1 hour ago, aaronwhite said:

I would love to mark all of those types of things in the system now, but it's just brutal having to manually input all of that stuff yourself.

You may not be aware of the Coordinate Converter Tool by FalcoGer that helps with this type of setup.  Not quite the same as doing it in the ME and having it already loaded in the aircraft when you spawn in, but you can capture all those points with the crosshairs on the F10 map, then hit "Transfer" in the tool and sit back for a minute or two while the data is entered in the KDU automatically.  You can also save those coordinates as a file that can be distributed to other players for them to load into their aircraft.

So these 8 coordinates captured in the tool:

Become these points on the TSD:

 

And I agree that having more navigation assistance from George would be nice to see in the future.

[Hootman9104]

It would be nice to have a function to QUICKLY select next or previous waypoint, but I don't think that's a function in the real world. Now that I think about it though, the fix is a quick setup in Voiceattack, to press the required buttons in sequence. You can then also assign that Voiceattack function to a single HOTAS press.

This, of course, requires that you have all functions programmed in VoiceAttack, such as the MFD  button presses, which I painstakingly did over many, many weeks and months. It took me a bit to figure out how I wanted those buttons pressed, and ended up with just using VoiceAttack commands based on simple thinking. So each button became T (top) B (bottom) L (left) R (right) and then 1,2,3,4,5,6 left to right and up and down. Or just "TSD" or "FCR" for named buttons.  So to press the left panel left side bottom button, I say "left, L 6". 

So to program a command for Previous waypoint, I would create a Voiceattack "script", telling it to execute each button press one after the other. I will assign that Voiceattack command the keywords "Previous waypoint" "Navigate back" and "Next Waypoint" "Navigate forward" or something like that. And also program that particular Voiceattack script to run on a HOTAS button press if I don't want to speak it out.

I love VoiceAttack, penny for penny probably the best bang for your buck utility ever created, for anything that uses a keyboard, HOTAS, or mouse for actions. Without a doubt.