Sephyrius

Can highly recommend FFB users to utilize the simFFB program. - Deadzones, curves and saturation changes messes up the DCS FFB, and even with the Gazelle option for curves, curves are flat out painful to use for precision control in a heli (at least for me). - Since simFFB operates outside of DCS, you can change the joystick settings all you want without messing up trimming. This is what I'm currently using for the Gazelle (I should probably add a small deadzone too) since 99% of the time you wont even yank the stick to its extremes, so why waste half the joystick range on it. - Also using a stick extension for the Sidewinder FFB2, and using simFFB to max out the centering and damping force to make up for it works great. - Very reliable. Got frustrated after countless times that the FFB via DCS would go slack and require a trimmer reset, suddenly invert the position (despite having swapped axis already), and so on. The negative would be that you only want to use it for helis (for example you'd lose the force/shake/stall effects in WWII aircraft), and that it wont alter its own position if you use the trim hat (personally I dont).

Can confirm that centering works. I faintly recall having felt the FFB effects of stalling the Mirage in the past, but doesn't seem to be the case. Or, well, it handles so ridiculously well that I had trouble stalling it just now even at max-stick high-AoA turns at a snail pace of 100. Haven't flown the mirage in months, is that actually authentic? Feels like the kind of things you'd see in FC3 FMs, maybe I've just been flying choppers and the Viggen for too long.

Bought the Normandy map to make up for the lack of a Baltic Map / Caucasus 2.5 with collidable trees, but sadly performance drops so much at low altitudes that it's unplayable, and flying a Viggen in Nevada feels rather dumb.

Kinda regretted the purchase, mostly went for it just to get collidable trees (which NTTR has, but so few that it's not worth it, and DCS 2.5 for it to be implemented for Caucasus seems to happen in 2018 at best) and while reduced performance compared to those maps was to be expected, it's at the point of barely even being playable. At 1200p, most things reduced to a point that would probably be considered low or medium-low, and still averaging about 28-35 frames in a Gazelle at low levels, down to 16ish (!) in cities. 8320 at 4.4Ghz, R9 290X, 16GB RAM, SSD. Bottleneck seems to be in GPU computation, while VRAM is dangerously close behind. Guess being above recommended specs means nothing and it has just been copy-pasted across the board, because it'd require a very large amount of optimization for it to seem genuine. *cries in AMD*

Got it to work just fine, but that was when rebound to a joystick key (since the real life switch is on the joystick handle) so not sure about the S binding.