Sano

Thanks for the track, just took a quick look, and the problem is that the gear is not ready to be retracted when you start cranking the handle. For gear up, 3 controls need to be in the correct position, but you only set one of them: - Gear lock (handle in the front): forward (yours was back) - Gear direction (the "middle" handle): up (yours was correct in the up position) - Brake spring handle (the handle in the back): forward (yours was back) Alternative resource: Chuck's guide at page 55: https://chucksguides.com/aircraft/dcs/i-16/

You should probably post a track, i just now checked and it still works correctly on my end.

The order of the calls depend on where they are added. In your above code, the first "if" will always be called before the second "if". They also are not entirely identical: if "myAIGroup" is not a table with a "getSize()" method, for example when it's nil, some random string or number, the if-check will throw an error. So again, depending on how and where it's used, it's generally safer to do: if not group or (group and group:getSize() == 0) then -- ... end This first checks if the group does not exist (so is dead), or if it still exists, it should not have units. There's also a small mistake in your snippet, getSize() should be with capital S.

On my end, seems there is a difference between setting controls "in a mission" vs "in the main menu". In the main menu, my controls were saved/persisted correctly after a game restart - while it did not when i adjusted controls in a mission. Can anyone confirm if this makes a difference for them?

A software-only workaround is possible using vjoy+joystick gremlin. Vjoy can be used to create a new virtual device that will show up in DCS. Joystick gremlin can do a lot of stuff, including remapping your ejection handle pull to "3 pushes of button 1 on the virtual device". Then in DCS map "virtual device button 1" to the ejection control

Same here. Initially had left and right engine axes mapped to a split throttle, but the custom curves kept on resetting the next day. After switching to the single thrust axis (and clearing the other two), the settings on that axis persist after restarts