jaylw314

I can't remember off the top of my head, does the STRINFO page change when you cycle steerpoints with the STEERPT rocker switch? Or only when you select a new waypoint with LSK L3?

Wait a minute, are you trying to change displayed waypoints by using the STEERPT switch on AAP, the STEER switch on the UFC, or the DMS switch on the HOTAS? If so, I suspect the problem is your use of the STEERPT sub page in the WP menu. This displays the data for the steerpoint at the time you select the STEERPT subpage. Cycling the current steerpoint afterwards using any of the above methods does NOT change the data shown. You have to use the LSK's on line 3 to select a different waypoint, or go back and select the STEERPT subpage again. Likewise, if you select the WAYPT sub page, it goes to the last displayed waypoint, but does not change when you cycle steerpoints. In both sub pages, the data displayed is for the waypoint on line 3, not the steerpoint # noted on line 1

It's mentioned in the legacy Hornet's flight manual, the speedbrake significantly reduces directional stability and control (especially crosswinds and wet runways). It's not prohibited or a limitation, though, just a recommendation, so unless you break something, nobody will come after you for using it

Yeah, at the time, I recall we thought it might be some kind of transparency issue with fog/smoke, but we couldn't consistently reproduce it, and then it seemed to go away after an update. Obviously, it's still in there somewhere under certain circumstances

Ah, you're right, I had that backwards in my head And even if it was backwards, it would be at an altitude of about 90,000' MSL

TACAN gives you slant range, not ground range, hence the distance error

@Wroblowaty is correct, speedbrake is not recommended. FULL wheelbrake once wheels are firmly on the ground, you've got anti-skid so take advantage of it. You can start feeding in back stick to put more weight on the wheels and cause more drag, but two caveats: Don't start pulling back on the stick until AFTER you've started braking for obvious reasons Don't pull back on the stick far enough to catch the stick on the ejection handle

As @Yurgon said, it should be displaying the waypoint elevation, but if you need to prove that to yourself, set it to something high like 10,000' MSL, and you should see the waypoint at that altitude in the HUD or HMCS

I've not seen a control bind for speed brake fully open. Since the speed brakes take a little more than 3 seconds to fully open, if you had a keybind app like Joystick Gremlin, you could make it hold the button for you for 4 seconds. There is no speed brake status or indicator in the cockpit. You're expected to look out the window to verify they're deployed

Decimal hours is a pretty common thing to see in US aviation. Alternatively, there's always the E-6B slide rule calculator

When flying with people in Hornets and Vipers, they saw it too, so it's likely an engine issue

No idea. I'd speculate the answer is no, since no ED module has any working IFF as far as I know

This was a weird glitch that has been present since 2.7, but I've never had success getting it to show up consistently. I recall seeing it first on the Syria map, but others found it in PG and Caucasus, so it's not map specific. I can't find any of the old threads, though

The only significance of the IFF panel is that SRS can capture your transponder state and send it to someone using LotATC (both are 3rd party mods). Otherwise, it does bupkis--you can do nothing with it and other friendly aircraft will still detect you as a friendly

AFAIK if you let SRS read the DCS mic state, you cannot use the mic switch without the radio menu coming up. I think this is true for all modules. The only workarounds I've heard are: - turn on "ALWAYS allow SRS hotkeys" and turn off "allow incockpit DCS controlled PTT", then make DIFFERENT keybinds for the SRS mic's. Now your SRS mic will be independent from the in-game mic and won't set off the radio menus - use VAICOM Pro. It can modify DCS to not show the radio menus (but will break integrity check in multiplayer) Also, the HOTAS VOIP bindings are for the DCS in-game VOIP, not SRS. I'm not sure how they're used, though.

True, but how does that compare to other aircraft with high-bypass turbofans? Granted I haven't heard of the USN sending S-3's on missions to get shot at, but there are plenty of cases of airline engines with birdstrikes and damage from debris making it home ok, too My point was more that the A-10 was designed to survive hits and limp home, rather than being protected from hits. It's less like an airborne tank than it is an airborne version of the Black Knight from Monty Python's "The Holy Grail." "Okay, we'll call it a draw"

LOL, in the words of Scott Manley, "Fly Safe."

The engines are vulnerable to any kind of gun fire. Their position somewhat reduces the chances of getting hit, but once they're hit, it's just like any other turbofan getting hit. The idea that the A-10 is a flying tank is a bit of a meme. The PILOT is well protected, but the rest of the plane is (mostly) sheet aluminum. The systems are well thought-out in terms of redundancy, but that doesn't mean it shrugs off bullets and cannon shells.

LOL, I'm glad I'm not the only one

Haven't checked in a while, but I recall this being fixed almost a year ago. You need to turn on the TACAN and ILS audio on the intercom panel, they default to OFF, so you need to either push them in or pull them out (I can't recall which way).

Not to beat a dead horse, but emphasizing what SPI stands for as the "Sensor Pointer of Interest" might suffice

The way I visualize learning is like balancing something on your finger. When you start out, it's almost impossible to balance it by keeping your hand in the right position. Instead, you start by swinging your hand back and forth in large movements in a rhythm. As you improve, that back-and-forth movement gets smaller and smaller, and the rhythm gets faster, until eventually a skilled balancer looks like they're (almost) standing still in the correct position. However, in their brain, they are still going through that oscillation, just with small movements and fast pace. So I actually suggest people start out with large, maybe even exaggerated movements of the stick and throttle. As long as they're opposed by the opposite movements, it allows some station-keeping for beginners. That allows them to get started, and then the focus becomes reducing the amplitude and increasing the frequency of those movements.

True, but the smaller tanker means your visual position cues are more precise. If you move 3 feet, the S-3 looks obviously different, while the KC-135 looks pretty much the same.

The answer is to use markpoints so frequently that they no longer distract or bother you. Draw some twig & berries on the ground for practice

That's how HUD's are supposed to work. They're not just a simple screen reflected off a pane of glass. There's a series of lenses that project an image that remains focused at infinity, in the same position and the same size no matter where you move your head. Look up 'optical collimator' for details how