Suddenly! Throttle decides to stop working.

[AdmiralTigerclaw]

I'm fairly new to this sandbox, so I feel like I'm encountering either a bug, or an unexpected configuration glitch.

But there I was, flying around in a V-22 (the one with it's own manual), when the upwards throttle tie to my controller throttle axis just... stopped working. That is to say, no matter how many times I pushed the throttle up to full, nothing happened. I could pull the throttle all the way back to idle, and the vehicle would conversely throttle down just fine, but the upwards axis (which is tied to a full throttle peg, mind you), just... stopped registering.

After that incident, I reloaded the V-22 from the work bench and got the same behavior, and eventually a total failure of the throttle unit to respond to up OR down throttle commands via axis.

After checking with the control screen, and seeing that the axis was still detected correctly by the game, I ruled out controller problem.

So, what gives? Anyone have any clue on why SW would decide that suddenly throttle axis AREN'T anymore? (And yes, I even restarted, and the problem persists.)

I am tasked. This problem tasks me, and I shall HAVE IT!

[ElfBossHogg]

The problem may not be the throttle input device itself but what it may be connected to.

If it is connected to a PID and set to full throttle then you may get in to a situation where the component driven by the output of that PID can't actually get to the value specified by the top throttle value. The result is a PID that is constantly increasing its output value but that increase does nothing as the input doesn't make a difference. For example, you set a throttle so that an engine will run at 12 RPS. You set that as you set point on a PID which has the RPS from your engine as your variable to watch... then you turn the engine on... and the engine can only ever make it to 11 RPS max. However the PID doesn't know that and is constantly increasing the throttle value to your engine. The problem is that when you dial the engine required RPS down it is still at high and takes a while to come down and then the PID also "recalls" what it took to try to ramp up and the integral build up is now slower.

[AdmiralTigerclaw]

Originally posted by ElfBossHogg:

The problem may not be the throttle input device itself but what it may be connected to.

If it is connected to a PID and set to full throttle then you may get in to a situation where the component driven by the output of that PID can't actually get to the value specified by the top throttle value. The result is a PID that is constantly increasing its output value but that increase does nothing as the input doesn't make a difference. For example, you set a throttle so that an engine will run at 12 RPS. You set that as you set point on a PID which has the RPS from your engine as your variable to watch... then you turn the engine on... and the engine can only ever make it to 11 RPS max. However the PID doesn't know that and is constantly increasing the throttle value to your engine. The problem is that when you dial the engine required RPS down it is still at high and takes a while to come down and then the PID also "recalls" what it took to try to ramp up and the integral build up is now slower.

I don't think it's a PID issue. This vehicle was running just fine for the better part of an hour, then this problem happened. And then it kept happening (and got WORSE) even after respawning it from the workbench, restarting from a save, and starting a new sandbox game.

It's odd because it's acting like I suddenly went and changed my input from the options menu. And to be specific about it, I can still hit UP and DOWN on the keyboard, and I can click the green buttons just fine. It responds as it should, but not from my physical throttle input. Yes, 'control input' via the J key is enabled.

I'll probably try again in the morning and see if something changes. For all I know, there's a bug buried in the game engine involved in inputs weirding out over time.

[AdmiralTigerclaw]

Okay:

So I tried something. I unplugged an extra game pad before I restarted, and when I jumped in, the controller config was an absolute mess. Half the settings were blanked (set to 'NONE'), and the throttle setting had been moved to the number seven slot for no apparent reason.

I remapped the axis set and it's working again.

It's strange how that seems to have happened. While the game pad was plugged in, my HOTAS was seen as 'pad 2'. And as I said, everything had worked fine for upwards of an hour. Then it broke for no visible reason. The first axis was reset to pad 1, axis 1. Which shouldn't happen without telling it anything.