[ALREADY REPORTED] Radar scan, b-sweep

[Eagle7907]

I ran into another radar scan problem. Can’t really figure out what caused it, but basically I engaged mig23s and after firing two AMRAAMs at them did I notice the b-sweep was broken. It seemed somehow to lose about the last 20 degrees on the left. I can try to lock in that area, but during regular RWS scan it won’t.

 

Track to follow.

 

OB, latest update 2/13/19

 

 

Sent from my iPad using Tapatalk Pro

[Eagle7907]

Disregard the track. Pointless. For whatever reason the track doesn’t register me targeting an SA6 before my mig engagement. So you won’t even see what happened. I just get shot down.

 

 

Sent from my iPad using Tapatalk Pro

[GGTharos]

Your b-sweep is compressed in AZ from 140 to 80 degrees probably. Check on your DDI. The scan centering is not functioning yet, ie. the scan center is literally centered on aircraft heading, and that's the problem you're facing.

 

I suggest that you use LHACQ for now to fight contacts that you'd normally pick up on the gimbals.

[Eagle7907]

[NEED TRACK] Radar scan, b-sweep

 

Your b-sweep is compressed in AZ from 140 to 80 degrees probably. Check on your DDI. The scan centering is not functioning yet, ie. the scan center is literally centered on aircraft heading, and that's the problem you're facing.

 

I suggest that you use LHACQ for now to fight contacts that you'd normally pick up on the gimbals.

 

 

 

I checked that. I went through all the azimuth settings and same result, the last quarter or eighth was cut off.

 

 

Sent from my iPhone using Tapatalk Pro

[mcfleck]

I can confirm this bug, as I am experiencing it too from time to time.

Today I wanted to quickly try the new TWS function. After the initial engagement (and after I shot both enemy planes) I switched back to RWS and there it was again. I tried all azimuth settings. In 140° i.e. the radar scanned completely to the left, but stopped at about 58° to the right.

I thougth, great I can submit a track file and maybe help getting this bug fixed.

But replaying the track file I saw, that the recorded file sometimes came nowhere near to what really happened. So keep that in mind.

After killing the second jet, I tried several different modes and a few moments later I switched back from TWS to RWS.

 

Have a look and see for yourself.

 

 

Version: Latest Open Beta (21. December, 2019)

 

 

P.S.:

Dont judge the engagement itself, as it was flown without any VR/Headtracker and was only meant to quickly test the TWS feature. I know it was horrible.:music_whistling:

The mission I am using here is an adapted TTI Mission, which I turned into a pure AA Training map.

 

All Credits and thanks for it are going to Deadlyfishes for his brilliant work.

Centering Bug.trk

Edited December 21, 2019 by mcfleck
Added Track File, Added Information

[al531246]

I've been waiting for someone to make a bug report on this. I'm experiencing the same.

 

You lock up a guy in TWS, turn it into an STT, guide a weapon to kill the target and then return back to RWS. The center of the radars sweep will be the target's last position whilst you had him locked up.

[Eagle7907]

This happened again to me the other day as well while trying out TWS. Somehow, don’t know how, but the b-sweep was not completely going to the right.

 

This time I didn’t really know what I was doing. Trying to learn TWS by trial and error. Evidently if you just do lots of sensor select or or other TDC presses and undesignates can cause it as well.

 

 

Sent from my iPhone using Tapatalk Pro

[falcon_120]

Its definitely happening and I'm not sure how to reproduce it but it is related to the logic switching from a TWS AUTO back to RWS by pressing the OSB button. If Im able to reproduce it I will post a track.

[mcfleck]

Well even if this may happen more frequently after the TWS implementation, I had seen this bug way earlier.

Btw:

A track is attached by now, so the thread title can be changed (the part in [...]).

[Ziptie]

I ran into another radar scan problem. Can’t really figure out what caused it, but basically I engaged mig23s and after firing two AMRAAMs at them did I notice the b-sweep was broken. It seemed somehow to lose about the last 20 degrees on the left. I can try to lock in that area, but during regular RWS scan it won’t.

 

Track to follow.

 

OB, latest update 2/13/19

 

 

Sent from my iPad using Tapatalk Pro

 

Same thing just happened to me today as well. Lost the left 20* of sweep. It was off center, by 20* . A similar bug popped up awhile back, but it was fixed with a hotfix/patch. Guessing and/or hoping that the same will happen this time.

 

 

@bignewy - OP posted a track file for reference.

 

 

Cheers,

 

Don (callsign Ziptie)

[Eagle7907]

I can confirm this bug, as I am experiencing it too from time to time.

Today I wanted to quickly try the new TWS function. After the initial engagement (and after I shot both enemy planes) I switched back to RWS and there it was again. I tried all azimuth settings. In 140° i.e. the radar scanned completely to the left, but stopped at about 58° to the right.

I thougth, great I can submit a track file and maybe help getting this bug fixed.

But replaying the track file I saw, that the recorded file sometimes came nowhere near to what really happened. So keep that in mind.

After killing the second jet, I tried several different modes and a few moments later I switched back from TWS to RWS.

 

Have a look and see for yourself.

 

 

Version: Latest Open Beta (21. December, 2019)

 

 

P.S.:

Dont judge the engagement itself, as it was flown without any VR/Headtracker and was only meant to quickly test the TWS feature. I know it was horrible.:music_whistling:

The mission I am using here is an adapted TTI Mission, which I turned into a pure AA Training map.

 

All Credits and thanks for it are going to Deadlyfishes for his brilliant work.

 

 

 

Same thing just happened to me today as well. Lost the left 20* of sweep. It was off center, by 20* . A similar bug popped up awhile back, but it was fixed with a hotfix/patch. Guessing and/or hoping that the same will happen this time.

 

 

@bignewy - OP posted a track file for reference.

 

 

Cheers,

 

Don (callsign Ziptie)

 

 

 

I didn’t. Someone else did. Credit where credit is due.

 

 

Sent from my iPad using Tapatalk Pro

[NineLine]

Thanks for the track, unfortunately it looks like the server or mission is using custom scripts. if possible could you create a script-free track of the issue? Thanks!

 

I can confirm this bug, as I am experiencing it too from time to time.

Today I wanted to quickly try the new TWS function. After the initial engagement (and after I shot both enemy planes) I switched back to RWS and there it was again. I tried all azimuth settings. In 140° i.e. the radar scanned completely to the left, but stopped at about 58° to the right.

I thougth, great I can submit a track file and maybe help getting this bug fixed.

But replaying the track file I saw, that the recorded file sometimes came nowhere near to what really happened. So keep that in mind.

After killing the second jet, I tried several different modes and a few moments later I switched back from TWS to RWS.

 

Have a look and see for yourself.

 

 

Version: Latest Open Beta (21. December, 2019)

 

 

P.S.:

Dont judge the engagement itself, as it was flown without any VR/Headtracker and was only meant to quickly test the TWS feature. I know it was horrible.:music_whistling:

The mission I am using here is an adapted TTI Mission, which I turned into a pure AA Training map.

 

All Credits and thanks for it are going to Deadlyfishes for his brilliant work.

[mcfleck]

Oh shoot! Yes, sorry it is the mission where the scripts are dynamically loaded.

I will try to reproduce it in a script less mission.

[Ziptie]

It’s ok I think - as another thread was marked as “reported.” Although the title was different, the complaint and scenario is really the same - should be addressed as NL has reported it...

 

https://forums.eagle.ru/showthread.php?t=258503

 

Cheers,

 

Don (callsign Ziptie)

[NineLine]

Yeah, I agree, closing this one as already reported.