ACM radar mode bug/question

[dadunn1700]

Is it normal to have to re-select the ACM radar mode every time you lose track/lock? During a dogfight I constantly find myself having to re-select Vertical Scan mode. Seems like if the pilot selects an ACM radar mode it should stay in that mode until the pilot chooses something different. Coming back to DCS after being away for awhile. Never remember this being a thing with the Hornet.

Edited November 27, 2019 by dadunn1700

[majapahit]

Use the helmet (is prob what the devs are thinking how urgent this is)

[dadunn1700]

Use the helmet (is prob what the devs are thinking how urgent this is)

 

I have. When losing lock the HMD leaves HACQ and/or LHAQ (HMD boresight modes) as well. I'm constantly having to re-press the "sensor control switch" to re-enter the radar scan mode.

 

It's weird. The radar stays in ACM mode, but instead of reverting back to boresight, vertical scan, HMD HACQ, etc. after losing lock it goes into a sweeping RWS scan in ACM mode which does nothing but give away your position. If the radar was put in silent mode after losing lock until I selected a radar mode I'd at least find some reasoning behind it.

 

Basically, I'm just trying to confirm everybody else is experiencing the same thing, or if I have some weird bug with my install.

Edited November 27, 2019 by dadunn1700

[majapahit]

I have. When losing lock the HMD leaves HACQ and/or LHAQ (HMD boresight modes) as well. I'm constantly having to re-press the "sensor control switch" to re-enter the radar scan mode.

 

It's weird. The radar stays in ACM mode, but instead of reverting back to boresight, vertical scan, HMD HACQ, etc after losing lock it goes into sweeping RWS ACM (which does nothing but give away my position on a RWR without being of any use during a turnfight).

I have this hunch Devs considered AACQ as a 'default milestone - good enough for now -' and went on to develop the F16.

If only AACQ worked as it prob does in real life, as in actually working as a tool and not modelled halfway to theoretical spec, so not switching to tracks 30 of 60 miles away that would have been actually a good consideration, but now it’s not.

Wags said about Mini-updates devs will develop SPOT mode starting december, let's see if that works, a - wider - locking beam to look around without the faulted ‘automatic’ AACQ and beyond LACQ (10nm), and if they can adjust all these 'radar is thinking for a second on the wrong bloody track, tough luck' nuisances, which are quite the disadvantage to fly merged,

who knows we can actually be on par and defend 27’s IR locks (with 9X and we be in an advantage then).

Edited November 27, 2019 by majapahit

[Shimmergloom667]

Wags said about Mini-updates devs will develop SPOT mode starting december, let's see if that works, a - wider - locking beam to look around without the faulted ‘automatic’ AACQ and beyond LACQ (10nm), and if they can adjust all these 'radar is thinking for a second on the wrong bloody track, tough luck' nuisances, which are quite the disadvantage to fly merged,

who knows we can actually be on par and defend 27’s IR locks (with 9X and we be in an advantage then).

 

He also acknowledged that AACQ will be worked on in December, so I'm pretty confident we will see it working as intended soon.

[Arctander]

I also find that you can’t unlock a target in ltws like you used to with undesignate/nws. I found I have to cycle into acm mode and out again...