Radar lock issue

[Kalmo]

Made a small practice mission for myself aginst AI and while practising missile evasion and radar use I noticed that when you lose radar lock for whatever reason (gimbal limits, notching, target unlock button, etc) you can lock him again second time but after second lost lock you lose the target for about 1 minute. After when the target is on scope again I can lock and unlock him as many times as I want

 

 

I've attached 2 tracks so you can see what I'm talking about. First enemy is C130 almost head on, second F14 same headings. Both times I used unlock target HOTAS button. Bandits are higher than me and there is no notching nor ground clutter involved. Radar elevation is fine also. I think it happened both on TWS and STT. Changing radar cone width or number of bars had no effect on outcome.

 

 

Wasn't sure if this is a bug or if there is something about the radar that I don't understand or what so moderators feel free to move this to right section. I tried to find similar bug reports but couldn't find exactly same problem. I can run more tests tomorrow if needed.

test1.trk

test2.trk

[Kalmo]

Ok, more tests. 4xC130 closing. Different distances. When I lock bandit at > 40nm on TWS and unlock it few times, all contacts > 40nm disappear and contacts closer than 40nm stay on radar scope. Lost contacts appear again just under 40nm on RWS. It doesn't matter which target I lock, it's just on lock number 3 which causes those targets to disappear.

 

 

Over 40nm is far and you probably shouldn't try to lock that far but still it seems a bit wrong. Could it be that there is a bug which is connected to tws and radar range?

 

 

Track attached.

 

 

Comments anyone. Am I after something or am I just hunting ghosts?

test4.trk

[ZHeN]

Radar has been broken for two weeks already

And since there's no update this week, we're going for the third one. With baguette on the shelf.

 

I like how both bug tracker and forum are silent about the most broken build of the module in two years. You can only find developer's acknowledgement on discord.

[Shimmergloom667]

And since there's no update this week...

 

Where did you get that from?

[ZHeN]

From BIGNEWY on discord

[Shimmergloom667]

Thanks!

[33-DFTC]

I like how both bug tracker and forum are silent about the most broken build of the module in two years.

 

Razbam simply left behind their customers on this forum that are not willing to create accounts on Facebook or Discord, that's why. I wish Eagle Dynamics would do something about this situation.

[falconzx]

Radar has been broken for two weeks already

And since there's no update this week, we're going for the third one. With baguette on the shelf.

 

I like how both bug tracker and forum are silent about the most broken build of the module in two years. You can only find developer's acknowledgement on discord.

 

I noticed the big bugs on the Radar too, i just didn't reported all the bugs i found because i red RAZBAM declaration about the radar that's not what they intended to release ( i wonder about how they don't TRY things before releasing ..)

So i'm confident they will fix in the next patch all the problems we have now like:

 

-Negative Antenna Elevation doesn't react to rising axis command, it waits bars to complete before rising.

 

-BFR completely broken, or non-existing anymore.

 

-Loss of contacts, even if the elevation is correct, parameters correct.

Temporary fix: turn STANDBY/ON the RADAR to reset and avoid the bug.

 

-Top bar spotting contact indication is barely invisible, i don't think real one is like that...You need a lens to see the little segments on the tails of the contact symbol.

 

-The number of the bars near the antenna elevation indicator on VTB is often un-aligned, expecially when negative.

 

- Special Modes (CCMs) are completely uneffective, if this radar is capable to STT lock an hot target at 30miles, i don't understand why a boresight mode is not capable to find a target more than 4-5 miles. It has a 10miles max range, so il should work from that range in optimal condition.

Same story about the SVI mode, 20miles, and you can't find anything over 5 miles in optimal conditions. What's the sense to have 20miles limit then?

 

-Remanence switch and functionality (do we will have it sooner or later?) A radar rework could be a nice occasion to fix it.

 

Probably there's more but i don't remember now.

Edited September 18, 2019 by falconzx

[Ramsay]

I have several hours of experience with Mirage in DCS; I just fly after some months of standby and I could not fire weapons AA neither AG.

 

There are some procedure that has changed in the last 3 months?

 

I'm not sure how far behind the curve you are, for A2A you need to use the HOTAS commands

 

To sum up, handy way to use A/A Weapons:

First, select 530 on PCA while not having the Hotas Gun or Magic mode selected

Then:

- Select A/A Gun with GUN Select Hotas Command

- Select Magic with MAGIC Select Hotas Command

- Select 530 with PCA Select Hotas Command

 

For reminder MAG button on the PCA does NOT select Magic, it performs another function.

 

To use A2G weapons you select them on the PCA and use the HOTAS special modes switch to toggle the HUD mode between Nav and A2G symbology.

 

PCA/HUD Updates: https://forums.eagle.ru/showthread.php?p=3975179#post3975179

[jeffdude]

I noticed the big bugs on the Radar too, i just didn't reported all the bugs i found because i red RAZBAM declaration about the radar that's not what they intended to release ( i wonder about how they don't TRY things before releasing ..)

So i'm confident they will fix in the next patch all the problems we have now like:

 

....

 

They declared something about the radar?

 

I wanted to thank you for your "off and then on again suggestion" it worked to get targets back on the screen. Not ideal of course when targets are closing fast and it was a two ship! :joystick:

[Britchot]

I can't unlock a target with "NAV Update/MAGIC unlock", some changes too?

 

"NAV Update/MAGIC Unlock" will only unlock the IR seeker head from a target (the circle), not a radar lock.

 

To unlock a target from the radar, use "Weapons SystemCMD Depress", which used to be something like "Target Unlock".

 

3. Following keybinds are modified:

3.1 Special Modes FWD to Weapons SystemCMD FWD

3.2 Special Modes AFT to Weapons SystemCMD AFT

3.3 Target Unlock/Special Modes Deselect to Weapons SystemCMD Depress

Edited September 24, 2019 by Britchot

[RedSky]

There's definitely more to it than this. I was 100% blind all day today, with the radar even refusing to lock contrails in the middle of boresight after several standby cycles. I hope there's something identified here to be patched, otherwise the Mirage isn't really functional outside of a cold war environment. Nothing like getting repeatedly shot down by targets you had been prowling for several minutes and had dead to rights if the systems worked.

[Soviet Kitty]

You have to be at the almost exact altitude as your target to pick up anything. I think the antena elevation doesn't work.

As for boresight, SVi and special modes, you have to be within 5-6nm which renders them almost pointless. Sometimes the heatseeker will pick up targets before the radar.

[Oceandar]

You have to be at the almost exact altitude as your target to pick up anything. I think the antena elevation doesn't work.

As for boresight, SVi and special modes, you have to be within 5-6nm which renders them almost pointless. Sometimes the heatseeker will pick up targets before the radar.

Yeah thats ridiculous. Here we are without the patch for another week due to preparation for the Viper. I wish ED could maintain reguler patch even if its only few bugs fix.

[RedSky]

Hi RedSKy, do you know that procedures to lock a contact has changed some weeks ago?

 

Yes, I know how to operate the system with the changes. The problem isn't switchology in this case, there's something genuinely wrong with the radar modeling right now. I heard secondhand that it was a known issue, but have seen no direct confirmation as of yet.

[33-DFTC]

You won't see any confirmation from the dev team on their official board as they're no longer willing to share their work with us. However they confirmed on their Discord server there is indeed a problem with the radar and a fix is already ready to deploy with the next OB.