F-15C's A.I. taxi problems

Hello there,

I've noticed an issue with F-15C's and taxing. It only occurs on some airports though. I've discovered both Nalchik and Maykop have this issue. But airports like Mozdok and Sukhumi did not.

Anyway, if there is a que for the runway, and the taxing aircraft come to a stop, they get stuck in that position and won't move anymore.

Simple testing was setting up 2 groups of 4 F-15's. One as Ramp Start, one as Hot start. I'm sure it doesn't matter, but I thought I'd just put that variable in there too. The first few F-15's get off the ground, but that's it.

This image below is from a mission I created. 2 F-16's successfully departed before this.

Stable DCS version as of 3/20/2016 1.5.3.51417

- Apache600

Ack, I just noticed that there is a "Release Version Bugs and Problems" subfolder after posting this. I can't seem to delete this post, and don't want to double it up. Mod, if you see this, any chance you can move it over there?

Still got this sort of thing, my wingman always stops on the runway and just sits there.

Hit the horn, maybe they will move.

I've had this happen with P-51D's too.

I had 4 groups of 4, all AI controlled that simply were supposed to take off from Tbilisi 'from the ramp', fly a number of turn-points, and then land.

At mission start, each group started up, and the group closest to the runway started moving first toward the runway.

It was obvious through observation that there are certain points on the taxi-ways close to the start of the runway, which cannot be passed until the first aircraft has taken off. All the other aircraft of the group gathered here, much like the above illustration. After the first aircraft took off, the next one made its way from the wait-position to the runway and took off, etc.

During this the other groups gathered at a position further back from the take off wait position.

The problem is, that once the first group had completely taken off, the other groups in the second wait position simply remained where they were, as if they were waiting on a trigger to allow the next group to move to the runway. This went on for 15-20 minutes until I broke the mission off.

Also during this time, the first group had flown off all if its turn-points, but instead of landing, it simply flew circles around the airport as if waiting.

I think the AI had the runway reserved for the next group to take off, so the first could not use it to land, but the next group did not 'realize' that the runway was free for it to take off.

Yes I have this issues in 1.5.4OB too.

Some days ago with AI Mirage 2000C in Krymsk and today in Sukhumi with AH-6A Apache....

Very annoying issue... That kill the mission, so now I have to make aircrafts already airborne to avoid it. :glare:

Yeah, fortunately, i am fixing this with a new class in the MOOSE framework ... A workaround, which i think is urgently needed to keep things working. A fix from ED will be months away for this one I guess...