Tuuvas Posted November 13, 2021 Posted November 13, 2021 (edited) Edit: I've updated the layout below based on feedback from many people in the community. You guys are all awesome! AH-64D Apache Longbow null Please keep in mind that the Apache is not released yet as of this post. This is simply to provide a layout for gamepad users so they have something once the Apache is available. The controls I've chosen to bind are based on the following resources: CasmoTV's Apache Controls Overview BradMick's Apache Control Mapping Recommendation Eagle Dynamics Discord - DCS Helicopter Chat channel Low Level Hell Discord - Apache channel Mi-24P Hind's Petrovich AI Menu Wags' binding and startup video Let me know what you guys think. Is there a more ergonomic way of laying out these controls? Are any key bindings completely missing? Perhaps there's some unnecessary ones? Edited May 16, 2022 by Tuuvas
Tuuvas Posted November 13, 2021 Author Posted November 13, 2021 Also, since there's a lot of talk about using an Xbox Controller separately for the TEDAC specifically, I just wanted to make it clear that this layout is meant to fully control the AH-64D. This is NOT a layout specifically for the TEDAC
kgillers3 Posted November 13, 2021 Posted November 13, 2021 I’d say with the limited amount of buttons and it being a game you could probably drop and realign alittle Force trim doesn’t work like that of a hind. Unless the arrows are place holders for the hat then I’m back with you. you can drop fmc release, it’s for an ep and people confuse how the fmc in the ah works in comparison to the ka, be my only guess why it’s there maybe one of the dudes testing it know something I don’t but in the real aircraft it actually hurts your controllability, unless you meant it as force trim release, but still doesn’t make sense because that’s apart of the force trim hat I was referencing earlier idk. You don’t need the boresight button it doesn’t do anything for this year. I’d personally want polarity a higher level, generally for hunting I’m a white hot guy but if I’m at distance trying to identify something I swap, also when flying under nvs I generally use blackhot. I hope this helps man. Oh you missed your sight select I think double checking Nm found it
kgillers3 Posted November 13, 2021 Posted November 13, 2021 (edited) I would combine sight select with was, radar functions as close together and tads as close together as possible, they’re a little intermingled and you’re gonna be forcing your self jumping more from modifier to modifier than necessary I think. As close together I mean on the same modifier button. Delineate like that as much as possible, there’s only a couple cross overs, you’ll use was more with tads then fcr especially at early release. Edited November 13, 2021 by kgillers3
Tuuvas Posted November 13, 2021 Author Posted November 13, 2021 (edited) Thanks for the input @kgillers3! I absolutely want to make sure there's as little movement between modifiers as possible. I've taken your suggestions and made them in the new layout below. Additionally, I made some other changes around the levels of a couple actions which I thought would only be used once in a while during the flight: NVS TADS/PNVS and SYMBOLOGY UP/DOWN. I moved these behind both modifiers since I wouldn't expect the CPG nor Pilot to use these terribly often. What do you think? Also considering I have 2 free slots in the Left Modifier section, do you have any recommendations on what I should bind to <- and -> ? Btw is it safe to say that the FCR FOV Z, N, W, M will also affect the TADS? It just depends on whether I've Sight Selected FCR or TADS? Specifically this hat: Edited February 14, 2022 by Tuuvas 1
kgillers3 Posted November 13, 2021 Posted November 13, 2021 So fcr scan size and tads zoom have to be two separate switches. unless you’re gonna double bind them, which probably would work As you have it now here are my suggestions. I’m just waking up so still a bit groggy. no modifier laser trigger swap with cued search weapon release move to right thumb z axis I just realised, you’re going to have to move laser trigger and weapons release down to left modifier. Unless you’re counting on iat / ai to take care of tracking for you. you’re going to want iat down, can’t think of the name off top my head but to reset / drop. I’ll think a bit more on it, worst case I think you have a working product that you can fine tune after you play and move things around so it’s easier. best of luck
kgillers3 Posted November 13, 2021 Posted November 13, 2021 Oh symbology Up / down. Honestly it depends how much night flying you’re planning on doing. I don’t think you’ll have to move it from double bumper tho. Running an Xbox controller with no ir track, idk how much fun night nvs will be. Not my place to decide. However, moving between transisition and hover at night will end up being pretty essential because at hovers. It’s impossible to determine your drift from sensor until you’ve moved quite a bit, unless you’re staring straight down and keeping your head in one spot. So unfortunately those get used a bit, they’re used a lot during day too but honestly it’s not as necessary. The benefit of not having ir track is as soon as you stop moving the camera it fixes so you can’t confuse head movement with aircraft movements! Big win
Tuuvas Posted March 17, 2022 Author Posted March 17, 2022 (edited) With the Apache release imminent, I went ahead and updated the original post with the latest version of the gamepad-only layout for the AH-64D Apache. If you're more interested in a TEDAC-only layout for your console controller, see my other forum post here for both Xbox and PS4/PS5 controllers: https://forum.dcs.world/topic/293233-xbox-and-playstation-gamepad-layouts-tedac-only-prerelease-drafts-will-update-on-release/ Edited March 17, 2022 by Tuuvas
Recommended Posts