Thermal

Either Helios or TouchBuddy. (You'll have to hunt for TouchBuddy files, it seems to be an abandoned project). "touchbuddy-1.3.0.18-20070614-Core"

Its not that complicated and you will need to program it for something eventually. When you use Target and run a profile, Target removes the Joystick and Throttle HID devices. In its place it creates a single, combined joystick/throttle combination called "Thrustmaster Combined". So in something like DCS, the default behavior is that DCS expects two devices, and all the keys are mapped for you. Running a profile in Target then breaks this - because the two devices are removed. You can disable the deletion of the the Joystick and Throttle devices, and you can, if you want, delete them from the original device, and reprogram their output with the "Thrustmaster Combined" device. And here is the profile: [color=#1e90ff][b]include[/b][/color] [color=#a52a2a]"target.tmh"[/color] [color=#32cd32]//program startup[/color] [color=#1e90ff][b]int[/b][/color] main() { [color=#32cd32]// When run, both the Joystick and the Throttle remain as separate DX devices[/color] [color=#32cd32]// the "Thrustmaster Combined" device is also created[/color] Configure(&Joystick[color=#ffffff],[/color]MODE_FILTERED); [color=#32cd32]// Filtered, can disable original in int EventHandle() below[/color] Configure(&Throttle[color=#ffffff],[/color]MODE_FILTERED); [color=#1e90ff][b]if[/b][/color][color=#ffffff]([/color]Init(&EventHandle)) [color=#1e90ff][b]return[/b][/color] [color=#ffffff]1[/color]; [color=#32cd32]// declare the event handler, return on error[/color] [color=#32cd32]// add initialization code here [/color] MapKey(&Joystick, TG1, 0); [color=#32cd32]// This disables TG1 for the "Thrustmaster Combined" device [/color] MapKey(&Joystick, S2, [color=#a52a2a]'a'[/color]); [color=#32cd32]// single keypress[/color] MapKey(&Throttle, LDGH, [color=#a52a2a]'b'[/color]); [color=#32cd32]// single keypress[/color] MapKey(&Throttle, APENG, DX1); [color=#32cd32]// This is the DX1 button of the "Thrustmaster Combined" device[/color] [color=#32cd32]// All buttons not explicitly defined here inherit defaults in Thrustmaster Combined[/color] } [color=#32cd32]//event handler[/color] [color=#1e90ff][b]int[/b][/color] EventHandle[color=#ffffff]([/color][color=#1e90ff][b]int[/b][/color] type, [color=#1e90ff][b]alias[/b][/color] o, [color=#1e90ff][b]int[/b][/color] x) { [color=#32cd32]// To disable buttons on the original Joystick and Throttle devices, add here[/color] [color=#1e90ff][b]if[/b][/color](&o == &Joystick & !(o[color=#ffffff][[/color]S2])) GameOutput(&o, x, o[color=#ffffff][[/color]x]); [color=#1e90ff][b]if[/b][/color](&o == &Throttle & !(o[color=#ffffff][[/color]LDGH]|o[color=#ffffff][[/color]APENG])) GameOutput(&o, x, o[color=#ffffff][[/color]x]); DefaultMapping(&o, x); } You can change as needed to suit your requirements, but the upshot is that the two original Joystick and Throttle devices remain with this profile, and only the keys you program are changed from the defaults. So you can surgically change what you want. Be aware that you might get double button presses in some apps. In the above example TG1 of the Joystick device is active, but its not in "Thrustmaster Combined" ("0" disables in the config). However TG2 is active on both - so two directx button presses will occur, one on the Joystick device, one on the "Thrustmaster Combined" device. Run the profile and then look at the output with the Target Device Analyzer.

Using Target gets this functionality.

From years ago: http://simhq.com/forum/ubbthreads.php/topics/3227915/Re:_TARGET,_Cougar_Control_Pan#Post3227915 And Izzy added this:

As stated, the Warthog Stick has a push button on the CMS, Cougar does not - apart from that they are functionally equivalent. They are slightly different in shape, size, button placement and button actuation force. Even the trigger itself is a new part. All the Cougar buttons require less activation force. Its all personal preference.

Aurel - Have a look at the Target Device Analyzer. That will show the SLEW inputs as analog, and demonsrate how non-axis it is like with the default settings. Thats probably better feedback for tweaking settings than in-game.

Please.

I've bought a U-HID card which is similar. Rotary encoders, where you end up pulsing commands via a directx button or HID keyboard keypress would work, but there would not be absolute physical stops. There is also an sdk for it. Isnt the issue though getting the sim to understand the input? i.e having the incremental up/down in the sim translated to a range of values that DCSW understands?

Thats a pretty good first pass explanation.

Awesome work Clear Dark. The only issue I have is that "I must spread some reputation around before giving it to Clear Dark again".....

They (the ftp servers) do that when under load. Grab the torrent instead.

I'm torrenting now.... http://www.digitalcombatsimulator.com/upload/iblock/89e/DCS-WH_Patch_1.1.0.7_EN.torrent

Nice work! What are use using for the rocker switches?

The ASI and the vario will most likely run on air-pressure... no electrics/electronics. The turn and bank... that will have an internal gyro. There will not be a way to induce external input to drive that. You'll have to completely re-engineer the insides.

Hmmm, just tested, running fullscreen - 50fps, windowed 30fps. No other changes. Same res, same number of monitors. When I run two screens and export MFCD's I get about the same performance - 30fps. Scatter - you running Win7?

scatter - what resolutions are you running? We have pretty similar system specs. I'm doing 60-ish fps (high settings generally) 1920x1200 - using a second monitor drops that to 30fps (irrespective of HawgTouch running or not).

From the doco: Note:I don’t use a second monitor and for me with a 1920x1600 resolution a dual MFD250x250 is acceptable. So does that mean you create a "virtual" screen with a 1920x1600 resolution, display only the top 1920x1200 on your monitor and display the MFCD's in the non-viewable part of the virtual screen?

I know what I am doing on the weekend! Thanks Ghost_Unit!

Thats because the OP has done artwork which is sized specifically for his iPhone. TouchIR works on my iPad just fine, and also does work on a iPhone 4.

I've just ordered a u-hid from these guys... http://www.u-hid.com/home/overview_board.php The specs look suspiciously cougar like. But its a USB board that is a 32 button, 8 axis directx joystick. It can also drive LEDs apparently. I'm thinking of shoving it inside my Cougar throttle and making it look like a hedgehog :)

FYI guys, Export ALL Indicators like MFCD via ViewPorts : http://forums.eagle.ru/showthread.php?t=70716 All props to Icemaker... genius!

wow! The TGP footage is impressive. Definately very usable. I want one :)

Looking great ghost! Looks like the mfcd screens are updating alot faster :)

Thats really awesome! The default starting position is great. Could there be a toggle for either a ramp start/runway start/instant action scenarios?

Thats awesome. How is the MFCD export with the TGP video? I take it that your screen grabbing the second monitor and MFCD output and then piping it to the iPad? So I guess that you could also use lua export for things with suitable development?