[CANNOT REPRODUCE] problems with the radar - elevation.

[NeedzWD40]

I can confirm a similar issue, but I get no radar control outside of locking; azimuth, elevation controls are completely unresponsive.

fa18c_radar_stuck.trk

[dorianR666]

just caught it in the wild again, ruining another campaign mission playthrough for me.

 

 

fix this ED pls, its literally the worst bug in the hornet right now. there is no recovery from it.

:mad::mad::mad::mad:

[dorianR666]

i dont remember exact steps well and track is bad

 

but i think i did:

1) locked the plane ahead of me with sidewinder + boresight

2) switched to gun

3) lost gun lock

4) at this point, the radar page was as if in gun mode but i was able to change range and so on

5) switched to AG mastermode

6) switched to AA mastermode

then it got broken

 

when i replicate these steps, it doesnt happen again. instead it causes a lighter version of the bug this thread is about - range/azimuth/bars settings dont appear and the issue is resolved by switching mastermodes. maybe i dont remember the steps right or maybe there is an element of randomness (uninitialized variable? race condition?)

 

 

if anyone has some ideas, they would be welcome

Edited September 28, 2020 by dorianR666

[dorianR666]

trying to discover the cause for this bug made me instead discover like 5 new ACM bugs. :doh:

 

im gonna have to put this module on ice for a couple months i guess. aa radar seems to be more and more broken over time. too frustrating.

Edited September 27, 2020 by dorianR666

[Harker]

Had it happen to me yesterday, but it doesn't show up on the track (long track too). It was a MP session.

 

Things I did, in order:

 

 

1. Entered A/A mode by selecting the AMRAAM.

2. Switched to TWS, shot down 1 bandit.

3. Entered GACQ by selecting the gun.

4. Switched between different ACM modes, notably HACQ and WACQ, locked up a second bandit and lost lock a few times. My wingman shot him down.

 

5. Repeat 1-3.

6. Use GACQ to lock up remaining bandit, then select AIM-9 and keep the bandit in RWS + LTWS (intercepting the remaining bandit).

7. Bandit moved to attack my wingman, so I switch to gun and GACQ and shoot him down.

8. Select AMRAAM again, but radar is reversed.

 

A 140/4B scan is now reversed and scanning only the middle of the scope, while the elevation caret goes all the way up and down (like a VACQ scan that scans the entire elevation).

 

Scan settings are reversed as well. Switching azimuth options limits the elevation scan and switching bar options limits the azimuth scan.

[dorianR666]

A 140/4B scan is now reversed and scanning only the middle of the scope, while the elevation caret goes all the way up and down (like a VACQ scan that scans the entire elevation).

 

Scan settings are reversed as well. Switching azimuth options limits the elevation scan and switching bar options limits the azimuth scan.

yep, sounds like it.

you can see a youtube link above to compare it with. i found out there is a second bug similar to this one, but it lacks some of the control options on radar page and is recoverable.

 

this bug is just great in campaigns. some of the Raven One missions are 150 minutes long, just awesome when the entire aa radar gets bricked during those. :doh:

[Harker]

yep, sounds like it.

you can see a youtube link above to compare it with. i found out there is a second bug similar to this one, but it lacks some of the control options on radar page and is recoverable.

 

this bug is just great in campaigns. some of the Raven One missions are 150 minutes long, just awesome when the entire aa radar gets bricked during those. :doh:

Yep, exactly like the video you posted.

 

The occurrence of this bug is strange. It happened to me once months ago and then 2 times this week. And I haven't done anything special, just BVR engagements that lead to guns. I've done it dozens of times in between these two time periods.

[dorianR666]

happened again

 

this time i noticed that shortly before the bug appeared, i got into a state where HUD showed boresight ACM mode while radar page showed vertical ACM mode scan pattern. the boresight ACM mode was not commanded by me.

 

it may be another bug, upon which this thread's bug is futher based.

 

it would make sense from programming perspective i think - upon entering vertical scan mode, you flip the axes and upon leaving vertical scan mode you flip them back. if you somehow manage to get into state where the program errorneously forgets its still in vertical mode, the axes wont be unflipped (as the vertical mode isnt correctly exited) and the flipping is forgotten.

 

if thats true, perhaps there is a path to recovery by replicating the steps that cause it, which would make the number of axes flipping even and thus return to normal. :smilewink:

 

 

tldr: bugs layered on top of bugs...

[Svend_Dellepude]

There is already a thread about this in the bugs section. This happens if you use undesignate while in a-a guns.

[VIXEN413]

how is it noted in the bugs section (no time to look for it, i m on phone connection): reported? investigating?

[dorianR666]

There is already a thread about this in the bugs section. This happens if you use undesignate while in a-a guns.

can you link the thread please? i know there have been multiple, but they always got ignored by ED and i havent seen causes being discovered

[Svend_Dellepude]

Here it is: https://forums.eagle.ru/showthread.php?t=282041&highlight=radar+axis

 

I wrote the steps to reliable reproduce, but they couldnt.

 

Another one here is reported though.

 

https://forums.eagle.ru/showthread.php?t=265518&highlight=radar+axis

[dorianR666]

thanks!

 

i was able to reproduce with the steps described in the first thread (the second thread is unrelated though, thats a different bug). it even happens without undesignate, if you lose the track. yikes...

 

so this means entering AA gun mode with target already locked must be avoided. annoying but at least hornet becomes playable again with this information. thanks again.

Edited October 1, 2020 by dorianR666

[Svend_Dellepude]

Maybe I misunderstood, but I thought they were somewhat related. Reading again I understand they are not.

 

Actually i don't know if it makes a difference whether or not you have a designated target before entering guns mode. Don't know if I ever checked it.

Should be easy to check, but I'm away from home these days, so I can't.

[dorianR666]

i have played couple missions and some multiplayer, carefully undesignating in RWS before entering gun mode and the bug hasnt appeared yet, so i think that was it.

 

 

its possible this rule can be relaxed to something less restrictive, but as it is, it seems to work