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

There are probably sections where it will work, maybe you're outside that. I paste these at about line 600 just before CLOCK section. Don't remember why now, but it works

It's not available (unless added recently), I use a custom binding to create it. In PATH\DCS World OpenBeta\Mods\aircraft\Mi-24P\Input\Mi_24P_pilot\joystick\default.lua I add these lines: -- Course setter {cockpit_device_id = devices.GREBEN, pressed = greben_commands.ZK, value_pressed = -0.025, name = _('Course Setter - Left (Slow)'), category = {_('Instrument Panel'), _('Custom')}}, {cockpit_device_id = devices.GREBEN, pressed = greben_commands.ZK, value_pressed = 0.025, name = _('Course Setter - Right (Slow)'), category = {_('Instrument Panel'), _('Custom')}}, {cockpit_device_id = devices.GREBEN, pressed = greben_commands.ZK, value_pressed = -0.05, name = _('Course Setter - Left'), category = {_('Instrument Panel'), _('Custom')}}, {cockpit_device_id = devices.GREBEN, pressed = greben_commands.ZK, value_pressed = 0.05, name = _('Course Setter - Right'), category = {_('Instrument Panel'), _('Custom')}}, {cockpit_device_id = devices.GREBEN, pressed = greben_commands.ZK, value_pressed = -0.1, name = _('Course Setter - Left (Fast)'), category = {_('Instrument Panel'), _('Custom')}}, {cockpit_device_id = devices.GREBEN, pressed = greben_commands.ZK, value_pressed = 0.1, name = _('Course Setter - Right (Fast)'), category = {_('Instrument Panel'), _('Custom')}}, IIRC I borrowed them from this project: https://github.com/Munkwolf/dcs-community-keybinds

I find the red hard to see in 2D just from being a bit colour blind. The yellow/green for free fire/hold fire is also too similar for me. Maybe one day these things might be changeable as a setting, can always hope!

The engines have been dropped to 90% in the mission files, so yes some takeoffs are very challenging/rolling down hills to get airborne etc. You could change this setting in the ME if you want. There are lot of problems in the campaign, it's really showing its age now, but I doubt these old campaigns will ever get properly overhauled now, after all this time. Occasional bug fixes at best, more than that is just probably too costly for ED. Anyway I have 2 missions left to go, and then it's getting deleted, never again.... It's also great to see how good modern campaigns are in comparison, people really are making some great stuff these days.

?\DCS World OpenBeta\Mods\aircraft\AH-64D\Missions\Training

Open the missions in the Mission Editor, then save them and it should be fine. It's a bug in the first 3 only I believe, probably will be fixed soon anyway, but re-saving sorted it for me.

I opened the training missions in the ME and just re-saved them, problem solved, didn't need to change anything. I believe it was only the first 3 missions that had the issue but I re-saved all anyway.

I've just found the same thing in some of the training missions, game mode is not on in the settings or in the mission options but its in effect as you described. I opened and saved each training mission and all fixed now.

IIRC Look for Source + -

I've seen this as well recently. Starting from trimmed in level flight, engage the Alt hold and its nose up and then nose dive and panic. Not sure if I'm doing something wrong though...