[TM F18 Stick Grip Wobble]

Thanks,

I'll be interested in their reply. In the interest of preserving my warranty, I will wait until they send me permission to do that.

I do appreciate the piece of mind you provided, that it's not serious issue.

Thanks.

[Georgian Hammer - pilot leaving plane]

That'll teach you to be fickle with the platform.

[TM F18 Stick Grip Wobble]

I have a loose connection where the black grip and the mounting shaft meet. Not in the mounting nut. The connection to the base fits very tight, but the play still exist in the grip. It's not severe, but my experience with these things is, they only get worse with time.

The looseness is only in the back and forth direction. Not a great deal of play, but just enough to be annoying. :joystick:

 

 

 

That is what I reported to Thrustmaster Customer Service today after an initial phone conversation. Apparently I'm the first to have this issue.

 

Ya me!

 

 

Thought I'd put this here in case others experience this as well.

 

 

An FYI. Warranty for those of us outside the EU only have a 1 year warranty from the time of purchase. So if you have an issue don't hesitate to inform them an get it documented.

[Mini VR Desktop]

Windows Mixed REality

Thanks

[Thrustmaster Driver Issues]

My TM WH stick and throttle have always showed up in the "Devices and Printers" page as Multimedia Devices. MFDs and TPR rudder are in Devices section.

 

 

I exempt TM devices from driver updates unless I initiate from a manual DL from TM site.

[Mini VR Desktop]

WMR?

[TARGET program joystick trouble]

I am having problems using the target program.

 

For some reason, the warthog joystick doesn't always register with TARGET, so I have to fiddle with the windows recognition software to get it to work. But what's really frustrating is that when this happens, it completely erases all the buttons and axes assigned to the stick in DCS, even in the lua files, causing me to have to remap the buttons on the joystick whenever this happens, anyone know the solution, or what causes it?

 

I don't plug it into USB 3.0 ports.

 

 

Are you using the GUI or the SE(Script Editor)?

 

I don't know anything about the GUI, but I can share some best practices I follow with SE.

 

1. Add this to your script:

   Configure(&Joystick, MODE_EXCLUDED);    //Needed for F18 grip to work better.

   or

   Configure(&JoystickF18, MODE_EXCLUDED);    //Needed for Standard grip to work better.

   
   

2. In Windows Device Manager, check to see that power management is not checked for usb devices / root hubs
   
3. In Windows Device Manager, check to see that power management is not checked for HID devices
   
4. Unplug stick when not in use. Seems to work fine after plugging in
   

As for losing the bindings in DCS. I don't know. My DCS setting page has a column for "Thrustmaster Combined", that is the TARGET Virtual Controller, combining all your TM products present in the script. Allowing you to map DX_Buttons/Axis , not key presses, to DCS in that column. If you have mapped anything in there and hit the OK button at the bottom of the page, then it was saved. When ever your TARGET Virtual Controller is present, your bindings should be there.

 

If you see TM Joystick, Throttle, MFD..., column headings in the DCS settings/controls page, DCS is not seeing your TARGET Virtual Controller. For what ever reason.

 

Whatever you mapped under the TARGET Virtual Controller heading, as described above, will(or should) be there when DCS reestablishes the TARGET Virtual Controller.

Add this to best practices:

Never plug/unplug or run/stop SE script while the DCS settings page is open. That scenario has only worked out fewer times than the Sun has failed to rise in the East.

I hope this helps. I use TARGET a lot and see the issues you describe rarely any more. It mostly reappears after Windows Update.

[Can I get non Thrustmaster stuff into the T.A.R.G.E.T]

Copy that sausage finger. What are you going to use as a controller?

I use a tinsy3.6 for my controller. Use tinyduino for the programming.

[Thrustmaster TPR versus Slaw Device RX Viper V2]

This is by no means a through review

 

 

You could have fooled me. He went down a pretty detailed list of comparisons with accompanied conclusions offering no empirical data to support his claims.

 

Sounded like he was trying to influence the market place to me.

 

 

 

I may have been a little short with my immediate reply, but the triggering mechanism for me is the callus manner in witch he declared one product to be trash and the other to be Gods gift to Simmers. It may be the beginning and end of all rudder pedals, but he could have expressed his excitement without tearing the other guy down.

[Can I get non Thrustmaster stuff into the T.A.R.G.E.T]

I don't think TARGET will recognize any usb device other than what's listed in the target.tmh and I don't think you can just add usb IDs.

 

Can I ask, what is it you want to change, or aren't happy with? What if you just disassembled the MFD and used the pcb/usb interface in your new device. Then I would imagine TARGET would just see it as a TM MFD and Bob's your uncle.

[Thrustmaster TPR versus Slaw Device RX Viper V2]

he only thing that I can't make it work right it's the same amount of pressure on both toe brakes, sometimes I apply more input on the right or in the left brake, but it's manageable and since the VKB olny had virtual toe brakes I need to get used to it.

 

 

I found that a little dead zone on the extremes eliminated this issue.

[Current Warthog HOTAS Availability UK]

Check Amazon.

[Collective owners?]

It's threads like this that make life with the woman difficult. Now I have to make a collective to go with my pedals.

[Thrustmaster TPR versus Slaw Device RX Viper V2]

I must say your comparisons don't delve to deep into detail.

I half tempted to report this as advertising.

 

 

But, I'd like to know what makes the electronics of SLAW better than TPR?

[Is it possible to use the Cougar microstick without Foxy and Target?]

In DCS mapping screen, it should be joy_RX and joy_RY. I always have to manually select the axis from the drop down menu mapping page.

[Some help understanding how the key bindings work in the sim please]

Not only do you have settings for all Modules, but there's also a "General" category. I tend to erase all mappings in this category after every update.

 

 

If you use TARGET with your TM devices, they'll be combined into a "Thrustmaster Combined" column. This presents it's own set of challenges when mapping and saving bindings. If your mapping a Direct-X button, it goes in the "Thrustmaster Combined" column. If your mapping a key stroke, it goes in the "Keyboard" column regardless of the device your using.

[Upgrading my HOTAS to the Warthog?]

https://deltasimelectronics.com/products/thumbstick-slew-sensor-adapter would be definitely worth a look, albeit perhaps not overly attractive for a newly purchased device.

 

I've had my WH for around 3 years now and this mod has given the throttle's slew control a totally new lease of life.

 

 

That's gospel brother.

 

 

Don't be afraid to try TARGET Script Editor. It beats the hell out of the GUI and there's so much more you can do with the Stick and Throttle.

[Realteus ForceFeel Haptic Pad Review]

there's always small claims court.

[Radar stick question]

For the enthusiastic users of TARGET, a function to spit the two stage trigger.

One issue I've always had was how to reliably split the two stage trigger when using TARGET. The problem is that physical trigger is made up of to switches actuated by a cam. Unfortunately when trigger 2 is actuated, trigger 1 is also actuated. That makes doing things like the radar stick tricky to map.

 

 

I have finally split the triggers.

 

 

Put this in a .tmc script

 

//Trigger
MapKey(&JoystickF18,TG1, EXEC("Trigger();"));//    Split Trigger Function Call TG1
MapKeyR(&JoystickF18,TG1, CHAIN(
                               EXEC("ActKey(DX24);"),
                               EXEC("ActKey(DX25);"),
                               EXEC("ActKey(PULSE + KEYON + DX23);")
                                   )
                                       );// Simple CHAIN to Release TG1 & TG2

MapKey(&JoystickF18,TG2, EXEC("Trigger2();"));//    Split Trigger Function Call TG2
MapKeyR(&JoystickF18,TG2, CHAIN(
                               EXEC("ActKey(DX24);"),
                               EXEC("ActKey(DX25);"),
                               EXEC("ActKey(PULSE + KEYON + DX23);")
                                   )
                                       );// Simple CHAIN to Release TG1 & TG2  

and this in a .tmh file. Name it whatever you want and "include" it in you script.

//*************************************************************************************************
//*******___ Viggen ___**********
// Trigger Split for Viggen Radar Fix

int    Trigger1()    {
   if(JoystickF18[TG1])
   ActKey(KEYON + DX24);
   }
   
int Trigger2()    {
   if(JoystickF18[TG2])
   ActKey(DX24);
   ActKey(KEYON + DX25);    
    }

Make sure to map radar stick controls in DCS.

 

 

• T0 to DX23
  
• T1 to DX24
  
• T2 to DX25
  

This has worked a hoot for me.

[VoiceAttack: Programming Wingman AND Flight AND Element?]

Did you look at ViaComPro? It works. It's worth the some odd dollar.

Everything is already mapped for you. It takes a bit of getting used to but it works in the end.

https://www.vaicompro.com/

https://forums.eagle.ru/showthread.php?t=198297

[Getting an RTX 2080 TI....]

dburne

 

Thanks for the instruction.

[Warthog Mapping Chart Editor]

I would love to see direct import of TARGET Script Mapping.

Example would be:

 

MapKey(&Joystick, TG1, Macro Name I use for the button); (I normally use the Trigger_First_Detent as a macro here)

or

MapKey(&Throttle, LTB, Change_to_Pilot_Pit); (witch is a macro I use for switching seats in the F14)

 

 

In this case you would have two variables that are in a predictable format. The actual button name (TG1, S2, H2U...) that can point to a specific text field to be filled, and a variable location that already has text to put in the proper field(Trigger, Weapon_Release, Flaps_Down...).

 

 

I hope that makes sense.

 

Regardless of what you decide. This is a great tool. I'm having much fun making my profiles. I look forward to further developments.

[Control setting lever request for gear and hook.]

So I've got mine set to operate the Gear Up, Gear Down, Hook Up, Hook Down, and the Nose Strut Kneel (a.k.a. Launch Bar Extend). Works like a freaking charm.

It makes me feel so authentic.

[Getting an RTX 2080 TI....]

(make sure you remove the old driver correctly and install the latest Nvidia driver for the 2080 ti (which as of now is 436.30 I believe))

 

 

Can you expound on that? How do you remove the driver correctly? When I update I always do a clean install.

[Control setting lever request for gear and hook.]

It doesn't register if you use a throttle lever.

 

 

Put this little didy in your TARGET Script and you too can have a gear handle on the little grey lever.

 

 

 

KeyAxis(&Throttle, THR_FC, [color=#ffffff]0[/color], AXMAP2( LIST(0,30,70,100), Gear_up, 0, Gear_Down)); 

 

 

But, asking Heatblur to go to the trouble to assign an axis to a binary switch, that is not something I can get behind.