Pizzicato Posted November 28, 2019 Share Posted November 28, 2019 (edited) Grabbed today's 2.5.5.40269 Open Beta, and it looks like wingmen are suddenly able to detect targets at very extreme ranges. Flying the F/A-18 with my AI wingman, he started calling out targets at anywhere from 200nm to 350nm (see attached screenshot). Given that the Hornet's maximum radar display range is 160nm, this seems like a bug. EDIT: Added a very brief track demonstrating my wingman detecting two Mig-29s at 400nm.Wingman Detection.trk Edited November 28, 2019 by Pizzicato i7-7700K @ 4.9Ghz | 16Gb DDR4 @ 3200Mhz | MSI Z270 Gaming M7 | MSI GeForce GTX 1080ti Gaming X | Win 10 Home | Thrustmaster Warthog | MFG Crosswind pedals | Oculus Rift S Link to comment Share on other sites More sharing options...
Frederf Posted November 28, 2019 Share Posted November 28, 2019 I think it's the RWR. Try setting an enemy F/A-18 and then fly against it at long range with and without your radar on and pointed in their direction. Link to comment Share on other sites More sharing options...
Pizzicato Posted November 28, 2019 Author Share Posted November 28, 2019 I think it's the RWR. Try setting an enemy F/A-18 and then fly against it at long range with and without your radar on and pointed in their direction. I'm not sure I understand. It's my wingman who's detecting the targets, not me. I'm not sure what turning my own radar off would achieve. I'm also not sure why an enemy F/A-18 would be a better test case than an enemy Mig-29. Am I missing something? i7-7700K @ 4.9Ghz | 16Gb DDR4 @ 3200Mhz | MSI Z270 Gaming M7 | MSI GeForce GTX 1080ti Gaming X | Win 10 Home | Thrustmaster Warthog | MFG Crosswind pedals | Oculus Rift S Link to comment Share on other sites More sharing options...
Rowan Posted November 28, 2019 Share Posted November 28, 2019 "AI Wingmen will use radar by default without player permission." This was in the latest beta patch, so maybe that's what causing it. Link to comment Share on other sites More sharing options...
ED Team BIGNEWY Posted November 28, 2019 ED Team Share Posted November 28, 2019 Hi yes wingmen are now using RADAR by default, which is what you are most likely seeing here thanks Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2 Link to comment Share on other sites More sharing options...
Pizzicato Posted November 28, 2019 Author Share Posted November 28, 2019 Hi yes wingmen are now using RADAR by default, which is what you are most likely seeing here thanks Yeah, I know that. My point is that they shouldn’t be able to spot targets at 400nm when the radar’s display limit is 160nm. i7-7700K @ 4.9Ghz | 16Gb DDR4 @ 3200Mhz | MSI Z270 Gaming M7 | MSI GeForce GTX 1080ti Gaming X | Win 10 Home | Thrustmaster Warthog | MFG Crosswind pedals | Oculus Rift S Link to comment Share on other sites More sharing options...
Pizzicato Posted November 28, 2019 Author Share Posted November 28, 2019 Given the responses to date, I feel as though I've done a poor job of communicating the issue. Just so we're all on the same page, the reasons I think this is a pretty major and important issue are: 1. REALISM / CHEATING - When the AI can see 3x further than a human pilot flying the same aircraft, that's a really major issue. Aside from the clear issues with realism, I suspect that this also implies a bunch of gameplay issues, too. 2. IMMERSION-BREAKING - It totally breaks any potential for surprise/discovery/ambush when your wingman acts like a mini-AWACS and instantly calls out every single contact on the map. There's no anticipation or foreboding about what might lie in wait at the target point when your wingman's already announced absolutely everything. 3. ANNOYING RADIO CALLS - I've been building a mission that has a lot of air traffic. It's now the case that the wingman makes 30+ "new contact" calls after takeoff - even when the targets in question are 3x further away than his radar should be able to see. Put these all together, and this feels like a really significant issue that needs to get resolved in the pretty near future. i7-7700K @ 4.9Ghz | 16Gb DDR4 @ 3200Mhz | MSI Z270 Gaming M7 | MSI GeForce GTX 1080ti Gaming X | Win 10 Home | Thrustmaster Warthog | MFG Crosswind pedals | Oculus Rift S Link to comment Share on other sites More sharing options...
falcon_120 Posted November 28, 2019 Share Posted November 28, 2019 (edited) Given the responses to date, I feel as though I've done a poor job of communicating the issue. Just so we're all on the same page, the reasons I think this is a pretty major and important issue are: 1. REALISM / CHEATING - When the AI can see 3x further than a human pilot flying the same aircraft, that's a really major issue. Aside from the clear issues with realism, I suspect that this also implies a bunch of gameplay issues, too. 2. IMMERSION-BREAKING - It totally breaks any potential for surprise/discovery/ambush when your wingman acts like a mini-AWACS and instantly calls out every single contact on the map. There's no anticipation or foreboding about what might lie in wait at the target point when your wingman's already announced absolutely everything. 3. ANNOYING RADIO CALLS - I've been building a mission that has a lot of air traffic. It's now the case that the wingman makes 30+ "new contact" calls after takeoff - even when the targets in question are 3x further away than his radar should be able to see. Put these all together, and this feels like a really significant issue that needs to get resolved in the pretty near future. You did a perfectly fine job of stating the point in the OP, the responses on the other hand were not related to the issue you raise. By all means that seems like a bug. PS:Additionally, even if they detect the enemy planes thanks to their RWR, it would still be a bug since they should only give you bearing not distance. Edited November 28, 2019 by falcon_120 Link to comment Share on other sites More sharing options...
Exorcet Posted November 28, 2019 Share Posted November 28, 2019 AI radar performance is reported: https://forums.eagle.ru/showthread.php?t=244357 Awaiting: DCS F-15C Win 10 i5-9600KF 4.6 GHz 64 GB RAM RTX2080Ti 11GB -- Win 7 64 i5-6600K 3.6 GHz 32 GB RAM GTX970 4GB -- A-10C, F-5E, Su-27, F-15C, F-14B, F-16C missions in User Files Link to comment Share on other sites More sharing options...
Pizzicato Posted November 28, 2019 Author Share Posted November 28, 2019 (edited) AI radar performance is reported: https://forums.eagle.ru/showthread.php?t=244357 Ah. Perfect. Thanks for the response and the link, Exorcet. Much appreciated. :thumbup: It's obviously less great that it hasn't been addressed 5 months after being reported, though... :hmm: Edited November 28, 2019 by Pizzicato i7-7700K @ 4.9Ghz | 16Gb DDR4 @ 3200Mhz | MSI Z270 Gaming M7 | MSI GeForce GTX 1080ti Gaming X | Win 10 Home | Thrustmaster Warthog | MFG Crosswind pedals | Oculus Rift S Link to comment Share on other sites More sharing options...
ED Team BIGNEWY Posted November 29, 2019 ED Team Share Posted November 29, 2019 yes it is already reported Thanks Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now