F-14 with Supercarrier in Multiplay - No take off on CAT

[TOMCATZ]

HI,

 

I have the following problem: 

I cold started dark in multiplay on the deck of the aircraft carrier. I did the cold start normally, taxied to the CAT and everything was fine.

After connecting to the CAT and the officer showed me the signals to start the engines:

I pushed the engines to Full AB, saluted, and nothing happens. 

 

I saluted several times but no start was possible. There is also no more undocking from the CAT. My Tomcat is trapped and the only solution is to disconnect from the server. 

 

Ot happens more than 20 times on "Through the inferno" servers in the Caucasus and Syria. 

 

In the external view I clearly saw that the pilot saluted the officer. It seems that FA18s are not afflicted with this bug. 

Sometimes the take-off is possible - sometimes not. It's quite frustrating because I really don't know what causes this kind of error. 

 

Maybe I am the only one who has this problem. But I have it since the last update, so maybe other Tomcat drivers have the same problems?

 

And no - I don't have any tracks. But I think it might be helpful to report a user problem. 

 

Thank you very much for your support,

with best regards and cheers,

TOM 

 

Edited September 3, 2021 by TOMCATZ

[draconus]

Have you tried the actual launch binding, which is Lshift+U? Salute is not connected to the launch in the Tomcat afair, but the launch command does make the pilot salute too.

btw: It's the spool up signal, not start the engines

Edited September 3, 2021 by draconus

[TOMCATZ]

Hi ,

 

yeah - sorry: spooling up...of corse. 

 

Whatever- Yes I tryed even LShift+U . And without solving the problem. Even a disconnection from the CAT is not possible. 

I haven't tested it for the Stennis - Because I'm interested in the Supercarrier only.

 

Cheers

Tom

[Whiskey11]

On 9/3/2021 at 12:30 AM, TOMCATZ said:

HI,

 

I have the following problem: 

I cold started dark in multiplay on the deck of the aircraft carrier. I did the cold start normally, taxied to the CAT and everything was fine.

After connecting to the CAT and the officer showed me the signals to start the engines:

I pushed the engines to Full AB, saluted, and nothing happens. 

 

I saluted several times but no start was possible. There is also no more undocking from the CAT. My Tomcat is trapped and the only solution is to disconnect from the server. 

 

Ot happens more than 20 times on "Through the inferno" servers in the Caucasus and Syria. 

 

In the external view I clearly saw that the pilot saluted the officer. It seems that FA18s are not afflicted with this bug. 

Sometimes the take-off is possible - sometimes not. It's quite frustrating because I really don't know what causes this kind of error. 

 

Maybe I am the only one who has this problem. But I have it since the last update, so maybe other Tomcat drivers have the same problems?

 

And no - I don't have any tracks. But I think it might be helpful to report a user problem. 

 

Thank you very much for your support,

with best regards and cheers,

TOM 

 

 

 

As someone who spends a lot of time on the 107th's TTI servers in a Tomcat, I can't say I've had issues in either the -A or -B Tomcat.

Out of curiosity, what was the deck state like when you were hooking up?  What was the time of day?  Remember, the F-14 only launches at night/morning/dusk via the lights.  I'm not sure if having the lights on in the day makes the aircraft unable to launch (if so, that's a bug), but if you are doing an auto start or something, check the lights to make sure they aren't on if it's day.

One final thing to note, is sometimes you'll have problems hooking up to the cats if a Hornet is also on the cats.  I always have to remind myself to hit the "Request Launch" command in the radios before taxiing, otherwise the deck crew sometimes doesn't recognize you.  Sometimes the Hornets on the cats just wont let you hook up at all and you have to wait.

[TOMCATZ]

Hi,

 

thank you very much. I will try it in future. 

 

Maybe I started early in the morning without lights on because I went into combat. And I never requested a launch via command line. So I will try all of this in future in hope all will be fine. 

 

I will write if it solve the problems I got. 

Cheers

TOM

[Tank50us]

On 9/6/2021 at 2:23 AM, TOMCATZ said:

Hi,

 

thank you very much. I will try it in future. 

 

Maybe I started early in the morning without lights on because I went into combat. And I never requested a launch via command line. So I will try all of this in future in hope all will be fine. 

 

I will write if it solve the problems I got. 

Cheers

TOM

 

In the F-14, when in low-light conditions the signal to the cat crew that the pilot is ready to launch is when he turns off the exterior lights and turns them back on. So if you must make sure the lights are on while taxiing, then once you're hooked up and given the spool-up signal, and you're ready to launch, flick the lights on and off, and it the shooter should give the launch signal

[draconus]

1 hour ago, Tank50us said:

In the F-14, when in low-light conditions the signal to the cat crew that the pilot is ready to launch is when he turns off the exterior lights and turns them back on. So if you must make sure the lights are on while taxiing, then once you're hooked up and given the spool-up signal, and you're ready to launch, flick the lights on and off, and it the shooter should give the launch signal

To be precise, RL procedure is to not use any lights on the boat until you're ready on the cat, then you turn nav lights, so the ground crew launches the Tomcat. What HB made however is not reaction to lights but rather the "Master lights on" binding in case of the night (or the Salute command if you use the F-14 special option), which is wrong because you can turn the master lights earlier and only move the nav lights switch later, which will not work in DCS.

[Tank50us]

13 minutes ago, draconus said:

To be precise, RL procedure is to not use any lights on the boat until you're ready on the cat, then you turn nav lights, so the ground crew launches the Tomcat. What HB made however is not reaction to lights but rather the "Master lights on" binding in case of the night (or the Salute command if you use the F-14 special option), which is wrong because you can turn the master lights earlier and only move the nav lights switch later, which will not work in DCS.

 

Either way, with any luck, this will solve his issue.

[TOMCATZ]

 

ITs NOT A BUG! ITs A FEATURE! 

 

 

Hi guys,

Thank you very much for your helpful answers. I think the lights have put me on the right track. I turned the lights on just before starting and everything worked fine and as expected. LAter I found this statement in the HeatBlurSection. Yes, a case of RTFM :

 

Night Catapult Signalization

 

The standard way of launching off of the carrier at night is to flash the aircraft’s lights to signal the carrier crew. This is now implemented in the F-14, and takes the place of the standard salute during daytime.

 

Edited September 14, 2021 by TOMCATZ