LorenLuke

Any additional information on this, including whether or not it's even planned, anymore?

This bug still persists after the C-130 update. (2.9.22)

I can confirm that this is an issue I experienced, but have only experienced it as a CP/G of a multicrew AH-64. I have added two .TRK files, including my and the pilot's perspective. I can confirm that this occurs with axis bound controls. HOWEVER, after initially tapping the control while in ATM of the radar as the CPG, the radar elevation would constantly descend. If the sight was not selected, it would cease descending in elevation angle. In the track, I switch to TADS several times and you can see that it doesn't immediately command movement downward. Additionally, you can see that the downward movement resumes the moment FCR is selected once more. Within the track, I fire a hellfire twice. The first time, I fire the hellfire after ensuring that my axis for the MAN TRK Y Axis is unbound. You can see after this point the radar elevation continues to lower when it's selected as sight again. I confirm the control is unbound, and fire another hellfire. After this point, I confirm again the control is indeed unbound, and then click the 'Up' elevation arrow on the radar. The radar slews up a bit, but continues to descend all on its own. While it may be true @BIGNEWY that you cannot reproduce this bug using only keyboard commands, I would hope that you don't simply declare 'There's no issue' just because it doesn't happen to affect your particular style of play personally, and will see with a more rigorous testing methodology that this bug does still exist, and does still affect those of us that use axes to control the AH-64 A2A radar. A2A-Bug-CPG.trkA2A-Bug-Pilot.trk

If the I-beam is aligned with the cross in the center of your monocle, you're good to shoot. If it's not, turn in the direction of the I. If you're using your helmet as a sight, make sure that cross is also over your target when you shoot.

While this can all be true, this doesn't change that there's no current way to command George to use the FCR.

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.