correct as is TDOA doesn’t update threat ring for flightlead

[Moonshine]

yeah been doing that for years now. still requires direct line of sight and doesnt work if the weather is bad and hence you cant see it. on top of that, requires TGP point track to generate a markpoint, which will - upon entering point track - already shift the coordinates compared to what your SEAD Page would have shown.
only thing that would work is the AG FCR.

[Hobel]

vor 7 Minuten schrieb SpecterDC13:

That is why you should have a TGP with you. When you lock a target on the HAD the TGP will be in the general area of the SAM. The higher the PGM the closer the TGP will be which will allow you to create a markpoint. Sounds like a lot of work but that is where being proficient with the aircraft comes into play and lots of practice.

you don't even need the TGP, it also works with the FCR

[VarZat]

Thank you very much for investigating! I am happy with the outcome.

[Red Dog]

23 hours ago, VarZat said:

1. You and your flight is out on a mission and you spot an emitter with your HTS pod
2. As master in the flight you engage TDOA and signal your flight to start triangulating the emitter
3. Once you reach PGM1 you send the data to your flight with IFF IN long press
4. Now your flight members all have a steerpoint set exactly on the emitter aswell as getting a threat ring on their HSD giving them good SA on where the threat is

5. You as FL and master now have no steerpoint for the threat you have just triangulated, and you dont get any of that great SA on the threat position on the HSD that your wingmen enjoys. 

Point 5 is actually partially incorrect. A long TMS left initiates TDOA but a short TMS left displays the coordinates in the DED.
Hence making you believe a steerpoint could easily be created if not already
Mayve a M-SEL should make that an active steerpoint (untested) like any other markpoint
It would be interesting to know if the threat ring would magically appear in DCS for the host if these coordinates are made into the relevant system SPI
 

Logic is much better knowing the threat ring over the network is an error on DCS implementation side. It kinda solves the inconsistency indeed
Can't wait to have a solid DTC in DCS because all these lines, PPt and threat rings are dearly missing - even if they are not updated with TDOA
 
 

Edited December 18, 2024 by Red Dog

[TheBigTatanka]

There is an unclassed, but not publicly available, weapons school paper on F-16 M4.2+  datalink that says the TDOA event (along with pre-planned SEAD threat points) will generate the SAM's number with a slash through it on the HSD, and also in the joint helmet -- which is something DCS has never done.    We should be able to see those positions on the ground through our helmet.  

There are also many many unclasped and not publicly available instructional briefs on SEAD in M4.2+ that say the master of TDOA in fact does get a Steerpoint when the emitter is located within 1K feet.   Tapes beyond 4.2 get index numbers to keep track of that across jets when you have multiple people sending out Steerpoints.   But, in 4.2, we just have to be athletic.   But, yes, DCS should save a SEAD Steerpoint for the PT (TDOA) Master.

Lastly, in DCS, memory emitters on the HAD time out in 3 minutes and disappear (the green threats). That should not happen.  Those should stay there forever.  Shooting at memory emitters is part of the F-16 SEAD shot doc hierarchy .   The HTS has a hard drive that stores these threats so Intel can process them post mission.   They definitely shouldn't vanish from the pod in 3 minutes, that's either a bug or a misunderstanding from ED.   

 

Lots of work to do on this stuff.  I know you have limited sources and resources -- but we have like a 69% solution to the problem right now.  

[BIGNEWY]

10 minutes ago, TheBigTatanka said:

There is an unclassed, but not publicly available, weapons school paper on F-16 M4.2+  datalink that says the TDOA event (along with pre-planned SEAD threat points) will generate the SAM's number with a slash through it on the HSD, and also in the joint helmet -- which is something DCS has never done.    We should be able to see those positions on the ground through our helmet.  

There are also many many unclasped and not publicly available instructional briefs on SEAD in M4.2+ that say the master of TDOA in fact does get a Steerpoint when the emitter is located within 1K feet.   Tapes beyond 4.2 get index numbers to keep track of that across jets when you have multiple people sending out Steerpoints.   But, in 4.2, we just have to be athletic.   But, yes, DCS should save a SEAD Steerpoint for the PT (TDOA) Master.

Lastly, in DCS, memory emitters on the HAD time out in 3 minutes and disappear (the green threats). That should not happen.  Those should stay there forever.  Shooting at memory emitters is part of the F-16 SEAD shot doc hierarchy .   The HTS has a hard drive that stores these threats so Intel can process them post mission.   They definitely shouldn't vanish from the pod in 3 minutes, that's either a bug or a misunderstanding from ED.   

 

Lots of work to do on this stuff.  I know you have limited sources and resources -- but we have like a 69% solution to the problem right now.  

Hi TheBigTatanka

If you have evidence to help please DM me, or best to post in the closed beta forum area where you have access. 

If a document is not publicly available it shouldnt be discussed here

thank you