rud

I find using a linear profile helps me out a lot. I just use a straight horizontal line at a suitable sensitivity for each axis. In the A10 I find I want about one and a half times sensitivity for pitch compared to yaw. Making your profile as insensitive as possible helps too. I have to crane my neck a bit to watch my engines start (or check that my tail is still there...) but it sure helps when my head is looking ahead. There's always some noise with TrackIR, and if you're like me there's some noise built into your head movements too, the less things get amplified the easier it is to click switches. Repositioning TrackIR's camera can sometimes help a lot. At a LAN recently, a buddy was really fighting with his to keep his view steady, just bumping the camera down about 10 degrees made it much more precise. One last thought, I personally can't stand precision mode! It just seems wonky to me but to each his own. I do however love pause, and have that mapped to my joystick instead. It helps immensely! I have it set in my X-52's profiling software, but I'm pretty sure you can just click the box for the keyboard button in the TrackIR software and press a button on the joystick instead.

I've been doing this for a couple versions now, as soon as I'm ready to start left hand engine I bump the left throttle then immediately bump the right throttle. check out the picture from DCSWiki: http://www.dcswiki.com/index.php?title=File:A10EngineStartDiagram.png According to the schematic there is an electrical interlock in the air system that prevents both engines from being started at the same time. So it really does seem like when you bump both throttles the second engine waits in line for bleed air until the first one no longer requires it.

I wish we could mod the INS align time, that's all it would take to dial startups from about 6 minutes down closer to Ka-50 start times. In MP especially, I think having an option for shorter align times would be a real hit.

the diamonds, crosses, and other symbols represent what your sensor of interest (SOI) is. For instance, DMS up zooms in the map if the TAD is SOI, or it zooms in the targeting pod if your TGP is the SOI, or switches to the next steer point if the HUD is the SOI, etc. It really confused me at first how the same HOTAS button has multiple functions like this and it only gets more messy when you consider long/short key presses. It all becomes rather intuitive eventually, the real world designers did a good job even if it seems a bit chaotic at first!

I'm actually finding the whole CDU steps unnecessary if you have a TGP. Just read off the coordinates, or listen to your buddies, and slew the TGP manually to those numbers. It's really pretty easy once you get the knack of it and almost always faster than messing with the CDU. once SPI broadcast is fixed in multiplayer it's gonna be a whole lot easier!

The air speed indicator has several failure modes depending on which part of the of the pitot-static system is blocked (http://dcswiki.com/index.php?title=Airspeed_indicator_%28A-10%29) Icing can occur in the pitot or static tubes (or both). For the OP here, it sounds like the pitot tube is the culprit. When this happens the air speed indicator functions as a crude altimeter, diving makes the needle drop and gaining altitude makes it go up. It's confusing and it can be deadly. Turn on your pitot heat!

you do not need to clear the joystick commands in game if you use the SST profiler. Once you've set a button on the X-52 to perform a keyboard command it stops sending the joystick button itself through.

well, this is awesome! Thanks be to forum member reemit0772 who told me how to enable mouse clicking in the communications menu! Guess it was here all along: In the folder: FUI/resources/radio. Edit 'menu.res' and change 'acceptmouse{0}' to 'acceptmouse{1}' Works a treat for me. Just unbound the function keys from my X-52.

don't see this on the list yet: the blades on the turbo fans are individually numbered! Of course, it's a little hard to see unless you take a look before engine start.

I was thinking today, while trying to juggle the F1-F12 keys I have mapped to the toggles on my X-52 (plus pinky for F7-F12), that the comm system we have basically dates back to the days of non-clickable cockpits and planes that were flown without a mouse nearby. Since we now have 3D clickable cockpits the mouse never leaves the joystick's side, at least for me. I think it would be great if the menus brought up by hitting the mic switches could be clicked with the mouse as well as the F1-F12 keys. I know this would make it easier for me to get the right message sent as quickly as possible. Any one else think it's a good or bad idea?

Also you need to have all four SAS switches on to engage the EAC switch

I actualy haven't messed around with TACAN much yet, but for your radio make sure you're using the correct mic switch (AM, FM, UHF) to call them and also that your radios are powered. The FM and AM radios need APU or engine generators to be running, the UHF radio can run off the battery. I like bumping the squelch switch and see if I can hear any static to make sure the radio's functioning. The HUD has some switches on the armament contorl panel on the left side of the dash board. The IFFCC switch turns it on, off, or test and there's also a day / night switch. It's in the manual under "cockpit controls -> Armament Hud and Control Panel". For brightness, the Up Front controller right under the HUD has a rocker switch labeled "INTEN". They had plenty of room to write "INTENSITY" but chose not to :music_whistling:

how about a command to push the switch up and a command to push the switch down? Sorta like how the switches work with the mouse, you already can rotate the master arm from safe through armed to get to training, or you can go the other way and flip it immediately down to training. Personally, I don't have any commands set that aren't on the HOTAS of the A-10C. The clickable cockpit is too much fun to use, heh but that may just be me. If you're fairly proficient at scripting it wouldn't be too hard to write an AutoHotkey script or something similar that would take care of this outside the game, though it'd be nice to have it built in.

Keep in mind the number of people that are buying $500 joysticks to get the full warthog experience with this sim.

YES! I thought for sure we would see this feature by the time the A-10C was released. It is literally, the only gripe I have with the sim. I liked that mouse look mode a lot, it was received very well when it was added to BS. I have no idea why it isn't available here.

there is a checkbox during the install for the 32-bit binaries. If it's checked it will install the 32 bit binaries to an x86 folder inside of the bin folder.

kind of reminds me of the Tigerfibel. The German instruction manual for the Tiger tank was written in humorous rhymes and packed with lots of illustrations, a lot of which are of pretty girls instead of the tank.

I fly this plane with the keyboard all the time. I have an X-52, rudder pedals and TrackIR, sometimes I just can't be bothered to plug everything in (yes, I'm THAT lazy). It's a lot easier than flying DCS Black Shark with a keyboard. If you think it's impossible you aren't trying hard enough! This here A-10C is steady as a rock, thanks to all the bells and whistles like PAC strafing tanks using the cursor keys is a breeze. Just don't try to do any formation flying :-)

here's a tip: go to the controls page in DCS A-10C and start mashing buttons. When you hit a button that is bound to a command, the screen will jump to that command and highlight it. Sometimes it seems like I have to cancel out of the control screen and get back into it for this to work. Just keep mashing buttons until you find ones that aren't hooked up :-P This is also a good way to play "what does this button do?" with your joystick without crashing the plane... Personally I tend to use Alt+F# combinations for TrackIR.

This is actually something even Movie Maker can do, not that it can do much else! You don't have full control over the speed, for instance you can't say you want it to run at exactly 38% like you could with Adobe Premiere. You can however specify the speed to be be a quarter, half, double, or quadruple, etc. This is in Live Movie Maker, the newer version, but I remember this feature from regular old Microsoft Movie Maker I had on XP as well.

You don't have to wait! When you install the game, there is an option to install the 32 bit binaries. Reinstall the A-10 Beta and make sure to select that option. I'm also on W7 64 bit, but I'm playing DCS A-10C with TrackIR just fine as long as I don't use the 64 bit DCS binaries.

we can hope, we can dream, we can pray. Boy how I would love a two seater! I almost always play Black shark and now the A-10C with just one other buddy on a LAN. Doing some front-seat / back-seat co-op missions would just be a blast.

I think most of us can agree that oxygen is important and it's a good idea to have a bunch of it handy when one is flying a plane. I'm just glad the environmental system has such a pronounced effect. I hope that Black Shark gets patched up to include this and we see a rush of Ka-50 pilots taking off their weapons, taking on only 10% fuel, and shooting up into the sky to try and see it for themselves.

I just found out turning on the 100% oxygen supply in your mask instead of normal air greatly speeds your recovery from hypoxia in game too.

Koyan's idea is great I use an X-52, my 2nd mode is for comms and I have f1-f6 bound as the stick's toggle buttons, then F7-F12 bound as the same toggles plus pinky switch. Trying to figure out which combo I hit to send F9 in combat has killed me a half dozen times, not to mention it takes two hands!