Radar shows azimuth affected by aircraft bank

[Pikey]

I'll be first to admit i've never seen a radar operate and my findings are a question based on two very important pieces of data:

1. That this type of radar operation in Mirage is completely different to all the other radars modelled in DCS so it is an exception.

2. That this particular operation does not make good logical sense and will confuse pilots, virtual or otherwise.

Abstract: "Should aircraft bank affect the displayed target azimuth on radar scope?". 30 degrees right should remain 30 degrees right, no matter what the aircraft bank angle is. Once you bank the aircraft, azimuth changes, so much so that you can have a contact left of nose, but if you bank 90 degree right, the contact moves right of scope.

 

There is also a very high chance of breaking lock due to pilots becoming disorientated as to the actual real azimuth of a contact when trying to put the contact on gimbals. I believe that THIS issue has been responsible for most of the "Mirage always breaks lock" threads and the excuse provided of notching has been disguising this issue for too long now.

 

Reproduction example:

1. Lock target on nose. Relative bearing to contact on radar is 0 degrees

2. Bank to 90 left. Pull 30 degrees of ownship heading left.

3. Observed behaviour at 90 degrees of bank: Target is still at 0 degrees relative bearing on the nose.

4. Expected behaviour: Target should show 30 degrees right nose

5. Roll out level and (often) lose lock or watch the target move rapidly to 30 degrees right of the nose.

6. Further demo: Put the target at 30 degrees left or right of the nose and roll the aircraft continuously. The target moves rapidly from 0 degrees to 30 degrees azimuth. It may drop lock during this randomly.

 

 

 

This makes trying to bank and put an aircraft at your gimbals very difficult because even if you use the heading and give some margin of error, if you roll to gimbals the azimuth rapidly flicks around and often the track is dropped as you generally have no idea how close to gimbal you are, or even what direction the bandit is in under heavy manouevring.

 

Now this is important, because putting an aircraft and keeping it targeted on the gimbal whilst violently manouevering in bank and azimuth is a 101 BVR requirement to change your F-pole length after firing, or to bracket efficiently, or offset, or any number of positional jousts that Fox1 engagements require you to do and simply put, I've found the Mirage to be a nightmare ever since early access release for it's main purpose of engaging the enemy and killing him. The effect of this is that you are going to lose lock, get pulled into a search effort and lose positional advantage or just lose him forever in the last few seconds of the engagement.

 

Is this known and tracked by development and do we have an ETA?

[Azrayen]

Is this known and tracked by development and do we have an ETA?

Yes. Dunno what you mean. No.

[Zeus67]

This specific problem has been solved and is now undergoing tests before release.

[myHelljumper]

Yay

[Pikey]

Fantastic to hear :)

This specific problem has been solved and is now undergoing tests before release.

[Azrayen]

Good news, Zeus :)

[Sarge55]

Now "that" is how you present your observations... not one of these whiny "I'm a customer" entitlement rants.

 

Thanks Pikey.

 

@Zeus, good to hear.