x64WarGopher

Here are some clean log files of this problem. I noticed on the debrief log the second launch doesn't get listed on the log. dcs.log debrief.log

This bug popped up with 2.9, not sure if it's the most recent update that did it. I haven't played much since the 2.9 release. What Happens First launch from the Forrestal works fine no issues. If I land on the Forrestal and then try to launch again from the catapult the stick and throttle are locked in place and can not be moved using the joystick or keyboard controls. Trim and rudders still work. What I have tried. Supercarrier: Works fine, no problems. Payload/no payload: no change, still happens. Refueling/Rearming vs no refueling/rearming : no change, still happens. Launching from different carrier or airfield and landing: no change, still happens. Multiplayer/Single Player: no change, still happens Single/Multithreaded: no change, still happens. Different catapult: no change, still happens. Client Info Version: 2.9.0.47168 Windows Version: W11 Version 22H2 Build 22621.2428 I don't have any mods installed. I tried a repair, and that didn't fix it. What I can do in the mean time I can get around this in multiplayer by re-slotting after landing. I just need to remember to do so. Single player missions will need to be changed to SC module carriers. Edit: Further Testing Uninstalled Super Carrier module. All carriers have same problem. Request Launch vs Not Requesting Launch from radio menu: no change, still happens.

nullEvery time I'm trying to take off on GS.

I keep buying modules for DCS, but I keep coming back to two aircraft. The F-5 and the F-18. Every once in a while I'll give a module a fair try but I tend to just get bored with it and go back to flying these two jets. So now I'm curious. How many modules do you consistently play, and what are they?