Jump to content

[BUG] F-14 Won't Launch From Carrier, All Parameters Met


Recommended Posts

Posted

Having the same problem, after enough times I see what "appears" to be the pattern.

 

Basically, as you creep forward to line up with the shuttle, if the nose gear/bar goes past the shuttle, even if when you hit "u" and it pushes you back slightly and raises the blast shield, hitting the salute key combo (LShift-u) does not initiate the catapult launch. Also, I notice that when you've gone past the shuttle and hit "u", the plane (from the cockpit POV) is shaking quite a bit. Whenever I see the shaking, it's pretty much guaranteed not to launch after the salute.

 

So basically the solution I've seen, is to release the shuttle ("u"), enable nose wheel steering and move (i.e. in a circle) to re-align with the shuttle again. But this time, I'm very careful about not passing the shuttle... almost like you have to be just short of it when you latch to the shuttle ("u"), and not observe any (major) shaking - then the salute launches OK for me.

  • 2 weeks later...
Posted

Hi Guys how are you spawning onto the carrier ?

Ive noticed that this sometimes happens if i leave my throttle open when spawning ready on the runway also check that you don't spawn with your flaps down

it normally fixes if I do a quick throttle down and or move my flaps up

Hope that helps ?

[sIGPIC][/sIGPIC]

Posted

Guys, this is still happening! Do we have an idea yet what can be causing this? This bug might have been introduced a couple of updates ago. I have missions that I built a couple of months ago, and I don’t have a problem launching the Tomcat on those. Whatever it is, it may have something to do with engines. I noticed that as soon as any of the engines are started, the airplane starts to slide towards the forward part of the ship. When I shut the engines down, the airplane stops sliding. I’ve made changes to parallel the old missions, but I haven’t been successful in braking the code! Is there a workaround for this yet? Have we identified a cause? Thanks.

 

Bones

Posted

Unfortunately I’m out of town this week so I can’t access the tests I’ve already done, but I’ve managed to narrow it down so that I can at least avoid the problem. The problem is directly related to the Tomcat’s deck sliding and/or relative wind speed.

The Tomcat can’t launch at “realistic” carrier speeds, meaning ~25kts wind over the deck. If your carrier speed is set higher than around 15 knots then you’ll experience wicked deck sliding in the F-14, attached to the shuttle the plane will shake fairly consistently, and you won’t launch after salute. There may be a weather/wind component required (ex. 17kts carrier/8kts wind or 10kts carrier/15kts wind), but with realistic winds over the deck the Tomcat won’t launch after saluting. Lower the carrier speed and/or wind velocity (below realistic values) and the ability to launch returns.

  • Thanks 1

i7 7700K @5.0, 1080Ti, 32GB DDR4, HMD Odyssey, TM WH, Crosswind Rudder...

Posted
Unfortunately I’m out of town this week so I can’t access the tests I’ve already done, but I’ve managed to narrow it down so that I can at least avoid the problem. The problem is directly related to the Tomcat’s deck sliding and/or relative wind speed.

The Tomcat can’t launch at “realistic” carrier speeds, meaning ~25kts wind over the deck. If your carrier speed is set higher than around 15 knots then you’ll experience wicked deck sliding in the F-14, attached to the shuttle the plane will shake fairly consistently, and you won’t launch after salute. There may be a weather/wind component required (ex. 17kts carrier/8kts wind or 10kts carrier/15kts wind), but with realistic winds over the deck the Tomcat won’t launch after saluting. Lower the carrier speed and/or wind velocity (below realistic values) and the ability to launch returns.

 

Man, I’ve tried at a default of 11 and 27 knots for the carrier, and I have not been successful. However, on an older mission with the carrier set to 27 knots and a wind of just 4 knots, I can launch without a problem. On the newer missions, as soon as I start the number 2 engine, I can see the airplane drift starting. Shut down the engine, the drift stops. On the older missions, the airplane wobbles a little on the deck, but it stays in place.

Posted

For me it seems that the F-14 is not physically attached to the shuttle because when the deck sliding starts to happen, i could observe that the Launch Bar icon on the caution panel also starts to come on and off. It seems to me that the aircraft is sliding out of the shuttle area even if you are already hooked. My solution to the problem is that i observe the caution panel for the Launch Bar to light up again and hit salute as quickly as possible.

Specs:WIN10, I7-4790K, ASUS RANGER VII, 16GB G.Skill DDR3, GEFORCE 1080, NVME SSD, SSD, VIRPIL T-50 THROTTLE, K-51 COLLECTIVE, FFBBeast Virpil Alpha+VFX Grip, MFG CROSSWINDS, JETPAD, RIFT S

Modules:A10C, AH-64D, AJS-37, AV8B, BF109K4, CA, F/A18C, F14, F5EII, F86F, FC3, FW190A8, FW190D9, KA50, L39, M2000C, MI8TV2, MI24P, MIG15BIS, MIG19P, MIG21BIS, MIRAGE F1, P51D, SA342, SPITFIRE, UH1H, NORMANDY, PERSIAN GULF, CHANNEL, SYRIA
 
Thrustmaster TWCS Afterburner Detent
https://forums.eagle.ru/showthread.php?t=223776
 
My Frankenwinder ffb2 stick
Posted

Check out a Tomcat mission named Bone or something like that. Is the one where you escort some B-1s to target. I’ve deleted the carrier, added a new one, changed its course, speed, changed altimeter setting, temperature; I’ve even changed the weather from static to dynamic, and nothing!

Posted
For me it seems that the F-14 is not physically attached to the shuttle because when the deck sliding starts to happen, i could observe that the Launch Bar icon on the caution panel also starts to come on and off. It seems to me that the aircraft is sliding out of the shuttle area even if you are already hooked. My solution to the problem is that i observe the caution panel for the Launch Bar to light up again and hit salute as quickly as possible.

 

Yeah, the airplane is always on a constant drift in the same direction as the carrier.

 

Bones

  • 3 weeks later...
Posted

Bump: Any movement on this?

System Specs: System Specs: MSI Tomahawk Z590 wifi, I9 11900K Processor, 64gb Corsair Vengance 3600mhz ram, 4070TI Video Card, Windows 11 Pro, 2 Samsung NVMe SSD (2tb and 1 tb), Valve Index VR system

  • 4 weeks later...
Posted

Figured nearly a month was enough to bump this again and see there has been any progress?

 

Our group is still experiencing this on our mission. Seems an easy fix is to try another catapult. Then we get launched as normal.

 

We've just got used to saying "Cat 1 is out of service! Moving to Cat 2!" :lol:

  • 2 months later...
  • 1 month later...
  • 6 months later...
Posted

Just bumping this, had the same issue last night on a MP server. Cold and dark startup on carrier, taxied and hooked up fine, powered up, salute and nothing.

 

As it’s been ongoing for what looks like almost 6 months, any chance of an update please.

 

I’ve only just started learning the F14, hence why I’ve only just come across this issue. But not being able to use a carrier aircraft, on the carrier, is kinda a major issue

  • Like 1

 

 

[sIGPIC][/sIGPIC]

 

Fighter pilots make movies, Attack pilots make history, Helicopter pilots make heros.

 

:pilotfly: Corsair 570x Crystal Case, Intel 8700K O/clocked to 4.8ghz, 32GB Vengeance RGB Pro DDR4 3200 MHZ Ram, 2 x 1TB M2 drives, 2 x 4TB Hard Drives, Nvidia EVGA GTX 1080ti FTW, Maximus x Hero MB, H150i Cooler, 6 x Corsair LL120 RGB Fans And a bloody awful Pilot :doh:

Posted

This but seems to have worsened with the last OB. Previously I was able to hold the kneel switch for a couple extra seconds and I could launch, on the current version there doesn't seem to be any workaround to get the cat to fire.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...