Gadroc

They are accurate size for an F-16. The A-10C has larger MFCDs (5" instead of the 4.25" of a F-16 if I remember right). In addition the A-10C MFDs have a rotary switch in the lower left and an additional horizontal rocker in the lower left.

That won't work for a native windows 7 touch screen (aka one that uses the built in capabilities of windows 7). Windows 7 maps a digitizer to a monitor and with Eyefinity the monitor and Windows sees the Eyefinity group as one big monitor. So when you touch the left third of the touch screen that will map to the left hand monitor in the Eyefinity group, etc. There are some third party touch screen which do not use the direct Windows 7 support and can be manipulated to represent a partial monitor in Windows. The older 3M drivers could do it with unsupported registry settings (I had two Dell 15" touch monitors mapped onto one dual head 2 go at one point). I foresee this being less and less common as time goes on.

Good catch! Looks like the aspect ratio is trigging the abnormalities, which explains why I wasn't having the problems others where. My current setup has a 2560x2520 resolution which is nearly 1 ;).

Selling barley used Force Sensing mod for a Thrustmaster Cougar. Asking $375 and buyer pays shipping (small and light). It works great I could just never get used to it. I have a cougar I would be willing to sell if you need one.

I am selling my two side screens. I love these monitors, but I'm going to start the slow progression to hard switches. I have two of these available which retail for $259. Both work great and have no problems, although one of them had the USB port come off and I had to re-solder it back on. Asking $200 for the like new one and $175 for the one with the re-soldered USB port. Buyer pays shipping costs.

What OS and touch screen are you using?

We chose to take down the store front for a variety of reasons. Primarily we decided it gave the wrong impression of what we really are, which is a few guys who make flight sim pits and software in our spare time. We can't offer overnight same day shipping of these types of products with out making it a full time job and the money is just not there to make that a reality. People where expecting amazon like service from a couple of hobbyists. Flim does runs of the physical kits as his day job allows and I've moved Helios to donationware for similar reasons. If there is something specific you want contact Flim directly and he may be in a position to work something out with you.

I'm also very interested in the rear projection front console. It may make it very easy to make some interchangeable front consoles!

No, they only work for touch screens which use the egalax chipset, which a lot of inexpensive touch overlays use.

Scooter, You need to edit the View.lua file and set the max fov to 220. Also it works best if you modify the snapviewdefaults to start at 220 viewangle. I'm away from my pit for the week but when I get home i'll double check my settings.

Hannibal, There seems to be some confusion from the other threads you have. Helios can be used without lua modifications, you just can't use the built in DCS A-10 interface or gauges. If you do nothing except bind against keyboard commands it will work just like Touchbuddy. The only thing touchbuddy can do that Helios doesn't is run in client/server mode.

You have to manually edit the options.lua file in Black Shark to input a non standard resolution.

Froglips, Send me a PM/e-mail with the exact dimensions you need.

You still miss the point... First eSATA has variants just like regular sata (3Gb/s version and 6Gb/s version). I'll not include those as they are essentially identical for our purposes to regular SATA, they only add additional requirements for shielding, cable length and connectors. Theoretical Performance is what you are listing and it actual goes in this order. USB (12Mb/s) < Firewire 400 (400Mb/s) < USB 2.0 (480Mb/s) < Firewire 800 (800Mb/s) < SATA 1.0 (1.5Gb/s) < SATA 2.0 (3Gb/s) < USB 3.0 (5Gbs) < SATA 3.0 (6.0Gb/s) < Thunderbolt (10Gb/s) The key word being theoretical in that metric. That does not take into account protocol overhead, duplex (being able to send and receive at the same time) and other things like bus topology. You'll notice that no USB 2.0 storage system ever got close to 480Mb/s throughput. It is just plain silly to buy an SSD drive and put it on a USB 2.0 bus, as mechanical hard drives are bottlenecked by that spec. USB 3.0 has yet to be proven in this area, and I highly doubt it will ever replace a dedicated storage bus like SATA for primary OS drives. I'll restate again in my opinion anyone buying an SSD would be wasting their money putting it on an USB bus. It's highly unlikely that you'll find a machine that comes with USB 3.0 that doesn't come with SATA 3.0 as well.

USB and SATA are very different beasts, and I'm not sure using USB3 as your primary drive is realistic yet. Speed is not just determined by the theoretical bandwidth limit, just like you can't tell real CPU performance just by clock speed (remember how fast those 3Ghz Pentium 4s are compared to current i7). I sure as hell wouldn't spend the kind of money you do on a SSD and drop it on USB, especially if that USB controller has anything else hung off it. Here are some benchmarks I could find comparing USB3 to SATA. Notice the only one where USB3 is better requires a "USB3 Turbo Mode" which I have no clue what it is. http://www.sansdigital.com/performance-comparison/eliteraid-usb3-performance-feature.html http://www.crunchgear.com/2010/02/05/esata-is-faster-than-usb-3-0-at-least-right-now/

Gadroc == Helios programmer, so yes I can confirm that's not a problem. Just create a profile and do not add the DCS A-10C interface. Just drag and drop buttons and bind them to keyboard send actions. This is the exact same thing as touch buddy once you remove the DCS A-10C interface from the profile. Keep in mind the profile other people have posted are bound to the DCS A-10C Interface so you'll have to rebind to keyboard commands, but the graphics and layouts will work.

You can do the same with Helios... just have to stick to Keyboard actions instead of the built in FC2/DCS integration. You can't use gauges though.

I don't think you can, but you can write a c/c++/c# application which can talk to lua via sockets.

FYI - the bank account statement wasn't ment derogatory or mean. The warthog is expensive by any means and it does require pedals for the fullest. You really pay for the feel and not everyone values it the same way.

Annoying but the base plate is attached by 4 screws, and is designed to be taken off if you want to mount it in a pit. If this is truly on your list of complaints I think you're looking for excuses to say CH is better. Sorry but.... go buy pedals. You knew there where no pedals on the unit when you bought it right? While there where a folks who had bricked throttle I have not heard of switches going bad. I've had zero problems with mine. The internet sometimes becoming an "echo" chamber where you see vocal minorities. The only people who could tell you if there was a statistically high failure rate are Thrustmaster. Do you notice this "sticknation" or are you just parroting what you've read on the stick. I feel nothing of the sort on mine neither do many of the owners of the stick. Well no joystick allows you to map multiple functions to the same button with out running their mapping software / drivers. TARGET is very very versatile but can have a steep learning curve. That being said DCS games have built in support for this. Open the controls section and click the modifiers button then click add... now press whatever button you want to be the shift button. Now you can use that as a modifier in other bindings. The paddle works just fine, just the default bindings in DCS don't have anything mapped to it because the real A-10 doesn't have a paddle switch. Just open up the controls section of DCS and map it to whatever you want.... this would make a great "shift" button from above or wheel brakes. To be quite honest your list above seems a contrived list of things you've tried hard to find reasons to send it back. The CH stick will require you to use the CH equivalent of Target or assign modifier keys just like the Warthog. The Warthog throttle has far more buttons and switches to map than the CH equivalent. There is no reason you have to use them as labeled feel free to create a mapping that does 2-4 times as much. Out of the box it gets mapped identical to the real HOTAS. The only real issue is cost and rudder. You could get a different set up with pedals for the same cost... but you would give up the real feel you get with the HOTAS warthog. You're tho only one that can put value on your bank account.

Nothing special you have to do aside from turn off fullscreen in the options. Aside from that follow the multi-monitor setup guides in the A-10C Support forums.

That's not true. Neither Hawgtouch nor Helios allow the MFDs to be displayed. They only display the bezels and allow interaction via the touch screen or mouse. Putting the MFDs on a second video card and many people have done so, but you will loose FPS by doing so. How much depends on many factors. If you already have the hardware try it.

You can find and run Phantom Monitor Fix from early black shark days, or if you run Helios check phantom monitor fix in the DCS A-10 settings screen.

Deadman, I could use one... already have the regular set so I would only need the extended stick.

Helios supports the Phidgets LED Controller board and can be used to do this for you with out any LUA programming.