LeCuvier Posted March 7, 2020 Posted March 7, 2020 When I engage hostiles with AIM-120C in BVR mode , I get the "Shoot!" cue only when I'm at a range of 11 nm. And that's fairly independent of whether I'm flying almost head-on, with a closing speed around 800, or in pursuit with a much lower Vc. My winman fires his missile from a range of 20 nm which sounds much more like BVR range. Does the F/A-18C have a bug in the logic that determines when to display "Shoot!"? LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5
Fri13 Posted March 7, 2020 Posted March 7, 2020 I get periodically at around 14-20 nmi depending common values. If I wait further down, close to NEZ regardless that target is non-maneuvering and head-on (set in editor not to evade or do anything) I have change to hit one. But if I launch on moment I get "shoot" it likely miss. I don't trust that system a bit... i7-8700k, 32GB 2666Mhz DDR4, 2x 2080S SLI 8GB, Oculus Rift S. i7-8700k, 16GB 2666Mhz DDR4, 1080Ti 11GB, 27" 4K, 65" HDR 4K.
DD_Fenrir Posted March 7, 2020 Posted March 7, 2020 AI will fire when just within Rmax. Their PK will be substantially lower. If you are waiting for the flashing shoot cue, you're waiting for Rne, which will increase your PK markedly. Altitude will also play a part. Under 20,000ft 11nm for an Rne launch seems about right.
AEOLUS3 Posted March 7, 2020 Posted March 7, 2020 my opinion is that amram 120c is totally stupid ! I've noticed a lot of times in Tackview how easily following chaff and losing the Target. I am fan of the F/A-18C but on that moment AMRAM is totally stupid. For example, for 27ER or SD-10 or Phoenix does not happen the same ! Is it fair ?
David OC Posted March 7, 2020 Posted March 7, 2020 (edited) my opinion is that amram 120c is totally stupid ! I've noticed a lot of times in Tackview how easily following chaff and losing the Target. I am fan of the F/A-18C but on that moment AMRAM is totally stupid. For example, for 27ER or SD-10 or Phoenix does not happen the same ! Is it fair ? Please don't use words like fair lol.:) Not what I'm seeing going against good players online in the JF-17 More like this. Same 120c just on the F-15 See Tacview 7:08 Edit Unless something got nerfed last big BETA updates (Not tested) Upload track and or Tacview would help. Edited March 7, 2020 by David OC i7-7700K OC @ 5Ghz | ASUS IX Hero MB | ASUS GTX 1080 Ti STRIX | 32GB Corsair 3000Mhz | Corsair H100i V2 Radiator | Samsung 960 EVO M.2 NVMe 500G SSD | Samsung 850 EVO 500G SSD | Corsair HX850i Platinum 850W | Oculus Rift | ASUS PG278Q 27-inch, 2560 x 1440, G-SYNC, 144Hz, 1ms | VKB Gunfighter Pro Chuck's DCS Tutorial Library Download PDF Tutorial guides to help get up to speed with aircraft quickly and also great for taking a good look at the aircraft available for DCS before purchasing. Link
LeCuvier Posted March 8, 2020 Author Posted March 8, 2020 Very interesting stuff David! Actually it was a useful lesson for me. Thanks for the good work! LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5
WOPR Posted March 8, 2020 Posted March 8, 2020 More like this. Same 120c just on the F-15 We don't actually know this to be a fact. I agree it would be silly if it weren't true, but I have noticed different performance with different launch platforms (and like you, I haven't tested with this patch).
Harker Posted March 9, 2020 Posted March 9, 2020 We don't actually know this to be a fact. I agree it would be silly if it weren't true, but I have noticed different performance with different launch platforms (and like you, I haven't tested with this patch). The missile is the same. From my tests, assuming that the launching platforms maintain the same speed and altitude, what changes is the ASE circle and range cues, the way it's supported by the radar and (sometimes) its mid-course flight profile. All of these are platform-specific and very much WIP, at least in the Hornet. For example, if an AMRAAM is launched in TWS in the Hornet, it does not receive mid-course guidance and that's clearly a bug. The steering dot is also wrong for lead, for example, so that's WIP. The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord. F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3 - i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro
CBStu Posted March 10, 2020 Posted March 10, 2020 This is weird to me that there seems to be so much variation in performance between posters. I do single player only against the AI in the missions in Caucusus and PG. For me the 7 is useless and the 120 my favorite.
Harker Posted March 10, 2020 Posted March 10, 2020 This is weird to me that there seems to be so much variation in performance between posters. I do single player only against the AI in the missions in Caucusus and PG. For me the 7 is useless and the 120 my favorite. That's because the testing conditions are not consistent between different players. One person might be testing at 20,000 ft and Mach 0.9, another at 30,000 ft and Mach 1.2, against an incoming target at the same speed and altitude or something else. Or fail to take the differences between launching platforms into account, ie the F-15C can fire at much higher speeds than the F-18, so if the test is "spawn-> go full AB for a bit-> fire", then of course the AIM-120 fired from the F-15C will perform better. The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord. F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3 - i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro
Preendog Posted March 10, 2020 Posted March 10, 2020 This. You can get kills with sidewinder at 25 miles engagement range under the right conditions.
CarbonFox Posted March 10, 2020 Posted March 10, 2020 Before the rework, I usually had to wait until I was within 20nm to launch an AIM-120C in most scenarios, including higher altitude. After rework, I've had far more consistent launches from 25nm+ from target. The farthest launch I had was at 32nm. F/A-18C; A-10C; F-14B; Mirage 2000C; A-4E; F-16C; Flaming Cliffs 3
Baikingu Posted March 10, 2020 Posted March 10, 2020 The missile is the same. From my tests, assuming that the launching platforms maintain the same speed and altitude, what changes is the ASE circle and range cues, the way it's supported by the radar and (sometimes) its mid-course flight profile. All of these are platform-specific and very much WIP, at least in the Hornet. For example, if an AMRAAM is launched in TWS in the Hornet, it does not receive mid-course guidance and that's clearly a bug. The steering dot is also wrong for lead, for example, so that's WIP. Yeah I have posted these issues in the bug section. Both the mid-course guidence and steering dot lead bug. Santi871 said the TWS mid-course guidence bug was already reported internally. But I have'nt gotten a confirmation about the steering dot lead bug yet
Recommended Posts