SGT Coyle

Discord is not looking for a "Button 4"(DX4) push form TMWH Throttle. It's looking for a DX4 from Windows. Discord does not differentiate controllers like DCS does. If you use TARGET, your controllers will be combined into one virtual controller and only DX4 button push could be assigned.

As Shadow_1stVFW said, it could be a setup or a desire. In my case, it's a disability. I also use Oculus, but some switches and knobs are way down low and to the back. Due to a helo crash I'm left with a limitation on how far I can articulate my neck to be able to put the cursor on a switch or knob. I really need to have a keyboard command to be able to map it to controller.

Close Thrustmaster "Fast service" from the task manager. That should close everything TARGET related. You may have to re-enable to run TARGET. Then make sure you run TARGET as admin.

After spending some time with Tech support on the phone, nicest gal I've ever had an issue with, I got the stick Drivers to update and the firmware to update. Ya! Maybe not a piece of shit!.... WTF! TPR Rudder drivers messed up. No properties window available. Firmware install fails.

There is a limit of 8 axis per controller. That's a windows thing. The good part is that the limit is for each controller. The Stick, Throttle, Rudders, MFDs (Left & Right respectfully), are all individual controllers. They are seen as individual controllers in DCS and none of these controllers have more than 8 axis by themselves. If you use TARGET software, the controllers are combined to makeup the virtual controller. DCS will see this as one controller and you will be limited to 8 axis. If you use Stick(X and Y axis), Throttle (witch has 5 axis available for mapping), and Rudder with toe brakes(X,Y and Z axis), you could run out of axis pretty quick. For the A10C a complete setup has more axis than are availible with the windows limitation. Stick 2 axis (X,Y) Throttle 5 axis (Z and RZ- Left and Right Throttles, X and Y for Slew, Slider for zoom control ) Rudder 3 axis (Z for rudder and X,Y for toe brakes) ___________________ 10 axis But all is not lost. You can modify the TARGET .tmh file to eliminate the Rudder Pedals from the virtual controller and still have them seen by DCS as an individual controller. That will leave you plenty of axis to map to stick and throttle. I think this is the trhread you were looking for: https://forums.eagle.ru/showthread.php?t=219716&page=2

It doesn't work with the TARGET Script Editor. There's no way to assign keyboard presses to buttons. Very disappointed in this release.

Just got mine and there's no TARGET button mapping. Unless I'm missing something. I tested with a simple profile and it just gives the native DX button presses. What a piece of shit.

:):):):):)This is my favorite thread.:):):):):)

Using TARGET, I assigned several views to the Trim Hat and the Button 1. For the Trim Hat I use it for all the trim functions Nose up, down, left, and right. Shifted-In layer I assign a sequence of F1, F2, F4. On a shifted-In layer I assign a sequence of F1 and F10, on Button 1. //Trim + MapKeyIO(&Joystick,H1U, SEQ( F2_Aircraft_view, F4_Chase_view, F1_Cockpit_view), Trim_Nose_Down); MapKeyIO(&Joystick,H1D, SEQ( F10_Theater_map_view, F1_Cockpit_view), Trim_Nose_Up); MapKeyIOUMD(&Joystick,H1R, Trim_Rudder_Right, Trim_Right_Wing_Down); MapKeyIOUMD(&Joystick,H1L, Trim_Rudder_Left, Trim_Left_Wing_Down); There's an example of the TARGET .tmc code I use for the Trim Hat.

Try adding a little dead zone to the center and see if it helps. There's so much stuff hanging off that aircraft I'm amazed it will trim at all.

I don't know why it was closed, but at least it was reported. Frustrated that it only took 6 months. I hope it doesn't take another six moths to get corrected.

Any more news on this OP?

Thanks for the reply. I got the axis assignments to work. The issue was not the axis assignments but some confusion as to the trigger switch operation. I'll take that to a different thread.

I dread adding another thread, so I'm putting this hear to sound out any experience out there. I assigned the Radar Stick axis to my TM mini stick. The mini stick axis are working, But I can't get any response for the Radar or the EP-13 (RB-75 sight). Are the axis for the Radar Stick working or is it keyboard inputs only? I'm working with Release 2.5.5.33184

I believe it's a two stage trigger like the WH. T0->T1->T2

I would imagine the the Super T operates from a much less improved airstrip. A big plus when talking about low intensity warfare, for lack of a better term.

I don't think you're nitpicking. You're cherry picking. And offering up that test video as their "Monthly" / "Quarterly Update Video" is a stretch well and beyond the reach of any reasonable person. I thought it would be insulting to asked if that was intended as their June update in the comments, so I didn't, but since you brought it up, I will.

They also said there would be a new video in June. So...

So where's the update video for June?

Got it and installed it yesterday and am very happy. Do people like the square pattern bezel or the round that comes ready to install?

+1

But this is my wish. Maybe your wish is for me not to get my wish, but this is my wish list thread. Go get your own and stop trolling me.

I never thought of that.

Yes, but tough to see and compare if in VR. The Windows controller setup window keeps dropping behind my game even when I'm not in VR. I like that Control indicator. It really helps when I' trying to determine weather there's a problem with the hardware or the software.

Slew Axis on the control indicator. Mostly for trouble shooting. I see some modules have erratic behaviors, but it's hard to tell if its input signal issues or just buggy performance on the module side. Or mission related.