AstonMartinDBS Posted May 21, 2021 Posted May 21, 2021 (edited) The already reported and in this thread described issue is still present in the current OB. I'm unable to track the movin' tanks - even under a distance of 1 nm. @BIGNEWY commented there as follows: Tracks: LITENING: FA-18C LITENING PT issue.trk ATFLIR: FA-18C ATFLIR AUTO issue.trk BTW: Sorry for opening a new thread, but the original one has already been closed. Edited May 21, 2021 by AstonMartinDBS 1 [Modules] A-10C, A-10C II, AH-64D, F-4E, F-14A/B, F-16C, F/A-18C, FC3, Ka-50, P-51D, UH-1H, CA, SC [Maps] PG, NTTR, Normandy, Sinai, Syria, TC [OS] Windows 11 Pro [PC] MSI Pro Z790-A, i9-13900K, 128 GB DDR5, RTX 4090 24 GB GDDR6X, 2 x SSD 990 PRO 2 TB (M.2), Corsair 5000D Airflow, HX1500i, H150i RGB Elite, Acer X28, TM HOTAS Warthog (Grip@WarBRD Base), MS SW FFB2, Thrustmaster TFRP, TrackIR 5 & TrackClip Pro [Checklists] A-10C, F-16C, F/A-18C, AH-64D, Ka-50, UH-1H
ED Team BIGNEWY Posted May 21, 2021 ED Team Posted May 21, 2021 Hi, It is reported and the team are reviewing it currently. We lock threads after they have been reported so we dont get pointless +1's and none report related comments, it just clutters up the bug forum and hides reports that may need to be addressed still. 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