Zeus67

There are a couple of bugs with status change and new threat tones.

Unfortunately the AV-8B's ALR-67 cannot identify friendly contacts, so now all contacts are considered threats and thus subject to reclassification.

The ones you have now are default DCS sounds. The ones in the video, which will be released on next openbeta update, are new and are similar to the ones used by the real aircraft.

Please read the pocket guide. It explains the steps you need to follow so you can input the data required for the alignment.

This is not in agreement with the documentation I have: 1. Critical Threats: Long Stems (1.5 X normal length). 2. Lethal Threats: Dashed Stems (normal length). 3. Non Lethal Threats: Short Stems (0.5 X normal length). With your logic this threat: Is being considered lethal. With the documented logic, it is a non-lethal contact (short stem).

Please check these images you sent me: https://imgur.com/a/E7yLw1k This is an AV-8B during an air refueling. You can see a RWR contact that is being identified as lethal. I seriously doubt that pilot would be calmly taking fuel if he really had an enemy lethal radar contact in his RWR. I'm quite sure this is a friendly radar that is being identified as lethal due to signal strength.

I talked with a current USMC pilot and all he was willing to say on the issue is this: The ALR-67 in the AV-8B is not connected to the IFF. Although radars can be identified with the built-in library, no contact is identified as "friendly" without IFF. Of course, this does not apply to the F/A-18, who may have integration between the IFF and the ALR-67(v)3.

I'll check the issue

RWR Update: HUD RWR "lollypops" are ready and working. They also follow the: Non-Lethal, Lethal, Critical signal aggregation. Short stem = Non Lethal, Dashed Stem = Lethal, Long Stem = Critical, Long Stem with Arrow = Radar Lock!, Flashing Long Stem with Arrow = Missile Launch!! I will say that with the RWR divided into threat bands, it is easier and clearer to check for priority threats. Also, the no sound bug was squashed.

I told ED about the problem with the intercontinental AGM-65E.

You forgot something else: The real E is not capable of self-lasing.

This is DCS limitation. We cannot change that. Perhaps you could ask ED to increase the limit to 15 nmiles.

We will check.

Only correction, the AV-8B cannot discriminate between friend and foe. The ALR-67 is not connected to the IFF. So in your sample it is classified as Non-Lethal because it is a search radar.

If you keep fighting, I'll turn around this thread and close it. The CTD was fixed by ED and released with 2.5.3 for OpenBeta. Stable will have to wait until ED pushes 2.5.3 to it.

As I said, ED has been making changes to all missiles. That was the source of the CTD on the previous update.

Check this post: https://forums.eagle.ru/showpost.php?p=3427180&postcount=1

RWR is still being upgraded. It will be available in the near future.

Probably the button is in the EHSD EW page.

None that I've seen.

Interesting. The only transposed position are the critical and non-critical bands. The middle ring still is the lethal band. Unfortunately although both the Hornet and the AV-8B use the same device, both use different versions. The AV-8B uses the ALR-67(v), which is the oldest one. The F/A-18 uses the ALR-67(v2) and now the ALR-67(v3). So my docs could refer to a different version than yours. Still thanks for sharing this.

New RWR format test. It is more useful to determine threat priority and position.

Wait for our MiG-23MLA. :smartass:

Yes. It also means that the sounds bug will be squashed.

I can't say. I have both ODU and UFC mapped to joystick buttons and they work fine. I'm not sure how to help you, I believe a saved track file would be of limited use. But send one if you like.