investigating Sweeps for TWS Track-files

[_UnknownCheater_]

In TWS mode the contacts won't automatically displayed as HAFU,and NSW button can't turn the contacts to L&S,need manually use TDC to soft lock the target.No track files,hope someone can upload it.Just check the pic below:

Update：In SP test u can't feel so hard to lock,bcz the stupid AI always can be scaned by radar 5 times.You can go PVP like GS server play a round and u know now how trash the F18 TWS is.You even can't lock the target 20-40Nm bandits without jamming,the HAFU already show it is a bandit with a red highlight diamond but u can't use TDC depress soft lock or NSW set L&S,but Sensor switch right can be do STT.This a big problem for me,before this I thought I lost my keybinds, I know that I have tested many times and found that it is a radar problem.

Edited July 27, 2022 by zhouyut001

[_UnknownCheater_]

Track files uploaded.This test in SP,u can see the RAW contacts need a long time to change to HAFU,if bandits so close with me like 20nm, the RAW contacts wont change to HAFU,and NSW most of time cant set L&S.This is SP test,if u are in MP with normal desync bug and networking issues,the RAW contacts need more time to change to HAFU or wont change to HAFU.So what ED patched in this version?F18 radar died again?Almost fixed ACM bug and add new bugs?

123.trk

Edited July 25, 2022 by zhouyut001

[Tholozor]

Keep in mind the default ageout time for the 120's radar profile is 4 seconds. You can change the time on the DATA submenu, top-right corner, and the weapon radar profile defaults can be saved with the SET option in RWS.

Edited July 24, 2022 by Tholozor

[_UnknownCheater_]

29 minutes ago, Tholozor said:

Keep in mind the default ageout time for the 120's radar profile is 4 seconds. You can change the time on the DATA submenu, top-right corner, and the weapon radar profile defaults can be saved with the SET option in RWS.

 

This is target lost,target symbol alive time not the raw to HAFU time.Important,my target not lost.

Target Aging. The amount of time a target symbol remains on the display after radar contact has been lost can be adjusted with successive presses between 2, 4, 8, 16 and 32 seconds. 

Edited July 24, 2022 by zhouyut001

[wilbur81]

From the changelog...looks like an improvement.  However, it takes five B-Sweeps now to build a track for a hot target at 12 miles off the nose. Intended behavior?

TWSsweeps.trk

Edited July 24, 2022 by wilbur81

[Swift.]

Are you in four bar scan? Not at home so cant check the track, sorry

Edited July 24, 2022 by Swift.

[_UnknownCheater_]

TwS mode need long time, or never change RAW contacts to HAFU

[wilbur81]

5 hours ago, Swift. said:

Are you in four bar scan? Not at home so cant check the track, sorry

 

No, 2 Bar.

[BIGNEWY]

posts merged, investigating

[Max Mak]

On 7/24/2022 at 10:16 AM, zhouyut001 said:

Track files uploaded.This test in SP,u can see the RAW contacts need a long time to change to HAFU,if bandits so close with me like 20nm, the RAW contacts wont change to HAFU,and NSW most of time cant set L&S.This is SP test,if u are in MP with normal desync bug and networking issues,the RAW contacts need more time to change to HAFU or wont change to HAFU.So what ED patched in this version?F18 radar died again?Almost fixed ACM bug and add new bugs?

123.trk 440.53 kB · 2 downloads

 

 

 

I do think the big change in this patch is that the generation of track files required 5 sweeps hits of a brick and turn into HAFU. I actually take control your track files in your last attemp for a Su-33 within 20nm. In this moment you just move too down for your Antenna elevation control, it didn't got the consistent 5 sweeps hit to build the track files. Therefore, I move the radar elevation up a little bit and finally got a consistent 5 sweeps hit to generate the track files. Then, I immediately change to TWS auto to maintain the scan zone focus on the targrt and shoot him a AIM120C and he is hitted. 

I attached my corresponding track file and tacview file in regard to the video above here for your reference. 

123 re-fly by MAX 20220726.trk Tacview-20220726-013918-DCS-123 re-fly by MAX 20220726.trk.zip.acmi

Edited July 25, 2022 by Max Mak

[_UnknownCheater_]

On 7/26/2022 at 2:08 AM, Max Mak said:

 

 

I do think the big change in this patch is that the generation of track files required 5 sweeps hits of a brick and turn into HAFU. I actually take control your track files in your last attemp for a Su-33 within 20nm. In this moment you just move too down for your Antenna elevation control, it didn't got the consistent 5 sweeps hit to build the track files. Therefore, I move the radar elevation up a little bit and finally got a consistent 5 sweeps hit to generate the track files. Then, I immediately change to TWS auto to maintain the scan zone focus on the targrt and shoot him a AIM120C and he is hitted. 

I attached my corresponding track file and tacview file in regard to the video above here for your reference. 

123 re-fly by MAX 20220726.trk 368.55 kB · 2 downloads Tacview-20220726-013918-DCS-123 re-fly by MAX 20220726.trk.zip.acmi 108.62 kB · 2 downloads

 

The important thing still is the contact always need 5 sweep can be locked.This is SP test,if u are in PVP, you even cant lock 20-40nm  HAFU or RAW contacts by TDC or NSW,it looks like ur keybinds lost,this is a big problem.

Edited July 27, 2022 by zhouyut001

[Max Mak]

4 hours ago, zhouyut001 said:

The important thing still is the contact always need 5 sweep can be locked.This is SP test,if u are in PVP, you even cant lock 20-40nm  HAFU or RAW contacts by TDC or NSW,it looks like ur keybinds lost,this is a big problem.

 

Yes, now the 5 sweeps are the minimum counts before the track can be generated. Thus, you can only narrow the scan zone to make it becomes faster to build a track. I think it will take forever to build a track if you use 140 degree and 6 bar scan. 

Don’t know if this 5 sweeps rule also applied to other ED modules like F-16, I will give it a test soon.

[_UnknownCheater_]

4 minutes ago, Max Mak said:

Yes, now the 5 sweeps are the minimum counts before the track can be generated. Thus, you can only narrow the scan zone to make it becomes faster to build a track. I think it will take forever to build a track if you use 140 degree and 6 bar scan. 

Don’t know if this 5 sweeps rule also applied to other ED modules like F-16, I will give it a test soon.

Nope,2BAR*20 still need 5 sweep,1 Bar did't test.F16 need at least 3 seems,but u can lock it.In F18 even the HAFU show up,you can't lock with TDC or NSW.

Edited July 27, 2022 by zhouyut001

[Max Mak]

3 hours ago, zhouyut001 said:

Nope,2BAR*20 still need 5 sweep,1 Bar did't test.F16 need at least 3 seems,but u can lock it.In F18 even the HAFU show up,you can't lock with TDC or NSW.

 

Yes, I’m just saying that in whatever setting you need 5 sweeps now, so narrowing the scan zone will get faster for those 5 sweeps to build the track. That’s why I anticipated that in 140 degree 6 bar scan will now take forever to make enough 5 sweeps to build a track.

Edited July 27, 2022 by Max Mak

[Harker]

Seems to be a combination of two issues I reported already.

During my testing, I found that there are two separate issues at play. I'm not sure what goes on under the hood, but perhaps it's better if we treat these two issues separately.

1st, valid trackfiles (with resolved azimuth, altitude and velocities) cannot be designated as soon as they're ready. Trackfiles are objects generated by MC2 in the Hornet, so having "unusable" and "un-designatable" trackfiles makes no sense, based on what I've read on IRL manuals. This is reported here: https://forum.dcs.world/topic/305485-valid-trackfiles-cannot-be-designated-immediately/

2nd, TWS takes more sweeps to display a trackfile, even if the trackfile is ready and can be designated manually (NWS, TDC Depress). The trackfile is already visible in the SA and AZ/EL pages, it's only not shown in TWS, on the RDR ATTK page. This makes no sense, since TWS should display valid trackfiles for up to the 8 highest ranked targets, as soon as they're available. This goes beyond the previous issue, since the trackfile now can be designated, but it's not yet displayed on TWS. This is reported here: https://forum.dcs.world/topic/305484-tws-on-the-rdr-attk-page-does-not-display-hafu-as-soon-as-trackfile-is-ready/

[rfxcasey]

After the latest beta update, B Sweep Won't Re-Center and Antenna Elevation Way Off When Switching RWS/TWS and visa versa. I have got a video recording of the B Sweep bug I'll have to make tracks for both when I get the chance. Antenna is a big problem, when switching from RWS to TWS and back. With the cursor centered and range the same elevation will be like 35K - 10K but when switching to TWS it goes to 99K - 99K. Very hard to get it to reset along with the beam sweep being stuck off to the side and won't center no matter what. Funny thing is, I've only seen it do it when no contacts are on the radar. If you get a radar contact in RWS and switch to TWS it seems to be fine. I say that, but after a BVR engagement I was in that turned into a dogfight, the radar was messed up afterwards, beam wouldn't re-center no matter what I did.

Edited August 1, 2022 by rfxcasey

[Blueleader]

Hello,

I noticed this too and I completely agree with you.

This is a bug which I hope will be corrected very quickly to return to the previous version which worked perfectly well !

[BIGNEWY]

Will investigate, if you have any public evidence please PM me

[BIGNEWY]

14 hours ago, rfxcasey said:

After the latest beta update, B Sweep Won't Re-Center and Antenna Elevation Way Off When Switching RWS/TWS and visa versa. I have got a video recording of the B Sweep bug I'll have to make tracks for both when I get the chance. Antenna is a big problem, when switching from RWS to TWS and back. With the cursor centered and range the same elevation will be like 35K - 10K but when switching to TWS it goes to 99K - 99K. Very hard to get it to reset along with the beam sweep being stuck off to the side and won't center no matter what. Funny thing is, I've only seen it do it when no contacts are on the radar. If you get a radar contact in RWS and switch to TWS it seems to be fine. I say that, but after a BVR engagement I was in that turned into a dogfight, the radar was messed up afterwards, beam wouldn't re-center no matter what I did.

 

Posts merged, we are investigating sweeps, please include a track replay showing the issue

thank you