Flappie

Thank you. These slots are taken! I'll wait in line. EDIT: it's OK, I took a dynamic slot and I can reproduce the constant squelch sound, thank you very much. A-10A is affected too, and Soviet aircraft cannot be spawned here, but I guess all FC3 are affected. It looks like the radio beacon issue. I'll check. Tracks don't replay the issue.

(all terrains are affected apparently) Persian Gulf is affected too. Syria is OK.

My mistake, it did. I'll check with devs whether it's intentional (I doubt it is). Is Caucasus the only affected terrain?

It didn't. You can select any grid here in the F10 map: And in the Mission Editor, click the Key icon and voilà:

If it's only in MP, it's a different bug than the one I was talking about. Thank you for the indication, I'll give it a go right away. EDIT: the Contention server needs a password that I don't have.

I agree something could be done to indicate the base belongs to OPFOR.

Hey! I'm fine, thank you. How are you? I've just tested this with my keyboard and couldn't reproduce the issue. Is the mission Training > "L-39C. Start up, Taxi and Takeoff"? Does it work with keyboard only?

Tell this to my wife! I may have a selective memory, yes. Yes, it looks like an hesitation between "it's sunny outside" and "the sun is about to disappear". The sim graphic engine is far from perfect when it comes to Sun/Moon transitions (occasional black screens caused by sunset/sunrise, Moon light disappearing completely though the Moon is still up...).

When "live" (non-static) enemy units are present in an airbase or FARP, they capture the base, which is what happens here: No idea why SP lets you spawn at the base, though. EDIT: I think I understand the difference between SP and MP. SP missions start with the player. I assume base is BLUE at T=0, so the player is spawned. Then, one second later, the base turns RED. In MP, you pick at slot at T>0, the base is already RED.

Hi. It's a classic question in the Ka-50 because there's another setting which is not module specific (Options > Gameplay > Avionics Language > English).

@Snoopy English is not my first language. Sorry if I said something that makes you think these issues were considered solved. Let me say it differently: "I've found two bug reports which are waiting for a fix: PPLI symbols on TAD only present for AI planes in multiplayer Human controlled F-18 & F-16 not visible on TAD & HMCS Is there anything else you'd like to report about the A-10C/A-10C II TAD?" I saw your links, but since the A-10C is not my cup of tea (it's even the opposite), I don't know much about it. Why am I here, then? In normal times, I wouldn't dare to answer threads about A-10C systems bugs, but my friend @Tarres asked me to take a look, which I did.

This should be fixed in the next update (same issue than this one).

Thank you. I can confirm this issue will be fixed with the next update.

This does not load either ("Mission load fail"). The problem which as been fixed internally is not about Voice Chat, it's about the squelch which can be heard at the end of radio comms with AI (ATC, wingmen, tankers...).

Don't activate the laryngophone and it won't happen. null

From what I read, the AGM-88 is supposed to be low smoke, as is the AIM-120. Let's say the AGM-88 should smoke as mush as the AIM-120. Do you agree?

@Tarres I found two open internal reports: PPLI symbols on TAD only present for AI planes in multiplayer Human controlled F-18 & F-16 not visible on TAD & HMCS Is everything there?

Thanks for your feedback. I've just bumped the internal report about the RPM desync which sets this alarm on.

@Tarres Kerman: NDB instead of DME -> already reported Abu Musa: NDB instead of DME,or combined as Misnky said -> already reported, should be combined (NDB+DME) Bu Hasa: NDB instead of DME -> I couldn't find anything about it -> now reported

Thank for the heads up. It looks like the error was spotted internally. A fix is on its way.

Issue reproduced and reported! Thank you.

@Nealius Can you please share a track or at least the mission file?

Thank you. Your track was way too long, but thanks to your screenshots and to the mission, I could reenact the shot. I'm not sure this shot is the worse when it comes to "cheating" AI : the Tunguska has a radar, and the helicopter was not hidden behind a mountain (also, helicopters are quite noticeable on a radar). The missile went through the forest, that's for sure. I need a more obvious proof that Syria trees are not as "thick" as Caucasus trees, that is from a unit which has no radar I did a few tries with the S-60. I'll see if what I can do. shot_through_trees.trk

Issue reproduced and reported. Thanks for the heads up.

Thank you, @Northstar98. The issue is now reported along with the La Combattante IIa similar issue.