Hey guys, I've managed to improvise a moving trim implementation for the Harrier with telemetry! Apparently you can completely override DCS input subsystem and send back X/Y axis commands directly using LoSetCommandLoSetCommand functions. So in essence TelemFFB becomes two way telemetry. So the caveats are: DCS input system overriden for control axes and FFB Spring control is overridden with TelemFFB too. But since the harrier has static FFB, no loss there.
This also opens up more possibilities to enhance DCS FFB experience
What do you mean? It should work on any aircraft including the upcoming F-15, if they don't implement it there too. The way it works is I take virtual cockpit stick position, real physical stick position, do some math and send back adjusted input x,y values back to DCS. This way real stick (Rhino) is offset from center (trimmed), but DCS thinks it's at center.
If I read correctly what W wrote: once he releases next TelemFFB version you will specify in its config.ini file which aircraft you want to use it for. All the other modules are unaffected and you'll never have to touch the file again. It's probably just a line of plain text like override_DCS_input = YES (not the actual line) which you add under [AV-8B]. If you need the same for any other module, you just add the same line under [the other a/c handle].
It's a bit more involved. We need to also find the arguments for the stick position and export them with the telemetry packet for each aircraft separately in the LUA file as StickX and StickY (pedals will be added too in the future)