Olethros

Pretty much what the title says. The moment you get within 8km of the airfield (any airfield) the glide slope indicator needles on the HSI go all the way down and to the left. This affects both the Su-25A and the Su-25T. Su-25T ILS Bug 1.trk

According to Logitech's support pages, the newest version of the gaming software should recognize the Attack 3, so I'd try upgrading it if you haven't done this already. If that still doesn't work, then yeah, time to get Joy2Key, XPadder or AutoHotKey. I prefer the latter, seeing as I already use it for a ton of other stuff. Something like this should do the trick in your case: #NoEnv #SingleInstance force SendMode Input SetWorkingDir %A_ScriptDir% SetbatchLines -1 1Joy3::SendInput t Assuming the Attack3 is at the top of the list of gaming controllers on your PC. If it is no. 2 you use 2Joy3 and so on.

Have you tried simply assigning button 3 to "T" in Logitech Gaming Software?

Also, as with the P-51, you have to make sure that you have the correct HF frequency for whoever it is you want to talk to on one of your radio's presets. This is usually set by the mission designer, or it can be done in the pre-flight arming screen. Additionally, the Dora's battery has a rather unfortunate tendency to run out a couple of minutes into the flight, so your engine has to run at 1200+ RPM for the generator to power the radio set.

http://xkcd.com/763/ You asked.

Yep, that's what I first suspected as well, but they were still on 0% and quite clearly unticked.

That's odd. To me takeoffs seem almost ridiculously easy now, but I still have to haul that stick halfway into my beer gut on finals.

Did you add the commands to both the Input\Joystick\Default.lua and Input\Keyboard\Default.lua? From your description it sounds like you've added them to only one of them. Anyway, in today's "I really can't believe they left out this command" segment: Separate up and down keys for the landing gear in the P-51D/TF-51D. Working perfectly: {down = device_commands.Button_3, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 1.0, name = 'Gear Up', category = 'Systems'}, {down = device_commands.Button_3, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = -1.0, name = 'Gear Down', category = 'Systems'},

The Bodnar boards really are quite handy. I've made a Cougar TQS + Amiga joystick controller out of one myself and still there are 3 axis and 19 buttons left for a switch panel once I get the parts in the mail. It should end up pretty similar to the Saitek Pro Flight panel, only mine will work in other games besides FSX as well as being quite a bit cheaper. Also, maybe a bit late seeing as the thread was started two years ago, but the Saitek throttle quadrants seem to have a bit of an undeservedly bad rep for wearing out when what is actually happening is the construction of the potentiometers lend them open to the grease from the mechanism gunking up the resistor track inside them. Mine started spiking quite badly after two years, but cleaning and lubricating the pots got it back to working as if it was brand new. And it still is today.

Unless the trim wheel is radically different from my throttle quadrant, then it really couldn't be simpler. Set the axis to "directional key presses" or whatever, choose which key command/macro to repeat as the wheel moves up and another one for when it moves downward and then adjust the sensitivity or, more precicely, how many times the commands are triggered per revolution of the wheel. Just how well it works in the game, however, is another matter entirely.

The real FW-190 didn't have trim tabs connected to wheels in the cockpit like the P-51, but rather an electrical motor with a worm gear that moved the entire horizontal stabilizer up and down like a modern airliner. This electric motor was operated with a simple toggle switch on the left console marked "Kopf lästiger"/"Schwanz lästiger" - head heavy / tail heavy. So I assume it isn't possible to assign vertical trim to an analog axis in the game. It should be possible, however, to use the Saitek programming software to assign the trim wheel to output directional key presses.

They are stored in the "base_joystick_binding.lua" file. (Can't remember exactly where in the main game dir it resides right now - my work computer unfortunately doesn't have DCSW installed...) To get airbrakes working as you say on the X55 and, in my case, the Cougar Throttle, the easiest is to simply add an "Air brake hold" command to the list in the configuration panel. Like this (not sure about the specific iCommand spelling as I'm writing this from memory): {down = iCommandPlaneAirBrakeOn, up = iCommandPlaneAirBrakeOff, name = 'Air brake hold', category = 'Systems'}, Then you can simply bind this to any button(s) you want to keep pressed to have air brakes deployed in the configuration panel. Ideally, additional commands should probably be included in its own mod, as described here: http://forums.eagle.ru/showpost.php?p=2060773&postcount=40

The only mistake I made during my first flight in DCS's Pony (save for a couple of slightly awkward ground loops while taxiing to the runway) was not saving the track afterwards. Compared to Il-2:1946 it's actually quite a bit easier nailing a three-pointer here, even in full simulator mode with no rudder or landing assists of any kind. The lack of ground effect in Il-2 tends to turn an almost perfectly timed flare into a jarring, bouncy embarrassment, but the DCS flight model seems a lot more forgiving in this aspect.

Same problem here. Win7x64, wired XBox controller with the latest drivers. DCS World is the only program that acts up with the controller connected, so it might not necessarily be the VC redis or .Net libraries. Does the program itself write a crash log or similar? That could help track the issue down, but I haven't been able to find anything in the game folders.