Zectivi

This is the video provided to me: I’d tend to agree, but then it would cause loss of contacts or other data though, right? Simply just losing the team member association is the oddity.

Hello all! Looking to see if anyone has seen this behavior, and if it is expected. Some members of my community have recently seen it where upon activation of ECM mode 3 with the long pod by someone in their flight, they lose team member information, i.e. the DL contact goes from blue to green. Position also occasionally becomes shaky or more delayed. Example 2-ship scenario: Plane 1 activates mode 3. Plane 2 sees the contact jump away and back on HSD/FCR, jamming member changes from a blue (1) to a solid green. Plane 1 may jump around on HSD/HAD/FCR (or HUD if DL bugged). Plane 1 deactivates ECM. Plane 2 sees blue (1) return where it should be with no further degradation. I tried to read and get smarter on the whole TNDL network implementation, but something simply might have not clicked yet for me. From everything I've read, FC communication over MIDS should be fighter to fighter, and as such, messages with the STN should be able to be correlated and referenced. But I also understand that while MIDS has anti-jamming tech, it may not be completely impervious if the bands line up (understanding that ECM band jamming is not implemented to actually do that). Still odd to lose specific team member correlation. One of our members has video that shows this behavior dating back to June of this also occurring in a 4-ship. Can share if desired. Thanks everyone!

Launched the harms, kept the tanks, stayed in cat III and got the Stores Config warning. Had about 1500lbs fuel left in each wing tank.

I'd also like a clear understanding on it. I had 10200lbs of fuel across the internal and 2 wing tanks, and after launching the 2 AGM-88s I had, the light came on followed by Betty giving her 2 cents. My track from that session is attached. Pretense_hotstart_syria_m_1.1.4-20231220-165415.trk

I have the same issue with mine. No firmware version since getting it and no app version going back to 1.6 has made the beep setting in SimAppPro actually work and turn that beep off. I've tried different cables and different USB ports. I've read the manual(s) on WW's website as well as the one near the top of this forum, and none of the relevant manuals seem to even mention the beep setting. If you have an idea what manual this might be in, I'd be happy to concede that I didn't read that manual.