ItsCrisp Posted November 7, 2015 Posted November 7, 2015 (edited) Hello, With this most recent update, changes to the AI behavior have caused collisions on the taxiway between AI pilots. This is a repeatable problem. Description: Playing MiG-15 module. MiG-15 was not started up, nor was ATC contacted in any way. AI only acts according to mission instruction & ATC commands. While holding short for takeoff, an AI controlled Su-27 is rear-ended by another AI Su-27 because it either does not stop in time, or thought its 'collision bubble' was much further away/smaller than it actually was. Another Su-27 collides with the first pair, followed by 2 MiG-29's, which do not make contact with the Su's, but this may be due to the 29's smaller size (57ft vs. 72ft long). The AWACS behind them holds short at a safe distance. Image Track System Info Additional remarks: Before this update, the Su's would take off as intended, however, the 2nd of a group of 3 MiG-29's (3 ship after the Su's takeoff) would refuse to take off after the lead Mig-29 took off, and would hold short on the taxiway, blocking the path for the other MiG-29 and the AWACS. Those MiG's now seem to continue down the taxiway as intended, but stop too close to other aircraft. Edited November 7, 2015 by ItsCrisp
pittnuma Posted November 8, 2015 Posted November 8, 2015 (edited) Just to confirm, I get this aswell. It is repeatable and with the same mission in previous version the crashes did not occur. Also sending my wingman back to RTB causes him to stop on the runway Edited November 8, 2015 by pittnuma Pitt Learn from the mistakes of others. You won't live long enough to make all of them yourself.
rrohde Posted November 9, 2015 Posted November 9, 2015 (edited) Confirmed! According to the patch notes: "Fixed issue when AI get stuck while taxiing if object is in front of a 'junction' for their route." is now a bit too lax. See screenshots here as well; my AI wingman crashed into me while a) I was holding short, and then again b) while I was on the RWY ready for takeoff. Edited November 9, 2015 by rrohde PC: AMD Ryzen 9 5950X | MSI Suprim GeForce 3090 TI | ASUS Prime X570-P | 128GB DDR4 3600 RAM | 2TB Samsung 870 EVO SSD | Win10 Pro 64bit Gear: HP Reverb G2 | JetPad FSE | VKB Gunfighter Pro Mk.III w/ MCG Ultimate VKBcontrollers.com
Barao Posted November 13, 2015 Posted November 13, 2015 I had this problems again (new hotfix 1.5.1.47025.98 ), during taxi, the wingman collided with me while I waited for permission to enter the runway. Dell U2715H 27" IPS 2560x1440 / 60 Hz; Ryzen 7 7700x; 32gb DDR5 6400; B650M Aorus Pro; Water Cooler Arctic liquid freezer II 280
Scaley Posted November 15, 2015 Posted November 15, 2015 Similar issue: Taxied onto the runway and the following AI A-10 (different flight) taxied onto the runway and took off - missed me because I'd lined up for a formation takeoff position as practice. Of note no radio calls heard at any time from the AI A-10 despite being on the tower frequency on VHF AM.AI Takeoff.trk 476th vFighter Group Main Page -- YouTube -- Discord Scaley AV YouTube - More videos from the 476th
Backy 51 Posted November 18, 2015 Posted November 18, 2015 Yep ... working on a multinational coalition mission as we speak and the Mirage 2000-5 keeps pronging my CMOR F-15E's ... Q-3 for ground operations ... :doh: I don't need no stinkin' GPS! (except for PGMs :D) [sIGPIC][/sIGPIC]
Trailer Posted November 19, 2015 Posted November 19, 2015 So is there any word on this? This is a completely game-breaking bug.
Recommended Posts