L2MUM Drone Footage

[GrEaSeLiTeNiN]

The L2MUM drone footage will always show a target it alone decides to pick.

At the moment, L2MUM drone footage does not follow the AFAC ME assigned targets or the AFAC auto target & lase script. It basically has a mind of its own. The coords of the target (selected randomly by L2MUM) as indicated in the footage are correct. But the coords of the drone as indicated in the footage will always be that of the drone you select in the INIT page, regardless of the target in the footage.

I tested this with a custom mission: I had a Reaper AFAC with two assigned arty vehicle targets and a Predator AFAC doing the auto target & lase script with its targets marked by red smoke. When I started the mission, the L2MUM footage showed a completely unrelated target. It was a target not assigned to the Reaper, whether before or after the 9-line procedure. The target was also not lased by the Predator as the red smoke was at another target. Regardless of which drone I selected in the INIT page, it was the same target footage (no change). But after I destroyed the target in the footage, the 'L2MUM drone' decided on its own to pick yet another unintended target.

So for the time being, to use this fun feature, it seems you basically target and destroy whatever the 'L2MUM drone' decides. Your drones' targets as intended in your mission design will not be followed. This may be the module's current design intent due to limitations in DCS?

The above problem was somewhat mentioned in this tutorial vid.

Hoping this will be corrected in future updates so the L2MUM drone footage follows your selected drone's mission design targeting.

Edited June 27, 2024 by GrEaSeLiTeNiN

[YoYo]

+1

[shinobi61]

+2

[doedkoett]

In addition, the drone might even select to look at a unit not yet spawned, showing nothing but empty terrain. This will not be a problem once we can control, from the ME what the drone should be looking at, but anyway. Might be worth looking in to.

[GrEaSeLiTeNiN]

Bump - not fixed

[Ratcatcher]

Bumpty bump...bump!

[adirtynurse]

This was addressed on Discord. The reaper is an ED product, which they don't think is a priority to develop, since none of their modules have a function like the L2MUM. So for the time being PC and other 3rd party devs have to play magyver with ED's toolset OR start creating a whole new module just for the AI. Its also something to do with local vs server assets. Supposedly in testing the devs implemented community mod stuff, that would work in SP, but not in MP etc.

Edited August 13, 2024 by adirtynurse

[GrEaSeLiTeNiN]

3 hours ago, adirtynurse said:

This was addressed on Discord. The reaper is an ED product, which they don't think is a priority to develop, since none of their modules have a function like the L2MUM. So for the time being PC and other 3rd party devs have to play magyver with ED's toolset OR start creating a whole new module just for the AI. Its also something to do with local vs server assets. Supposedly in testing the devs implemented community mod stuff, that would work in SP, but not in MP etc.

Yes I heard about that. Was thinking perhaps the L2MUM display could replace the ME drone names with just one drone called "L2MUM drone" or some other name since as described in OP, a 'ghost' drone is doing random targeting regardless of which ME drone you select. 

Edited August 13, 2024 by GrEaSeLiTeNiN

[AirSenpai]

+1