Greyman

I went this way and it works really well. Many thanks @Tuuvas, for sharing.

From the still on the video you have linked, you can see an adjustment knob just beneath the "M" of "MFG". Just loosen that a bit and the bottom end of the spring it adjusts can be removed, altogether or left so loose that it has very little effect.

MFG Crosswinds will be worth a look. They have a centre tensioning spring that can easily be removed to adapt them for helicopter flying and they are solidly put together.

At least some of the screens do not appear to have limits for the cursor coordinates, which means that although the cursor appears at the edge of the screen, its actual coordinates might be miles off outside of the screen. This will probably be fixed, but in the meantime, maybe try moving your cursor away from the edge, until it starts to move again.

Does that throttle have a button at the lower end of its movement and might this button be mapped to a non-axis throttle command?

Many thanks for that. I've done all of the illustrated mappings and all i need to do now is to remember what they all are, whilst wearing a VR headset. I think I might need to peak a little.

That's the word i was looking for. So do i need to find buttons on another controller for the first detents for those two triggers?

Sorry, I've apparently not been too clear. It was the apparent lack of the 'Weapon Trigger First' and the 'LRFD Trigger First' mappings that i was referring to.

Could it just be that having what is effectively a single command axis bound to multiple controller axes, in the same category/seat, is causing said controller axes to effectively compete for control and cancel each other out? Maybe try just having one controller axis bound in each seat.

Yes, but unless you have a lot of physical buttons/axes on your physical controller(s), you're still likely to be struggling to map everything you need.

I'm probably missing something, but in the first couple of diagrams in the OP, for the xbox/ps controllers, there doesn't appear to be any mention of the "First" versions of the two triggers, whereas on the PS specific diagrams, both "first" and "second" triggers are included. Where would i select the first level triggers on an xbox controller?

As curves are basically there to allow what is likely to be a relatively short physical joystick, commonly used by PC simmers, to behave as though it is a longer virtual joystick/cyclic and as that relationship is not going to be massively different from joystick to joystick, I chose to start with the curves of 8 that Wags uses in his controls video. I've not had to tweak the curves since, so they can't be far off. Alternatively, if your joystick allow it, you could choose to add an extension to your joystick, that makes its length comparable to the length of the Apache cyclic, which would preclude the need for a curve at all.

Check the option for the throttle detent in the special tab. I was having these issues when i had it set to automatic. Maybe select the finger-lift option and see if that corrects your issue

In a word, "modifiers". If you've not used them before, they're a bit like the Shift and Ctrl keys on a keyboard, in that they effectively multiply the number of control button combinations you have available for mapping.

What we ideally need is for VAICOM Pro to add voice control for George, as it does for Jester in the F14. Being able to just tell George what to do would be so much more realistic and user friendly, especially if it can also remove the need to display the George AI interface.

Particularly given the rather off-putting display of the George AI in the Apache, when in VR, being able to give verbal instructions to the pilot, when in the CPG seat, would be awesome.

they would be questions that you would be far better to ask in the M-2000 forum, via the first link in my previous post

Have you checked out the forum for the M2000? M-2000 - ED Forums (dcs.world) Maybe try one of these:- User Files (digitalcombatsimulator.com) There appears to be a few profiles that others have created.

You might be right, so it looks like I might have to "get off my backside" and develop one for myself. It'll probably take a while, but let's see if I can create one that will be a "good profile".

I made the mistake of being too keen to get up in the air and didn't spend enough time setting or, perhaps more importantly learning, my controls. It looks like I'm going to have to start again and take my time, hopefully with the aid of someone else's expertly put-together and generously uploaded TM Warthog profile. The Apache definitely looks like it is going to be worth that effort. Many thanks ED

I'm looking forward to a 1-minute, comprehensive Crash Laobi guide to flying and using the Apache.

...it might also pose an interesting challenge or three for navigation systems.

I'm just getting back into using DCS World and Vaicom Pro, after a bit of a break, so I am probably doing something really stupid, but whenever i try to go through the FINISH steps, it looks like only the AIRIO commands are being copied to the clipboard? The reason i am trying to do this, and again i must have forgotten how to do it, but when i press one of the PTT buttons and give a command, "inbound" for example, the VA log appears to suggest that it has been recognised, albeit followed by "(Awaiting additional input)", but there is no sign or sound to suggest that the command has been registered in the cockpit. The PTT display correctly shows that i am flying the A10C (the A10C 2 actually), so there must be some communication going on between DCS and VA/VP, but apparently not yet fully. Edit: Never mind, all's well. I did a Windows uninstall on the 'VAICOM Pro for DCS World' app and reinstalled it again. It seems to now be working just how i remember it. If only my memory were that reliable.

That sounds similar to a problem that an early, maybe beta, version of Quake produced on many networks, back in the day, including the one in my workplace, where some clandestine lunchtime carnage might have gone unnoticed, had it not brought the network to its knees. Apparently, each of the many bullets generated by chain guns caused a network packet to be sent along the peer-to-peer connections, generating a massive amount of network traffic. I don't know exactly how the developers solved the issue, but i suspect that they somehow combined streams of bullets into a far smaller number of packets. Those were the days.

It's when the floor starts shaking and getting warm that you'd need to start worrying. :)