Delta99

Good points here and hopefully ED are paying attention and picking up some potentially good ideas and solutions from this thread.

Which waypoint is your landing waypoint or which waypoint is your last waypoint?

This is GOLDEN. I'm glad I jumped in at year 8 and saved myself 6 years of grief. But now I've got two years of grief under my belt. Does that count for anything??!!

Everyone was told to use the names exactly as is in the map display. This seems to work. The mapping in Moose wasn't done yet so that was the work-around. Might still be. Not sure the mapping has been done or if it has it hasn't been released yet and is in the development branch.

I think what Grimes is saying is that no matter what way you do it via scripting you're going to get a "flyoverpoint" so until they fix that you are out of luck.

This sounds like its coming from someone that has never written a line of code or attempted to develop a multiplayer mission. You can have 3 lines of script but there are fundamental problems with MP that have nothing to do with either decent or poorly written code. Or any code for that matter. I'm not going to educate you on what all these are because its well known in the community and been reported on the forums for years. The only good news is that it seems that MAYBE, finally there has been some effort put towards fixing these fundamental problems. Time will tell.

Even if you are not trying to host a large MP server this applies to us that like to fly with a few friends. In other words anything more than SP. These problems affect servers with just 2-3 players on them too. And I'm talking the most basic of issues never mind lag and such. I think it is time for ED to give some serious time in fixing these issues after finishing adding cows to the game.

@Hardcard, I don't know what "settings" would be passed to ToGroup() or whether you are setting up some variable based on some example. I would remove it. Don't think it is required. Might be a documentation error OR since it isn't documented I have no clue what it should / would be. I bet if you remove that it will work.

Yes, set them up in the ME first. They can be in a trigger that will never fire. This adds them into the mission.

I haven't touched my mission but tested in the latest DCS version and all seems OK again.

You are only querying the speed and altitude ONCE. You need to get those every time your scheduler runs.

I think you can have a unit engage only a specific unit via the ME. I don't use the ME that much at all but pretty sure under advanced it is there and likely can be set to restrict this. Or at least make that unit much more of a priority than the player.

Yeah, prefix is a bit misleading in that I believe it was meant to be what the prefix will be when the units are actually spawned. Or its just plain wrong to use Prefix here.

Likely you need the full group name not a prefix.

You cannot spawn client so no go.

I think your initRandomizeRoute is killing the ROE options you have set in the editor. Change it to InitRandomizeRoute(0, 0, 20000)

BUT, ED could potentially do this because they do it currently for FOW purposes. So it is modelled and done just not exposed via the same API call I guess. I think it is likely also that a player controlled unit is not technically a controllable (or is it)?

Track replays have been bugged for many years.

Yeah, I understand your additional requirements. Was just thinking this could be built on top of RAT rather than re-inventing the wheel. The only additional part is the dynamic generation without using ME templates. You should see what funkyfranky has to say about this as he is the actual author of RAT. Although RAT I'm sure uses the underlying Moose spawning function which currently is dependant on ME templates so it might not be that easy to incorporate.

I believe this is a long standing audio bug for many years. Not sure if they will ever get around to fixing it.

To a large extent this already exist in Moose as RAT - Random Air Traffic

That must be left over stuff. The best to look at is this line which I missed initially as I thought it came AFTER the Moose loading line:

Hi all, this mission might be busted right now. Seems something that ED changed recently is bugging out the spawning of aircraft. Hope to fix this soon when I get some time and can figure out how to!!!

Probably not without some scripting whereas you rebuild the waypoints orbiting the carrier periodically

It looks like you are running v1.1 if I am reading the log right which is very old.