My RWR can't identify anything


My rwr can’t identify anything even though it could before, I’ve tried using different aircrafts but the results are the same. This picture is an example of a j-15t .

1 Like

The RWR was changed to K/RKZ2200 in the last major update iirc. No longer has that feature. Likely the same for the rest of the aircraft youve flown

1 Like

Something else they butchered?

1 Like

It has nothing to do with that.

Couple days ago they broke the RWR’s with one of the small uptade, now some RWR’s doesn’t work properly or not working at all.

1 Like

It’s happening to me too
Happens with the Rafale, Su30SM2, EF-2K


i made a bug report: RWR bug: Not showing threats name (even on top tier jets) // Gaijin.net // Issues

1 Like

does still happen with you too?

@Smin1080p_WT

Is it possible that devs aware this issue? High tier jets/helicopters are completely unplayable due this RWR problem.

Same with me, I guess this bug happends only on minimal client version (correct me if I am wrong). RWR does not identify contacts on any plane or helicopter. I also have posted a bug report but still no response a day after (ofc). Hope they fix it soon enough, because it is completely impossible to fly on top tier jets rn.

yes

I think you are right about this only happens on the minimal client version

1 Like

I don’t think so, because all the aircraft I tested had the same problem, the rwr couldn’t identify the type of threat.

idk bbut i hope it’s just the RWR for minimal client version

Thank you sooo much for letting me know that this only happens on minimal client. I installed the full client and issue solved.

But still, they need to fix that on minimal client.
Also, the RWR on the full client has the font bolder and blurry

Glad you were able to solve this problem by downloading the full client version, actually @Shaurmik21 figures it out this issue only occurs on the minimal client version

Issue persist on full client as well.

Im using Full ultra hq client yet it still happens on some planes/helicopters.

Looks like bug was fixed in the 22.55.1.61 update.