*Aquila*

This. Once your FPM is on the runway's treshold, there are only 3 important things: 1) AoA 2) AoA 3) AoA In this order.

That, for sure, is the question. I haven't bombed with the Hornet for a while and I'm far from home and my sim station. But one should get the answer to the question by making bombing runs with JDAMs at high speed (Mach 0.8) and from 5000 ft AGL, with and without firing the laser before releasing the bomb.

Laser is also for rangefinding. Every laser targeting pod has a receiver for its own laser beam, even those without the LST capability (like LANTIRN). It's good practice to use that feature when targeting. Otherwise, your pod only relies on ecartometers to know the target's location as an offset of yours, which is not optimal.

At the beginning of Operation Enduring Freedom in 2001, only VF 213 (F-14Ds) and VF-102 (F-14Bs) had the 40.000 ft capacity. VF-14, VF-41 and VF-211 had to deal without it. The info is from the book F-14 Tomcat units of OEF.

I engaged 2 Foxhounds that way with AIM-54A Mk60s and had no problem: first one killed in TWS, break when TTI = 16 sec; Second one killed in BRSIT. Tacview file joined. Tacview-20201104-225823-DCS-Caucasus-AA-BVR.zip.zip

Depends on how long it flies. Not sure the active from the rail feature is intended for BVR purposes (euphemism intended).

I don't know if it is related with what we're talking about but during TGP setup, you get an MSK mention loading, and whatever I have on the rail besides the TGP's one, it's A6.

Dear Bignewy, It is not correct and this video is gonna show you that it is definitely an issue. And the laser does NOT fire through the aircraft. The IR pointer does. We, ED's customers, are also your beta testers for free. I think we deserve to be listened to a little bit better than we are.

Thanks guys. Which means that the "MASK ZONE IS CORRECT" sentence lacks a few words: "regarding DCS limits." LMAO...

Thanks. Does this have something to do with the collision model?

New test, new track. Now, we're at night. Same configuration as in my previous post. The target is clearly inside the FLIR's FoV. On the TGP page, LSR OSB is set to BTH. And guess what: the laser is masked (and the Mav is lost) but not the IR pointer, which is designating the target as you can see in the MFD as well as outside with the NVGs. "Mask zone is correct"? :huh: a-10CII-laser-mask-night.trk

Here's another track. Just so everybody understands why I'm insisting so heavily... Here's how the laser designator, spot detector, FLIR and CCD sensors are arranged in the optronics ball: So you'll understand that for the laser being masked while the target is in the FLIR's and CCD's FoV, we need some explanation, won't you? Here's what's happening when, in my track, my laser is masked (L stops blinking in the HUD & MFD, as well as M): The point I'm lasing is clearly visible, in my 2 o'clock, 6.5 nm away. Nothing is physically masking the laser designator. Here's what I see while looking outside. The target is the SPI. So my friend Icemaker and I are able to explain it in the review we're writing right now and which will be read by a few thousand people, can someone tell me if it's a bug, and if it's a feature, why the laser is masked in this configuration? And why it is not in other simulations of the same TGP by the same designers? Thank you so much in advance. a-10CII-laser-mask.trk

I don’t speak about the TGP being masked but about the laser being masked while the camera is NOT. I’ll make another track. Anyway, I won’t argue anymore on this topic with anybody not being a dev nor a CM, especially you. I feel like I’m speaking to my hat. Kind regards.

C'mon Yurgon, looks like you don't want to understand. Have a look over there. Try to lase that way with the A-10C II and come back to tell me what you found out.

The pods were LANTIRNs, a couple generations older than the Litening II, so off topic. I'm not speaking about how the aircraft or ordnance mask the field of view but the way the laser is masked in a cone far smaller than the field of view (see track). The F-16s which Litening targeting pods are seen lasing in a wide arc over there are not early access : That's a typical reason why I can't accept the way that question was (not) answered.

Another question being : why the Litening on the F-16 & F/A-18 does not have that "correct" mask zone ? You have no problem lasing an object while circling around it with those two planes. I think that topic deserves an argued answer. Just editing the title looks a bit nonchalent to me regarding what it's about.

Gamma also can be a thing.

Looks like the Litening is unable to illuminate a target farther than a few degrees on the right or left side, which makes it impossible to lase a target on the sides. Quite a problem for many kinds of GBU, missile and APKWS runs as well as for buddy-lasing. Track provided. a-10CII-laser-angle.trk

I bought it the minute after it was made available in 2011 and flew thousands hours with it. I kindly suggest you sir make sure you know before you teach :smilewink: What you can read here was the initial thing. It was then changed twice, the way you can see in my previous post.

Once upon a time, available laser codes for the A-10C were in this data range: Now, they're in that one : Could you check if the laser code you tried to input was in the second data range ?

Once upon a time, available laser codes for the A-10C were in this data range: Now, they're in that one : Could you check if the laser code you tried to input was in the second data range ?

i/e 1688 :crash:

AP bugged : track Guys, it's not any kind of misunderstanding. It is a bug. Perhaps the AP works for some of you but it does not for others. See track. AV-8B AP bug.trk

Every early access release goes to the OB first, so they can clear out the most annoying bugs before moving the module to the stable.

Most of them spend a lot more hours flying than posting, which makes relevant info sometimes hard to find on forums ;)