MARLAN_ Posted August 26, 2022 Posted August 26, 2022 (edited) DLZ do not correctly indicate ranges which is extremely important for knowing whether a shot is valid or not. I would guess a calculation somewhere is incorrect, and may also be relevant to why the LOST cue is still indicating at the wrong time consistently. Tacview-20220826-180901-DCS-DLZInaccurate_40NM_35K_0ATA_AND_35NM_35K_45ATA_HOT.trk.zip.acmi Tacview-20220826-180751-DCS-DLZInaccurate_25nm_25K_45ATA_HOT.trk.zip.acmi Tacview-20220826-180700-DCS-DLZInaccurate_5NM_15K_0ATA_COLD.trk.zip.acmi DLZInaccurate_5NM_15K_0ATA_COLD.trk DLZInaccurate_25nm_25K_45ATA_HOT.trk DLZInaccurate_40NM_35K_0ATA_AND_35NM_35K_45ATA_HOT.trk Edited August 26, 2022 by MARLAN_ 3 Virtual CVW-8 - The mission of Virtual Carrier Air Wing EIGHT is to provide its members with an organization committed to presenting an authentic representation of U.S. Navy Carrier Air Wing operations in training and combat environments based on the real world experience of its real fighter pilots, air intercept controllers, airbosses, and many others.
ED Team BIGNEWY Posted August 29, 2022 ED Team Posted August 29, 2022 I have asked the team to take a look. thanks 1 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, PIMAX Crystal
maxTRX Posted August 30, 2022 Posted August 30, 2022 This issue has been reported in the bugs forum and the tracks provided by MARLAN_. I haven't seen the tracks. Perhaps some of them already confirm what I've just noticed. In a co-altitude engagement, I didn't see any obvious discrepancies between NIRD zones on the HUD and LZ on the ATTK, when using Amraams. In a steep look down, the NIRD indications were different from LZ. I think LZ was correct... then again
MARLAN_ Posted December 17, 2022 Author Posted December 17, 2022 (edited) LOST cue was reported 8 months ago (and has been a problem much longer), DLZ 4 months ago (also a problem for a much longer time than that) Do these bugs have any priority? The LOST cue flashing when missiles are in fact not lost is distracting, confusing for new players, and hides valuable information such as ACT XX or TTG XX. The DLZ being inaccurate still perhaps may be attributing to why the LOST cue is inaccurate, and the DLZ itself is very very important for knowing when your missiles are, or aren't valid but if the DLZ can't be trusted then it loses its purpose entirely. Depending how the code is coupled, the steering dot may also be relevant to these issues because if correct lead and loft angles are not calculated by the aircraft that will also drastically affect the predicted DLZ. Edited December 17, 2022 by MARLAN_ 5 Virtual CVW-8 - The mission of Virtual Carrier Air Wing EIGHT is to provide its members with an organization committed to presenting an authentic representation of U.S. Navy Carrier Air Wing operations in training and combat environments based on the real world experience of its real fighter pilots, air intercept controllers, airbosses, and many others.
ED Team BIGNEWY Posted December 17, 2022 ED Team Posted December 17, 2022 When we have news to share we will. thanks 1 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, PIMAX Crystal
Gierasimov Posted January 25, 2023 Posted January 25, 2023 (edited) Hi Is this "correct as is"? Same engagement, 1st attempt - when AMRAAM is fired in VISUAL mode, I can get a kill from ~25nmi. The max that worked for me when tried repeatedly was 30nmi in this particular setup (.miz) - 120-Visual.trk 2nd attempt - If I lock up the target, the Maximum Launch Range (RMAX) is computed to about 13nmi. - 120-Locked.trk Also in the 120-Locked.trk there seems to be few seconds delay between target locked and HUD display symbology, in particular target box, range and AIM-120 Time to Active (ACT). I know that Steering Dot issue is already reported (lack of SHOOT cue) but I am specifically asking about the engagement ranges between two modes of firing. OR perhaps, this is all connected to current issues with Hornet A2A mode altogether and this post is not needed at all? Thanks. 120C-Locked.trk 120C-Visual.trk Edited January 25, 2023 by Gierasimov added a screen confirming a kill from visual Intel Ultra 9 285K :: ROG STRIX Z890-A GAMING WIFI :: Kingston Fury 64GB :: MSI RTX 4080 Gaming X Trio :: VKB Gunfighter MK.III MCG Ultimate :: VPC MongoosT-50 CM3 :: non-VR :: single player :: open beta
MARLAN_ Posted January 25, 2023 Author Posted January 25, 2023 If I understand you correctly, you're comparing the actual missile performance (launch in VISUAL) vs. the predicted missile performance (rmax in this case)? If so: DLZ has been bugged for a long time, hopefully something ED can fix soon. Possibly attributes to other issues like the LOST cue has been broken for a very long time. 1 1 Virtual CVW-8 - The mission of Virtual Carrier Air Wing EIGHT is to provide its members with an organization committed to presenting an authentic representation of U.S. Navy Carrier Air Wing operations in training and combat environments based on the real world experience of its real fighter pilots, air intercept controllers, airbosses, and many others.
ED Team BIGNEWY Posted January 26, 2023 ED Team Posted January 26, 2023 Posts merged, we do have a report open to check DLZ implementation thanks 1 1 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, PIMAX Crystal
Recommended Posts