eletrobull

Both radio channels, 199 and 200 are datalink channels.

Tried, Does not work either.

Would like an update to this issue please @uboats. It's been a while...

I'll give a little more detail. This is Multi-player environment issue. Masters can connect to AI AWACs. Slaves cannot connect to Masters. Also I think Masters were able to Donate data between Masters, now not able and unable to see other Masters on the CLNK Table.

In the video the first and last notching defences in the video the symbol moves in the HSD since I over turned, so this is fine. Incorrect, so once the missile got notched, the "missile" HUD text and voice warning remained with the flashing Indicator symbol on the HSD. I guess the expected outcome should be, once missile is notched there should be no "missile" HUD text, no voice warning and no indicator on HSD. Idea: However having the Indicator remain solid for a set period of time (like 8 seconds) before being removed. Also being removed on new spike from missile.

Detailed description When an incoming enemy missile gets notched, the RWR indication "sticks", however the warning remains until missile destroys itself or moves out of the field of view of the RWR sensors. This affects all Fox 3's, A120 and SD-10 are easier to have this demonstrated. This has been a long standing issue, I think this is why most people find it hard to notch in the JF-17. How to reproduce Simple just try and notch a missile as early as possible, notice how the RWR missile is stuck just fore or aft of the 3 - 9 line of the aircraft. Yet the missile warning indication and sound still goes off. See video below that demonstrates this and the tacview attached. Track files will be useless here since different hardware will make the AI behave different. Tacview-20230321-073530-DCS-JF-17 Thunder A2A Short Caucasus.zip.acmi

Brief introduction DCS Version 2.7.15.25026 Radar Elevation not tracking a bugged / selected target, Radar Mode switching on unexpected target loss. Detailed description When the Radar is bugged on a target that is above or below and you invert the aircraft, the radar fails to auto correct the elevation causing an unexpected loss of target. This unexpected loss seems to trigger a radar mode switch, perhaps there is no code to handle an unexpected loss? How to reproduce I'll keep it simple: -Select target above or below you -Go inverted and hold -On target loss your radar may switch modes Video demonstrating this in both TWS and RWS modes. Radar_Elevation_Bug_RDR_mode_switching_bug.trk