[REPORTED]Su-33 will not launch from carrier with F-5E-3 in the mission.

Since this bug/problem is a failure of two modules to work together, I'm posting this here rather than in the two separate aircraft topics.

The release of version 1.5.5.60314 Update 3 and the hotfix 1.5.5.60338.212 has caused my first Su-33 Carrier campaign mission to cease to function properly. In single player missions, as a player or client in an Su-33, you cannot launch from the carrier when there's a F-5E-3 in the mission. In multiplayer the Su-33 launches fine with F-5E-3's in the mission.

I've attached two simple missions here that demonstrate the single player bug. Simply run the mission part 1, start engines and takeoff. You'll have no problem. Now re-start DCS and run the mission part 2 and you'll see that after starting engines, you cannot accelerate and takeoff, it's like you are stuck to the deck. It doesn't matter if the F-5E-3's are in the air, on the ground, or haven't even been activated yet. If they're in the mission anywhere and in any state, this happens. Don't forget to re-start DCS before running part 2.

Is this an Su-33 problem, or is this an F-5E-3 bug? :dunno:

CarrierTestPart1.miz

CarrierTestPart2.miz

Just tried it and someone crazy glued my plane to the deck in mission 2. I played this mission several times before the latest update and it worked fine.

Too bad as I enjoyed the mission and I was looking forward to more from Winston 60.

Cheers

Don't despair Rotor57, I'll be continuing the US Navy Squadrons Carrier Ops campaign as soon as this is fixed. Funny, no comment so far from ED on this bug.

Hello

The Su-33CarrierOps1Single. Miz does not work! The SU-33 can not be started by the aircraft carrier. The jet engines are running, but the aircraft stops.

Please look at the attached files:huh:

Challenger444

.trk

dcs.txt

Confirmed for me as well.

Downloaded both CarrierTest1 and 2 and had the same results as Winston when restarting DCS for mission 2. With F-5E-3 in the mission, there is no getting off the carrier........stuck like glued down. Hopefully ED is tuned in and can help us out with this problem. This is a fun mission when working as it should.

BadBud

BTW don't know if this means anything, but my buddy and I flying a MP carrier mission I was hosting. I was not able to get off the carrier but he was...and we have F5e-3s in there.

BTW don't know if this means anything, but my buddy and I flying a MP carrier mission I was hosting. I was not able to get off the carrier but he was...and we have F5e-3s in there.

Let me guess... client takes off, but the host/server is stuck to the deck, right?

For now, until ED fixes this, replace the F-5E-3's in your mission with any other plane and you won't have the 'stuck to the deck' problem.

Can we get a comment or an acknowledgement from ED on this bug, please?

This bug remains after patch 1.5.5.60503 Update 4 of Dec 23, 2016. Can we at least get this reported please?

How can I get bug this reported? :xmas:

BIGNEWY, after you created your new mission, did you close down and then restart the game before running it? Seems the problem only occurs on a freshly started game.

Thanks for looking into this. :xmas:

Yes, funny how a restart of the game always insures that this bug is present. Thanks for following through with this for us. I'm eager for a fix so I can continue posting my new Su-33 campaign missions. :xmas:

Confirmed, the "no launch" bug in single player has been squashed with today's 1.5.5.60565 Update 5 patch. Thanks again BIGNEWY for all the help with this very strange bug. We'll be testing as multiplayer client later tonight but I don't expect any problems, flying as client was OK before.