LorenLuke

+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.

To clarify, can I drop a waypoint after using the pan mode, and then use the pan-to-point functionality to cancel out the desync of the previous pan-mode usage? i.e. pan to the target area, drop a waypoint, pan-to-point onto it, and then drop the CAQ point/BAM zone from there?

Re: Comms menu- Sometimes certain servers disable easy comms. This means the regular comms menu will not work by default when not on the ground. Check out bindings specifically for the radio and test those. Those should always bring up the menu. Re: TADS- Just to be clear, you do not have the PNVS on? Depending on the position of certain switches, the PNVS switch from the backseat can actually take control of the TADS instead of the PNVS and render it unusable to the front-seater for the duration of its usage. It's possible that this could be a reason that I could think of a to why the TADS could be unusable from the front seat.

While in a multicrew apache, BAM Zones and CAQ points may be inaccurately placed or represented to the crew, and may jump around upon activation or switching of the BAM page. Apache_BAM_Test-CPG.trkApache BAM Test-Pilot.trk

Honestly, some civilian stuff for vehicles, infantry, and aviation assets. Pretty much every time I see a foot-mobile, it's almost assured just by existing that they're a bad guy. Having neutral plain-clothed, unarmed personnel to complicate the battlespace, plus having actual regular unarmed vehicles that aren't some sort of military vehicle or 5 ton truck (other than the bus), would be nice, too.

Not 100% sure, I think SKR becomes available when a hellfire is in a LOBL mode, and either points to where it's seeing the laser energy or, for a Longbow hellfire, the target on which it has an RF MISSILE TRACK.

did you 1) make sure the circle in Weapons -> Util -> Laser is filled in 2) make sure TADS is current sight 3) make sure the Laser Spot Search is set to 'off' 4) make sure the aircraft is armed (and Ground Override is on first, if you're on the ground) 5) make sure you have the second detent of the Right Hand Grip (RHG) properly bound ?

Can you not use the rearm menu to set the laser code for the pod?

It's based, as far as I can tell, on hot start vs cold start.

This, though I use instant trim.

I don't care if this is a setting that mission makers can turn off, but allow for some way to access the data cartridge menu while on the ground and in the jet. Servers like Contention or Grey Flag have dynamic missions that pop up and can't really be accepted outside of one's aircraft. For this reason, the ability to interact with the mission planning interface (waypoints, etc) in the future, route-planning version of the DTC workout leaving the aircraft to do so, and for subsequent quick editing, saving, and export to flight members, would be most welcome.