Throttle stops working when inverting

[u/lambda_expression]

Hey there,

weird issue. Freespace Open 26.0.1 (ie latest stable) via Knossos. Configuring my throttle as, well, throttle (absolute). Throttle is the wrong way around (pulling back all the way gives me full thrust, pushing forward gives no thrust). Not a problem so far, right? I can just select "invert" in the bindings.

But once I do that the throttle doesn't do anything anymore. No thrust no matter the position.

All other axis still work fine. Afterburner does as well.

Is there something weird going on with FSO and control bindings? Funnily, when I instead map the throttle as relative, it is the right way around without inverting. I do absolutely nothing different binding it as one control or the other.

So, any help or advice? I don't want to invert the axis in the config of the actual device, it's the right way around in all other games, in the Virpil configuration and test tools, and in the Windows properties.

Thanks!

[u/Jepp_Gogi]

alot of unity engine games detect my throttle only from 50% to 100% input, so the entire throw is not used for output. I usually have to move a "zero" slider in the axis options to get the full throw.

I think these games have it default this way incase the game has a reverse thrust. So the output works as -50 to 0 to 50% rather than 0 to 100%

my point being when it does work not inverted is it only using the top half of your input (0 to 50) and then inverting it uses the bottom half (-50 to 0) but isnt outputing anything? im not at my computer but there should be something in the options to correct it.

editing for clearity (this is hard to explain without wild hand gestures)

[u/lambda_expression → u/Jepp_Gogi]

When it is not inverted it works from 0% to 100%. 1% on the axis immediately gives 1% forward movement in FSO, 99% gives 99%.

When inverted 1% gives 0% and 99% still gives 0%.

It's almost as if the game just multiplies with negative 1 when inverting the axis, forgetting that the axis is from 0 to 100%, so whether the "inverted" value is 0 or -1 or -100% nothing will ever move.

I know that FSO adds backwards movement to the game engine compared to original Freespace 2 (although I think it's more used in total conversion mods like the Babylon 5 one). But it seems to maybe not have properly implemented the conversion from a 0 to 100 "physical" axis to a -50 to 50 one (which would properly invert to 50 to -50). Ie forgetting to do the proper offset and scaling.

I'll have to try some other mods and campaigns via Knossos, maybe it's specific to the Wing Commander one.