LeCuvier

Adds a little dose of humour to the game

I shot up the Corsair (flying the Dora) so it had to emergency land. I strafed it once and then used F2 to look at the damage. And lo and behold, my strafing had produced an orphan tail section lying next to the Corsair. See attached photo. Just to be clear, there was only one Corsair in the mission. This funny bug won't make me lose any sleep, but maybe worth fixing.

Rocket Box I wanted to try the rockets and therefore bind rocket box switches, but I found none. Not knowing when Magnitude will fix this, I created my own. These are the lines I added to my "default.lua": {down = device_commands.RocketsBox_SwitchCover, cockpit_device_id = devices.WEAPON, value_down = 1.0, name = _('Rockets Box Switch Cover OPEN'), category = _('Weapons')}, {down = device_commands.RocketsBox_SwitchCover, cockpit_device_id = devices.WEAPON, value_down = -1.0, name = _('Rockets Box Switch Cover CLOSE'), category = _('Weapons')}, {down = device_commands.RocketsBox_Switch, cockpit_device_id = devices.WEAPON, value_down = 1.0, name = _('Rockets Box ON'), category = _('Weapons')}, {down = device_commands.RocketsBox_Switch, cockpit_device_id = devices.WEAPON, value_down = -1.0, name = _('Rockets Box OFF'), category = _('Weapons')}, {down = device_commands.RocketsBox_ArmSafe, cockpit_device_id = devices.WEAPON, value_down = 1.0, name = _('Rockets Box ARM'), category = _('Weapons')}, {down = device_commands.RocketsBox_ArmSafe, cockpit_device_id = devices.WEAPON, value_down = -1.0, name = _('Rockets Box SAFE'), category = _('Weapons')}, {down = device_commands.RocketsBox_SingleAuto, cockpit_device_id = devices.WEAPON, value_down = 1.0, name = _('Rockets Box AUTO'), category = _('Weapons')}, {down = device_commands.RocketsBox_SingleAuto, cockpit_device_id = devices.WEAPON, value_down = -1.0, name = _('Rockets Box SINGLE'), category = _('Weapons')},

Setting the takeoff trim (Yaw and Bank to 6, Elevator to 1) seems challenging and causes me neck distortion due to poor visibility of the dials. Just like the "Trim Reset" command, there should be (in my opinion) a "Takeoff Trim" command. I have managed to create such a command for myself by adding this line to the "default.lua": {down = device_commands.iCommandRudderTrimAxis, pressed = device_commands.iCommandEleronsTrimAxis, up = device_commands.iCommandElevatorTrimAxis, cockpit_device_id = devices.CONTROL, value_down = 0.22, value_pressed = 0.44, value_up = 0.05, name = _('Trim for Takeoff'), category = _('Flight Control')}, It's a bit of a cheat, but so is the "Trim Reset" as far as I know.

I executed the start procedure exactly as described in the EA Guide, and it worked. Except I never saw the "Engine primed" message, maybe I was not looking where I should.

Two little issues: 1. I never see the spike of the radar echo on the A-Scope. This does not prevent me from locking and hitting the ship, but doesn't look right. 2. For familiarization with a new weapon I like to use the "Unlimited Weapons" option. This doesn't seem to work with the BAT bomb. Pity!

I created bindings for the 3 positions that work. They can be bound to 3 pushbuttons, or to a 3-position switch. But frankly, they do nothing other than changing the position of the 3-way switch in the cockpit. I don't think you'll ever be able to view gun camera footage. So it's probably a very low, if any, priority.

Thanks for checking. I reviewed on my end and it was a binding to the airbrake.

After the 23-JUL-2025 I see continued and new issues at mission start: 1. Continued: Mission starting on runway has wings folded up. In other words, I'm in position for the takeoff run, but my wings are still folded up. This makes no sense at all. 2. New issue: In missions starting in the air, my Corsair has the landing gear down. And no matter how much I slow her down, I cannot retract the gear at all or I can only retract one of the two "legs". This is a show stopper for me as I fly mostly air-start missions.

These lines seem to do it: {down = device_commands.Mixture_control, cockpit_device_id = devices.ENGINE, value_down = 0.0, name = _('Mixture Cutoff'), category = _('Engine')}, {down = device_commands.Mixture_control, cockpit_device_id = devices.ENGINE, value_down = 0.33, name = _('Mixture Auto-Lean'), category = _('Engine')}, {down = device_commands.Mixture_control, cockpit_device_id = devices.ENGINE, value_down = 0.66, name = _('Mixture Auto-Rich'), category = _('Engine')},

Good catch! Actually embarrassing for the developer. These lines would have worked if they had put them into the key commands section of the file (after this line): join(res.keyCommands,{ But they put them into the Axis section, (after this line): join(res.axisCommands,{ And that obviously cannot work.

If you are willing to add a line in the "default.lua" under "joystick\" or under "keyboard\" you can create it for yourself. This is the line: {down = device_commands.Clock_Chronograph_Button, up = device_commands.Clock_Chronograph_Button, cockpit_device_id = devices.CLOCK, value_down = 1.0, value_up = 0.0, name = _('Chronometer Start/Stop/Reset'), category = _('Flight Control')}, I tested it and it works just fine. I don't like the category "Flight Control" for the chronometer, but I didn't find a suitable one. You can change it to whatever you want.

Sorry, I goofed. Forgot to remove the key commands. This should work for you: {down = device_commands.AutoStart, cockpit_device_id = devices.AUTOSTART, value_down = 1.0, name = _('Autostart Procedure'), category = _('Engine')}, {down = device_commands.AutoStop, cockpit_device_id = devices.AUTOSTART, value_down = 1.0, name = _('Autostop Procedure'), category = _('Engine')}, I tested it this time and it works. Edit: I went to the post with the PDF file and I downloaded it in the normal process. No idea what went wrong for you.

The MiG-21 wasn't always so extraterrestrial. I used to kill the AI flying the Bf-109K4 (no kidding!), and that wasn't even very difficult. That of course was unrealistic too.

I have done some more sparring with the Corsair AI (Ace) flying the Bf-109K4, and this confirms my earlier impressions: The damage model of the AI seems over-vulnerable. It takes just a few hits with 13mm rounds and the engine dies. I'm fairly sure the Corsair was more robust than that.