Jump to content

Recommended Posts

Posted

Has anyone had trouble with laser mav accuracy when lasing with the targeting pod? My missiles seem go be going a couple hundred yards long.

 

This is on NTTR with targets at ~4700 feet elevation. Firing from 5-10mi

 

LGB's are hitting long, too, about the same distance.

 

I have a waypoint on top of the targets, which I have set to ground level, also tried setting it to sea level which didn't make any difference.

 

If it's just me, that's OK I'll keep working it. But, I'm not having any trouble getting the mavs to lock, arm, fire and explode. Consistently, on the same spot. It's just the wrong spot.

Ryzen 5600X (stock), GBX570, 32Gb RAM, AMD 6900XT (reference), G2, WInwing Orion HOTAS, T-flight rudder

Posted (edited)
Has anyone had trouble with laser mav accuracy when lasing with the targeting pod? My missiles seem go be going a couple hundred yards long.

 

This is on NTTR with targets at ~4700 feet elevation. Firing from 5-10mi

 

What is your distance from the target at the time of impact ?

 

In DCS the TGP Laser Designator has a range of ~8 NM, if the selected target is further away than that, the laser spot floats in mid air.

 

Edited by Ramsay

i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440

Posted (edited)

Thanks NineLine.

 

First pass: I've been releasing in straight and level flight, 15-20K feet. Kinda close the gimbal limit, maybe that's it?

 

Second pass: But here, I'm closer, in a dive, gimbal is closer to center. Same thing

 

Interestingly Tacview is scoring a solid hit every time.

 

ETA: @Ramsay: yeah I was outside of 8mi on both releases, went back and tried at 6mi and 4mi, the latter about 4000' AGL, same result

AGM65E_TPOD_NTTR.trk

Edited by DeltaMike

Ryzen 5600X (stock), GBX570, 32Gb RAM, AMD 6900XT (reference), G2, WInwing Orion HOTAS, T-flight rudder

  • ED Team
Posted
What is your distance from the target at the time of impact ?

 

In DCS the TGP Laser Designator has a range of ~8 NM, if the selected target is further away than that, the laser spot floats in mid air.

 

 

Have you checked recently, I thought it was extended somewhat, but I would have to search around to see.

64Sig.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

Posted
Has anyone had trouble with laser mav accuracy when lasing with the targeting pod? My missiles seem go be going a couple hundred yards long.

 

This is on NTTR with targets at ~4700 feet elevation. Firing from 5-10mi

 

LGB's are hitting long, too, about the same distance.

 

I have a waypoint on top of the targets, which I have set to ground level, also tried setting it to sea level which didn't make any difference.

 

If it's just me, that's OK I'll keep working it. But, I'm not having any trouble getting the mavs to lock, arm, fire and explode. Consistently, on the same spot. It's just the wrong spot.

 

Are you using point track or area track? If you are using ATRK, try utilizing PTRK (which is achieved by pressing sensor select in the direction the FLIR is displayed on DDI). You will get a box inside the gate display of the FLIR page. Seems like that might be what you are experiencing...

 

 

Cheers,

 

Don

i7 6700 @4ghz, 32GB HyperX Fury ddr4-2133 ram, GTX980, Oculus Rift CV1, 2x1TB SSD drives (one solely for DCS OpenBeta standalone) Thrustmaster Warthog HOTAS, Thrustmaster Cougar MFDs

 

Airframes: A10C, A10CII, F/A-18C, F-14B, F-16C, UH=1H, FC3. Modules: Combined Arms, Supercarrier. Terrains: Persian Gulf, Nevada NTTR, Syria

Posted
Hi! I want to know, ladies and gentlemen, how far can F/A18C's aiming pod detect friendly laser?

 

Within DCS, at least 15nm. Can depend on altitude, visibility and other factors. I’ve had longer LSS detections than 15nm, but that is a for sure detectable range. Real world, classified.

 

 

Cheers,

 

Don

i7 6700 @4ghz, 32GB HyperX Fury ddr4-2133 ram, GTX980, Oculus Rift CV1, 2x1TB SSD drives (one solely for DCS OpenBeta standalone) Thrustmaster Warthog HOTAS, Thrustmaster Cougar MFDs

 

Airframes: A10C, A10CII, F/A-18C, F-14B, F-16C, UH=1H, FC3. Modules: Combined Arms, Supercarrier. Terrains: Persian Gulf, Nevada NTTR, Syria

Posted (edited)
Have you checked recently, I thought it was extended somewhat, but I would have to search around to see.

 

IIRC the Laser designator range for *some* AI ground units was increased recently (it had been very short 1-3 km?, might be 2-3 NM now but I haven't tested).

 

The Litening Pod has the same range it's always had, if the slant range between the TGP and target opens up to more than 8.1 NM, the laser spot lifts away from the target and floats mid air (causing laser guided missiles and bombs to miss).

 

I haven't been able to reproduce DeltaMike's bug yet but I've been launching from lower altitudes (7,000 ft) in the Caucasus, so will need to take a closer look at his NTTR mission.

 

Tested with AV-8B and F/A-18C in DCS 2.5.5.35461

Edited by Ramsay

i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440

Posted
Within DCS, at least 15nm. Can depend on altitude, visibility and other factors. I’ve had longer LSS detections than 15nm, but that is a for sure detectable range. Real world, classified.

 

 

Cheers,

 

Don

 

Thank you very much.

Posted
If it's just me, that's OK I'll keep working it. But, I'm not having any trouble getting the mavs to lock, arm, fire and explode. Consistently, on the same spot. It's just the wrong spot.

 

I saw the same behaviour in your NTTR track/mission.

 

It seems the static "Comms tower M" (and perhaps the (inactive) smoke marker) is too close to the targets.

 

Moving the static objects 2400 ft East of the T-55 tank column, allowed the TGP laser to illuminate the target tank and mavericks to hit.

 

It's likely the "hit box" for the tower's support cables was overlapping the tanks, causing laser guided bombs/missiles to miss.

i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440

  • ED Team
Posted
IIRC the Laser designator range for *some* AI ground units was increased recently (it had been very short 1-3 km?, might be 2-3 NM now but I haven't tested).

 

The Litening Pod has the same range it's always had, if the slant range between the TGP and target opens up to more than 8.1 NM, the laser spot lifts away from the target and floats mid air (causing laser guided missiles and bombs to miss).

 

I haven't been able to reproduce DeltaMike's bug yet but I've been launching from lower altitudes (7,000 ft) in the Caucasus, so will need to take a closer look at his NTTR mission.

 

Tested with AV-8B and F/A-18C in DCS 2.5.5.35461

 

Thanks, I will look into it a little more, I thought airborne lasers were up to 15nm, but I might be thinking of something else, I know ground ones were slightly increased.

 

I am not sure what can be done about the floating in mid air thing. Maybe if the laser is being used out side its limits it shouldnt be picked up at all.

64Sig.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

Posted
Thanks, I will look into it a little more, I thought airborne lasers were up to 15nm, but I might be thinking of something else, I know ground ones were slightly increased.

 

I am not sure what can be done about the floating in mid air thing. Maybe if the laser is being used out side its limits it shouldnt be picked up at all.

 

Yeah it shouldn’t be picked up at all. The limited range is due to scattering, so a floating designation point makes no physical sense.

 

And I remember linking some public data on older targeting pod (like the LANTIRN) having a range requirement for designation of 15 nm, with newer pod being like 20. I’ll try finding those links again.

Posted
... I thought airborne lasers were up to 15nm, but I might be thinking of something else, ...

 

The designator's range is 15 km = ~8.1 NM, perhaps that's the number you are thinking of.

 

I'm not sure on the LSS - it's about 14.5 NM (27 km) when testing for CTLD's JTAC laser spot using the A-10C in 2.5.5.35461

i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440

Posted
Yeah it shouldn’t be picked up at all. The limited range is due to scattering, so a floating designation point makes no physical sense.

 

And I remember linking some public data on older targeting pod (like the LANTIRN) having a range requirement for designation of 15 nm, with newer pod being like 20. I’ll try finding those links again.

 

The larger issue here is that different lasers will have different ranges so to speak, based on actual laser power, attenuation (like through clouds/dust/smoke), and then the detector sensitivity/signal processing on the pod/weapon. Then you have downstream issues of lasing stability/spot jitter.

 

Not the hardest stuff to simulate, but it might be hard to find good numbers. You could simplify it by broadly defining "generations" both for lasers and detectors and then ignore stuff like jitter even though its a real issue at long range. But that would at least let you differentiate things like the difference between the Litening II and Lantrin, or Different generations of Paveways.

New hotness: I7 9700k 4.8ghz, 32gb ddr4, 2080ti, :joystick: TM Warthog. TrackIR, HP Reverb (formermly CV1)

Old-N-busted: i7 4720HQ ~3.5GHZ, +32GB DDR3 + Nvidia GTX980m (4GB VRAM) :joystick: TM Warthog. TrackIR, Rift CV1 (yes really).

Posted
I saw the same behaviour in your NTTR track/mission.

 

It seems the static "Comms tower M" (and perhaps the (inactive) smoke marker) is too close to the targets.

 

Moving the static objects 2400 ft East of the T-55 tank column, allowed the TGP laser to illuminate the target tank and mavericks to hit.

 

It's likely the "hit box" for the tower's support cables was overlapping the tanks, causing laser guided bombs/missiles to miss.

 

Good find! I'll try it without the tower

Ryzen 5600X (stock), GBX570, 32Gb RAM, AMD 6900XT (reference), G2, WInwing Orion HOTAS, T-flight rudder

  • ED Team
Posted
The designator's range is 15 km = ~8.1 NM, perhaps that's the number you are thinking of.

 

I'm not sure on the LSS - it's about 14.5 NM (27 km) when testing for CTLD's JTAC laser spot using the A-10C in 2.5.5.35461

 

Ah, you might be right... too many numbers in my head.

64Sig.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

  • ED Team
Posted
Yeah it shouldn’t be picked up at all. The limited range is due to scattering, so a floating designation point makes no physical sense.

 

And I remember linking some public data on older targeting pod (like the LANTIRN) having a range requirement for designation of 15 nm, with newer pod being like 20. I’ll try finding those links again.

 

Please and thank you, I might have seen them before, but for the sake of checking again, I'll look into it.

64Sig.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

  • Recently Browsing   0 members

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