Minijohn

I have had the same problem in different maps, I recently started using the "combined joint task force" setting and that's when my problems started. The group I belong to tested a new mission build last night using Syria map with the AWACS in the "combined joint task force" setting and AWACS would only give CLEAN and MERGED messages nothing else, this morning I have just tried as suggested above and set it as USA and it works as it should. ALL other aircraft in BLUE coalition are set to "combined joint task force". As a follow up I set it up as a UK aircraft and it again worked correctly, all though not extensively tested it does point to the setting "combined joint task force" being used

I had the same problem, tried the fix "try going to savedgames/MissionEditor/settings.lua and deleting the line listing the soundPath" and I also moved the file shown in the soundpath out of my sound folder, first try seems to be successful

Had similar problem tonight on a multiplayer session, no-one saw the FLOLS overlay as it failed to appear for all users (six users online at the time). Tested it in single player and appears to work as advertised

We had the same problem flying with 6 A/C this evening, I kept hearing my number all the time, even though I had not asked for the re-join, others were saying that they heard their number in similar situations.

I have had a similar problem, I made 3 flights to depart from Lincoln, the flight I was lead of spawned around the deck and were blocked by other aircraft set to depart on a switch latter in the mission. I could taxi as I was in the first spot near the forward cats, but No. 2 spawned just forward of the island in a slot blocked by other aircraft. I have tried numerous ways to overcome this and the only way was by using LATE ACTIVATION, which sort of ruins the effect of a deck full of aircraft on start. Would/Could it be possible to select slots for AI as at an airfield, then it would be possible to prevent a latter departing flight from blocking an earlier flight.

While building a mission I used a TRIGGER ZONE AND TRIGGER to illuminate the German searchlights. This worked fine. During the mission bombs dropped close to one of the illuminated searchlights and the game crashed. I made a quick test mission to check if it was the light causing the problem as I had not had this problem before I illuminated the lights. 1/ I tried first with searchlight OFF, hitting the searchlight and destroying it without problem 2/ Tried with searchlight ON and just as weapon hit game crashed 3/ Tried again with trigger zone of 500 feet around the searchlight and trigger to turn OFF light on weapon detect, this again worked. Although the fix worked it is messy if you do not know what weapon may destroy the searchlight.