Ergo 1-1 Sharko

You can find a Track after downgrade here to better illustrate the issue Data Ageing DCS 2.8.5.40170 Open Beta .trk You can find the same track with the current version here. Data Ageing actual version.trk I wanted to point out this topic in relation to the "track files" because it is indeed a problem of track files that disappear when they should not. I apologize if I did not put you on the right track right away."

Hi @Lord Vader, When the aircraft is at 80 or 10 nautical miles, with the data aging set to 32, in TWS, the track file should not disappear instantly as it is currently. The HAFU contact should turn to dim yellow (which means that the radar no longer has the lock on the target for approximately 16 seconds and plays the extrapolation during this period, then disappears if the target is not recovered. In case of recovery of the target, the HAFU contact turns to bright yellow, which means that the radar has resumed acquisition). Regardless of the distance or the fact that the target is not recovered by returning, the fact that the track file disappears instantly is a problem. I have videos that illustrate the problem, but no track file. If necessary, I will have to downgrade to a version prior to June 8 to easily prove my claims. Thank you for your attention. Best regards,

With data ageing set to 32, the HAFU contact should remain visible on the radar for at least 16 seconds. If the contact is not reacquired during that time, it should disappear. However, currently, the contact disappears immediately.

Dear Eagle Dynamics, I am writing to you today to express my concern about the "Radar track files" bug in the F/A-18C. This bug has been present since the DCS 2.8.6.41066 Open Beta update, and it has not been fixed in any of the subsequent updates. The bug affects the "data ageing" setting in the radar menu. This setting controls the number of seconds that a target track is kept in memory after it is lost. With the bug present, the "data ageing" setting has no effect, and target tracks are lost nearly immediately after they are lost. This bug has a significant impact on the F/A-18C's beyond-visual-range (BVR) capabilities. In BVR combat, it is important to be able to keep track of multiple targets, and the "data ageing" setting is essential for doing this. With the bug present, it is very difficult to keep track of multiple targets. This bug was reported to the DCS World forum on June 9th, 2023, by other users as well. The thread was closed by a moderator with the message "reported earlier." The stable version of DCS World has now been updated, and it is unclear whether people who play the stable version will have to deal with this bug until the next update, or if you have decided that it is not a bug after all. Thank you for your time and consideration. Sincerely, Data Ageing.trk

Hi @Flappie sorry for the late response. I had already installed the pack a long time ago, so I can't say anything about it. Since the last issues, I haven't been playing with the MT version. I will test it again soon. Currently, I am not experiencing any problems with the old drivers and the non-MT version.

Hello, I also have a RX 5700 XT and, like you, I have the same problem. For me, the up-to-date AMD drivers crash every 5 minutes. At the moment, the only solution I have found is to use the 22.5.1 drivers and not play in MT. Since the last update, I thought the problem was solved, so I tried playing in MT while still using the 22.5.1 drivers, but I had the crash again. On my end, I have noticed that crashes occur very often in Syria and less often in Caucasus. dcs.log-20230417-194024.zip