Is there a detailed log of mission I can analyze?

[skyelaird]

Hi

I'm playing with Mission Editor and trying to figure things out.

 

I have a couple of events that are blocking things up and I'm trying to troubleshoot them:

 

- when I load troops into a chinook for transport, some of them load and then at about the 10th soldier they stop. I'm well below the aircraft capacity of 33.

 

- I sent a couple of Su-33s to bomb a runway. part way out, wingman RTBs and then the lead RTBs as well about 75% to the IP. Using unlimited fuel, so that shouldn't be an issue?

 

- I have a squadron of Tu-95s I send out to launch some cruise missiles. Occasionally, one will abort and RTB.

 

I'd like to dive into an event or parameters log to debug the bumps, but I haven't found any documentation to that effect.

I'm not using MOOSE or anything smart, just the generic ME stuff for now...

 

:helpsmilie:

 

Joel

[Hardcard]

In other words, you want to trace DCS scripting engine activity.

 

I've only used tracing in MOOSE scripts, so I have no idea if/how DCS scripting engine processes can be traced.

 

Anyway, even if you could trace it all and find the problems, there's little you could do about them in ME (sure, you could try finding workarounds within ME, that's about it).

 

The problems you described are the sort of thing that make people learn scripting (myself included).

 

 

Regarding the troop pickup problem, the ME trigger might be capped or maybe there's a trigger conflict somewhere.

 

Regarding the runway bombing task, it requires unguided bombs and you also need to specify attack quantity.

If the attacking plane(s) don't have compatible weapons (unguided bombs), they'll simply RTB.

 

Regarding wingman behaviour, it's often problematic in DCS. Sometimes wingmen will RTB even if all task requirements are met... in such situations, I try to use individual unit tasking instead.

 

 

In any case, scripting cures many ME ailments, sometimes it's better to just avoid ME functionality and script stuff instead.

Edited May 28, 2019 by Hardcard

[skyelaird]

Thanks Hardcard!

So, I need to learn MOOSE (unless there's a lower threshold scripting engine around) - I take it MOOSE beats LUA hands down?

(I haven't looked into any of this yet - guess I should now...)

[Hardcard]

Lua is a scripting language, MOOSE is just a scripting framework for DCS, which is built on Lua.

[Pikey]

Sounds very core DCS related and not the type of thing that can be debugged. AI behaviour in all DCS API scripting is limited to... Did I tell it what I wanted it to do correctly? Yes/No. Stop. You only get feedback on what was not understood programmatically, not whether a plane did something odd. DCS.log doesn't output things like what the AI decided to do and when.