Gnadentod Posted January 10, 2020 Posted January 10, 2020 (edited) When it happened once I just wrote it off as ... well whatever. Now, I had it happen two times in three sessions that, when I want to bug a bandit in TWS radar mode when we're approaching each other very fast within about 10 to 20nm the radar actually locks a bandit behind my wanted target in STT mode, which was still 70nm away from me. They were in about the same direction in relation to my aircraft heading. The one which was of zero danger was locked in STT mode although my cursor wasn't even close to being near the radar contact on the MFD. My radar wasn't even configured to scan 80nm but 40nm range at the time, so it makes even less sense. Needless to say this happens in the worst possible time, losing the radar contact of the dangerous bandit and thus the ability to give off the first shot when we're about to merge. Killed me 2/2 times. I've started to watch both trackfiles to upload them and give exact timeframe but once my aircraft approaches the runway it's actually showing me taking off besides the runway, crashing into trees and shit when I never crashed in reality?! So no trackfile I guess. Am I the only one? E: I was on about 3000ft, bandit closing on me in front on 2000ft, like 15 nm. The bandit which was locked behind my actual threat was flying like 17k to 26k feet (guessing from the HUD symbology) and was 77nm out. Edited January 11, 2020 by Der Hirte Terminology
Gnadentod Posted January 11, 2020 Author Posted January 11, 2020 https://megaupload.is/xd7ejdM7n7/Trackfiles_zip I'm not 100% certain TF2 is the correct one, since I can't watch it like I said, but pretty sure. The described situation is at the end of the track, after taking off for the first time. In TF1, after getting to the enemy ground assets and finding out after some time that the TGP and CCRP AG mode isn't usable when there are no waypoints present, I went back to the mountain region to provide some CAP. You'll see described situation pretty quick from there on, it really is near the end of TF1, I guess about 30 to 40 minutes from track start. Hope you can watch the tracks properly synchronized, because I couldn't.
ED Team BIGNEWY Posted January 13, 2020 ED Team Posted January 13, 2020 Hi Unfortunately I could not get the track to play back correctly, We will look out for this, if you see it in a shorter track we would like to see it thank you 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
Gnadentod Posted January 13, 2020 Author Posted January 13, 2020 Yeah, weird isn't it? Especially two times. I will report and provide a new trackfile in case it happens again. Keep up the work, DCS future is probably almost as bright as the sun if things keep going. :7
falcon_120 Posted January 18, 2020 Posted January 18, 2020 Yeah, weird isn't it? Especially two times. I will report and provide a new trackfile in case it happens again. Keep up the work, DCS future is probably almost as bright as the sun if things keep going. :7Exactly the sames happens in the f18. The range gate that should stop this from happening is not implemented (wip), and the viper and the hornet shares a lot of the radar code... Enviado desde mi SM-G950F mediante Tapatalk
jayst0r Posted January 20, 2020 Posted January 20, 2020 YAP can confirm happend to mee too, very rare though.
Recommended Posts