Jump to content

Recommended Posts

Posted (edited)

Tonight the wing I belong to flew a long range deep strike. My flight, the strike flight, dropped 8 GBU-16’s in auto-lase from 30K. All aircraft had individual laser codes set into the Stores profile and in the TGP. We each armed our lasers. We dropped on moving SCUD launchers. All bombs missed...Is there anyone with similar problems? Was 30,000 too high? A review of tacview indicated the releases were kinetic, did not appear to track any laser. The last two were dropped manual guided by laser the moment bombs left the pylons.

Edited by davidzill

Asus Prime Gaming Wifi7 // Intel 14900K @5.5GHz // 64Gb DDR5 6000MHz // 3090 RTX // 4TB Samsung NVME M.2

 

 

 

Posted

IIRC laser designator range in DCS is hardcoded to 8nm, so at Angels 30 your slant range indeed might have been to high

i7 - 9700K | 32 GB DDR4 3200 | RTX 2080 | VKB Gunfighter Mk II /w MCG Pro | Virpil T-50CM2 Throttle | TrackIR 5 | VKB Mk. IV

 

AJS-37 | A/V-8B | A-10C | F-14A/B | F-16C | F-18C | F-86F | FC3 | JF-17 | Ka-50 | L-39 | Mi-8 | MiG-15bis | MiG-19 | MiG-21bis | M2000-C | P-51D | Spitfire LF Mk. IX | UH-1H

Posted

I experienced this recently between angels 15 and 25. I've dropped these with no issues before well over angels 30. I've tried a few times to reproduce for a track file and no luck so far. I was on an MP server as well when it happened.

Nobody likes me because I'm unsafe.

Posted

Dropping on moving targets from high altitude in the Hornet, in my experience, presents two problems:

 

PTRK does not update the designated target location, so if you acquire the moving target early, you'll be aiming the bomb at a location far off from when it'll be when the laser turns on. I usually hit TDC Depress at around 5 seconds to release to update the point, and if I'm dropping from very high altitude or on a fast moving target offset my aimpoint slightly in the direction of travel. 

 

Even if you've aimed perfectly, the AUTO release cue is aiming where the target is at the time of release, not where the target will be when the laser turns on. For longer bomb fall times, such as at very high altitude, target movement can take it outside the bomb seeker's field of regard by the time auto lase turns on. For these attacks I will usually manually lase at around TTI=30s. 

  • Like 1
Posted

Just tested GBU16's in the Syrian map. No problems dropping from 30k on a building. Auto lase.

I also had 2 movers running through the desert at 45 miles/h. Obviously I wasn't planning on an attack from 30k but... I sure as hell tried, lol. I did see 2 dots on the FLIR but I wasn't able to lock'em. Besides, I was almost directly above them when I saw them.

I did lock them nicely from low altitude and the laser tracked the mover with no issues. The second vehicle must've been disabled and stopped so... easy pickings.

The track didn't record correctly and the MS game DVR records my VR like crap, scaling down from 3168x3092 per eye to 1920x1080🤢

I can post it if anyone wants to see it.

Posted

I think the issue turned out to be not updating the auto aim point via a tdc depress closer to release. Because of this the bomb fell, but the laser was outside of the seeker heads field of view. Why does the pod update it's coordinates when slewed, but this doesn't also update the aim point for auto releases? Is this how it is in the actual plane?

  • Recently Browsing   0 members

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