RangerGav

A slim chance i know, but has anyone heard of a anyone making extra keybindings for this module? In particular for the CNI (CDU) unit num-pad and keyboard?

@Hot_LZ - Thanks for sharing this, I think it's cleared up something I've been wondering about for the Chinook (irl vs sim). I'm flying with a force-feedback base and wasn't sure if the 'magbrake' type resistance was normal or part of the "force trim" which was all that was available in the initial version. I'd reverted to using the "force trim" after trying the trim-hat in the newer version because I was finding I was always fighting against a rigid stick (phrasing). I'm also not sure if the CD Rel functionality is properly modelled for FFB though. I'm sure I've tried using it with no obvious effect - so maybe it's a work-in-progress (or I've been using it wrong)! I'm interested to give it a try and see if it works like you've said above. Having said that, I've noted that switching the manual/auto trim in the cockpit doesn't seem to make any difference. So again, might just be early access things!

Finally got around to setting up bindings for the CH47 only to find there was nothing for the MFDs... I was confused! Then found this excellent work and just got everything set up. Fantastic stuff dude!

As per the subject - is anyone sharing these profiles or knows where some are shared please? I'm really hoping that this becomes more popular and we get some actual pilots of the modern aircraft make up profiles that match the real thing as close as possible. What I'm looking for is the 'real feel'... so just doing random-ass settings myself feels daft.

Further to this, I'm now experiencing full game crashes when trying to create a route (currently in MP on SInai map if that makes in difference). I make a couple of normal waypoints, go in to nav setup, open the empty route and it either crashes there or when i go to add leg.

There's a another post regarding this issue too. I've found the moire effect extremely strong in VR - to the point it makes it hard to see anything when moving the MMS. I recall a previous module that I think had this issue and they either toned it down or got rid of the effect for VR users. Definitely needed here!

Same bug here and in VR. Clicked a button on the left had MPD and suddenly all the "screens" were attached to my viewpoint and moved everywhere my head did.

As the title says, I've found a repeatable crash bug with the route setup. To recreate: 1. Create new waypoint (1W) 2. Go to routes and add waypoint 1W 3. In same route then try to add waypoint "PP" This caused a full DCS crash for me, and a friend who also tried it afterwards. I think you can do it slightly differently and you just get an "ERR" message when you try to add the PP point. But doing the above caused me a full crash to desktop.

Agreed - I'm having trouble in VR with the scan lines/moire being so intense when moving the MMS that I can't see stuff. I feel like there was another module not long ago that had a similar problem and had to have the effect turned down (or removed) for VR users.

I actually found one random one earlier that was 'switch up' and 'switch down' - I think the multi-function display one - which is momentary anyway so makes sense. But yeah, I realise it's probably annoying from a programming perspective to have three or so different ways to bind each switch/button/whatever - but I really think it should be a standard part of every module (and part of some proper standardisation that ED should be driving with their own and third-party modules).

Ah thank you! I didn't think to check there (always forget those copilot bindings have their own axis page).

Hoping someone from Polychop sees this! I'd really like to see some additional bindings included in a patch at some point that would give us more options for controlling things. The major one would be SWITCH UP and SWITCH DOWN options for all toggle-type switches (especially three-position ones). Honestly, I think this should be part of EVERY module. Some of the common flight sim hardware we're using (particularly Virpil) features mostly temporary toggle switches. So, if the bindings only have an "on" or active binding for a toggle switch it doesn't work for the majority of the physical switches we have. If you're able to add bindings for "UP" and "DOWN" that allows us to cycle through the positions of each toggle switch that would be a big help! I'd also like to see an axis binding for the MMS if possible please - so if we have a mini-stick on our controls we can use that instead of a hat switch.

Pimax Crystal here... had same problem with Jester wheel. I seem to have fixed it by setting the DCS resolution in the graphics options to 1280x960 (4:3). I already had VR settings set to use DCS resolution (right eye mirror). Previously I had it on the lowest resolution in the list (5:3 ratio) and that was cutting off the bottom of the Jester wheel (especially stuff like the ground air controls). Only just started the tutorials so haven't had the other Jester questions pop up yet (like asking to start alignment) - which was also previously cut-off and I couldn't do anything to interact with it.

Even better: DCS: Mi-24P Hind by Eagle Dynamics Added: Bind for radar altimeter dangerous altitude setting Thanks for adding this ED (or whoever did so)!

As the topic says... Am I correct in thinking there's no binding for the radar altimeter dangerous height adjustment dial in the Hind? I can't find any setting under any name I could think of for it. Not in buttons or axis. Have I just missed it somehow???

Ahhh... looks like I had the problem @Holbeach referred to above... the copilots axes were screwing things up!

I decided to try the Gazelle out again today to see what the first iteration of the minigun AI was like. Unfortunately I couldn't fly it as I kept getting ghost control problems. Collective would suddenly snap to full power while just idle on the pad getting set up. Cleared all axis bindings for it and redid them - still happened. Tried a different Gazelle config and in SP mission (first tried in MP), and same thing happened. Then got up in the air finally (had to keep wiggling the collective to correct it if it snapped to full), only to have the heli suddenly flip over for no reason. I went through and cleared all flight control key bindings as well so there's nothing but the specific device controls set up. Heli still acting crazy. Any ideas?

I have the same question (sort of). I've rewatched the videos to make sure I'm doing things correctly. I get set up in a hot-start Apache - FCR on and active, FCR screen selected, master arm on, trigger guard off, get in position, hover, scan - nothing shows up (except for one time - one vehicle out of several appeared for while then was gone in subsequent scans). I've tried adjusting elevation - no luck (so set it back to auto). Since then nothing has shown up on FCR in two different missions with different vehicle types (Russian armour and SAMs). What am I missing please? --------------- EDIT: Just hopped in a MP server and tried it out - all working as expected (as per Wag's videos). Not sure what was happening with my SP training missions - some setting missing or wrong somewhere I assume.

Hi, love your app and want to ask if we could get the keyboard for the Ah-64 Apache included in the UFC app at some point?

Thanks for this. This helped me understand what those numbers meant when trying to move the Huey crew status (although I still can't get it to appear where I can actually see it).

Any idea how to move all this over for a monitor setup that's not left aligned? I have a left-side monitor that's not used for DCS. Then a main monitor (2560x1440) with a smaller one (1920x1080) below it for MFDs. The main and MFD monitors line up on their left edges. I've tried various combinations of numbers but can't get the crew window to show up anywhere. What are the number values measuring... Pixels, inches, ?????

Hi all! o/ Wanting to know if anyone else has had an issue with the Throttle cut-off release - depress button not working? I'm quite sure it was working for me previously for cold starts and full shut-downs, but I've been playing MP lately with hot-start jets, so not sure when this changed. Might be since multi-threading, or since the most recent open beta patch (2.8.4.38927). I was using a throttle button for this command, and I've tired other buttons and keyboard keys with no improvement (just in case that button was faulty). The Idle-off and idle-on switching still works, but not the single cut-off release command.

Hi ED team, Any chance we could please get incremental keybinds for the "A-60 A2A missiles Active Launcher Selector" dial? We have "next" and "previous" keybinds for most other dials in the cockpit, but that one (which you probably want to use in a hurry) doesn't appear to have them. Many thanks!

Still far too many bugs in these training missions... which honestly appear to have been forgotten about. Really dumb/frustrating stuff at times too such as only two IRMVs for the Mav/Sidearms training (instead of the needed three - there's an extra LMAV for some reason). Very aggravating for a new pilot in a more difficult aircraft!

I have had similar issues with it. The route mode doesn't seem to head to the waypoints even after choosing the waypoint on PVI and setting route mode. Sometimes it just seems to turn in a lazy circle. Other times it seems to be following a diamond pip on the HUD compass tape that doesn't seem to align to any of the waypoints at all. Also, not sure how the ARBIS (?) fits in with the PVI -as the "to" waypoint on there doesn't seem to coincide with the PVI set one - but it does update when passing the waypoint (which I've had to fly to manually to trigger). The way the map moves in that thing is fucking frustrating too!