Cannot map Master Caution Accept/Reset button

[andyfoot]

Not sure if this is a bug, but I cannot map the Master Caution Accept/Reset button successfully using the in game mapping from the Options menu. The key command is for M, and I can map it to a button or HAT position, but it just will not function. i.e. I'll double click on the box that allows me to select which button I want to map to it, it accepts the button no problem (proving it is not my joystick or throttle, I have tried it with several buttons) and it is listed as the button, but it just does not function either in the game or in the Options menu. When I select other buttons for other commands, pressing the button whilst in the Options menu will take me to the relevant command, but this does not work with the Master Caution Accept/Reset.

 

Anyone else experiencing this issue?

 

I am running Win7, 64 bit, with a Thrustmaster Warthog HOTAS, Track IR5, Saitek Rudder pedals.

[spikenet]

just curious if you are using the bs2 default unmodified keymaps or did you copy some from your bs1 install?

 

I initially copied some stuff from BS1 and had a similar issue to you, looked fine in the options but the mappings would not work in the game

[andyfoot]

Using the default. I haven't played BS1 for some time, and only recently got the Warthog HOTAS so haven't got round to mapping it in BS1.

 

When you pressed the button in the Options menu, was it taking you to the relevant command and highlighting it?

 

Pressing the "m" button on my keyboard does work fine, both in the Options menu, and in-game

Edited November 6, 2011 by andyfoot

[nomdeplume]

Yep I've got this issue too. Thought I was going mad. :D

 

I've tried binding it to the autopilot engage/disengage button the TM Warthog throttle, and also to a button on a VRinsight panel. Neither works - it lets me bind it but is ignored both in-game and in the options screen. The 'M' key does work.

 

Other commands seem to work fine, although with some oddities:

 

1. 'Burst length - long' and 'Burst length - short' options can only be mapped to the TM Warthog throttle or keyboard - every other controller is disabled. Also, it seems to require being held in position; I've mapped it to the pinky switch on the throttle forward/back positions and it works as hoped for in that configuration, i.e. putting it forward or backward selects either long or short burst as appropriate, and putting it to the middle position selects the normal burst length.

 

2. 'Shkval narrow view 23x' and 'Shkval wide view 7x' is a bit weird too. Seems like the narrow view one needs to be held down, and it automatically reverts to 7x when it's released? I initially mapped this to 'china hat fwd' for narrow and back for wide; so it didn't really work out as I'd hoped. Changed it to use the boat switch instead so the forward position will be held in and it works that way. But, it seems very odd...

[spikenet]

maybe try using the TM software to map keystrokes to the sticks rather then using the in game setup.

 

Works for my x52.

[andyfoot]

I was hoping to not have to use the TARGET software, haven't delved into it yet. It definitely looks like it is a bug as nomdeplume has the same issue.

 

Nomdeplume, ref your Shkval zoom issue, you've probably seen it already, but have you looked at this thread

 

http://forums.eagle.ru/showthread.php?t=81042

 

The Burst length, I also left to the default which is the Flaps selector on my Warthog Throttle, works fine and I'm quite happy to leave it there.

[RedX]

This seems like a bug to me. I had the same problem with both master caution light pushbutton and throttle lever up/down commands. I was able to map the keys just fine by manually editing the files under Windows user folder \ black shark 2\Config\Input\Joystick using Notepad++.

 

There are lines with up = ... and down = ... with values specific to "actions" in the simulator. I checked with the functional keyboard commands file in the Config\Input\Keyboard folder, and in the case of master caution and throttle up/down the numbers differ. I replaced the up/down numbers in joystick file with those from the keyboard file and everything works just nicely.

 

I didn't try it yet, but perhaps the "hold to zoom" problem with Shkval can also be corrected by manually editing the up/down commands in the joystick file. I guess "down" is when pressing the button and "up" is button release. Are they?

 

In addition to master caution, I had problems assigning the same joystick key (TMWH stick button 6) for both "gun fire" and "release weapon". I assigned BTN6 in the joystick file for both using notepad++ and it works (my BTN2 switches gun trigger on/off).

 

To conclude, the numbers in my files differed for at least:

1. throttle up / throttle down (keyboard: PgUp, PgDown)

2. master caution push button (keyboard: M)

 

If you find any other assignments with the same problem, please list them here for others, too.

Edited November 7, 2011 by RedX
typo

[andyfoot]

RedX, thanks for that, can't check it out now as about to leave for Mombassa, back next week so will check it then.