I'm partial to 1.16 because I contributed code to it. I fixed the automated altitude controls and auto hover so it actually works now. You can fly Nap-Of-The-Earth. The original code was messed up, the original programmers used a proportional-only feedback loop which was unstable. It has to have some differential feedback in order to work without over shooting the goal all the time. I can now put my helo into Altitude Lock, focus on my targeting screens, and use the equipment like it was meant to be used without crashing into the ground. Just my 2 cents worth.

Stability is more a function of which additional mods you've installed. Some mods aren't quite perfect and glitch every now and then.

Where's 1.15.4? I didn't find a release thread for that.

I'll give 1.16.2 with no additional mods and see how stable is. I've read some stuff about the flight model not being too good.

Is it the same for all versions, or better in an older one?

I don't have any additional mods to the source code or included sim files (cockpits, terrain, dyn files, etc) beyond the stock 1.16.2. From the beginning of 1.16 series I've experienced CTDs when rolling inverted, and now am getting the same ASSERT errors as I got with the blackhawk cockpit that didn't go away with uninstalling & reinstalling EECH and completely deleting all those files. I also don't see any actual evidence that tab 3 1 and tab 3 2 ever worked properly as they still seem busted on the CD-ROM 1.4.1c version.. I will continue to investigate my issues, but thus far I can't particularly find a reason not to go with 1.16.2 as 1.15 wasn't completely stable, either. Cuba was working until recently in 1.16.2 until suddenly it wasn't. The increased amount of infantry and MANPADS and fact that in 1.16-on I can finally get the flight model to be fairly acceptable with finagling leads me to think that I wouldn't install an earlier version in spite of the continuing and increasing issues I've had.


The flight model can be made better than it ever has before in EECH 1.16.x. Here's how you choose and alter the ini accordingly:

Crosscoupling ON or flying a coaxial:

flight_model=0
drv=1.0
dra=1.0
drd=0.1
dmrl=0.9
dtrd=10.0
dyal=2.5
dyad=3.0

Plus Translational Lift Options-Dynamics setting to ON.

***

NOT flying a coaxial and you have crosscoupling OFF:

flight_model=2
drv=1.0
dra=1.0
drd=0.1
dmrl=1.1
dtrd=10.0
dyal=5.0
dyad=3.0

Plus Translational Lift Options-Dynamics setting to OFF.


Here's my GWUT:

https://drive.google.com/file/d/1n3DUCoXDh0JvFSObCKLLLtqZnI6lPRzS/view?usp=sharing

Here's my ini, and obviously your joystick config will be different. I am using FM 0 and all in-sim dynamics settings ON.

https://drive.google.com/file/d/1tXP7UzHE4r_dbfTfqzYNDBE_rIBpzRpU/view?usp=sharing


If you have a pole cyclic or FFB joystick then no need for PPJoy and GlovePIE. If you want Longbow 2-like rate command & attitude hold, here's a good GlovePIE script for that:


var.nlzs = sign(Joystick2.z) // Collective nonlinearity that can be made more gradual near center.
var.nlzm = abs(Joystick2.z)^(1.0) // Previous Exponent of 2.0 for true nonlinear with large gradation in the middle, but 1.0 is linear.
var.nlz = var.nlzm * var.nlzs

var.yawrange = (smooth(deadzone(joystick2.slider, 0.008), 10) + 2 ) ^ 1 // Bottom throttle thumb rotary assigned as a yaw range.

var.nlzrots = sign(Joystick1.zrot) //Nonlinear pedals.
var.nlzrotm = abs(Joystick1.zrot)^(2.0) //1 will make it linear. Higher, less linear.
var.nlzrot = var.nlzrotm * var.nlzrots

if var.nlzrot = 0 then { //Better pedal fix.
var.pedalfix = -0.999999
else
var.pedalfix = var.nlzrot // pedals
}

var.dial = smooth(deadzone(joystick2.dial, 0.008), 10) //yaw trim

if shift+t then begin { //Auto trim clear
var.xhold = 0
var.yhold = 0
PPJoy1.Analog0 = var.xhold + deadzone(joystick2.x, 0.075)
PPJoy1.Analog1 = var.yhold + deadzone(joystick2.y, 0.075)
PPJoy1.Analog5 = (var.pedalfix / 1 - var.dial / 20 ) / var.yawrange //For pedals. Usually bypassed unless FM 0 or 1 with coaxials.

else

var.xhold = EnsureRange(deadzone(joystick2.x, 0.075) / 30 + var.xhold, -.4, .4) //Roll auto trimming. Over -.5/.5 causes continuous roll, but -.75/.75 is nicely responsive.
PPJoy1.Analog0 = var.xhold + deadzone(joystick2.x, 0.075) //Roll
var.yhold = EnsureRange(deadzone(joystick2.y, 0.075)/ 30 + var.yhold, -.75, .75) //Pitch auto trimming
PPJoy1.Analog1 = var.yhold + deadzone(joystick2.y, 0.075) //Pitch
PPJoy1.Analog2 = var.nlz * 0.7 - 0.15 //Collective currently reducing/adjusting range to prevent overpowering VRS and to reduce decel
PPJoy1.Analog5 = (var.pedalfix / 1 - var.dial / 20 ) / var.yawrange //For pedals. Now with yawrange on thumb dial.

}

var.GPbank = PPJoy1.Analog0
var.GPpitch = PPJoy1.Analog1
var.GPcollective = PPJoy1.Analog2
var.GPyaw = PPJoy1.Analog5

var.xaxis = Joystick2.x
var.yaxis = Joystick2.y
var.zaxis = Joystick2.z
var.zrot = Joystick2.zrot
var.slider = Joystick2.slider
var.xrot = Joystick2.xrot
var.yrot = Joystick2.yrot
var.dial = Joystick2.dial

Version 1.15.4 for me is the best. More complet and stable.
1.16.2 need to be more stable and need too Thealx gunner cockpit, BH cockpit, but the other side has better graphics.
Only my opinion, thanks.

Do you have a guide on how to use this with PPJoy and GlovePie? Is the idea of the script to cancel out the wings levelling effect? I couldn't get it setup properly to work, so it didn't seem to make much difference.

I'm using 2 sticks instead of HOTAS and pedals. One stick has two axis that can be used for throttle, so I've got 3 throttle sliders in total.

So is your script only applicable if you're using a hotas and pedals to make the FM feel better?