Mac D Posted December 26, 2024 Posted December 26, 2024 I don't know if this a issue with the Super Carrier module or the Heatblur F-14A/B module, so I'm gonna put it here : Looovvveee the new deckcrew, but I'm hittinh a problem I can't figure out what teh cause could be. So up to launch I'm doing the same as I use to do with the F-14 : Taxi, being guided to CAT 1, wings out, flaps down, launch bar kneel, drive over cat , stop, tension catapult and getting signal from the shooter to throttle up, and salute : This is were it goes wrong. Even at full throttle (in afterburner) and saluting (I tried saluting in the comms menu and using the keybinding, the shooter just keeps giving the signal to throttle up : he won't launch. Then I tried it with the F/A-18C : works like a charm. So am I doing something wrong or is it a Super Carrier/Heatblur F-14 A/B bug ? (I've bin searching the forum last night and this morning and I haven't found any topic reporting the same issue I'm having)
Viral-51st-Vfw Posted December 26, 2024 Posted December 26, 2024 What time of day/ case are you launching under? I'm guessing you need to turn your lights on if my assumption is onSent from my SM-S928U using Tapatalk
Mac D Posted December 26, 2024 Author Posted December 26, 2024 4 hours ago, Viral-51st-Vfw said: What time of day/ case are you launching under? I'm guessing you need to turn your lights on if my assumption is on Sent from my SM-S928U using Tapatalk Early morning , Kola map , on local time (07:45 december 2024) so still dark. I had the lights on the F-14B on, except taxi. Lights were on bright. Tried every thing now : Mil power (nozzle gauge 0) Full afterburner Flaps down, flaps up. Nothing nada zero : no launch.
rob10 Posted December 26, 2024 Posted December 26, 2024 I don't really fly the F-14, but have you tried turning the lights OFF and back ON? I think you need to flash them maybe?
Mac D Posted December 26, 2024 Author Posted December 26, 2024 1 hour ago, rob10 said: I don't really fly the F-14, but have you tried turning the lights OFF and back ON? I think you need to flash them maybe? I'll give it a go, thanks.
markturner1960 Posted December 27, 2024 Posted December 27, 2024 I think you need to use the "catapult salute " keybind, rather than "salute" ....try that System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.
Mr_sukebe Posted December 27, 2024 Posted December 27, 2024 With the F14, you need to salute befit starting the cold start, then again at launch from the cat 1 7800x3d, 5080, 64GB, PCIE5 SSD - Oculus Pro - Moza (AB9), Virpil (Alpha, CM3, CM1 and CM2), WW (TOP and CP), TM (MFDs, Pendular Rudder), Tek Creations (F18 panel), Total Controls (Apache MFD), Jetseat
Mac D Posted December 27, 2024 Author Posted December 27, 2024 1 hour ago, markturner1960 said: I think you need to use the "catapult salute " keybind, rather than "salute" ....try that 48 minutes ago, Mr_sukebe said: With the F14, you need to salute befit starting the cold start, then again at launch from the cat I tried it : No response on radio menu salute. Binded catapult salute to a knob on 1 of my controllers : This works for being guided from the start position on carrier to the ramp, yet when your in the launch position : no response (aka no launch)
Nealius Posted December 27, 2024 Posted December 27, 2024 If at night salute doesn't work in the Tomcat. External lights need to be turned on, as is real procedure. The Hornet's procedure is still unrealistic in that the launch crew doesn't respond to lights, and still requires salute at night. 1
Mac D Posted December 27, 2024 Author Posted December 27, 2024 Just modified a different scenario : Syria, daylight, and in this scenario the Tomcat DOES get launched. Got a feeling I know what going on my Kola scenario : I have a S-3B that's getting launched before me and my wingman, got the feeling this is screwing up the launch. 1
markturner1960 Posted December 27, 2024 Posted December 27, 2024 yeah, AI flights spawning around your start do seem to mess things up, buty I have not yet been able to figure out exactly how and why and therefore be able to work around it. Its complicated also by the fact that what happens depends on how many AI you have spawning or taking off and indeed, how many players you have spawning and taking off. There does not see to be an order they follow. In a mission I am working on, for example, I have deliberately left spawn points 0,1,2,3 free of statics and other flights, yet the AI flights dont spawn there.....I cant figure it out..... System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.
Mac D Posted December 27, 2024 Author Posted December 27, 2024 FOUND IT : When on catapult, turn external lights off and back on again, salute and off you go 1
DD_Fenrir Posted December 27, 2024 Posted December 27, 2024 5 minutes ago, Mac D said: FOUND IT : When on catapult, turn external lights off and back on again, salute and off you go In RL lights should be off on deck; you turn them on only to signify ready to launch and turn them off as you taxi out of the landing area once you have successfully trapped. 2 1
draconus Posted December 28, 2024 Posted December 28, 2024 The true solution is to use the "external lights switch" binding for the night launch. The crew does not react to the actual lights at all. It was reported to HB but they don't give a ... enough care. There's also special option for F-14 to use "salute" binding also for the night launches. 1 Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
Recommended Posts