Sylosis Posted May 26, 2021 Share Posted May 26, 2021 On a few recent occasions I have flown missions where I click the HSI button to designate my waypoint as my target and it sends the TPOD looking god knows where. Just recently, was flying a mission in the Raven One campaign, selected waypoint 8 in the HSI and used Waypoint Designate to slave FLIR to said waypoint. Waypoint was 15 nm away, to the east, but TPOD went looking north at 90nm (distance to target). I switched back to WPT 7 and back to 8 again, and then it was correct. Anybody has any idea? Windows 10-64bits, i7-8700k, GTX 1080Ti, 32 Gb RAM, MSI Monitor 32in 165Hz. Mirage 2000C, F5-E, Mig21bis, A10-C, FC3, F-18, AV-8B N/A, F-14, F-16, SuperCarrier Link to comment Share on other sites More sharing options...
ED Team BIGNEWY Posted May 26, 2021 ED Team Share Posted May 26, 2021 We do have wpdsg and mark point issues reported we need a short track replay showing your issue to confirm if it is reported already or not. thanks 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, HP Reverb G2 Link to comment Share on other sites More sharing options...
Sylosis Posted May 26, 2021 Author Share Posted May 26, 2021 Yeah... was kinda pissed that I got shot after that "possible glitch" and forgot to save the track. I need to fly it again, so this time, if it does it again, I'll save it and share here. Windows 10-64bits, i7-8700k, GTX 1080Ti, 32 Gb RAM, MSI Monitor 32in 165Hz. Mirage 2000C, F5-E, Mig21bis, A10-C, FC3, F-18, AV-8B N/A, F-14, F-16, SuperCarrier Link to comment Share on other sites More sharing options...
mmoccio Posted May 28, 2021 Share Posted May 28, 2021 (edited) +1 exact same thing happened to me. I can also provide a track if needed. It happened in my own custom mission on Syria. Edited May 28, 2021 by mmoccio F/A-18C | F-16C | JF-17 | F-14 | FC3 | AV-8B | AJS-37 | F-5E | M-2000C | Mig 15bis | C-101 | F-86 | A-10C | P-51D | Fw 190 A-8 | Christen Eagle II | Bf 109 K-4 | Ryzen 5 2600 | MSI RTX 2070 Super | ASROCK B450m Pro | 16GB G.SKill Ripjaws 3200 DDR4 | 500GB WD Blue Internal SSD | 1TB Samsung Evo 860 SSD | Logitech X56 HOTAS | PSEYE Track IR | Delan Clip | :joystick: Link to comment Share on other sites More sharing options...
Heroman30 Posted May 28, 2021 Share Posted May 28, 2021 +1 for me also. I cannot get the pod to lock on to my waypoint target and after I reselect waypoint designate, the pod targets another random coordinate. Link to comment Share on other sites More sharing options...
pete_auau Posted May 28, 2021 Share Posted May 28, 2021 you guys seen this thread at all https://forums.eagle.ru/topic/272228-litening-pod-wont-slew-to-waypoint/?tab=comments#comment-4673043 Link to comment Share on other sites More sharing options...
BATCARLO Posted May 28, 2021 Share Posted May 28, 2021 (edited) On 5/27/2021 at 12:14 AM, BIGNEWY said: We do have wpdsg and mark point issues reported we need a short track replay showing your issue to confirm if it is reported already or not. thanks You can see a short 30 sec. video with the bug here: https://www.dropbox.com/s/ksqdgsqgte3qjmc/PROVA.mp4?dl=0 The designation does not happen on the selected wp, but on the position where the TPOD sensor is even if there was no target designation. Also when the designation is removed, the TPOD sensor moves further close to the aircraft. Same thing if you try to designate the points marked with markpoint, the designation moves to the sensor position of the TPOD. Edited May 28, 2021 by BATCARLO Link to comment Share on other sites More sharing options...
ED Team BIGNEWY Posted May 28, 2021 ED Team Share Posted May 28, 2021 thanks, this is reported 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, HP Reverb G2 Link to comment Share on other sites More sharing options...
Recommended Posts