Delta99

I THINK it still remains a bug that re-arming doesn't ALWAYS work. That is, it is bugged SOMETIMES. I reported this probably more than a year ago and if I remember correctly Grimes confirmed its a bug. So try ruining your mission a bunch of times (like 10). And half the time or more you will see units NOT rearming. Then you'll know if you are just running up against a good old DCS bug. Once rearming is NOT working in a mission it doesn't work across the entire mission for the rest of the mission run. Super annoying.

OnSpawnGroup() is likely your friend here. You'll be able to determine the group that was spawned so you can then do whatever you like with them.

That is some awesome stuff there Pikes

Glad you got it working. If you didn't know make sure you monitor dcs.log as you'll see script errors there.

These commands trigger.action.pushAITask("DRONE_1", 1) are not Moose related so this is better asked as a general scripting question.

That is a bit odd. Unless you are giving them a different spawn location I would think they would start exactly as position in the ME. But perhaps there is some odd small translation "bug" in Moose. Don't know. If you want you can submit the issue on GitHub and someone MIGHT look at it. Doesn't sound too serious though. In reality if you weren't watching the units it probably wouldn't even be an issue cause you would never know and there would just be a minute or two delay until they started moving out properly. But I've been in those situations as well thinking, look how dumb these units are cause you're debugging and watching and WAITING!!

Likely NOTHING to do with Moose and most likely 99.9% due to DCS AI. If this is all that happens you're super lucky!!!

MOOSE for most everything.

Awesome work

I like Hardcards idea of creating a new thread for Moose with a generic account so Moose Devs can get in and Change the OP when needed. Also we might have enough control of github to make changes to startup type docs etc. We need someone to step up and put it together though. Nobody likes to write docs!!!

See my response one post up.

I'm not exactly sure what the request is but if you are NOT talking about client aircraft then you can do what you are looking to do with Moose of course and a ton more. Nothing with any scripting can mess with client spawns so you are out of luck there.

Its been buggy for ages. Works sometimes, sometimes doesn't. Same mission, same groups etc. Just your normal DCS bug that has probably been around for > 3 years or so.

Just a quick response: 1. You cannot set client waypoints at all within the scripting framework. 2. SET_AIRBASE should only be giving you airbases on the current map as far as I know.

DAMN, how have I not seen this mod till now!! Definitely need to try it out.

I thought this was a well known issue for many years. Maybe with this track file it will be something simple that they can find.

What would be better is to post your solution in case others run into the same issue.

Great stuff Pikes.

Very strange. Try it with a regular Spawn() and remove the SpawnScheduled. Somehow could be due to SpawnScheduled messing something up??!!

My guess is your are defining the zones incorrectly. Should work and works in my missions.

Far as I know you cannot script anything to do with the weather at all. Whether you are using dynamic or not.

Yes, shouldn't be an issue. Lots of people do that.

You will also probably need an OnSpawnGroup otherwise this may or may not work. Or will work sometimes but not others due to when the plane actually gets spawned. Spawns have an inherit delay in them sometimes and due to that your code for setting up the AI_CAP may not work as the group it is trying to reference may not exist yet.

Whats the rest of your script look like? With just one line printed its hard to tell why. Likely a syntax error.