Rhayvn Posted 18 hours ago Posted 18 hours ago AI aircraft do not react to ARH A2A missiles at all since the patch. Multiple tests. They fly as if the missiles are simply not there. Sometimes a very last minute change can be seen as if they see the missile visually well within a mile. With the same group settings, an SARH missile causes the AI to evade as they did pre-patch. Mostly bad attempts. With a notch and dives or attempts to outrun the missiles but at idle thrust(?) both in notch and extend phases. But, at least they react. Something was broken in the patch. Please don't ask me for a track. This is easily re-created with two AI aircraft in an empty miz with Fox 3s and watching for 30 seconds. 1
rob10 Posted 11 hours ago Posted 11 hours ago You know, the reason why you're going to get asked for a track is that that's a lot easier than messing around trying to recreate what you did. In this case: what player aircraft? What AI aircraft? What ARH A2A missile (AIM-120? Russian one?). What elevation were each at? What bearing were they at? What Advanced Waypoint settings? It saves everyone a lot of time if you take 20 seconds to save and post a track file.
rob10 Posted 10 hours ago Posted 10 hours ago ai non defensive.trk TRACKFILE - Caucuses map. Doesn't react after missile goes pitbull, just flies straight until it takes the missile in the face.
Rhayvn Posted 7 hours ago Author Posted 7 hours ago (edited) 5 hours ago, rob10 said: You know, the reason why you're going to get asked for a track is that that's a lot easier than messing around trying to recreate what you did. In this case: what player aircraft? What AI aircraft? What ARH A2A missile (AIM-120? Russian one?). What elevation were each at? What bearing were they at? What Advanced Waypoint settings? It saves everyone a lot of time if you take 20 seconds to save and post a track file. No, it's not. It takes less than one minute to recreate in the ME as you should know because you did it. All your specific questions are pointless because the answer to them is All. It's not a specific situation. One track file will not show that and people tend to dissect the specifics of a track file rather than looking at the base game issue that this one is. I'm also a little annoyed that something that was so obvious (Noticed in the very first post patch engagement) and prevalent was missed in testing and we are now stuck with it until ED decides to fix it. Which could mean a month or more where BVR lacks even a modicum of challenge. I already spent enough time testing the different aircraft, missiles and waypoint settings to waste more and go and turn track files back on and risk the return of the micro stutters that turning them off eliminated for me. I'm happy to help track down more obscure or difficult to recreate issues and have done so many times in the past. That isn't necessary here. Besides, some joker will almost always post a track when the problem is this easy to recreate, saving me the trouble. Edited 5 hours ago by Rhayvn
Yayo1 Posted 6 hours ago Posted 6 hours ago I also encountered this after latest patch patch. The issue was with sd-10, aim-120b and aim-120c. But AI fighters do defensive maneuvers against the R-77. I did not test it with the AIM-54A/C.
Rhayvn Posted 5 hours ago Author Posted 5 hours ago They seem to occasionally react to AIM-54 and R-77, but not always. It's difficult to tell when it's the AI launching against other AI because it sometimes fires 54s as Fox1. The R-77 also usually is launched in STT by the AI. STT locks cause the AI to react for both the 54 and 77, but not the 120.
rob10 Posted 5 hours ago Posted 5 hours ago (edited) 1 hour ago, Rhayvn said: No, it's not. It takes less than one minute to recreate in the ME as you should know because you did it. All your specific questions are pointless because the answer to them is All. It's not a specific situation. One track file will not show that and people tend to dissect the specifics of a track file rather than looking at the base game issue that this one is. I'm also a little annoyed that something that was so obvious (Noticed in the very first post patch engagement) and prevalent was missed in testing and we are now stuck with it until ED decides to fix it. Which could mean a month or more where BVR lacks even a modicum of challenge. I already spent enough time testing the different aircraft, missiles and waypoint settings to waste more and go and turn track files back on and risk the return of the micro stutters that turning them off eliminated for me. I'm happy to help track down more obscure or difficult to recreate issues and have done so many times in the past. That isn't necessary here. Besides, some yahoo will always post a track for me when the problem is this easy to recreate. This issue one would have thought they should have caught for sure with beta testers playing normally. I'm reasonably proficient with the ME and it too me longer than a minute to set it all up and boot into it. If you had bothered to post a track I wouldn't have needed to. And with the details you provided it definitely wasn't clear that it happened in all aircraft/with all weapons (saying you tested this extensively is meaningless because it could have been variations on the same specific combinations of aircraft that had an issue where others might not have). It baffles my mind why people are so completely resistant to posting a track when they say they've tested it extensively. Just hit save track and post the freaking thing. Honestly it's just the polite thing to do so somebody else doesn't have to spend time recreating it. And this "yahoo" definitely won't be posting tracks for you next time when you have that attitude. The number of times people have tested stuff that's broken, but when they do post a track it's user error..... Edited 5 hours ago by rob10
Rhayvn Posted 5 hours ago Author Posted 5 hours ago "The number of times people have tested stuff that's broken, but when they do post a track it's user error....." Was this user error? Downloading it then loading DCS and pulling up the track takes nearly as much time as setting up two AI aircraft in the ME. This is not a complicated test to create. It also does not tell you what the group/waypoint settings were, whether the recorder is using mods or scripting that may interfere, or a host of other things that can cause strangeness. Already someone else did the same type of test and found additional variables without resorting to a specific track file. Sometimes, doing a simple test yourself is the easiest way to proceed. You wasted more time with your track file lecture than it takes to setup the test. So here we are.
Recommended Posts