Voy

Vocab: "Launch recycle tone" is referring to the lower-pitch launch warning tone you hear every 15 seconds after the initial launch warning tone. When the RWR is detecting a missile launch, and it's been more than 15 seconds, meaning you've just heard the first launch recycle tone, breaking the lock will immediately play another launch recycle tone. Attached track shows me putting the SA-10 missile into my RWR's blind spot right after I've heard the launch recycle tone, and you will hear another one play right after. This should not be happening, as that tone should only play every 15 seconds following the continuous detection of missile guidance. I believe this has been a bug since the January update when the tone was added, but apparently never reported. F-16 RWR extra launch recycle tone.trk

I made this report which was reported as fixed in the 2.9 OB changelog: "Fixed: RWR continues to signal actual threat warnings during BIT." There is still a couple situations where threats are being signaled during the self-test. 1. The UNKNOWN button continues to flash "U" indicating presence of unknown emitters during the BIT. (Same concept as the SEARCH button with "S", but that one is fixed.) 2. If you start the BIT while detecting a missile launch, the LAUNCH button will continue to flash and will correctly stop if the RWR stops detecting the missile launch. I've attached a track showing both of these situations. When I start the BIT during the missile launch, you'll notice it accurately stops flashing when I put the missile in the RWR blind spot, even though the RWR's operational mode should not be active and it wouldn't have knowledge of current emitters. F-16 RWR BIT while launch.trk

After you perform the BIT on the RWR, lock tones no longer work. You still get indications you are being locked, but no audio. Attached track shows me performing the BIT, then getting locked by an SA-6. Issue is on both MT and standard. F-16 No Lock Tone After BIT.trk

The SEMI and AUTO modes for countermeasures still work even if the RWR is turned off, giving "counter" voice messages and dispensing countermeasures when locked by a radar. Without system power to the RWR, the ALE-47 CMS would not know if the aircraft is being locked. F-16 SEMI And AUTO With RWR Off.trk

I was doing some research on the AN/ALR-56M RWR and came across some information that describes some behaviors that are not in DCS. How did I get this info? If you look up "CDC 2A354C Volume 3" (Better results on something like DuckDuckGo than Google), you'll find several practice test websites with flashcards all containing the same (or very similar) questions & answers made all by different people with different dates. From what I understand, a CDC is a Career Development Course, basically a test that airmen take to prove their qualified in certain aircraft/systems. That specific CDC Code is for F-16C/D avionics and systems. The best one I found is this one (pages 4-5) which specifically talks about the ALR-56M. Behaviors 1. The LAUNCH Button When you press the LAUNCH button, it should play the missile launch audio, and presumably test the LAUNCH button lamp. 2. System Initialization When you power up the RWR, there should be a *3* minute long initialization process where"I" should be display in the center of the RWR display (Same place as "S" or "L" when using the Search & Low functions). Side note: You can still hear the Hornet's ALR-67 power up sound in the F-16 when you turn on the RWR, this is leftover from day 1 when the F-16 had all Hornet RWR sounds. 3. BIT / SYS TEST When performing the BIT on the RWR, there is currently no Lamp test portion, all the buttons on the threat warning panel should be lighting up like a christmas tree! (Added in Feb, 2024) Also the audio test part of the BIT currently in DCS is pretty questionable, but I don't have enough info to say what it should exactly be. 4. Symbol Positions While Maneuvering I interpreted this one as; Since the ALR-56M has the navigation data (including heading), when you are turning, the symbols on the display should be changing their position/azimuth in real time. Currently, the symbols only update their position every time the emitter scans the aircraft. So, if a radar scans me every 5 seconds, and I make a 90 degree turn in 3 seconds, the symbol would be showing in the completely wrong spot (90 degrees off), and then jump to the correct location. This can get really disorientating when trying to notch, as I'm sure most of you know. Conclusion I know ED will most likely not use this data, since it is not a first-hand source, but I hope having knowledge of these supposed behaviors might make it easier to find usable documentation since they'd know what behaviors to specifically look for. Or, maybe ED already has documentation on it and just misinterpreted it, who knows. If anyone finds some more information, or thinks I'm interpreting this wrong, I'd love to hear ya'll out. Also, this is not meant to give ED a hard time, I know finding documentation on these kinds of systems is difficult, it's all just in the spirit of creating the best F-16 sim!

Some of those lua files just have old/unused code, it's not actually using those referenced files.

Ah, my mistake, thanks for the explanation!

Just a small thing that's been bugging me for a bit, maybe we can get some clarification if this is 'Correct as is' or not. When you power up the RWR in the F-16, those 3 beep tones are leftover from the ALR-67 from the Hornet. When the F-16 first launched it had all Hornet RWR sounds, is this something that was just forgotten to be removed? I don't think our ALR-56M has a startup sound, or at least I don't think it's the same as the Hornet's.

When performing the BIT on the RWR, you can still hear the "new guy" audio tones when a new emitter appears during the BIT. As I understand, when the RWR is performing the BIT it should not still be functioning in the background, or at least audio tones from the operational mode should not be leaking over. In the attached track, an SA-6 is detected around 5-10 seconds into the BIT. F-16 RWR BIT Contact Sounds.trk

With bullseye mode enabled, and in the HOME mode on the Cruise page, the bearing for bullseye in the bottom-left of the HUD goes away. However, the range for bullseye still remains. I don't believe bullseye info should go away in this mode, and if it is actually suppose to, the range is still there. F-16 HOME No Bullseye Bearing.trk

What is TDOA?

After some further testing, I've noticed this bug is much more exaggerated when in a laggy mission. If you are trying to reproduce this, I suggest trying a very big mission if you have a powerful computer. Additionally, at least for me, I can only notice the audio choppiness around 50% of the time. Just to clarify: This is only with the Launch and Launch Recycle sounds during the BIT. When actually being fired upon, the Launch sound seems perfectly normal.

I've talked to a couple people who have had the same issue, so I do not believe it is unique to my game files. Also, being able to hear "new guy" sounds while performing the BIT sounds like it's own bug. Regarding the placeholder sounds conversation, I think you misread my post, I was talking about Lock sound, not Launch.

I'm not sure if it will come across in the track file, but when performing the BIT on the RWR, specifically both of the launch audio tones sound really choppy and broken up. It sort of sounds like it is being constantly stopped and re-played. Also just a side-note: I thought the launch audio test was for when you click the "Launch" button above the BIT button. Obviously I do not have access to ED's sources, but is the BIT audio just a best guess or fake? I mainly say this because I thought sounds like the Lock sound were suppose to be the PRF of the emitter, and our current Lock sound was just a generic placeholder for now. So, if it is a placeholder, why would a random arbitrary lock sound be part of the BIT audio? Any insights would be appreciated, and maybe the team can take another look at this, cheers! F-16 RWR BIT Audio Bug.trk

Currently, if a new emitter is detected, the contact will pulsate in size as expected. But if that same emitter is lost, and then re-appears, it will not pulsate. From what I understood watching Wag's video (https://youtu.be/vjQI2eXuKbI?t=118), the expected behavior is that it should always pulsate when it initially appears on the RWR. The attached track file shows me detecting a couple radars, then going into a valley and losing them. Notice that when I start climbing again, the contacts re-appear, the "new radar" sound is played, but the contacts do not pulsate. This behavior is true even if the RWR is powered off and on. F-16 RWR New Threats Bug.trk

You can already change the display settings like contrast and brightness using the switches on the corners of the MFD. You can also change the WHOT/BHOT/TV mode using TMS Left. And you change the laser code in the DED (LIST -> MISC -> LASR). I'm not sure if I'm misunderstanding your question or if you just don't know how to use the TGP.

Pressing the BIT button on the RWR while the current RWR BIT is playing the missile launch audio or recycled missile launch audio will make it repeat infinitely until pressed again. Also, unknown if this is intentional, but you can run the RWR BIT before the display is turned on. F-16 RWR BIT Bug.trk