Strange Radar Behaviour

[JNelson]

Couldn't see any other threads mentioning this problem so excuse me if this is a duplicate.

 

I did the testing in the missile instant action.

 

The problem is when you TWS lock a contact the radar elevation drops down. The radar is no longer scanning the correct altitude range for the contact's distance and the contact is dropped of the radar. Then as soon as you elevate the radar back up the contact appears and you can repeat. As far as I understand the radar shouldn't be doing this. Attached is a video to explain it more clearly.

 

[Azrayen]

I concur that it seems to be something wrong with the elevation axis of the radar antenna.

 

Perhaps you could confirm what I encountered recently, too:

When you lock a contact (in PID, like you did) and roll your aircraft (level->bank left->level->bank right...) then the elevation cursor moves up/down with no apparent reason.

And, like in your example, you finish by "loosing" the lock.

[JNelson]

I concur that it seems to be something wrong with the elevation axis of the radar antenna.

 

Perhaps you could confirm what I encountered recently, too:

When you lock a contact (in PID, like you did) and roll your aircraft (level->bank left->level->bank right...) then the elevation cursor moves up/down with no apparent reason.

And, like in your example, you finish by "loosing" the lock.

 

Just confirmed that the scan elevation also moves when rolling left and right in PID mode.

[nomdeplume]

Sounds like this issue: Radar elevation wrong after unlock. When I was testing it initially I had the impression that banking the aircraft also caused the elevation to change, but when I was careful to not change pitch while rolling the effect was much lessened. So I came to the conclusion it's responding (weirdly) to aircraft pitch rather than roll. Might need to re-test that.

[Azrayen]

Interesting, nomdeplume.

Will try to check that too (can't promise when, though).

[TomCatMucDe]

Sounds like this issue: Radar elevation wrong after unlock. When I was testing it initially I had the impression that banking the aircraft also caused the elevation to change, but when I was careful to not change pitch while rolling the effect was much lessened. So I came to the conclusion it's responding (weirdly) to aircraft pitch rather than roll. Might need to re-test that.

 

i had the same issue. i couldnt reproduce it to and put a video of it. it seems that it either happens sporadically or under certain circumstances

[Frederf]

I can possibly be more clear on the issue. When locking PID the radar elevation (world coordinates) reverts to negative the airplane pitch or double negative elevation (airplane coordinates).

 

Flying at +4 pitch (level flight), elevation level with co-altitude target PID lock results in immediate antenna pitched 4 degrees below horizon or antenna -8 degrees down. Antenna is always pointing in PID as much below horizon as nose is pointed above.

[NaCH]

Don't know if this shows the issue, but you see on the beginning on the first TWS you see how the elevation "jumped"

 

Then it does no happen again, but I usual I have the issue that I loose the lock very easy specially when in STT.

 

 

 

Edit: sorry I put on the youtube the time but I guess is not working, to look at what I'm saying go to 8m20s

Edited May 7, 2016 by NaCH

[Frederf]

You can see the PID problem at

You pick up a target at 32/-8 gates antenna -2 at 18,600'. The second you PID the contact your radar jumps to 0/-40 gates antenna -8. That places the scan volume well below your contact. If you would have pitched up the gates would fall even more and pitching down the gates would have risen.

 

 

After break track for the next several seconds your antenna is searching -8 or so because you haven't touched the antenna elevation control. At 4:53 you touch the antenna control again and it jumps back up to where it was before the glitch.

 

PIC I think doesn't have this problem. The gates seem to be frozen based on the PID values that precede it except they shrink as range decreases. PIC loves the break lock on zero radial velocity (aspect 90) or chaff. I shoot an A-50 with chaff, lock is broken. I remove his chaff in ME, PIC to impact.

 

Off topic you should know you can bump the cursors against the bottom/top of the display to change range, improves readability. Also going PID-PIC you don't have to worry about putting the TDC over the contact. I would like to know how you managed to get the IFF working though.

Edited May 7, 2016 by Frederf

[NaCH]

You can see the PID problem at

You pick up a target at 32/-8 gates antenna -2 at 18,600'. The second you PID the contact your radar jumps to 0/-40 gates antenna -8. That places the scan volume well below your contact. If you would have pitched up the gates would fall even more and pitching down the gates would have risen.

 

 

After break track for the next several seconds your antenna is searching -8 or so because you haven't touched the antenna elevation control. At 4:53 you touch the antenna control again and it jumps back up to where it was before the glitch.

 

Yes I see what you mean, actually you have the same problem if you lock a "jamming" contact, I thought that was HOJ but has nothing to do with this :D

 

PIC I think doesn't have this problem. The gates seem to be frozen based on the PID values that precede it except they shrink as range decreases. PIC loves the break lock on zero radial velocity (aspect 90) or chaff. I shoot an A-50 with chaff, lock is broken. I remove his chaff in ME, PIC to impact.

 

Interesting, yes PIC is very susceptible to notching and to chaff don't know if this represent the actual performance of the RDI.

 

One thing that I'm learning is that is best to lunch the 530 at range without going pic and when is close go to PIC and the 530 will pickup and guide to him.

 

 

Off topic you should know you can bump the cursors against the bottom/top of the display to change range, improves readability. Also going PID-PIC you don't have to worry about putting the TDC over the contact. I would like to know how you managed to get the IFF working though.

 

 

Regarding TDC over the target to go PID-PIC, Yes but It happened to me that likes to lock other contact that could over the TDC. A good question will be if you are in PID if a TDC is showed or you need to brake lock to recover the TDC.

 

 

Regarding the IFF, right panel, just below the navigation and to interrogate you have to push the NWS:

 

[Conroy]

The problem is that we lose radar lock also at very close distance when S-530 missile has been already launched and it's (very) nearly to hit the target.

Is this related to the chaffs? It's a big iusse in combat. I try to fix switching on Magic as soon as i lost the radar lock, but it's usually too late.

Edited May 9, 2016 by Conroy

[tom1502]

I bought the Mirage at the weekend, but I'm having this problem. If I lock on to them at close range I quickly lose the lock and the missile misses, the aircraft are not using chaff or changing course - they are IL-76's. They're flying straight and level.

 

I was made aware of the change of scan area, so I'm correcting this when it happens, the real difficulty is when the missile has been launched. It means I am missing a sitting target at close range where the missile should not be missing.

 

Is there an estimate on when this could be fixed? I was flying online this morning and fired on someone who was going after a friendly - the instant I fired it broke lock and the missile missed. The RADAR was pointing up as high as it could at that instant.

 

I love the aircraft and this is the only problem that I have found with it.

[mattebubben]

The radar issue is known.

 

And hopefully it should be known quickly.

 

They know it happens they now need to figure out why it happens.

 

Atm i mostly use the Magics as they are the most effective weapon atm.

 

The Radar can maintain lock at sometimes (it often works in a chase when the enemy is at your altitude or slightly below)

 

But in a head on or for a maneuvering target it looses lock quickly.

 

I also find the a Close Combat lock often works better (both because you can very quickly Re-Lock a target but also it seems to loose lock less often.

But that could be because of the shorter range.

 

But yea atm i tend to use the Magics IIs as my primary and the super 530s in a chase or if i have been able to keep a steady lock for 5 sec (then i try to launch one missile)

And if i loose lock i wont try to Lock and fire the other since that would usually be a waste as it will usually just loose lock again if it has done so recently already.

[Conroy]

Just a question.

How can we move the scanning left and right like in the video posted above.

Sorry for this question but i can't sort it out.

[Rlaxoxo]

I have a question ...

 

Is the elevation notch suppose to move with the target?

Cus you can't move it manually and if target flies up he will just get unlocked lol kinda weird

[TheSnark]

Just a question.

How can we move the scanning left and right like in the video posted above.

Sorry for this question but i can't sort it out.

 

The radar has a 120 degree arc, if you select a 30(either way from straight ahead) or lower width you can then move the scanning left and right. It will not surpass the 120 degree arc in front of you though.

[Conroy]

Thank, i will give it a look.

 

Edit: confirmed, it does work with TDC. Thank!

Edited May 9, 2016 by Conroy

[Zeus67]

Okay folks. I've been silent for nearly a week now because I was busy with a game stopping bug that at last was killed today. :cheer3nc::drunk:

 

You did not experience this bug, because we never released the aircraft for update with it. :wassat: Basically STT lock was disabled. Long story short, it took me a week to find the bug: a "-" sign where a "+" should have been used. :doh: It is the little things that create migraine headaches. :crash:

 

Anyway that particular critter has been squashed and the radar is back to working condition. :beer:

 

BTW, I also solved two other bugs:

STT aperture limits, which basically created a too narrow tracking zone. Now it is as the real one with a 120º arc. :thumbup:

CCM bug: A problem with the antenna stabilization that was solved. :music_whistling:

[PiedDroit]

Okay folks. [...]

Yay! :cheer3nc:

Good work!

[Jugdriver]

Yes!

 

 

JD

AKA_MattE

[Conroy]

Great news, thank you!

 

Friday?

[Sarge55]

Excellent. Thanks Zeus.

[Rlaxoxo]

Awesome man!

[Rlaxoxo]

Radar now is pretty weird state you drop lock in such weird situations I was practicing Notching a bit and my target didn't even start to Notch me and I lost the contact just because he turned 5 degrees to the left

 

Also See that I lose lock if I bank a little to the left and I ended up losing lock when the target went into higher altitudes

 

Zeus will the next patch address these issues?

[Zeus67]

Radar now is pretty weird state you drop lock in such weird situations I was practicing Notching a bit and my target didn't even start to Notch me and I lost the contact just because he turned 5 degrees to the left

 

Also See that I lose lock if I bank a little to the left and I ended up losing lock when the target went into higher altitudes

 

Zeus will the next patch address these issues?

 

Yep. The radar is back to its normal quirkiness. :smilewink: