Script to get coords of player lased target

[ldwater]

Hey all,

Is there anyway I can get the coords of the player lased target?

For example:

I'm in the KW scouting a location and I want to relay coords to an AI artillery in waiting to fire on my target.

I want to be able to lase the target and be able to relay that target location information to the AI.

Obviously if the artillery was a human I'd be able to do this over comms and just tell them the coords directly and they would input them at their end and job is done, but with an AI it seems very tricky to be fully dynamic (ie, no preplanned locations)

The easiest way would be to directly grab the current lased target location info and pass it on to the AI group to do its thing.

I've tried other approaches like having to type in the coords via the F10 menu (which takes AGES) and using target / mark points, but I want to avoid using the F10 map if possible (to preserve that precious immersion  ) 

Thanks in advance

[sorcer3r]

this could be for you (and me ) https://www.digitalcombatsimulator.com/en/files/3338671/

[cfrag]

5 hours ago, ldwater said:

Is there anyway I can get the coords of the player lased target?

AFAIK, not in general (i.e. you can't get the location that an aircraft's targeting pod is looking at. There is a very interesting Gazelle-specific script by @CakeSorbus here: 

The downside is of course that this script is only for the Zelle, and can't be generalized (I shudder to imagine the amount of sleuth work that it took CakeSorbus just to find out which parameters to access in the Gazelle). I know it's a bit silly that this kind of vital information (what location is a unit targeting now) isn't available in mission scripting, but I guess that's DCS for your. It would be great, if, for example, we could get this information from drones - but not right now. Or more specific: I don't know, and would love to be told otherwise.

 

5 hours ago, ldwater said:

I've tried other approaches like having to type in the coords via the F10 menu

That approach is tried and tested, works well, can be implemented reasonably easy - and is entirely over-powered, I'm afraid. Simply intercept the Mark event, and get the map point. Can be done in a couple of lines.

Edited June 18, 2024 by cfrag

[ldwater]

Thanks, I had guessed but wanted to be sure.

The next best thing for me would be some sort of keyboard that you can use with the F10 menu option so you can just type the coords in and send.

Oh well.. 

[cfrag]

1 hour ago, Dzsekeb said:

In theory it could be adapted to any aircraft that has a built in camera that moves in game.

Indeed, and thank you @Dzsekeb! Tbh, that's exactly what I was afraid of and meant wrt Cake's effort. To get the drawArgument I need to view the model in ModelViewer. Modelviewer hates me. I then have to find the model - really fun. For example, the shape for the Huey is called "ab-212" (IIRC) and is hidden somewhere in the bazar structure. Really fun to find.

OTOH, you are correct and maybe this idea of using a sight to initiate some ray casting can be applied to some other modules (Kiowa? Ka50?). Thanks, if time permits I'll try and take a look (for example, maybe the values of 471 and 472 can be used to derive at a ray from the CP's position, provided that 473 is at 1.0). But my point more that mission designers should have an API for this to easily derive the point that a sensor is looking at. Any sensor. But I digress - thanks Dzsekeb, it's good to see you around.

[Gideon312]

On 6/19/2024 at 12:59 PM, cfrag said:

Indeed, and thank you @Dzsekeb! Tbh, that's exactly what I was afraid of and meant wrt Cake's effort. To get the drawArgument I need to view the model in ModelViewer. Modelviewer hates me. I then have to find the model - really fun. For example, the shape for the Huey is called "ab-212" (IIRC) and is hidden somewhere in the bazar structure. Really fun to find.

OTOH, you are correct and maybe this idea of using a sight to initiate some ray casting can be applied to some other modules (Kiowa? Ka50?). Thanks, if time permits I'll try and take a look (for example, maybe the values of 471 and 472 can be used to derive at a ray from the CP's position, provided that 473 is at 1.0). But my point more that mission designers should have an API for this to easily derive the point that a sensor is looking at. Any sensor. But I digress - thanks Dzsekeb, it's good to see you around.

I really hope you'll find the time LOL.