MeerCaT Posted February 23, 2013 Posted February 23, 2013 Here's an odd one for you. (May or may not be specific to the BlackShark, but I've not experienced anything like it with any other aircraft) I have a [modifer]+[button] HOTAS assignment for the 'Communication Menu' action. (i.e. radio menu) This action works fine while on the ground, but as soon as takeoff is performed this button assignment becomes 'inactive/disabled/lost/null'. Land again - it works. Takeoff - it does nothing. :joystick: I've always used this same button assignment, and since it works while on the ground I don't believe there is any issue with the assignment configuration or the physical HOTAS equipment, or anything like that. Has anyone else had experience of (or can anyone suggest a plausible explaination for) this change in control behaviour between gounded and airborne 'states'? Thanks
jib Posted February 23, 2013 Posted February 23, 2013 Are you using 3rd party software to program the buttons? I was thinking that maybe your gear up/down button was setting on some modifier and not turning it off. Mods I use: KA-50 JTAC - Better Fire and Smoke - Unchain Rudder from trim KA50 - Sim FFB for G940 - Beczl Rocket Pods Updated! Processor: Intel Q6600 @ 3.00GHz GPU: GeForce MSI RTX 2060 6GB RAM: Crucial 8GB DDR2 HDD: 1TBGB Crucial SSD OS: Windows 10, 64-bit Peripherals: Logitech G940 Hotas, TrackiR 5, Voice Activated commands , Sharkoon 5.1 headset. ,Touch Control for iPad, JoyToKey
codenamepanzer Posted February 23, 2013 Posted February 23, 2013 (edited) It is not the right button for communication (i know it is not logical). Search on forum. its "SPU-9 PTT" to be mapped on your button. I had this problem in the past. Edited February 23, 2013 by codenamepanzer
JG14_Smil Posted February 23, 2013 Posted February 23, 2013 (edited) Undocumented BS. Two different keypresses for your comm menus as you have found. For me it is \ and then RALT \ in flight. Nothing to do with SPU9 knob at all (unless switching to/from ground crew channel). Only reason I think this change would be made is to simulate a hand-off to an Approach ATC, but that should be done with a frequency change anyway. I bet it is a bug from the new comms menus in the 1.2. whatever version. Edited February 23, 2013 by JG14_Smil
Nate--IRL-- Posted February 23, 2013 Posted February 23, 2013 IIRC it was meant to simulate pust-to-talk, not sure it got it right though. Nate Ka-50 AutoPilot/stabilisation system description and operation by IvanK- Essential Reading
MeerCaT Posted February 23, 2013 Author Posted February 23, 2013 Excellent work guys, thank you; that hit the spot :) Interestingly, the "SPU-9 PTT" entry in the controls list was blank/disabled in the 'Saitek Joystick' (my controller, obviously) column. Meaning I was not able to assign this action to any of my HOTAS buttons; well not through the GUI at least. Instead I had to manually add the appropriate entry to my Ka-50 controls LUA file. Anyway, it looks to be working now so thanks again for the nudge in the right direction. Now then, I wonder if my spandex flightsuit still fits me...
Jafferson Posted November 18, 2015 Posted November 18, 2015 Excellent work guys, thank you; that hit the spot :) Interestingly, the "SPU-9 PTT" entry in the controls list was blank/disabled in the 'Saitek Joystick' (my controller, obviously) column. Meaning I was not able to assign this action to any of my HOTAS buttons; well not through the GUI at least. Instead I had to manually add the appropriate entry to my Ka-50 controls LUA file. Anyway, it looks to be working now so thanks again for the nudge in the right direction. Now then, I wonder if my spandex flightsuit still fits me... How did you do that ???
Recommended Posts