flyingfed

I'd love to see this happen too. Maybe it's a "feature" to get you to go with TrackIR or VR? If I wasn't used to what's behind them, I'd sure have trouble using the right side stuff, especially the ILS receiver. :book:

Noted back on June 6 here https://forums.eagle.ru/showthread.php?t=242492

Maybe it's an application of a reportedly old USAF saying about the three most useless things to a fighter pilot: 1. Runway behind you 2. Altitude above you 3. A tenth of a second ago

No bug. Any reciprocating aircraft engine will run without external electrical power, unlike your car for example. Aircraft engines have magnetos that are independent of the electrical system (if there is one) and of course dual mags for redundancy. For anyone who's had alternator/generator failure in a car, you know the headlights (seems it's always at night :smilewink:) get dimmer and dimmer and then finally the engine dies. In a car, the electrical system provides power to the ignition system, so no electricity = no engine.

I've been to the FHCAM Luftwaffe Fly Day a couple of times now (fortunately live about an hour away from Paine Field/KPAE) and it's always a treat to see and hear the collection in the air. Their 190A5 has been a reliable performer every time, so expect to experience it this August. Here's the announcement: https://flyingheritage.org/Visit/Events/Luftwaffe-Fly-Day.aspx

Exactly. Most vids of actual A-10 landings, including a couple of command sponsored USAF Tactical Demo Teams at airshows, show this.

Since there doesn't seem to be an indication short of looking over your shoulder to eyeball them, how do you get to 40% open on approach as suggested in numerous places? With the TM Warthog HOTAS, I find it happens to take 10 or sometimes 9 quick "blips" on the switch to go from closed to full open, so I've been doing 4 to approximate 40%. Any better ideas out there? :helpsmilie:

As a closeout, I decided to do an R&R, since the repair option disappeared from my Windows Start menu. The comm menus now behave as expected. A long day with a slow (1 mbs) connection but a couple of other little niggles have disappeared too, so worth the time. Thanks all for the help.

My experience exactly, Radial9. I asked about this in another thread and that was the consensus there.

I agree, and for me, the A-10C is a great place to start in DCS. I feel appropriately challenged with what's available at the moment, and yet pleasantly looking forward to the update. Great place to be. Thanks too for the tip on YouTube. I never thought to look there, but I will tomorrow night instead of flying. For tonight, I want to see if one of the suggestions resolves the comm menu issue. Whether it does or not, the other tips, like the trigger were the breakthroughs I needed to complete the lesson (and any future ones where the space bar isn't read).

For all that contributed, thank you! Being new to the platform, I had a fair idea of the community from the research I did before jumping in. Now that I needed a bit of support, I'm frankly overwhelmed with the positive attitudes and how many of you jumped in to help. I'm a moderator in another sim community where at times and with certain products I see a lot of negativity. Definitely not the case here.

Thanks for that. I'll give 113.00 a try later today. Assuming it's not a typo from 131.000, I'm surprised that 113.00 is usable as a comm freq, since it's down in the nav band (108.00 to 117.95).

Thanks for the suggestions and background.:thumbup: I've triple checked the assignments and the "HOTAS Mic Switch Forward" is associated with the corresponding movement by the TM HOTAS switch. As noted, the switch in the cockpit moves correctly when I do the button press on the hardware. No mods or other add-ons. Only the ED A-10C and the current (not Beta) DCS World. Thanks for the clarification/correction. I've also have printouts of all the relevant comm and nav freqs, but thanks for the reminder on the map. I'll add it to my growing knowledge and use of the game controls. Sounds like a reasonable explanation. Thanks for noting the correct F key to use. Guess I'd better get used to all of them. The TM HOTAS really spoils you by keeping you off the keyboard, but keys do have their place in the sim context. I can see I need to figure out how to integrate the F keys in a wider context. It doesn't help that the lessons use non-standard keys, such as the trigger to move to the next part in this lesson but not others. As a newby, one needs to remember that this is an evolving platform and as the A-10C was a very early module, it hasn't always kept pace. I can see that in the comments in other parts of the forum, and have no problem living with the limitation. So many of the other elements make it easy to overlook a few warts.

Thanks for the suggestion, GTFreeFlyer. Waiting didn't have any effect on getting the comm dialog to come up. I'm sure it's not just hiding, as when you're supposed to be done with it according to the IP, and you're instructed to hit the escape key that should exit the dialog, instead it takes me to the flight options menu (the one where you exit the lesson among other things. So the comm dialog just isn't coming up.

Great tip. I'd have never thought of it. Now that's out of the way, I can at least fly the lesson, although my comm still doesn't work. Any thoughts on a connection between no VHF freq shown on the CDU page, perhaps indicating that the sim doesn't recognize 131.000 as the correct freq?