DST Posted March 5, 2022 Share Posted March 5, 2022 As title says, every 2nd time I try my AI wingman does not take off from Forrestal Carrier, I have no clue why, it´s very annoying. I have attached the mission I try currently, but it could be every other mission too with Forestal and F14A with AI wingman. Maybe someone has a workaround? GulfTriggerCAPF14IIwSAM.miz I7 8700K 3.7 GHz 32GB RAM NVIDIA RTX 3080 Rift S Link to comment Share on other sites More sharing options...
DST Posted March 5, 2022 Author Share Posted March 5, 2022 OK, can confirm it´s not only forrestall carrier, it´s every carrier. Trying F14B now. I7 8700K 3.7 GHz 32GB RAM NVIDIA RTX 3080 Rift S Link to comment Share on other sites More sharing options...
DST Posted March 5, 2022 Author Share Posted March 5, 2022 Same with F14B. I´m really not sure, but could it have to do with turning on afterburners on carrier flight deck? I now catapulted three times without burners and wingman followed immediately. I7 8700K 3.7 GHz 32GB RAM NVIDIA RTX 3080 Rift S Link to comment Share on other sites More sharing options...
EnDSchultz Posted March 7, 2022 Share Posted March 7, 2022 Were you doing a custom mission? See if it helps to make sure you add at least one waypoint for your flight outside of spawning on the carrier. Link to comment Share on other sites More sharing options...
DST Posted March 9, 2022 Author Share Posted March 9, 2022 Yes, it's a self build little mission and waypoints are set. The strange thing is sometimes it does work and AI is lifting off as expected and every 2nd or third attempt it got stuck on the ramp and refuses to move. Still haven't figured what causes it and it seems i'm the only one with this problem I7 8700K 3.7 GHz 32GB RAM NVIDIA RTX 3080 Rift S Link to comment Share on other sites More sharing options...
DST Posted March 9, 2022 Author Share Posted March 9, 2022 Maybe I should add that I am on Pos. 1, AI wingman is on Pos. 2, and there are 2 AI Harriers at Pos. 3 & 4 that are set to do a bombing run whilst I & Wingman have job to escort them. Once the AI wingman has started, the Harriers start without problem. Maybe there is a problem with F14 and Harriers together on flight deck? In other custom missions I don't have problem with stucking F14 wingman I7 8700K 3.7 GHz 32GB RAM NVIDIA RTX 3080 Rift S Link to comment Share on other sites More sharing options...
draconus Posted March 9, 2022 Share Posted March 9, 2022 23 minutes ago, DST said: Maybe there is a problem with F14 and Harriers together on flight deck? They are supposed to start from the Tarawa. Win10 i7-10700KF 32GB RTX3060 Rift S T16000M TWCS TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria Link to comment Share on other sites More sharing options...
DST Posted March 9, 2022 Author Share Posted March 9, 2022 3 hours ago, draconus said: They are supposed to start from the Tarawa. So far the Harrier AI jets worked pretty well (when they had room to start cause of my stupid AI wingman) they even landed with no problems on Supercarrier and Forrestal. I7 8700K 3.7 GHz 32GB RAM NVIDIA RTX 3080 Rift S Link to comment Share on other sites More sharing options...
draconus Posted March 9, 2022 Share Posted March 9, 2022 25 minutes ago, DST said: So far the Harrier AI jets worked pretty well (when they had room to start cause of my stupid AI wingman) they even landed with no problems on Supercarrier and Forrestal. If the removal of Harriers fixes the problem you should reconsider if it works "pretty well". Win10 i7-10700KF 32GB RTX3060 Rift S T16000M TWCS TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria Link to comment Share on other sites More sharing options...
DST Posted March 11, 2022 Author Share Posted March 11, 2022 Update: has nothing to do with harriers or not on the flight deck. A simple custom mission only me and AI wingman and a couple of waypoints, and AI occasionally still refuses to take off no matter which start position. Happens on every carrier, SuperCarrier or Forrestal, F14A&B. Still can't pin down what causes this, sometimes it starts and sometimes it doesn't. Can't believe I'm the only one who encounters this issue. I7 8700K 3.7 GHz 32GB RAM NVIDIA RTX 3080 Rift S Link to comment Share on other sites More sharing options...
Grundar Posted March 26, 2022 Share Posted March 26, 2022 No this error occurs for me as well, so you aren't the only one. What i do as a work around is launch myself, then switch via F2 to my co-pilot view then R-Alt + J to take over, launch and then flick back over to my Cat and then order him into a specific formation. If i don't order a specific formation he often just engage burner until he runs out of fuel and then ejects. Link to comment Share on other sites More sharing options...
Recommended Posts