k1ebe

It's been a while since I look at this last and my helicopter profile is fairly complicated, so it's a bit difficult to decifer it for just this functionality. But I can at least try to get you on the right track. You need to use the awsome Boolean functions. These are really powerful and can enable you to do some pretty cool stuff once you play around with it and get the hang of how they can function. For this specific topic we need to enable two different ouputs from the same button press. This is done with the boolean function "NOT". Example: You want the physical button which you now use for the trim function as the input button. And you need to select a free physical button to use as output. Then you can set that physical button to point to whichever logical button you want which is the DX-button the game will see. This is pretty must the gist of it. I'm sorry I can't be more specific right now, but this should put you on the right track at least. Let me know if you need more specifics and I'll try to help you out.

Yes, it's printed in PLA. The M8 bolt presses against the shaft for extra support.

The shaft is held in place with two screws on the outside, undo those and open the main housing and detach the cable that runs through the shaft. Then the whole thing can be pulled out. It's really simple once you have a look at it.

This is just something I threw together in Thinkercad. There's no .step option there, but I've attached the stl-file for it. Collective damper interface v1.stl

The collar is a thing I 3D-printed to fit a 8mm machine screw which fits with the dampener.

No worries! I'm currently using that method to trim. I've also set my trimmer in DCS to "Joystick Without Springs and FFB" and set my trimmer button in VKBDevCfg to output a button which is set to the Force Trim Release in DCS. This way I also tell the helo that I'm trimming, which seems to me to give a more stable flight. But I might be imagining things. Further more, if you use VKBDevCfg to trim, I would advise to not use a curve in DCS, have the axes set to be linear. If you want a curve, set it in VKBDevCfg. This will give better results especially in trimmed forward flight. Where the game thinks your pitch axis is way forward of center and will give you the axis response rate of that position. A curve set in VKBDevCfg will give you the proper response rate when you have the stick physically in center, but trimmed elsewhere.

I've been trimming using a trim function on my Gunfighter and that works rather well. I just set the trimmer in DCS to no spring and set the curves in DCS to be linear. I've set the trimmer up to freeze the axes output so long as the trimmer button is held, this way I can take the time I need to recenter the cyclic. One caveat is that I have pedals that does not recenter, so I have no need to trim the pedals. There is an old thread about the cyclic trimmer here: http://forum.vkb-sim.pro/viewtopic.php?f=25&t=3501

Great find! I had not noticed that. This probably has something to do with the calibration procedure for the trigger. It's supposed to be down when starting the calibration and the GF does an auto calibration at start up, so having it up probably messes with that process.

I also see this from time to time on mine, and it's solved by recalibrating the device. For me it usually happens after I've done some changes in VKBDevCfg. When this occurs I recalibrate and use the "Set" function to write the config to the device. Not sure if the last step is necessary, but this usually solves it for me.

I mounted a hydraulic damper to it the day I got my collective. It stays where I put it and the damping gives the movement some nice heft to it.