FishBike

What's the weather setup in the multiplayer missions where this is happening? Specifically, the temperature? If the temperature is significantly colder than standard, it would be expected that the barometric altimeter would read higher than actual altitude, and this is not corrected for by the altimeter setting. At least that is what happens in the real world, so I'm wondering if that is modelled in the sim too. In which case perhaps the TAD info is driven by the altitude from the EGI rather than the barometric altimeter, and so it's not affected by the temperature? Just a theory that could use some testing as I have seen similar mismatch between baro alt and waypoint alt in missions I've design with cold weather.

I think I might have stumbled onto the trick to getting this to work. Today I tried changing all my AI flights' waypoints from locked time to locked speed, and still they ignored the required speeds. Except for the four planes I intend to turn into player-controlled ones. Each of those has only one plane in the flight, and they seem to be working properly. So I tried changing one of my other flights to a single plane and it worked! It's kind of looking like their attempts to maintain formation cause them to ignore the times/speeds in the flight plan. I'll redo the whole mission as single-aircraft flights and see what happens, but I have a strong feeling it's going to work.

I'm working on a mission with several flights of AI aircraft. For some reason, I'm having a heck of a time getting them to arrive at their assigned waypoints along their route at the time specified in the mission editor. Just wondering if there is some trick to it that I'm missing, beyond giving them a route where the ETA of some waypoints is locked? In all the different ways I've tried it, there have been no red indications on any of the waypoints to indicate an invalid flight plan, and the calculated speeds between waypoints seem like they're well within the capabilities of the aircraft. For comparison I have one flight assigned to "escort" duty and they are quite happy to go much faster to catch up with the planes they're supposed to escort.

To save you some time, here's a copy of my X-52 Pro profile. It maps the mini-stick to the HOTAS slew keyboard commands, and leaves everything else assignable through the controls setup in DCS World. As the previous poster mentioned, you do also have to disable the "clutch" button in the Saitek control panel before you will be able to map the (i) button in-game. DCS A-10C-Saitek X52 Pro-FishBike.zip

Yeah, StarTrekMike and I fired up a mission right after installing today's update to see if it fixed the problem, and unfortunately it did not. I'm the one running the server in this case, and it didn't crash on my computer. I don't know if there's any information from the server end of things that would be helpful for diagnosing this, but if there is, I can post it.