LorenLuke

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.

The weapon is selected, but it's not 'Actioned'. You cannot select a weapon this way, and must use the 'Weapon Action Switch'. You will know that the weapon is actioned (not just selected) if the ARM/SAFE box in the weapon page has several smaller boxes inside: null

Firstly: while I don't think it's the case that Boeing would want this, I ultimately don't know what is actually the case in real life. That said, the point of the flight model is to make it realistic, not necessarily what's 'easier'. If the more difficult, regressive, twitchier yaw channel is more true to life in the real aircraft than what we had before, that's the one that should be implemented in the simulator. I very much remember when the LMC ground stabilized when you turned it on and now it doesn't; it's not as easy to use anymore, but it is more realistic. This is how it should be. Now, yes, everyone (including the experts!) agree that the flight model needs improvement, but just because 'They think it needs to be better too' doesn't necessarily mean the areas they think it needs improvement in (e.g., crabbing) are the same areas you do (unstable yaw channel). My point is, I'm sure that they're trying to make the flight model as real to life as they can regardless of how 'easy' that ends up being. Because this game is ultimately meant to be a simulator as close as they can reasonably get, not some arcade airquake with simplified controls.

The back seat (pilot) cannot use or control the TADS. Only the front seat can. The switch for TADS in the back seat is there so that the helicopter manufacturer can use the same part for both cockpits, but the pilot's TADS switch is not connected to anything.

I know for firing Rockets, it's something like over 100-110kph. I imagine it's not too different for the X-25.

If you turn on the 'LMC' switch under the CPG's display, it'll keep it focused on a point a fixed distance away (at the last laser range).

What am I, chopped liver? Glad to find you got it working though, @GeoS72

It may be the logic limitations of the game's code itself that the AT-11 Sniper is a cannon-launched guided projectile, and not a 'guided missile' being shot, therefore not triggering the MWS.

To be fair, it did see action in the second Chechen War.

I mean clicky cockpit with systems. And while I am just as willing as the next guy to fart on ED's F-35 modeling methodology, I also believe that anything that is not quite an ideal simulation, but can or does move us towards a higher fidelity of simulation and away from any arcade-y elements that we have currently, right this moment (Combined Arms looking at you), is ultimately a win as delivering that kind of product means we end up closer to that simulation fidelity that we all want.

Even if it's not clicky, though I'd love a Full fidelity frogfoot (FF FF?), I do hope that the extra effort has them update the controls beyond the FC3 standards, just to increase the fidelity of the module a bit, e.g. wheel brake axes.

I tried the track, but couldn't seem to get it to work (I wasn't able to assume control of the aircraft). Just as a quick offhand, did you try turning off the hellfires before switching the laser codes? I believe the have to be in 'Standby' for you to change the laser codes, beyond just switching primary/alternate.

Any further updates on this?

Wait, a third party is doing the F-117? Where was this said?

I'm honestly surprised that this was the decision to go with, or that the amount of data purported to be available would be much less than some of the older, or even retired systems. I'm almost certain that something like an F-117A would have far more documentation given its older age, retired status, compromised make from being shot down, and far less likely to receive raised eyebrows and backlash that the F-35A has, while still being one of the more prolific stealth fighters in existence, an absolutely perfect candidate to go with the development of the Iraq map, and something that I'm sure would sell equally well.

In the Kiowa manual, the following procedure is provided for changing the user's 'Callsign ID'. nullWhile others can receive spot reports and the like from this will use this updated name. However, messages cannot be sent (that I know of) to this new callsign, as the menu retains the old callsign (I cannot find a way to change it), If the player changes their callsign back to their original, they can receive messages in this way once more, but that seems to defeat the purpose of being able to change your callsign at all. Attached below are two tracks from two separate kiowas in the same multiplayer mission demonstrating this, Anvil 1-1 and Anvil 2-1. Could someone ensure the menu updates with these changes, or if this is not a bug, otherwise address either how to change the available recipients in the datalink menu so that they can be messaged? Anvil11.trk Anvil21.trk

I would imagine from how the track system functions, and the fact they have diagnostic tools that let them take tracks apart in detail, that ED can see what buttons you're inputting, regardless of if they're tied to any controls or not, as well as what buttons you're pressing go to. Worst case, you put a track and they say 'sorry, we can't help.'

Still there, but to me (though I don't fly it a whole lot) it feels like it's slightly less than it had been before.