flankerjun Posted December 21, 2019 Posted December 21, 2019 Hello guys,I am practice TWS mode in MP server,but i find that the target is already in range,but no shoot on HUD. 223750_20191221203655_1 by fang jun, 於 Flickr 223750_20191221195205_1 by fang jun, 於 Flickr A-10C Warthog,Flaming Cliffs 3,F-16C VIPER,F/A-18C HORNET,Super Carrier,AV-8B Night Attack V/STOL,Mi-8MTV2 Magnificent Eight,Black Shark 2,SA342 Gazelle,UH-1H Huey,Persian Gulf Map,Combined Arms Intel i7-14700KF| Colorful iGame GeForce RTX 2070 AD Special OC GDDR6 8G | Acer PREDATOR 32g DDR5 6000MHZ | MSI PRO Z790A-MAX | Kingston KC3000 1T SSD M.2 | ST 12T HDD 7200RPM | AOC 2790PQU 27'' 4K |Thrustmaster Hotas Warthog PC
sgray Posted December 21, 2019 Posted December 21, 2019 We have had a member report that TWS didn't working in MP, but worked fine in SP. If this is true, I hope that it can be correct with another hot fix ASAP. vCAPT Scott "LoVis" Gray Chief of Naval Personnel Virtual United States Navy - VUSN vusn.org
CrazyGman Posted December 21, 2019 Posted December 21, 2019 I have noticed the same thing in single player when practicing with TWS Says that it's inside Rmax on the attack radar. but on the hud it shows that it is outside of Rmax. So one of them is wrong.
Longiron Posted December 21, 2019 Posted December 21, 2019 Also noticed if you hit uncaged while in rws + ltws you can get shoot cue, making pure tws totally useless. Only benefit would be tws engagement on more than 2 targets. Makes sense as there seems to be no Hotas for tws rws switching.
ED Team NineLine Posted December 21, 2019 ED Team Posted December 21, 2019 (edited) Hello guys,I am practice TWS mode in MP server,but i find that the target is already in range,but no shoot on HUD. Both your images show you just outside Rmax Edited December 21, 2019 by NineLine Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug**
CrazyGman Posted December 21, 2019 Posted December 21, 2019 Both your images show you just outside Rmax On the HUD yes, in the Attack radar on the DDI it shows it in range. That is the issue
maxTRX Posted December 21, 2019 Posted December 21, 2019 On the HUD yes, in the Attack radar on the DDI it shows it in range. That is the issue The top of the launch zone line on the DDI is MAX aero
Ramsay Posted December 21, 2019 Posted December 21, 2019 (edited) Both your images show you just outside Rmax On the HUD yes, in the Attack radar on the DDI it shows it in range. That is the issue Found the same when doing comparative tests of F/A-18C AIM-120C vs the JF-17 SD-10. For info. testing M1.2 @ 32,800 ft (10,000m) head on vs a non-manoeuvring target (MiG-23). DCS FA-18C vs MiG-23 Radar TWS detection/lock @ 70 NM Max range successful AIM-120C @ 44 NM (81 km) (impact @ 520 TAS i.e. almost stalling) AIM-120C Radar Max LAR range* = ~44NM Below 500 TAS, increased AoA/drag causes both missiles to fall *Doesn't match HUD cues in 2.5.5.41371 I assume the HUD range cues aren't dynamic, while the attack radar LAR(s) are. IIRC the max aero HUD diamond equalled approx 38 NM JF-17 AIM-120 test, 2_5_5_41371, LastMissionTrack.trk Edited December 21, 2019 by Ramsay Add track and screenshot i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
Harker Posted December 21, 2019 Posted December 21, 2019 The HUD cues should match the DDI cues, at the respective quantities (Raero/Rmax not sure, Rne, Rmin). I think it's simply a matter of updating the DLZ calculation to reflect the changes to the missile. Right now, it seems like the calculation doesn't take the new changes into account. 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
ED Team NineLine Posted December 22, 2019 ED Team Posted December 22, 2019 I'll look and see if it needs reporting, thanks! Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug**
maxTRX Posted December 23, 2019 Posted December 23, 2019 The top of the launch zone line on the DDI is MAX aero Finally had a chance to try it in SP. It is off. Even if the top of LZ on ATTK page is R_aero it doesn't match up with the HUD. 1v1 against JF17 (AI): https://youtu.be/OGO-L64w0AE
Cytarabine Posted December 23, 2019 Posted December 23, 2019 I think the HUD range queue might be the issue here as I have connected several shots (in SP) where the target has been in range according to the MFD but not according to the HUD which means no time to missile active or time to impact on the HUD.
ED Team NineLine Posted December 23, 2019 ED Team Posted December 23, 2019 I tried it on our internal version and all looks good. So next patch check it again and see if it's working correctly then. Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug**
NoJoe Posted January 16, 2020 Posted January 16, 2020 (edited) I tried it on our internal version and all looks good. So next patch check it again and see if it's working correctly then. I'm still seeing a difference after the latest beta. The DDI radar display shows the target inside the top of the range bracket, while the HUD shows it still outside the max aero diamond. Edited January 16, 2020 by NoJoe
maxTRX Posted January 16, 2020 Posted January 16, 2020 I'm still seeing a difference after the latest beta. The DDI radar display shows the target inside the top of the range bracket, while the HUD shows it still outside the max aero diamond. Same here. Hasn't been fixed yet.
Recommended Posts