Delta99

You must be doing something wrong or there is a bug somewhere. Has worked for me for ages. You might have to do some further debugging making sure your EngageDistance is correct. Of course with DCS it could just be a new bug ED has introduced or something that has changed in Moose recently (although I don't think escort has changed in ages).

1. The DCS scripting environment unfortunately doesn't allow joining groups. I'd bet this was a requested feature going back many many years but not certain. 2. The debriefing screen is completely separate from Moose scoring. Further anything spawned units will not be reflected in the scoring tallies for number of planes killed at the top left of the briefing. Once again a DCS limitation that only ED can fix. I believe those numbers only count what you create in the ME. If you've implemented the MOOSE Scoring class it is separate.

What you can do is examine how Moose / Mist does it and then write it yourself. In the end both systems are using the DCS API so you'll see what calls and how it's done. In the end you'll probably write 10-20 times more code (maybe even more) than you would just using Moose or Mist.

Not possible through the scripting API as far as I know for client waypoints.

Ah, so it’s probably a bug and coded incorrectly in the config.

Depends what you are trying to do.

Just want to say it should be easily doable with Mist / Moose and even the mission editor perhaps. I don't have any code handy unfortunately at the moment.

If it is a client group it can't be done to my knowledge. I've tried it and it crashes DCS at least for an F15C. Perhaps with other airframes where you can add/remove waypoints in the cockpit it will work but I highly doubt it. For AI groups, I do it all the time.

Are you sure you are checking both ammo types for the Tunguska. You'll get both listed in a table array I believe. So you may be looking at the wrong one. For the other SAM's you'll get just the one array for the only weapon it has.

There is no way to do this either!!

Probably depends how you are detecting the launches. The Tunguska might be the only SAM type unit you are monitoring that also has guns on it which might throw a wrench in how you are monitoring. But, I've monitored Tunguska SAM launches successfully before (I THINK).

If you are using FOW settings I think this is pretty much the default. If the enemy does not show up on F10 view then you won't get it via F2 either. At least that is my experience.

You can do that in scripting.

This is all done by scripting in the mission. You'll have to learn scripting and the mission scripting API to be able to build menu's, read map markers, and spawn units. I know this is a very high level answer but this is the road you would have to go down for something like this.

InitCleanup() needs to come before SpawnScheduled. Probably having that there messes with the scheduled spawns. I'd just remove the cleanup altogether. Probably not needed. As for DCS crashing that is a bug ED introduced a few updates ago. However, the version of Moose from the development branch has a work-around fix in it until ED actually fixes it themselves!!!!

Warehouse Airbase Resource Proof Of Concept Thought I would throw this here in case anyone is interested:

I created a short video on a proof of concept I put together using FunkyFranky's Moose Warehouse class to ferry airbase resources between airbases. Thought some people might find this interesting Checkout Moose Warehouse Class docs here: https://flightcontrol-master.github.io/MOOSE_DOCS/Documentation/Functional.Warehouse.html

Its bad on other maps too. Maybe not as bad but it can happen.

Note, this only works at the group level so you can set the entire group to Alarm State Red or Green but not individual units. Was just working on this the other night.

No, you shouldn't need to set anything in the advanced waypoints. You are probably missing something in the SA6 group.

This should be written like so otherwise you'll likely get some very odd behaviour: local flight1=SPAWN:New("FLIGHT1"):InitLimit( 2, 10):InitRepeatOnLanding():SpawnScheduled(30,0) Initially your error was that you had Limit() instead of InitLimit(). This would have shown up in an error most likely in your dcs.log file. Whenever something isn't working have a look there for errors.

This is great stuff. I am trying to think of what this data can be used for in a real-time sense for mission building.

What specific method are you talking about? If it is like other Route waypoint numbers. The first number is typically the first waypoint from the START and the 2nd one is the number of waypoints from the END. So (1, 1) would mean first and last waypoint. (2,2) would be the 2nd waypoint to the 2nd last waypoint. But it depends exactly what method you are talking about.

Yeah, my Huey was shot to pieces but still managed to barely fly it out of there. Bunch of systems not working so it was a little more challenging getting to the MASH but fun all the same!! :)

Can't tell from you screenshot but I believe the SA-10 has tracking radar(s) as well. You'll need at least one of them (maybe two, can't remember off the top of my head). It looks like you might have them there but I can't tell. Just list the units you have rather than a screenshot that can't be read.