Dr. Anti-Vehicle Posted July 5, 2021 Posted July 5, 2021 Track file is attached. Youtube link is here. Although in this example, there are more than one bandits. However, it also happens when there is only one. I don't know if it has anything to do with my own missile being scanned by plane's radar. Also, it almost happens 100% of the time. 1.trk
ED Team BIGNEWY Posted July 15, 2021 ED Team Posted July 15, 2021 Hi, I have tested, I can see it in your track replay, when I test on my own all seems ok on our dev build, I am wondering if it is to do with the missile being scanned, I'm going to wait until some fixes have been merged into our internal build and test again, but I think this maybe fixed already internally. 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
Dr. Anti-Vehicle Posted July 15, 2021 Author Posted July 15, 2021 2 hours ago, BIGNEWY said: Hi, I have tested, I can see it in your track replay, when I test on my own all seems ok on our dev build, I am wondering if it is to do with the missile being scanned, I'm going to wait until some fixes have been merged into our internal build and test again, but I think this maybe fixed already internally. That sounds promising. Will test it after the next update. Than you
wilbur81 Posted July 17, 2021 Posted July 17, 2021 On 7/5/2021 at 5:54 PM, Dr. Anti-Vehicle said: Track file is attached. Youtube link is here. Although in this example, there are more than one bandits. However, it also happens when there is only one. I don't know if it has anything to do with my own missile being scanned by plane's radar. Also, it almost happens 100% of the time. 1.trk 1.01 MB · 11 downloads I get this same behavior very frequently... i7 8700K @ Stock - Win10 64 - 32 RAM - RTX 3080 12gb OC - 55 inch 4k Display
Dr. Anti-Vehicle Posted July 17, 2021 Author Posted July 17, 2021 1 hour ago, wilbur81 said: I get this same behavior very frequently... Right? I experience this every single time. Not even exaggerating a bit. I waited weeks before reporting it cuz there is always someone reporting bugs ahead of me. Then I saw no related post. I guess we are very extreme cases?
wilbur81 Posted July 18, 2021 Posted July 18, 2021 1 hour ago, Dr. Anti-Vehicle said: Right? I experience this every single time. Not even exaggerating a bit. I waited weeks before reporting it cuz there is always someone reporting bugs ahead of me. Then I saw no related post. I guess we are very extreme cases? I think, as stated above, that it is related to the Hornet radar being SUPER sensitive to missiles. If you set up a simple BVR, head to head encounter with 3 or 4 bandits off your nose around 45 miles, using TWS/HI PRF... and try to step through the tracks with NWS HOTAS command, the locks are 'jumpy'. i7 8700K @ Stock - Win10 64 - 32 RAM - RTX 3080 12gb OC - 55 inch 4k Display
Dr. Anti-Vehicle Posted July 21, 2021 Author Posted July 21, 2021 On 7/15/2021 at 7:06 AM, BIGNEWY said: Hi, I have tested, I can see it in your track replay, when I test on my own all seems ok on our dev build, I am wondering if it is to do with the missile being scanned, I'm going to wait until some fixes have been merged into our internal build and test again, but I think this maybe fixed already internally. Hello Bignewy, After today's patch, the behavior is still there. I created a mission specifically for this. Single target, 2 AMRAAMs were fired. I used a narrower scan area so that lower refresh rate allows better observation. Track file is attached. I uploaded another video here for anyone is interested. The first "flickering" occurred at 0:24. Then the second series of strange behavior occurred starting from 1:36. After missile went pit bull in second launch, the TTG timer went up to 25 seconds even though bandit didn't maneuver. I am fairly amateur so this is beyond my understanding. Can you please help push this investigation further? Thank you 2.trk
Kapsu Posted July 21, 2021 Posted July 21, 2021 It does that because radar is starting to lose the track file before it does another sweep over the contact thanks to the bugged track file memory system. Increase age out setting from 4 to 8 in the DATA sublevel (aim120 selected) and use smaller scan zone to make it a lot better. [sIGPIC][/sIGPIC] DCS Finland - Finnish DCS community SF Squadron
Dr. Anti-Vehicle Posted July 21, 2021 Author Posted July 21, 2021 (edited) 4 hours ago, Kapsu said: It does that because radar is starting to lose the track file before it does another sweep over the contact thanks to the bugged track file memory system. Increase age out setting from 4 to 8 in the DATA sublevel (aim120 selected) and use smaller scan zone to make it a lot better. Thanks I will give it a try. But it’s annoying af. Update: Changing from 4 to 8 didn't really help unfortunately. Edited July 22, 2021 by Dr. Anti-Vehicle
Recommended Posts