OPPSpectre

I am also incredibly interested in your Voice Recognition software that you seem to be using. Seems like it would be an amazing part of immersion, would you mind sharing?

I think the only thing you're missing are the engines Deadman.:joystick:

There are a couple of things that you can do, you can turn on your Night Vision Goggles by using RShift + H, the Emergency Flood Lights switch located just above the Battery Power Switch on the right side of the cockpit, or you can just hit L (I believe) to turn on preset lighting conditions, I might be thinking of the FC2 shortcut, however.

I also had to pretty much learn all of these things myself, mostly from trial and error. You'll learn that you can't just head straight in to the engagement zone; you'll need to orbit wide around the SAM envelope (usually ~12 miles or so). When you first approach the area, try to keep your altitude above 20,000 to make sure you're clear of any SAMs (SA-19 I think), from there, use your TGP to find and execute any SAM. From there, start looking for ZSU or Shilka. Once you've got those you can start engaging everything else from ~6,000ft (Most vehicles will engage you with machine gun fire below that). To evade SAM launches, first identify (using your Countermeasures panels) what direction the missile is; instantly begin to dump either Chaff or Flare (or both) and try to get the incoming missile to either your 3 or 9 o'clock. If you can SEE the missile, and you're quick enough, wait until it is about 7-8 seconds before impact and turn hard into the missile. I'm sure others on here can help you out and give you much better information, but that's what I'll contribute. Hope it's right and makes sense.

DCS: A10-C was the very FIRST flying sim that I've ever played (ACE Combat really doesn't count as anything) so naturally, I had a bit of trouble at the beginning. The very first time I started the game I had a CTD, so I tried again and got the same thing. A quick, 3 minute visit to the forums told me that the necessary steps to take. It took me 1 minute to do these steps and I was able to play. My first mission was instant action, and the only thing I did was mess around and fly, mashing keys on the keyboard and trying to figure out what each key did. For about the first week of having the game, I did nothing but repeat the tutorial missions over and over until I could remember the keyboard commands. After that, I started doing more Mission Generator missions. Yeah, I got shot down every time and my flights lasted about 5 minutes, but those 5 minutes were pure "Awwwwwwwwwwwww yeah!". Eventually, I even managed to discover WHOT and BHOT, and found my first target. Overjoyed. Then, another week goes by and I get my first kill. Estatic. Then I got my HOTAS Warthog and it was all uphill from there. Basically, I started out as a complete newbie to any flight sim (and certainly nothing as complex as DCS A10C) and after a few minutes on the forum search engine, I knew whatever I needed to know. If someone is looking for a nice flight sim that they can take an evening flight with, have a simple "takeoff-fly for 12 hours-land" plan, then go back to something like FSX. If you're expecting a game like DCS A10C, with all of its complex AI and high fidelity cockpit controls, to not have errors and a bumpy start, then you're crazy. It's not just a flight sim, it's a modern military combat simulator, which means you'll probably need to do some reading and head scratching. /rant

I never started any Campaign missions or pre-made missions. I started off playing Mission Generator missions and then finally went to multiplayer. I was kind of nervous about playing online, but I found Iron Angels Server is pretty "noob-friendly" and a nice place to get used to flying with others before you move on to something more complex like VFS.

APU power was off. Here's how it went from what I can remember. Pulled in to spot>Requested Ground Power>Ground Power On>Left Engine Off>Right Engine Off>Rearm&Refuel>Wait for the bullet holes to disappear>APU Start>APU Gen>Requested Start Up>Left Engine Idle>Right Engine Idle>Disconnect Ground Power>Re-load Data. Everything went smooth for that. On an unrelated note, after I got repaired and back in the air, I experienced complete Right and Left hydraulic failures and ended up having to ditch. Don't know if that was just a random failure or if it was related to repairing.

I can totally confirm that this does in fact work. I landed at Batumi after expending munitions and taking some damage. Pulled in to a serviceable spot and asked ground crew for ground power. After they turned it on, I simply shut the engines down by moving the throttle to OFF. All of my systems stayed engaged, the only caution lights I had were my engines of course. Asked for refuel and rearm and waited for about 3 minutes and I suddenly had a repaired A-10C at my disposal. Everything still running. All I did was start engines back up, re-load data and go. Nice find RavenOne

And here I thought trying to find a SAM launcher in some trees was frusterating.:cry:

Out of sheer newbish-ness, I believe I ended up hitting the CNCMP OSB on the TAD screen instead of the WILCO simply because it was red and I was suffering from the "Don't push the red button" syndrome. Now I don't see WILCO or any other information. How can I get back to having the red triangle on the TAD and WILCO OSB or do I need to abort and ask for another tasking?