LorenLuke

Just to correct this fact, the Lima is not always LOAL. Target closer than, I think it's 2km (might be 2.5) are LOBL as well as trying to engage moving targets. The radar (or laser) cues the missile, but since the sensor isn't actively emitting to track the target when generating the data, it can't follow the target afterward. Therefore, to verify the target is where the aircraft believes it is, the missile begins emitting while still on the rail, searching for that radar target, and the HAD will display 'LOBL NORM'. If it cannot locate the target after a few seconds, a 'NO ACQUIRE' message is displayed in the HAD, and launch is inhibited; to reset this, you must de- and re-WAS the missile. If the missile does see what it believes to be the target, you will get a 'RF MSL TRACK' with LOBL symbology (what I call the 'Big Box'). In these cases, if you have the 'RF MSL TRACK' text and the Big Box, your missile is emitting on the rail, and it has locked the target before it launches.

Asked and answered. In LOAL, the missile's radar doesn't turn on until it's off the rail, meaning it might have an area to go to and search, but it does not, at time of launch, have a thing it's targeting.

Just to clarify, if you're talking the ability to hand off targets via FCR to flight members for Situational Awareness or targeting, that is implemented as the RFHO, and can be sent to Primary Datalink members. The FCR targets can be sent for only SA purposes via the TSD->RPT->TGT->All (if I remember the procedure correctly) to Primary Datalink members. Issue with BAM is that panning the TSD causes desync, so when you draw the zone and it activates, it doesn't go where it ought. Same thing with the CAQ point.

To be honest, I'd like to hear a peep about the terrain profiling mode they mentioned four months ago. null

My understanding is that if you perform a fix on a Bx point, it moves every single point in the nav system by a corresponding amount. If you perform a fix on an Mx point, it only moves the Mx point to the fix, and not the rest of the navigation points in the jet.

Is this still the case or is there INU functionality without using the GPS?

Are flechettes and/or MPSM planned? What about just a rocket zone interface for the loadout menu? My recollection is that they were announced initially (both in the roadmap thread and the initial early access guide), but I see no mention of them presently. Nobody officially has commented that they HAVE been removed or 'We're having a hard time getting literature on them' or anything like... Is there anything you can say about these? EDIT: Or for that matter, the smoke marker rockets (to be clear: smoke rockets used for actually marking targets for other forces, rather than just training rockets with a little 'hit indicator' smoke warhead)

F-16 only has a GPS-corrected INS, not a full Enhanced GPS-INS (EGI) navigation system. So when you make a mark point, it's an offset based on the INS present position. As you turn, especially for sharp maneuvers, the INS will drift, and with it, your markpoints (and really every waypoint, coordinate, and such in the jet) will drift as well, moving them off-target.

I believe it's not unheard of to hit on a PGM 3, and I think that's the lowest threshold which a HARM launch is considered 'feasible' to hit the target, but obviously if you can a higher precision value, go with that, and PGM 2 will be more on the money than PGM 3, but my recollection is that PGM 3 represents sort of the 'maximum sized basket' in which you could sling the missile and have no expectation to just straight up miss.

PGM 5 is the least accurate precision factor, PGM 1 is the most accurate.

Just as a work around, could you set your home pit ejection seat control to have functionality similar to a 'turbo' button, which just presses is input rapidly when actuated, instead of holding it?

That may by my confusion. I didn't realise this had changed, I don't often punch in target points manually, and just remember this being the case when I had, before. Good to know!

Just a quick addendum to note that if one saves targets via a mix of methods (both keypad entry and via shkval), any targets saved using the shkval and laser rangefinder will have their altitudes shifted as well, so if you go to engage those targets, be sure that your altitude is set to the same value when you stored the targets before caging the sensor to engage.

Make sure the binding for the front seat actually uses the WAS switch on the TEDAC and not on the cyclic grip. COOP rockets will not select if the gunner uses the cyclic grip. I'm no 64 pilot, but I've been lead to believe this is also the case on the real aircraft.

I believe the monocle is calibrated to the right eye, so you need to boresight with the right eye for it to work.

User error. I can tell immediately from the IHADSS that your acquisition source is set to a Cursor Acquisition/Terrain Point (TRN). Whenever you CAQ on the map, where you drop that point becomes the Acquisition Source (ACQ). The reason the dotted cross is pointing to an open field is because the dotted cross points out your Acquisition Source, and your Acquisition Source is a TRN point in an open field. You need to set your Acquisition Source back to TADS to see where George is pointing the TADS in your helmet (I recommend through the weapons page).

Exactly what the title says: Add an area search mode to George's current 5 area search modes, where he engages the Laser Spot Tracker to 'Automatic' for the duration of the search. Stopping the scan can be commanded with any other search, or repeating the area search, or when George finds a valid laser point, and all with appropriate dialogue to match.

Check out the DEST page for usage with Offset Aimpoints (OAP). If you're familiar with Chuck's guide, check section 7.1 (Pg 681, I think).

1 doesn't apply here, as if you see the small squares in the Arm/Safe box, and the lack of other wrap options in the bottom row, it indicates the weapon is WAS'd. That said, 2 appears to be in play. You'll definitely get a MSL NOT RDY indication if you have no missiles left of the selected type to shoot, and it appears those are all laser missiles. It's L for Longbow Hellfires, not L for Laser!

They mentioned the planned addition of the Terrain Profiling Mode for the radar in the newsletter, targeted for summer of this year (which I imagine is next update). According to the roadmap, the RFI is one of the items very closely following after that.

+1

One thing I've imagined as sorely lacking, both in technical versions as well as a static emplacement is any sort of recoilless rifle. Having some sort of serious AT capability bolted to a technical while still having an insurgent unit look like an insurgent unit (nevermind actual nations using something like a static SPG-9), would fill a niche that I believe to be lacking in our current unit list.

Barring the flight changes, it's got about all its currently listed early-access features. We've yet to receive the RFI (and the cued search function with it), the Terrain Profiling Mode for the FCR, and (initially but no longer indicated), red/orange marking rockets; Multi-Purpose Submunition (MPSM) rockets; and flechette rockets (and hopes of a more granular, thorough implementation of selectable rocket zones for the pods).

Honestly, I always thought that they should (to my recollection, they aren't but I could be wrong,) be categorised such that the top target should have the least angular difference between it and your george-up direction, and each subsequent one is just greater and greater angle differences from that point. Even if it's not, having some way to set that up as a menu option would be nice.