RS2001WRC Posted December 30, 2018 Posted December 30, 2018 Like in topic - when I select gun Auto Aquisition mode, no dashed circle is displayed on the HUD. Same situation is when I select vertical scanning - none of 2 vertical lines are displayed on the HUD. All this happened after latest update. Thanks in advance for the help.
RS2001WRC Posted December 31, 2018 Author Posted December 31, 2018 What does it mean [FIXED IN OPEN BETA]? It will be fixed in the next update?
Svend_Dellepude Posted December 31, 2018 Posted December 31, 2018 Well, in open beta it shows when you switch to guns. but if you chose another mode and then undesignate, then it doesn't revert to the widesearch like it used to. [sIGPIC][/sIGPIC] Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.
RS2001WRC Posted January 2, 2019 Author Posted January 2, 2019 Thanks for the reply, but in my case it never appears (dashed circle) even if my first selection are guns.
Svend_Dellepude Posted January 2, 2019 Posted January 2, 2019 Do you run OB or release? [sIGPIC][/sIGPIC] Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.
RS2001WRC Posted January 3, 2019 Author Posted January 3, 2019 You mean which version od DCS World I use or Hornet module?
Svend_Dellepude Posted January 3, 2019 Posted January 3, 2019 DCS version. If I'm not mistaken, the release is a step behind. OB is the test platform for an update, and if there are no showstoppers release version is then updated. So approx every two weeks OB and release is the same version. Then ED will update OB, and so forth. If you are on DCS release version, you will get the fix in the next update. [sIGPIC][/sIGPIC] Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.
RS2001WRC Posted January 3, 2019 Author Posted January 3, 2019 My version is 2.5.3.24984 so it is the latest one. I installed every single update since 2.5 version appeared.
Tholozor Posted January 3, 2019 Posted January 3, 2019 Latest Open Beta version is 2.5.4.25729, so you're probably on the Stable release. REAPER 51 | Tholozor VFA-136 (c.2007): https://www.digitalcombatsimulator.com/en/files/3305981/ Arleigh Burke Destroyer Pack (2020): https://www.digitalcombatsimulator.com/en/files/3313752/
unknown Posted January 4, 2019 Posted January 4, 2019 My version is 2.5.3.24984 so it is the latest one. I installed every single update since 2.5 version appeared. What Tholozor said, your are on the stable release branch, not on the open beta branch. DCS version overview: https://updates.digitalcombatsimulator.com/ Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings
RS2001WRC Posted January 4, 2019 Author Posted January 4, 2019 So I have done everything allright and only wait for an update or I have to do something to overcome this bug? :)
RS2001WRC Posted January 5, 2019 Author Posted January 5, 2019 Thanks, that's the answer I was looking for ;)
Recommended Posts