reported earlier Radar track files

[Ahmed]

In this last update, the radar track files seem completely broken.

After some testing, it looks like the track files are being dropped within 6 seconds, ignoring age setting. (EDIT: age setting is unrelated to this. However, the "new" 6 seconds are still wrong and result in anything with a frame time greater than 6 seconds being unable to generate/keep a track file. This processing is at the very least performed after one full frame).

This means that only very small search volumes (az/bar/prf setting) will result in a track file being generated and maintained in this DCS update... and severely affect Hornet air-to-air performance in SP and MP.

Track attached. 

rdr.trk

Edited June 9, 2023 by Ahmed

[Krippz]

This has been reported internally. 

[online1034]

  In this video, I try to shot down that F-15C with gun, but the ring only track the enemy a few seconds and stop, make the gun's crosshair inaccurate. So, this is a bug or new feature of the new radar model?
  By the way, I found BST mode also hard to lock enemy too, even an aircraft within 3nm, radar still can't target enemy aircraft easily.

 

[rob10]

Likely what you're seeing is what's described in this thread:

 

[vctpil]

Hi,

Just for information, I also have the problem with the F-16.

Cheers,

[stonewall197922]

1 минуту назад, vctpil сказал:

Hi,

Just for information, I also have the problem with the F-16.

Cheers,

Hi,

Does your "symptoms" looks like  to those described here?

 

[boerdi]

Quite frustrating when the radar gives you no STT lock in ACM mode

Or did I miss something?

Current Open Beta 2.8.6.41066 (MT)

 

[Blackfyre]

It is a bug

 

[BIGNEWY]

threads merged

[Ergo 1-1 Sharko]

 

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

Edited August 5, 2023 by Ergo 1-1 Sharko

[Ergo 1-1 Sharko]

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.

[ianick]

+1

TWS is quite useless nowadays

[Lord Vader]

Hi @Ergo 1-1 Sharko

I am a bit confused with what you are describing. What is reported is the fact that system tracks are being dropped too easily in STT, especially in ACM modes. This is still being addressed internally. Although the bug may interfere with BVR modes, you're referencing something different. You're talking about the "data ageing" setting, which is something different.

Observing your track, you lock the target with TWS and crank to the left, losing that system track. when you return, however, you're at 80nm range scan, when the target is about 90+nm. I took over then and was able to observe the brick in position. Note that you can see the "memory" track and the new ping from the first sweep, creating "two" contacts:

I was then able to lock again as a system target with TWS, unlock it, crank again, retain target general position in memory within the 32 seconds setting and recovered it once more.

What am I missing here? 

Thanks.

[Ergo 1-1 Sharko]

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,

Edited August 7, 2023 by Ergo 1-1 Sharko

[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."

Edited August 7, 2023 by Ergo 1-1 Sharko

[Lord Vader]

We will need to take a better a look at this. Thanks for letting us know. 

[BIGNEWY]

Hi, 

we have merged the post for now, we have some related work in progress regarding AGE for a future update. 

thank you