Dragon1-1 Posted March 20 Posted March 20 In M6, the starting positions mean the wingman tries to taxi first and collides with the player's aircraft. The only fix is to manually tell the crew to pull chocks and get out of the way. This positions probably work for Hornets, but not for much larger F-14s. I suggest moving the player to another spot that doesn't have this problem. 1
Sandman Simulations Posted March 21 Posted March 21 12 hours ago, Dragon1-1 said: In M6, the starting positions mean the wingman tries to taxi first and collides with the player's aircraft. The only fix is to manually tell the crew to pull chocks and get out of the way. This positions probably work for Hornets, but not for much larger F-14s. I suggest moving the player to another spot that doesn't have this problem. Hi, Thank you for your report. I'll take a look.
Sandman Simulations Posted March 21 Posted March 21 On 3/20/2025 at 5:57 PM, Dragon1-1 said: In M6, the starting positions mean the wingman tries to taxi first and collides with the player's aircraft. The only fix is to manually tell the crew to pull chocks and get out of the way. This positions probably work for Hornets, but not for much larger F-14s. I suggest moving the player to another spot that doesn't have this problem. Just tested and I wasn't able to replicate the issue. It shouldn't be the parking position as the wingman should never taxi befor the player unless there is a bug (again) with the deck crew. Do you have the latest version? In the last version there was a taxi issue where the wingman taxied immediately when the player saluted for taxi but that was fixed by ED.
Dragon1-1 Posted March 21 Author Posted March 21 (edited) I finished it (by taxiing out of the way before signaling) right before the update. I didn't check after the patch. It's possible it's been fixed. Edited March 21 by Dragon1-1
Sandman Simulations Posted March 21 Posted March 21 40 minutes ago, Dragon1-1 said: I finished it (by taxiing out of the way before signaling) right before the update. I didn't check after the patch. It's possible it's been fixed. Please report if the issue still happens after the update. If it's the same problem it was with both Hornet and Tomcat and in any mission.
Recommended Posts