Gadroc

Aelfewulf, 2560x1600 is a 16x10 aspect ratio. The FOV will be exactly the same as a 1920x1200 screen or a 1680x1050. What will be different is how many dots (pixels) per inch on the screen. In general a higher DPI will look better, but text can get hard to read if it is not properly scaled.

Not yet we need to get through the first prototypes to understand material and cutting time.

The intent is to sell it in a modular fashion.

Cezar, Sorry if I came off blunt, but your reading to much into my post. Just trying to point you in the right direction to get more info.

Cezar, There are several threads on the forum here that explain how to interface OC cards, even source code for direct SIOC to lua integration. I suggest you start with reading Oakes threads (BlackShark and A-10C are 99% identical in reading the clickabledata.lua). The devices.lua file is not empty on a DCS A-10C installation it just uses a counter to increment the value. Start with one on the first line that says = counter() and add one for each call to it (hint for Beta4 just subtrace 7 from the line number).

Same board here mine is rev 2.

Purg is correct. When you see people using iPads with Helios they are not actually running Helios on the iPad. They have software which makes the iPad look like another monitor to Windows. If your ePad has similar software it may or may not work depending on how well that software works. Helios does not directly support either of these configurations.

While many of the clickable action items use -0.1 or 0.1 the mouse wheel often is even finer grained than that. If it still feels clunky you can try reducing it further.

When you say hooked up ... how do you have it hooked up. Are you sending direct x button presses and mapping it in game or are you using some LUA integration. To make the resolution finer you will have to do your own LUA integration or use something like Helios.

I have two 10.4" raw LCD panels I use with 10.4 touch screen overlays. You can find these on ebay sellers PM me and I'll point you in the direction of who I bought them for. Only do this if you are comfortable fashioning your own case / surround depending on where how your going to mount them. I'll check my bookmarks links but I also found vendors who had 10" VGA/Touchscreens, but they all cost $200-$300 so might as well pick up an HP 21" touchscreen for that much.

For a touchbuddy profile or a static Helios profile they should work fine. You will have to test anything else (like deploying a gauge from Helios on it, or exporting MFDs to it) as the USB monitors do not have hardware acceleration. In addition check their support forums for driver issues win Win 7 x64, I know some of the chip set drivers for USB monitors have had problems there or only support one USB monitor at a time.

It's not a bad piece of kit for the price when you consider price tag includes a set of rudder pedals and is the same price or cheaper than a X52 Pro + Saitek Pro Pedals (depending on your area and who you order from). The joystick is very accurate, but the force feedback nature of the stick leaves a slop area in the center where there is no resistance but the movement is registered. This makes it hard to make some adjustments. This did get better with the last firmware, but not gone completely. You make these trade-offs to have force feedback on this stick. For Black Shark I like the trade off as I much prefer the trimming with force feedback, also if you get the FS Force add on to FSX it's also very nice. In the end I fly with the Warthog now and the G940 is in the closet.

Not yet. We are working on one now, for the final release which is targeted for Feb 7th.

The 3M calibration tool doesn't do it. You have to monkey with registry settings. I have not found a way to do it with the windows native tools.

That won't work. I don't think there is a way to do it with that touch screen. I know how to do it with 3m touch controllers.

Mack, What kind of touch screen do you have in the center?

If you have questions about that build you should look at his thread. He explains 90% of how he built them even with videos of the process.

Hey Ice, The basic dims we reverse engineered from pictures. Take a know dimension like the MFCD screen size. Then use that as the unit of measure and extrapolate other things. We did this using The Modern Hog Guide and then scaled things down to match the scale of the Thrustmaster MFDs.

Vega, Thanks for posting this! Do you know what the issue is with DCS running worse with 5760x1200 than 5084x2560? The 5084 is literally twice the resolution. I assume this was due to FOV causing more things to be rendered, but are there other factors. I've been considering a 3x28" 580Gtx setup, but if I go down to 18FPS it's a now go.

The HP is smaller screen 21" vs the Acer 23". Both there touch features work identically and actually use the same touch controller. They have similar viewing angles. Build quality the HP wins hands down. The Acer case squished and flexes as I grab it move it, while the HP feels solid. The HP only has DVI and VGA inputs. One tip if you are laying them flat is flip the upside down. They have better viewing angles that way.

The honest answer is we can't extract the video feeds. DCS would have to supply us a way to that read the video data and currently it doesn't.

The feature is already built into the latest Helios beta.

Actual that function works fine. Turns out that GetDevice(0) is randomly failing when connected as a client which was causing LuaExportActivityNextEvent to exit without returning the next execution cycle.

LOL.... no doubt that's outside where I was willing to go.

@power5 Yes the MFCD are rendered inside DCS and Helios is rendered over top of it and you can see through to the MFCDs. There really is no other way to do it right now. DCS has to be modified to do it any other way, as the A-10C uses the MFD displays for video feeds from the game engine it can not be "generated" based on data the sim sends us. Blackshark had the ability to do "shared memory" texture but that performed worse than the multiple screen window mode (still does as i have working exports for it in internal builds). These shared memory features don't work in A-10C as of yet. There is some ability to "replicate" images off the main display into the MFCDs, but that too has a performance penalty that is worse than windows multi-monitor in DCS at least with the current technique. I'm exploring code that would hook in similar to FRAPs to see if we can have less impact, but that is a lot of work and will be a ways out.