JohnW71

Hallelujah! Great to hear its sorted

Probably here but was a long time ago https://github.com/Munkwolf/dcs-community-keybinds/tree/main/InputCommands/Mi-24P/Input/Mi_24P_pilot/joystick

I have it under a different path but its here anyway. Weird how this isn't working as it was, it used to be so easy. default.lua I got the keybinds from here originally https://github.com/Munkwolf/dcs-community-keybinds, though I only used a few bits not the whole mod. Anyway it might have been updated since so maybe worth checking this mod out.

Sure, here it is

Sure, here you go default.lua

I had a quick look in DCS earlier (with no controls attached) and couldn't find them in the bindings either, should be under Instrument Panel but not there. Now I have my controls plugged in, go into DCS and there they are as expected. I have no idea why they wouldn't show before, maybe recent patch/bindings changes has muddled something here. Out of some old habit I have always placed my custom bindings in the file just before the '-- Clock' section. Anyway good luck, hope this helps somehow.

It's not there yet, I paste this into the file \DCS World OpenBeta\Mods\aircraft\Mi-24P\Input\Mi_24P_pilot\joystick\default.lua to add these bindings:- -- RALT {cockpit_device_id = devices.RADAR_ALTIMETER, pressed = ralt_commands.ROTARY, value_pressed = 0.025, name = _('Radar altimeter - Down (Slow)'), category = {_('Instrument Panel'), _('Custom')}}, {cockpit_device_id = devices.RADAR_ALTIMETER, pressed = ralt_commands.ROTARY, value_pressed = -0.025, name = _('Radar altimeter - Up (Slow)'), category = {_('Instrument Panel'), _('Custom')}}, {cockpit_device_id = devices.RADAR_ALTIMETER, pressed = ralt_commands.ROTARY, value_pressed = 0.05, name = _('Radar altimeter - Down'), category = {_('Instrument Panel'), _('Custom')}}, {cockpit_device_id = devices.RADAR_ALTIMETER, pressed = ralt_commands.ROTARY, value_pressed = -0.05, name = _('Radar altimeter - Up'), category = {_('Instrument Panel'), _('Custom')}}, {cockpit_device_id = devices.RADAR_ALTIMETER, pressed = ralt_commands.ROTARY, value_pressed = 0.1, name = _('Radar altimeter - Down (Fast)'), category = {_('Instrument Panel'), _('Custom')}}, {cockpit_device_id = devices.RADAR_ALTIMETER, pressed = ralt_commands.ROTARY, value_pressed = -0.1, name = _('Radar altimeter - Up (Fast)'), category = {_('Instrument Panel'), _('Custom')}},

This is still an issue; in my first two attempts my wingman crashed into the Mi8 during hover check, destroyed it, which then breaks the bombing stage later so is impossible to finish. On my third attempt he stayed on the ground, did no hover check, took off after me and from there everything was fine and finally completed the mission. I'm not aware of doing anything different on the third attempt though.

The campaign for ye olde Ka-50 seems to have mission 5 saved with Ka-50 III only, and although it can be loaded there is no slot available. null

I had same issue yesterday.

Same here, I can still see the steering cursor on the TADS video (from George) but not on my HMD, no idea what I'm doing wrong. Will have to get a track up at the weekend when I have time. The patch notes mentions Fixed: Missile Constraints Box and Rocket Steering Cursor not displaying when SAFE so I guess something changed here, but was not able to work out how to use rockets with George now. Definitely armed though, and can jump into front seat and just pull trigger and rockets then fire.

Guilty as charged m'lud! Thanks for the info

As Admiki made me doubt my own sanity I just tested it in current OB version, no flight controls attached. I've always had to do it this way and assumed it was intended. First noticed in a training mission way back. This was what I just did: Loaded a mission, choose cold start Apache Autostart, wait until finished Ctrl V brings up George menu Press 2 to jump to CPG Ctrl V does nothing Note cyclic is in flight position Press C, cyclic stows away Ctrl V now brings up the menu.

Its allowed the menu to appear for me when I've had that issue, was worth a try.

Try C to request control first, then try the George menu