jaylw314

My understanding with flaps in the DN position, the MAXIMUM it will lift with aerodynamic pressure is to 15 degrees, and in the MVR setting, the MAXIMUM it will lift is to 0 degrees.

referring to TO 1A-10C-1, when at speed and flaps are in MVR, and FER is engaged, the flaps are driven all the way up to 0 degrees by aerodynamic pressure. When flaps are in DN and FER is engaged, flaps are only driven up to 15 degrees by aerodynamic pressure. It sort of makes sense if you look at the flaps, which are fowler flaps rather than simple flaps. There is a hinge that angles them down, but they also slide on a track AFT. In general, flaps cause more drag than lift as they're extended further. Once they've they're fully down and slid aft, they cause so much drag they're pretty tough for the airstream to push them forwards. In the MVR setting, they create more lift than drag and they have much less distance to travel forwards. You should realize that with the flaps DN and FER engaged, the flaps essentially remain extended (you're only getting them up to 15 degrees). That means technically your maximum airspeed is limited to 200 KIAS (flaps extended). I don't think your crew chief will yell at you if people were shooting at you, though

Given the issue with the FER keybind you posted elsewhere, it may be worthwhile to double-check or even clear out your keybinds? Something's happening that shouldn't be, and if there is one keybind issue, there could certainly be another elsewhere.

Not that I'm aware of. By "read-only" I just meant the waypoints can't be modified in the STRINFO and WPINFO pages.

That was kind of the point of the very next sentence that you left out-- "However, the content is pretty useful and good curriculum for what skills to learn and in what order."

The STRINFO page is a read-only info page selected by turning the PAGE knob on the AAP to STEER (or pressing FUNC then 0 on the UFC). It's not part of the WAYPT subpage In the WP menu, the WAYPOINT OSB brings up the WAYPT subpage. You can change and modify any waypoint here. If you happen to select the waypoint that is the current steerpoint, you'll see SP to the right of the waypoint identifier. If you go away from this page and come back to it via WP menu -> WAYPOINT OSB, it'll bring up the last waypoint you had selected. If you press the STEERPOINT OSB from the WP menu, it will send you to the WAYPT subpage, but it will automatically select the current steerpoint instead of the last selected waypoint. As an example, if waypoint 0 is my current steerpoint, I can go to the WP MENU -> WAYPOINT OSB and select waypoint 3 to modify it. However, waypoint 0 remains the current steerpoint. If I go elsewhere in the CDU and return to via WP MENU -> WAYPOINT OSB, waypoint 3 will still be selected even though waypoint 0 is still the steerpoint. If, however, I press WP MENU -> STEERPOINT, it will bring up the WAYPT subpage with waypoint 0 selected instead.

I HATE the Maple Flag A-10C training campaigns, but the first two have been updated for the A-10C II. They're terrible for the learner because the only way to progress through the campaigns is if you already know the material and have the proper skills, which is pretty demoralizing. However, the content is pretty useful and good curriculum for what skills to learn and in what order. Search online for the "TO-1A-10C-1". It's the USAF A-10C flight manual and has a LOT of the technical details if you're interested in the "why" behind the "how". Since it's a military document, it's not kosher to post or share even though it's declassified, but you can find copies of it online if you look carefully enough.

On a stabilized gun run, they're only experiencing 1G On the other hand, if they're maneuvering and pulling G's, a lot of stuff in the HUD ends up near the bottom!

In VR, I instinctively lean forwards during gun runs, and then the whole HUD becomes visible. I suspect they do that in real life, too, but I've never seen cockpit footage of the pilot during an attack run...

Hey, uh, I'm pretty sure that's just a shot from DCS run through some blurring and video filters

You're thinking of Goldmember from the Austin Powers movie Flickers tap to communicate as well as feeding or making nests. You can hear another flicker in the background tapping in response

FWIW, here are some screenshots from VR. I reset my VR position to the default position immediately before hand. This is the right eye: Here's the left eye: And finally, I moved my right eye to the centerline: As you can see, the top of the HUD is significantly below the horizon and the TVV and boresight circle are impossible to see without leaning down and/or forwards (although not quite as low as I recalled earlier without the benefit of screenshots). Here's the same starting view in 2D mode: To me, it's pretty darned close to identical, maybe the viewpoint is a tiny bit lower, but it's definitely not the case that the VR default view was made perfect at the expense of the 2D default view. Whatever change was made was made to both equally.

Just to be clear, I was pointing out that the new default position in VR is pretty close to what you're describing. It's not better for or unique to VR. You can't see the whole HUD display without moving your head down, and on the ground you can't even see your TVV. It's not the case the view was changed to improve VR. It's a change that makes this an issue for everyone. I thought I recall reading somewhere that this was done because it was a more realistic position, but I can't find that reference now.

The default position did seem to get significantly higher in VR. The HUD field of view seems to be from the nose to just above the altitude/airspeed text in the HUD. The boresight circle is only visible if I lower my head and lean forwards, and the horizon is at least 5 degrees above the top edge of the HUD. I used to lower my seat because it seemed so wrong, but in retrospect, the masking of the HMCS makes more sense. With a lower position, the HMCS would display over the upper part of the HUD, but with the default position, the masking is correct. So I suspect this was actually their intention--no idea if this is the correct position IRL.

The iron oxide is just the oxidizer in thermite, or essentially a source of oxygen. Aluminum will burn in oxygen, but it's just so danged hard to ignite. Magnesium is easier to ignite, but it's still no slouch. Ironically, racing wheel rims are sometimes made of magnesium alloy, and rims with failed tires are probably one of the easiest ways to get it to ignite!

That's garrulous and uncalled for. The calculated wind is on the LASTE wind page in the upper right (also in the STRINFO page). If you enter data in the LASTE wind page, it overrides the calculated value. I don't know whether the value in DCS is actually calculated from position and air data or just copied from the mission settings, though there is not a practical difference in DCS

Yes, well, it only ignites at temperatures where you're unlikely to be alive enough to be worried about it. Sparks from signal wires are not going to ignite it. I'd also point out that aluminum is the main ingredient in thermite, but we still make planes out of it

Most controls are made of either aluminum or magnesium alloys. Aluminum is light and pretty strong, but magnesium is even lighter and stronger. Not sure about the A-10 IRL, but magnesium does seem to be preferred in aircraft controls for whatever reason--maybe tradition, maybe to reduce the inertia of the controls, maybe because magnesium is a little more corrosion resistant to sweaty hands?

The "on board computer" (I assume you're referring to the EGI) and even a student pilot would have the ability to figure out the wind strength and direction by comparing the aircraft's ground speed (using, say a GPS or landmarks) against the measured direction and speed (using the airspeed indicator and compass). That's precisely how you figure out what the wind is doing. To imply that information is not available to the aircraft is incorrect. Whether the RL aircraft or DCS aircraft do that, I can't confirm, but my 90's era aviation GPS does.

IIRC, one advantage of the WCMD is the ability to drop from high altitude (10,000' and up). Without INS, CCRP would be too inaccurate and CCIP would be impossible or impractical. Also consider the ability to drop it through clouds. Probably not politically correct, but still an option...

The behavior in-game is that of TV image tracking problems, not a gimbal limit. POINT and AREA modes supposedly track the target, not by the targets known position, but by moving the camera to track an area on the TV image by contrast and shape. Video tracking modes only seem to work at certain angles--you can see in other areas when they turn into P-INR and A-INR, the video tracking is presumably off temporarily and turned back on when the camera is in a better angle. The area in question is about 10 degrees wide about 20 degrees down from the boresight cross. If the camera passes through there, the video tracking algorithms fail for whatever reason. Unlike to the side and rear, the TGP does not revert to INR mode, again, for whatever reason. Whether this happens in real life, I have never heard any substantial information to confirm it does or does not. If it DOES, I would suspect it's a failure in the video tracking algorithm near the camera's longitudinal axis. The algorithm probably tracks the image with simple up/down/left/right commands, but as you get closer to that axis, the left/right commands become less and less accurate, since they tend to spin the camera more than translate left and right. At some point, the algorithm commands full scale left/right commands and can't keep up, and it gives up in petulance. This could be avoided by reverting to automatically reverting to INR mode like in other areas, of course. Of course, that's all speculation on my part, but I'm still hoping we'll someday hear someone with RL experience corroborate any of this

The CBU 97 has the advantage of being able to pair/ripple drop them for maximum CPU-melting chaos

Scorpion also has pretty colors

I suspect the problem is inherent to the 2.7 clouds, so without killing the clouds there's not an easy workaround

Wait, how do you take control from a track file???