Poor Yurik

I use Quaggle's Keybind Injector, but I still truly hope that ED adds more of these missing binds. Here is what I personally add to my own control config: return { keyCommands = { --HUD {down = 3002, cockpit_device_id = 7, value_down = 1, name = _('HUD Mode Grid'), category = {_('Ins HUD controls'), _('Custom')}}, {down = 3002, cockpit_device_id = 7, value_down = 0, name = _('HUD Mode Day'), category = {_('Ins HUD controls'), _('Custom')}}, {down = 3002, cockpit_device_id = 7, value_down = -1, name = _('HUD Mode Night'), category = {_('Ins HUD controls'), _('Custom')}}, --Targeting {down = 3001, cockpit_device_id = 11, value_down = 1, name = _('Laser Standby Switch On'), category = {_('Ins Targeting Mode Controls Panel PVR'), _('Custom')}}, {down = 3001, cockpit_device_id = 11, value_down = 0, name = _('Laser Standby Switch Off'), category = {_('Ins Targeting Mode Controls Panel PVR'), _('Custom')}}, {down = 3002, cockpit_device_id = 59, value_down = 1, name = _('K-041 Targeting System Power Switch On'), category = {_('Ins Targeting Mode Controls Panel PVR'), _('Custom')}}, {down = 3002, cockpit_device_id = 59, value_down = 0, name = _('K-041 Targeting System Power Switch Off'), category = {_('Ins Targeting Mode Controls Panel PVR'), _('Custom')}}, }, axisCommands = { {cockpit_device_id = 7, action = 3001, name = _('HUD Brightness')}, {cockpit_device_id = 8, action = 3002, name = _('IT-23 display brightness')}, {cockpit_device_id = 8, action = 3003, name = _('IT-23 display contrast')}, {cockpit_device_id = 23, action = 3001, name = _('Helmet device brightness')}, {cockpit_device_id = 46, action = 3006, name = _('ADF Volume')}, {cockpit_device_id = 49, action = 3002, name = _('R-828 (VHF-1) Radio Volume')}, } }

I was about to post a similar bug report, but assumed the issue I was seeing only occurred with the less common left eye monocle. You're saying this happens with the default right eye configuration too?

I'm having the same issues: 1) Mission 1 and 2 have both ended in a draw despite me doing all objectives. 2) Directions and beacon given for Otryka after dropping off the wounded are both wrong and send you on the opposite direction of what's intended. I'm enjoying the campaign, but the first two missions not finishing properly makes me worry there's mission-breaking trigger bugs later into the campaign.

I will try that, thank you! Still hoping ultimately for an official solution so that the range of motion issues you listed are corrected as well.

Hello! Two issues when attempting to operator the IFF switch on the right wall panel of the BS3 with a physical button or momentary switch (mouse clicks work correctly): 1) Pressing the IFF switch bind doesn't also first trigger the the IFF switch cover to open like all other switch binds which also open their respective covers (examples: EKRAN, Weapon power, etc.) 2) Pressing the IFF switch bind when the cover is open just makes the switch flick up/on for a split second and then return immediately to the down/off position.

Flappie, thank you!!! I didn't know it had been reported internally. Marking your reply as the solution for this thread.

This is great, unfortunately I believe we need an official solution as editing this file likely will prevent us from joining protected multiplayer servers. I ran into a similar issue when I edited my ABRIS behavior in the LUA to speed up the slew speed and had to revert it. ED: please please please add Axis binds for the Black Shark 3's dials. So many button boxes have dials on them that would be perfect for the Shark.

This would be great. +1

The Black Shark 3 rotor brake has two issues when bound to axis: 1) Its operating behavior is physically upside-down: when the rotor brake is visibly in the up position it registers as disengaged and when it's visibly down it registers as engaged. 2) When cold starting with "Synchronize Cockpit Controls with HOTAS Controls at Mission Start" enabled in the Misc. options, if the rotor brake starts in the up position (i.e. the disengaged position when bound to axis), it is not registered as disengaged. You must move the brake handle down then back up again to register as disengaged. I first reported these issues in April on the bug reporting section of the ED discord. Hoping I get more traction here, as I absolutely love this module and these issues have really bugged me (no pun intended). Thank you!

100% agree with the OP. There are a ton of 0-100 brightness knobs in the cockpit. All should be bindable to an axis. My two big axis dials on my Virpil Control Panel #1 have zero use in the BS3 (my favorite module) right now