Minor controls issue(s)

[Hippo]

Hi,

 

I realise that these aren't a big deal, but it would be nice if they could be looked into and fixed if it's not too much effort.

 

1. I have several TM MFDs and a Cougar, and try to not have to use the mouse / keyboard if at all possible. When I try to map rotating knob functions, e.g. the ABRIS select knob, or the HUD brightness knob, to buttons (or even the keyboard) they are too sensitive - i.e one press of the button equates to many turns of the cockpit knob.

 

2. The following functions don't appear to work when mapped to buttons (and it would be very useful if they did): the frame rate display, and door open/close.

 

Thanks for looking.

Edited March 14, 2012 by Hippo

[Yurgon]

2. The following functions don't appear to work when mapped to buttons (and it would be very useful if they did): the frame rate display, and door open/close.

 

With my Cougar, I've had the door open/close mapped to BTN T5 (throttle 4-way switch left) for ages and just mapped RCTL BRK to BTN S3 and it worked fine. Both done in Foxy 4.0. I don't think this is something ED need to fix because it doesn't appear to be broken in the first place. Could it be an issue between the Game mode and Sim mode keyboard mappings?

 

However, I agree that the keyboard buttons for the rotaries are very sensitive. It would be nice if they were adjusted to be a little less sensitive or if there was a config option to make them less sensitive.

 

Does anyone know if this can already be done with some LUA editing magic? :-)

[Hippo]

With my Cougar, I've had the door open/close mapped to BTN T5 (throttle 4-way switch left) for ages and just mapped RCTL BRK to BTN S3 and it worked fine. Both done in Foxy 4.0. I don't think this is something ED need to fix because it doesn't appear to be broken in the first place. Could it be an issue between the Game mode and Sim mode keyboard mappings?

 

However, I agree that the keyboard buttons for the rotaries are very sensitive. It would be nice if they were adjusted to be a little less sensitive or if there was a config option to make them less sensitive.

 

Does anyone know if this can already be done with some LUA editing magic? :-)

 

Quite right about the door, thank you for replying - not sure what I had done wrongly before.

 

However the ABRIS increase / decrease I really would like to have working on a button, and I cannot find a way to do this so that it works acceptably.

[Yurgon]

Quite right about the door, thank you for replying - not sure what I had done wrongly before.

 

However the ABRIS increase / decrease I really would like to have working on a button, and I cannot find a way to do this so that it works acceptably.

 

Yes, that's a bit weird. I mapped the 7-key (Abris Axis Decrease) on an HOTAS button. Without modifiers, only a single button press is created, no matter how long the button is held down. With this setting, ca. 2/3 of the button presses didn't yield any visible result at all, as if the Abris button was only rotated a tiny fraction, but not enough to advance the marker (in the flight plan for example).

 

By adding a /H (hold) modifier, the HOTAS button acts just like the keyboard key. In this case, it is very difficult to advance the Abris marker exactly one row (again, example taken from navigating the waypoints in the flight plan, but this problem is of course not flight plan specific); most of the time, the button is held just a little too long and the marker advances too far.