[UNABLE TO REPRODUCE]RWS scan spazing out

[Baz000]

just ran into my RWS scan going completely crazy on me with the elevation of the bars in a 4 bar scan it was spazzing out at like 2 bars scan and very quick duration. Track here:

 

https://drive.google.com/file/d/1Vbw9EEYa8wI8iuUevR8gRqdd8H6Y-dVv/view?usp=sharing

[fudabidu]

Watched it 4 times now and all I see is a normal 4 bar scan.

 

Only exception is around the 30 second mark, when the TDC gets towards the bottom left corner. The elevation twitches briefly and returns to 4 bar.

 

If this state was permanent on your end I don't know why we're seeing different things, unless of course the TRK system is as unreliable as it has always been.

[Baz000]

yeah it literally was cycling up and down like it was having a seizure at a super fast rate like it was in a 2 bar scan and not a 4 bar scan... I know how the 4 bar scan looks like normally and it looked nothing at all like that

[fudabidu]

Around 30 seconds into the track file I saw the vertical scan bar "having a seizure". It looked like a 1.5 bar scan, which doesn't make any sense to me in RWS. This didn't even last a second and the FCR returned to a normal 4 bar scan.

 

Latest OB. No mods.

 

Whatever your problem is, it doesn't show up for me in the track replay. I know what a 4 bar should look like and I counted every single bar from start to finish. It's just during that brief period where I see an anomaly.

[Baz000]

yes and it didn’t return to normal for me, it stayed that way until I quit the mission, maybe this was caused by pressing fly again button in mission debriefing

[falcon_120]

There is a rare bug in the hornet where azimuth and bars get inverted and stays in that state, it hapoens after messing aroung with acm modes and gun modes. It sounds it might be the same thing you might be seeing.

 

Enviado desde mi ELE-L29 mediante Tapatalk

[BIGNEWY]

So far I have been unable to reproduce, I will keep trying

 

thanks