Jump to content

Recommended Posts

  • ED Team
Posted

You are doing everything correctly so it does seem this is related to the already reported issues. 

I have bumped the report internally.

thank you, I will merge this with the other report.

 

  • Like 4

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

  • 4 weeks later...
Posted (edited)

Hi guys

My jdam won't hit accuratly anymore. Is there an issue? 

They always miss target my a few meters its annoying. 

Edited by Viciam1
Posted
vor 30 Minuten schrieb Viciam1:

Hi guys

My jdam won't hit accuratly anymore. Is there an issue? 

They always miss target my a few meters its annoying. 

 

Have never been accurate on the 16, issue is being worked on. At least I think so.

Posted

Hi guys

so up until a few months ago i used to put the tgp point track right under the target and the jdams would hit and destroy the target without fail

i stopped playing for 3 months and something has changed. Doing this and the jdam misses target.

so im guessing something changed. So where r u guys putting the tgp point track now to get accurate jdam hits on target in f16?

its annoying coz i keep missing my targets. 

 

Thanks

Posted

they used to be fairly accurate for me. Like 95% of the time if not 100%. 

I used to put target point just below the tank or whatever was to go boom boom. 

Now im seeing if putting it a few meters in front of target works

  • 2 weeks later...
Posted (edited)

With Open beta update 2.8.4.38947 (released 13. April. 2023) the setting of Markpints with the TGP and subsequent attack with JDAMS (GBU-38) are still bugged.

Setting Mark points with the TGP and then afterwards cycle the set Mark points, put´s the TGP way off the Mark point targets - appr. 10-20 meters.

Also dropping GBU-38's  misses the targets by a large margin, mostly serveral meters.

This is by following the exact same procedures as shown in this video (and other videos showing the exact same procedure: 

 

I do put the TGP on the base of the vehicles.

The outcome is the same regardless whether I use laser ranging or not.

 

Edited by fjacobsen

| i7-10700K 3.8-5.1Ghz | 64GB RAM | RTX 4070 12GB | 1x1TB M.2. NVMe SSD | 1x2TB M.2. NVMe SSD | 2x2TB SATA SSD |  1x2TB HDD 7200 RPM | Win10 Home 64bit | Meta Quest 3 |

Posted
3 hours ago, Moonshine said:

 

+1

Jup...

Just wanted to re-assign the issue, since the quoted post had been locked.

 

| i7-10700K 3.8-5.1Ghz | 64GB RAM | RTX 4070 12GB | 1x1TB M.2. NVMe SSD | 1x2TB M.2. NVMe SSD | 2x2TB SATA SSD |  1x2TB HDD 7200 RPM | Win10 Home 64bit | Meta Quest 3 |

Posted

yeah then again there was nothing in the patchnotes about that being fixed. i hope it wont take until the end of the year. kinda makes precision bombing useless unless its laser guided... and its been a couple months broken now

  • Like 2
Posted

Here are two tracks.

Both are with airstart inorder to rule out any misalignment.

This one is when going straight towards the target:

F-16_TGP_Mark_1.trk

Here is the outcome:

F-16_TGP-MARK_1.jpg

 

Here is one with an appr. offset of the target 20° to the left during setting the Mark points:

F-16_TGP_Mark_2.trk

And the outcome:

F-16_TGP-MARK_2.jpg

| i7-10700K 3.8-5.1Ghz | 64GB RAM | RTX 4070 12GB | 1x1TB M.2. NVMe SSD | 1x2TB M.2. NVMe SSD | 2x2TB SATA SSD |  1x2TB HDD 7200 RPM | Win10 Home 64bit | Meta Quest 3 |

Posted

JDAMs are still dead-on accurate for me. After creating markpoints and setting them as steerpoints, on-board sensors are not slaved to their location. You have to use CZ function (once). If you don't, markpoint (set as current steerpoint) won't act as SPI and therefore JDAMs will miss. I suspect that's causing the issue.

I have recorded my test:

 

 

Posted (edited)
51 minutes ago, Moonshine said:

they are accurate if you drop them on a set waypoint however they are not accurate if you drop them on a point track location designated with your TGP

 

I have provided a video evidence exactly for the scenario you mentioned.

Or do you mean by using TGP without markpoints? I works too. Maybe you're not using it correctly?

Edited by Jascha
Posted (edited)

Upon designating a target with the tgp either in area or point track, no matter how accurate you put your crosshair, bombs consistently fall short towards your ingress direction. Also check the linked post. There is enough evidence and you can assure yourself that i do in fact use the pod correctly

yes they drop accurately on markpoints etc but i should not need to make a markpoint for every target i want to hit prior to releasing the jdam. 

Edited by Moonshine
  • Like 1
Posted (edited)
8 hours ago, Jascha said:

JDAMs are still dead-on accurate for me. After creating markpoints and setting them as steerpoints, on-board sensors are not slaved to their location. You have to use CZ function (once). If you don't, markpoint (set as current steerpoint) won't act as SPI and therefore JDAMs will miss. I suspect that's causing the issue.

I have recorded my test:

 

 

 

I do press CZ after having set the first Mark point (26) and set it as Steerpoint by pressing M-SEL.

After that I set the other Mark points (27-29).

After having set Mark points with the TGP it shouldn´t be necessary to CZ the TGP for them to b accurate, since the Coordinates has already been set to each Mark point.

Maybe it´s map dependent, since it seems to work on the NTTR map for You, while it doesn´t on the Caucasus map, where they fall short.

Edited by fjacobsen
  • Like 1

| i7-10700K 3.8-5.1Ghz | 64GB RAM | RTX 4070 12GB | 1x1TB M.2. NVMe SSD | 1x2TB M.2. NVMe SSD | 2x2TB SATA SSD |  1x2TB HDD 7200 RPM | Win10 Home 64bit | Meta Quest 3 |

  • fjacobsen changed the title to Mark points with TGP and subsequent JDAM accuracy still bugged - Now with .trk files.
  • 2 weeks later...
Posted

Hi guys

In my sheer frustration with the current state of the TGP and the JDAMS when using MP's generated by the TGP got me to do some basic testing. I have not seen this specific issue raised, so here goes...... Just hope its not me being stoopid.

Basically, when you try save a MP from the TGP, The Lat/Long saved in the DED (MP 26+) is never the same as what your point track has designated.

Example Point track on the TGP says N36 39 778, and W115 29 209. Once sent to the MP, the Coords on the DED for that MP say, N36 39 775, W115 29 202. If you plot those 2 points apart in the ME, It is a 38ft difference. That's enough to make JDAMS miss right?

It happens every time without fail for me. There is that tiny difference between what is point tracked, and what is saved.

I was watching this youtube video from a while ago and took specific note of what was point tracked, and what was saved, and it was correct and identical https://www.youtube.com/watch?v=Q9Aao1Y0Nuw

So did it break? Can anyone else reproduce the same results?

 

BW

 

  • Like 1
Posted

Basically, it should be related to this and with the transmission it is then not surprising that it is not quite accurate.

 

 

 

 

  • Like 1
  • 3 weeks later...
Posted (edited)

Today I tested the TGP coordinate generation as well as target of opportunity GBU-38 accuracy and as far as I can tell it has been fixed or am I dreaming? If so was it his patch or another one? I did not see any relevant fixes mentioned.
 

 

Edited by Sinclair_76
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...