Puma

The combat pedals are what I have so curious to hear some feedback on them. I certainly agree they arent premium but ive never considered them part of the problem.

Great response, thanks so much

Coordinated or Centerline? Finally had a chance to fly again tonight. First discovery was that I had setup highly non-linear rudder curves to make fine steering easier, but with one engine out and using the more extreme edges of the rudder's range it was highly reactive which complicated things. But, question #1: Is it normal to experience significant roll when applying rudder in single-engine flight? In AF I recall rudder keeping the Falcon relatively level, and mostly yawing. In a warthog I do get expected yaw, but I find I need to fight a roll with opposite stick or trim. Feels almost like it's balancing on a point and with significant rudder yaw it's almost falling off balance. Question #2: It isn't wind, but rather the yaw caused by the single engine that is my challenge. What is the priority during single engine flight? If I attempt to maintain coordinated flight according to the slip-ball, my TVV drifts way off the hud, worse at slow speeds. But if I use the rudder to keep the TVV on the centerline, I am in way uncoordinated flight. I've attached pics of the two options. And lastly my advice from practice: Flying with trim is great under normal circumstances, but in these emergency circumstances, less trim, more "just fly" cause things change fast and chasing those effects with trim is not reactive enough.

Attachemtn attempt #2 Attachment's didn't go. Trying again. Tacview-20150705-213652-DCS.txt.zip

Some tracks to illustrate my struggles Maybe these will help. First one was single engine. Tried to abort and totally lost control. Second one was dual engine sanity check and even that was sloppy (but maybe would have worked had wingy not flown into me!).

Hey guys. I have a question about the effect of wind in game. I'm an A-10C newb. I had years of flying in AF, but years ago. I have a custom put with a warthog and saitek pedals, so there are some oddities in my configuration but generally nothing crazy. I find the effect of wind on landings challenging to say the least. I often find my TVV drifting out of the view of the HUD. Keeping 'er straight during takeoffs is possible but requires a lot of coordination. I often wondered to myself why mission planners put so much wind into training missing, figuring to myself that I guess it's fair to test us during training. I am currently working on EFATO mission from maple flag and find it damn near unflyable with one engine. I'm using so much rudder to keep straight flight coordinated, that as my speed or configuration changes the effect on pitch is dramatic, I end up oscillating chasing various parameters and honestly half the time right now end up out of control and flipping on to the deck. I'm realize how much this sounds like I am just a crappy pilot. I MAY be, but with my experience and equipment I am really struggling to believe this is supposed to be THIS hard. So I cross referenced the 5 m/s wind in the mission briefing with wind references online and found that is "light gusts". WTF!? So here I am. So has anybody heard of any configuration options or hardware which has increased the effect of wind? Does any of this sound familiar to anyone coming from AF? Help wanted, this is getting really embarrassing and frustrating to be having so much trouble with basic stuff when there is so much fun stuff coming up (I hope!).

Late evening out of nellis into night over vegas

"Mic button in" for the win!!! That's amazing. Thanks for revealing that. I couldn't be happier (and thats a little sad :|)

I have a warthog. The three standard mic positions are used, but up is available so i used it to simulate a keystroke for my voice activation software. Now i need a button for ptt in teamspeak. Id really love to have it on the mic switch somehow. Any ideas? I tried to see if i could use target to use a mod button to have a different keystroke but didnt see a way to do that. Any ideas or best practices?

I had a lot more luck today. My theory was that i took far too long to request startup since i was testing stuff, and (not kidding), atc went home. When i request on a more realistic schedule, i got cleared for startup, txi and takeoff. Sound possible?

Dies this mean you need to slect the correponding mode of the dial on the intercom panel? I jnew you needed to be on int for ground crew, but do you need to match fm or am for tower comms?

Yah, id buy that for taxi and takeoff, but i dont get one for engine startup requests either, and i cant possibly be in the wring position for that yet:) Also, for dme i had luck with ils and tcn buttons both depressed on the nmsp. This gave easy readouts to check against descent charts. Is there any reason not to use the nmsp with both enabled?

Im attempting test flights to validate my pit configuration. Usung the free flight ramp start mission. Two issues: 1) rare or no response from atc. Radios on and tuned. Often i get no response, but sometimes minutes after request i do hear a reply. Seems possibly position related. Is this a mission bug? 2). Ils approaches. If i enable ils i hear the tone and get localiazer bars, but dme readout on hsi goes to zero. I seem to need tacan and ils mode on nmsp to get dme and localizer bars. Is this correct? Manual said they were mutually exclusive modes?! Thanks everyone!

Multi monitor is a performance killer I spent a lot of time tweaking settings and multi monitor configuration. My conclusion was that settings can make small differences, but multi-monitor makes huge differences. In the end i actually ended up exporting my gauges onto my primary flight display, a row along the bottom. On the 39" monitor it still leaves enough world view. Its a compromise to be sure, but i was happy to pay that price in exchange for 4k flying.

I'm out.

Good recomendation. I watch one every night! I like recon Stewart's videos too. Not really training, but he's pretty verbal.

I had to familiarize myself with the systems because I was building a pit before I really know how the aircraft worked. Now it works on paper, and I realized how out of to practice I am!! I flew falcon AF a LOT with a squadron so some aspects will come back quickly... I hope!

Hey guys. Hoping to get some advice on good starter missions. I've finished my pit. Read the manual like three times. Happy enough with basic flight operations, and am ready to test my skills. I want some simple missions that will allow me to refine my flight ops, but add a little purpose to my flights cause flying in circles is getting old! Campaign?? Stock missions? What about those training. Missions from red flag?

Emergency trim I wired up my emergency panel via DCS-BIOS. Almost flawless. Thanks for the "reverse" setting as that saved me on a few this time! The emergency trim hat is weird. Visually it works perfectly. I.E. When I hold a direction, it stays in that direction in game. However, it doesn't actually trim the stick. Clicking in the pit does though, so I am convinced this is a DCS-BIOS issue. My 4 way didn't have a center-position wiring, so I set center as the default pin. I.E. [code} const byte efcpEmerTrimPins[5] = {-1, 2, 1, 3, 0}; DcsBios::SwitchMultiPos efcpEmerTrim("EFCP_EMER_TRIM", efcpEmerTrimPins, 5); [/code]. In the DCS-BIOS serial stream. I see posX when I push a direction, and pos0 when I release. What am I missing? Is DCS-BIOS supposed to support push&hold interfaces like this??

A solution for even noiser Potentiometers Good start Dirk. I found my pots were much noiser than that. I cut my resolution down by a factor of 20 and still found some pot settings generating a constant stream. I added a second averaging filter to approximate a low-pass, and for my setup, I'm in the money. Here goes: Potentiometer::Potentiometer(char* msg, char pin) { msg_ = msg; pin_ = pin; pinMode(pin_, INPUT); lastState_ = analogRead(pin_);//map(, 0, 1023, 0, 65535); memset( aLastStates, 0, HISTORY_DEPTH * sizeof(unsigned int) ); } void Potentiometer::pollInput() { unsigned int state = analogRead(pin_); if (abs(state - lastState_)<=3) return; // Completely ignore very small changes // Calculate the running average of the most recent changes unsigned int uSum = 0; for( int i = HISTORY_DEPTH-1 ; i > 0; i-- ) { aLastStates[i] = aLastStates[i-1]; uSum += aLastStates[i]; } aLastStates[0] = state; uSum += state; unsigned int uAverage = uSum / HISTORY_DEPTH; // Report change IFF the running average is significant enough (/20 => 51 steps, which is good enough for DCS!) if (abs(uAverage - lastState_)>20) { char buf[6]; utoa(map(uAverage, 0, 1023, 0, 65535), buf, 10); //utoa(state, buf, 10); sendDcsBiosMessage(msg_, buf); lastState_ = uAverage; } }

I don't understand this WildBill? Were you trying to make the question sound stupid or yourself? Its a valid question with a valid answer. Even if it wasn't, what's your point?

yup, she likes you.

You made it so clear you were not interested in a run, so I made my own.

Maybe I should have said " I want to be the kind of pilot who flies by charts"

I love and prefer charts... But to be honest there is usually enough to do that I don't get to reference them as often as id like. I love "cheats" like the three bars on the A10's aoa which show ideal climb, loiter and landing angles. Quick way to stay on spec without doing math.