Thermal

So there was a bug where Starforce was breaking axis input for the F15, and F15 alone (which is one weird ass bug). Maybe something similar? 4 people all having a similar, new issue is maybe more than co-incidence?

So the Pro is a straight up upgrade over my Warthog, that makes buying one a bit easier to justify :) Can anyone think of a use case for the 6th axis on the Metal Trigger on the Pro?

I just re-installed Win10 to fix an issue where my Warthog Joystick would work in joy.cpl "properties" window (or in game). When I plug in the Joystick, it registers, and looks like a valid HID device. It appears in the list of joy.cpl devices. When I hit "properties" and the sub-window opens up, where once there was the axis and button identifiers, there was nothing. (The throttle was working fine). I am not sure what went wrong, but it happened when I got a Roccat ISKU force keyboard, which is itself a HID game controller, and as it turns out, installs vJoy (which I had already installed). Now I has some success with this procedure: http://ts.thrustmaster.com/faqs/eng/thr_eng_00140.pdf (but only if you followed each, and every part of the procedure to the letter, including the reboots). But it was not a permanent fix across reboots. One very interesting thing was that even though the control panel could not see any axis of buttons for the joystick, running the Logitech "DIView" program, I could see the axis and buttons responding. So there seemed to be some driver issue blocking the joystick working in Win10, rather that a physical fault. Reinstalling drivers and removing all my HID game devices sort of helped, as in sometimes the joystick would work, but it never survived a reboot, so I did a completely fresh install from scratch, and everything seems happy (for the last 24 hours, touch wood!). One other thing I have done is used the on-board USB headers to add USB ports to riser cards - http://www.dx.com/p/usb-2-0-4-port-hub-expansion-cable-grey-black-multi-colored-30cm-302359#.WPMcwaLhVjE - so I dont need to use hubs for my critical stuff.

Cool mod! Do you need a USB hub to join USB together? Or can you solder your USB 4 wire onto the warthog onboard USB in parallel?

If you use the second throttle as a default directx device it should work. Running Target to program it? That would be a challenge.

I have just started looking at freepie for this. MIDI controllers are cheap usb button boxes if you can get them working.

FreePIE can convert MIDI to a virtual joystick (apparently). There seem to be a heap of cool looking cheap midi controllers that you could do like that. (This one seems pretty expensive). There is is also this: https://palettegear.com/index

They are all digital connections, so there is no image-quality concerns. The issue cichlidfan is talking about is that there *might* be encoding latency differences between the three ports on the graphics cards, so when the card generates a frame for each of the three monitors, they might not be perfectly synchronized as they get streamed onto the cable for delivery to the monitor. My gut feel is that its a non-issue (particularly on the all-digital ports). There is probably a small difference if your using an analog port (D-sub) as that would need an additional conversion process. Monitors vary wildly with input latency, and lots of people run different monitors in 3-screen setups and this is the first time I've heard mention of it, so my guess is that its not a thing (although if you have a 50ms latency potato of a monitor and a 1ms gaming monitor it might be noticeable).

Do you have any "mode" commands in your profile? Like this? // Configure(&Joystick,MODE_FILTERED); // Filtered, can disable original in int EventHandle() Does the issue happen with a plain, simple .tmc file running in the script editor?

Cool concept! Will you (or could you) do a right hand grip? Star Citizen and Elite:Dangerous might be a large market - thats an immediate use case for me to buy a T-50 base and grip - not as a replacement to my working TMWH (a replacement is harder to justify since the TMWH I have works just fine).

I think everyone should take a deep breath and wait for real Ryzen's to ship. The really important thing to note, in this forum, is how DCS scales with CPU cores. Will you be better off with i7-6700k @ 4.2Ghz (4 cores) or i7-6900k @3.8Ghz (8 cores, at 4 times the price). (You can substitute the appropriate Ryzen chips in the above if you like, the concept remains the same). Right now if you want the highest single core performance you get a quad-core - and 95% of games work best in this scenario. A few games scale better across more than 4 cores, but then they get hit with the lower turbo frequencies.

There are examples of just this function in the Target scripting manual.

You can execute Target at startup with a script. https://forums.eagle.ru/showthread.php?t=144584

Win!

Neil - You need Target to extend your Warthog to do anything else apart from being a vanilla A-10 stick. It helps overcome compatibility gaps between an A-10 stick/throttle and a Mig-29 or F-15 or a Huey or anything else. I cant see how you have enough data from this thread to be so authoritative in how someone should use their stick *and* that programming it using Target is actually wrong, all of the time. Especially since the question was not "how do I use my stick?" but rather "how do I solve a very specific programming question?". I think that once that subtle distinction was lost to you, and you kept following up on your initial error, you have totally clarified how clever you are. Given that there is an complete, active and expansive sub-forum dedicated to input and output for DCS, I think there might just be more than a few people that disagree with your simple world view.

No probs man, we've all been there :)

From the defines.tmh file in the Target install directory: define MOUSE_LEFT 4000 define MOUSE_RIGHT 4001 define MOUSE_CENTER 4002 define MOUSE_BTN4 4003 define MOUSE_BTN5 4004 define MOUSE_X_AXIS 9 define MOUSE_Y_AXIS 10 define MOUSE_Z_AXIS 11 Between the above and this: http://simhq.com/forum/ubbthreads.php/topics/3699590 It seems like the scroll wheel is maybe a mouse axis. Hopefully thats a start.

That is not quite straight from the manual. Your eaxmple quoted has H1U and H1D as the two keys. Your code is binding the same button on the throttle, twice. On the face of it, your doing both at once(??) and at best would get a momentary "q". What does event tester say?

Have a look at this: http://forums.eagle.ru/showthread.php?t=161759 Its not doing a "while", and you cannot interrupt it once it executes. But if you simply wish to "chain" some commands, that will do it. int counter = 0; int main() { MapKey(&LMFD, OSB1, EXEC("doSomething();")); } int doSomething() { while (counter < 200) { ActKey(DeferCall(counter, &ActKey, PULSE+KEYON+F3 )); counter = counter + 100; } counter = 0; }

There is no programming of the actual warthog. Everything is done via the software and drivers. So when it reboots the warthog is reset to default - lights on. You could use the above utility to turn off the lights on startup, or run a warthog script at startup to shut down the lights - as per the hints in the thread.

TouchBuddy will run on win10. (You'll have to hunt for it, it was written in 2006 and the author has abandoned it I think).

http://simhq.com/forum/ubbthreads.php/topics/4112787/Re:_Command_line_launch#Post4112787

And there is also this thread on SimHQ: http://simhq.com/forum/ubbthreads.php/topics/3806310/Is_there_a_way_to_assign_an_Up#Post3806310

I worked out DeferCall in a function :) When the function executes it basically forks both of the ActKey's into their own process. So in three seconds the first F3 is send, then 3 seconds later the second F3 is sent (not 9 seconds later). int FS() { if(Throttle[APPAT]) { ActKey(DeferCall(3000, &ActKey, PULSE+KEYON+F3 )); ActKey(DeferCall(6000, &ActKey, PULSE+KEYON+F3 )); } else if(Throttle[APAH]) { ActKey(DeferCall(3000, &ActKey, PULSE+KEYON+F2 )); } }

include "target.tmh" int main() { if(Init(&EventHandle)) return 1; // Send different keys depending on the state of the Autopilot switch MapKey(&Throttle, APENG, EXEC("FS();")); } int FS() { if(Throttle[APPAT]) { ActKey(PULSE+KEYON+F3); } else if(Throttle[APAH]) { ActKey(PULSE+KEYON+F2); } } int EventHandle(int type, alias o, int x) { DefaultMapping(&o, x); } There are probably other ways to do it too :) You could SEQ in a delay before the EXEC ... you might get some weird logic or edge cases because the test for the AP switch position is executed after the delay, so I dont know how to solve that issue. DeferCall in main has the same issue - delay and then call the function. So I am not sure...