Puma

Missing files I would love this as I have a fully funcitonal pit in front me of. But the link is broken. Help!

I noticed when I configure my Saitek Pro Combat pedals that I had to invert the axis to get the response I expected. I expect right foot forwards = turn left. Dunno why, thats just always how I've set it up and never thought more about it. I noticed while waiting for a nav alignment to complete one day, that when I looked down, the in-pit rendered pedals were moving opposite to my feet. Is this a bug in the game, or if I flew a real plane, would I go the wrong way? Cheers on this amazing product.

I used an old powered home theater sub which already had all required parts (amp) included. Just to cut out the cone and epoxy on some weights.

Missing the forest I'm thrilled to have found this tutorial, and other posts on EOS. Lots of the small details are here, and I have a good background in electronics so I am sure I can work through any little glitches. So, I can see the "trees", but I'm missing the forest! Can anyone shed some light on the architectural layout of a typical EOS/Arduino/PC setup? I am using a Teensy++ 2.0, which as far as I can tell has two UARTs, lots of pins available. The stock EOS interface compiled (save for one issue of TIMER_XX predefs not being present, so I just copied them from the arduino headers). Where I am the most confused is which UARTs are used for EOS, debugging, and which PC COM ports are involved. The Teensy is in a configuration which provides one UART over USB and is typically used for debugging. That would suggest that I need a second COM port on my PC and to wire that up to pins 2+3 on my Teensy. However this tutorial doesn't mention any additional wiring and it otherwise seems to complete. The next goal will be chaining multiple EOS board over 485. I understand 232 to 485 transceivers, but again am lost on the layout. Would I have a USB to 485 interface on my PC (or 232 to 485 on a com port), and then have every teensy have a 485 to 232 to pin 2+3? The PC is the master? Or do I use the debugging port to the first teensy, have it be the master, and use the second UART as the 485 bus to other teensy EOS slaves? I don't need a walkthrough, just a push in the right direction!

Resolved Finally got this resolved. Turns out that when you re-map your monitors, all input/output bindings are lost. Not sure why that's necessary since it seems like a geometric transform to me? Regardless, as suggested in a youtube tutorial, I opened two instances of the editor, started a new profile in my layout, and then copied/pasted the panels I wanted into my profile and that preserved the bindings. Time to FLY!

I was in love with the idea of this product when I saw what it could do, but I'm loosing my mind trying to get it to work. I'm ok with display layouts, but no matter what I've tried I can't get a single gauge to update. I have opened the profile, opened the A-10C panel interface and confirmed that it says "remove", implying that it is installed properly. I can see that it modified my exports.lua file. I open the profile and it appears on the correct display, but when I run DCS world, nothing changes on the gauges. Pushing buttons has no effect on the sim. I feel like I'm missing something obvious, but big. Win8 with UAC on, is that ok? Is there any way to debug this nightmare? I'm sick of trying the same things over and over again and expecting a different result. Please help!

Starts of great. Using the 1.5 profile, seconds after I start a flight, the guages start to spin but it then crashes. Any way I can extract a call stack or anything else to help debug

DockTo bottom? What are the support values for DockTo? I am trying to get BottomRight or LowerRight to work. It seems like it works, but I think its positioning it BELOW the screen. Maybe forgot to subtract the height of the panel from the new position?

Non-standard program files directory I installed DCS-A10C via steam, and I have a RAID array for data, so my path to A-10 is E:\SteamLibrary\SteamApps\common\DCS A-10C Warthog. I placed HawgTouch here: E:\Program Files (x86)\HawgTouch. When I launch HawgTouch, it says data export not found. When I click "Enabled", I get a not found exception saying it could not find the path "\Config\Export\Export.back". Looks like there might be an issue locating my DCS directory with this non-standard path. Help :)

Hotel Sierra or Sierra Hotel? Sorry to be that anal dude who jumps on something out of topic... but isn't the term "Sierra Hotel"? I read once that it was a navy pilot term abbreviating "SH$T HOT". Can anyone else confirm that?

That's perfect. Thanks!!

Can anyone who is lucky enough to have one of the first Thrustmast Warthogs please send me the dimensions of the two bases? I'd like to commit to my final pit frame but they are rather integral. Footprint of each controller is key, as is the depth from the top of the control panel to the bottom of the base. Thanks in advance guys!

Hi guys. I've been trying to solve this one on my own but I need to defer to someone more experienced than I. I've been working for 6 months on plans for my A-10 pit; my first REAL pit build. I thought I had it all worked out: I purchased a Hagstrom USB108 keyboard encoder for toggle switches and an XKeys for momentaries. For my pure rotary switches (volume, etc), I purchased four Teensy microcontrollers to convert 2-bit rotary into clockwise and CCW pulses, which I then planned on connecting to the USB108 to generate keystrokes accordingly. I had planned on using absolute rotary switches (not encoders) for rotary switches where each absolute position has a meaning, for example, the "FUEL DISPLAY SEL" rotary in an A10 or F16, but I read the DCS:BS documentation, and it appeared that the keyboard encoding only allow encoding "TURN CW" and "TURN CCW" keyboard commands for rotaries like these, so a absolute rotary switch would NOT work. I could use a rotary encoder and forfeit the absolute positioning of the switch, but I feel like I'm going against the grain here since its expensive to buy a rotary encoder, 4 ports on a Teensey plus two digital inputs on the USB108 for a simple switch. Am I missing an obvious, cost effective way to design such a switch? Or is there an alternate set of keyboard mappings which would say "Set this switch directly to its 4th position"? Any advice on the challenge is greatly appreciated. I'm so close to starting to build this darn thing it's killing me!

More than likely DCS Blackshark is listed on the "good" compatibility list @ nvidia, so almost certainly A-10 will too. As long as the game designers play nice with DirectX, they don't need to do extra work for 3D to work, so most games will work. No the real question is how much will it enhance the sim? In-cockpit effects should be impressive, but most exterior views will be so far away I wouldn't expect much of a difference between 3D and not... regardless... if I haven't bankrupted myself buying a HOTAS warthog, 3D will be next on the list!

DZUS or not to DZUS Can someone explain why I seem to be having so much trouble with this? I've seen on this and several posts people simply saying "the DZUS fasteners". DZUS is a company, and they make thousands of quick connects, none of which seem to me to match the pictures I've seen of military panels (including the ones on this thread). Does anyone have the actual part # for these fasteners, or better yet a link to a supplier? Thanks guys. Pit building is an amazing hobby!