Squeaky_B

@Nealius I did a quick test with 4x M939's on the Afghanistan map. I have mine setup so that the final waypoint is quite close to the first as the AI doesnt follow the road going from WP5 -> WP0 and in the Advanced (Waypoint Actions) I have "Perform Task". "Go to waypoint". Ran it for 3 loops and this method is still working. Also this method in my other missions appears to be working. Not sure if it helps.

This is working now for me with the latest patch (2.9.12.5336) , thanks folks! George testing out his new prescription.....

So I've done a bit of testing as I was still having issues when setting the fog to Off and manual. The only way I've been able to get George to put his glasses on consistently is to: Open any missions with fog set to Auto Change it to Off and save Close and relaunch DCS Start the mission from either missions or the editor. (It will only break again if you run a mission with the fog set to auto) I noticed that if I had tried to run a mission from the mission editor that previously had the fog set to Auto George wouldn't see anything, even after setting it to off, saving and backing out to the main menu and running from missions. It only worked consistently if I changed the fog to off, saved and relaunched DCS. Seems as though if at any point a mission has been ran with the fog set to auto it breaks George and you'll need to relaunch DCS in order for him to work again. Anyway hope this helps someone in the meantime while we wait for a patch.

@stonewall197922 Doesnt seem to effect the AI. Just did a SP mission on the Iraq map loaded with L's and an AI wingman with the same loadout. George couldn't spot anything at all but the AI was able to find and destroy all the targets. Luckily i also had rockets so the mission wasn't totally a bust but a really annoying bug.

@Thunk Interesting about the waiting for previous positions to move first. In my mission I have the carrier decks populated by a script at mission start. These statics once placed block spawn positions 1 - 6 forcing the player and the AI wingman to spawn on 7 & 8. The player is set to late activation and activated when the mission time reaches 3 seconds. (If I don't do this the player Spawns before the Carrier deck script runs and...."fire happens"). I wonder if the blockage is being caused not by the route to the cat but instead waiting for the spawn positions to become free pr move first? Some things I need to test: 1) Populate the carrier deck the old fashioned way in the mission editor and not use the script. Block Spawns so that the player starts on positions 8 & 7 and see if it still blocks. This should help figure out if statics on spawn positions block the directors. 2) Place down Uncontrolled AI first to block spawn positions 1 - 6 and see if they also block it. This should help me figure out if its anything on those spawn positions or just statics. Essentially I'm just trying to figure out a way to reliably create missions with populated carrier decks that dont always use Cat 1 Sorry for the late reply (Christmas got in the way :D)

I'm having the same issue with "Awaiting Taxi Permission" I have a mission where the carrier deck is populated with statics and the player +1 AI, spawn on elevator 4 to taxi to Cat 3 & 4. The taxi route is clear to the Cats but the directors aren't working and only see the "Awaiting Taxi Permission". What might be of use, is if I use the Tomcat, and go full afterburner in the chocks it can over power them and as soon as it starts to move the directors start working and direct to the cat without issue. As a workaround could you allow us to remove the chocks manually so that missions aren't scrubbed?

HAPPY DAYS! Tested again after seeing this was picked up in the patch notes today (2.9.9.2280) Did the usual, cleared DCS Folder, Ran the full repair, cleared mods out, created a new mission file in the same location as before. This time however I had 1 group with all the same units and 1 group with different units to test @Gierasimov's post. Both groups looped several times with no issues! So happy to say this is fixed. Thanks devs! 1 Tiny thing I did notice is that all of the subordinate units in the group, don't stick to the road when going to Waypoint 0 and instead go directly to it. Not a deal breaker by any stretch of the imagination and just happy they're looping now. Thanks again.

I haven't yet, taking a bit of a break from DCS and mission editing in particular for a while.

I'll give it a try with the same vehicles, thanks

Thanks, can you share a mission file or give any information on how it was setup, any differences from the above etc?

Just given this one a quick test. Steps Taken: Updated to 2.9.8.1107 Cleared out the "\Saved Games\DCS" folder Ran full repair Created a mission with 2 groups of AI, set to on Road with a circular route and the final waypoint with the Perform Task - Go to WP 0 Result: Same as before I'm afraid. Both groups follow the route in full once. When getting to the final WP it all seems to break down and they seem to go all over the place. (sorry I know thats not really helpful but I can't figure out what it is they're trying to do) DCS Test.mp4

Thats fair enough, I can totally understand wanting it to not open the mission for the reasons you've mentioned. I guess the long and short of it is we just don't know whether it was originally an intended change that wasn't included in the patch notes, or was it something that was fixed but wasn't mentioned in the patch notes. Ideal solution would be to just give a prompt when opening the mission that says something along the lines of: "The mission file you're loading contains modules that are not currently installed." With the options of: "Cancel" , "Load" , "Load as new mission" With the last one, creating a duplicate of the mission and loading the duplicate leaving the original untouched. I've been using the tool @HC_Official linked since this changed and works great. Albeit I have to run my missions through it whenever I make a change, in order to keep the missions accessible to others.

I probably wouldn't count your chickens before they've hatched chaps. It's not been recognised as a bug in either this thread or the one you linked so we're in the dark as to what the intended behaviour is supposed to be. Nor has it been mentioned in patch notes as "fixed". It'd be nice to actually hear from ED what this is supposed to be rather than just guessing.

It can only be done before mission start and doesn't work with spots set to "client" only Player, so the route tool would be ideal for singleplayer sandbox missions. If its not coming to singleplayer then fair enough, it is what it is, but the newsletter made me think otherwise is all

Just tested this again in latest patch 2.9.7.58923 After updating to the latest patch, I cleaned the \Saved Games\DCS folder and also ran a full repair. I created a new mission the same way as I created the ones above with the same composition and waypoints etc but this time on the Sinai map. Still the same issue. With 2 groups set to loop. They both complete the route. 1 of them stops at WP0 while the other does continue and loop however the pathfinding is sporadic. Sometimes it stays on the road other times it stops and goes cross country. Not salty that this wasn't fixed in the latest patch, just keeping this updated