[Breaking Ground] Binding throttle to rotor torque?

[Guest]

I can't seem to figure out how to bind throttle to control rotor torque. There's an action set "Wheel throttle" but that appears to do nothing. I have no controllers in use, just KB&M.

Binding it to the translate controls works but it'd be nice to see the setting in the throttle indicator too, besides which it's more intuitive. Anyone figure this out yet?

[Snark]

On 5/30/2019 at 11:07 AM, Brikoleur said:

Anyone figure this out yet?

Yep.  It's not a thing.  Main throttle binding isn't currently in the axis groups.

If it were available, here's where it would be in the UI:

...since it's not listed under Axis Groups, that means it's not available.

This seems like a pretty obvious thing for a player to want, and you're not the only person who's been asking about this.

So I imagine they'll probably add it at some point, but it's not available as of KSP 1.7.1.

[4x4cheesecake]

20 hours ago, Brikoleur said:

There's an action set "Wheel throttle"

This one confused me as well but apparently, it can be used to increase/decrease the torque or rpm of a rotor via "W" and "S" keys.

[Snark]

20 hours ago, Brikoleur said:

There's an action set "Wheel throttle" but that appears to do nothing.

35 minutes ago, 4x4cheesecake said:

This one confused me as well but apparently, it can be used to increase/decrease the torque or rpm of a rotor via "W" and "S" keys.

"Wheel throttle" refers to the keys used for accelerating rovers forward/backward.

I think it's W and S by default, yes, but that always struck me as asinine because those are the same keys as pitch up/down, meaning that rovers hit driving problems when reaction wheels and rover wheels don't work together.  I long ago remapped my own rover keys from WASD to numpad 8456 to solve this problem. 

[Guest]

Ahhhh thanks Snark! That explains it. That's good as it's one more axis to use but doesn't really solve the problem with the main throttle.

Anyone figure out the custom axis groups? What do you do to trigger custom axis 1 for example? I'm assuming it's not 1 since that would interfere with action group 1 and also it would need a second control to decrease.

[4x4cheesecake]

24 minutes ago, Brikoleur said:

Anyone figure out the custom axis groups? What do you do to trigger custom axis 1 for example? I'm assuming it's not 1 since that would interfere with action group 1 and also it would need a second control to decrease.

You have to bind these on your own, there are not set to any key by default:

Spoiler

 

[Kryten 2X4B 523P]

Mapping rotor torque to the Translate F/B axis group seems to work as a vertical control, although a bit awkward on key controls.

[bewing]

On 5/31/2019 at 8:56 AM, Brikoleur said:

What do you do to trigger custom axis 1 for example?

F6/F7 or use the "app icon" in flight mode.

[Guest]

8 hours ago, Kryten 2X4B 523P said:

Mapping rotor torque to the Translate F/B axis group seems to work as a vertical control, although a bit awkward on key controls.

That’s where I put it. I rarely touch it in flight though as vertical is through collective which I’ve mapped to up/down, this is nicer as K/I is the right-hand equivalent of S/W (pitch).

For a fixed pitch rotor I would map it to up/down.

 

[Superfluous J]

On 5/31/2019 at 9:52 AM, Snark said:

So I imagine they'll probably add it at some point, but it's not available as of KSP 1.7.2.

So there's going to be a 1.7.2?

[Snark]

6 hours ago, 5thHorseman said:

So there's going to be a 1.7.2?

Wouldn't be surprised, but in this case it was either a fat-fingered typo or a brain fart. Fixed, thanks for catching 

[aruoch]

right now the only way i've seen people controlling rotors is with action groups to give 0% or 100% power. as far as i can tell there's no way to link this to throttle or properly control it without fiddling with the prop torque directly.

[Gargamel]

Overlapping threads have been merged

 

[Superfluous J]

4 hours ago, aruoch said:

right now the only way i've seen people controlling rotors is with action groups to give 0% or 100% power. as far as i can tell there's no way to link this to throttle or properly control it without fiddling with the prop torque directly.

Use a KAL-1000, and put it in there, then tie going up and down that timeline with action keys. You have 4 sets of 2 keys, and have 5 things you can set to them so technically have 20 smooth motions you can go between without even using the normal keys.

I set /*, 89, 56, and 23 on my numpad to be the decrease/increase of action groups 1, 2, 3, and 4. I'd be curious to know what others use.

[OHara]

Using a keyboard with no numeric keypad, but the traditional cluster of home/end..pgUp/pgDn 
[edit: but that only works because I recently learned how to disconnect the 'Delete' key from docking mode (link)]

Then any rotor torque controlled by 'Custom Axis 4' responds to the usual throttle up/down keys and matches the throttle display
... unless I use the full throttle (Z) or cut throttle (X) keys, in which case the display is out of sync with the rotor torque until I go smoothly to full or zero throttle.

The corresponding feedback item https://bugs.kerbalspaceprogram.com/issues/22779 shows a way to edit a save-file edit that does properly bind a rotor to throttle, including full/cut throttle.

In general, allowing the slider controls for any part to be bound to axis groups seems to give us useful creative freedom with no extra complication to the interface: https://bugs.kerbalspaceprogram.com/issues/22822

(The F6 and F7 keys mentioned above, in the default keybinding, switch between action sets that we get if we 'Enable Action Sets' in the VAB)

Edited June 8, 2019 by OHara
forgot that I customized 'Delete' away from docking mode