Previous Thread
Next Thread
Print Thread
Rate This Thread
Hop To
#4256571 - 05/05/16 05:18 PM Microstick Blues  
Joined: Sep 2010
Posts: 2
SupeRaven Offline
Junior Member
SupeRaven  Offline
Junior Member

Joined: Sep 2010
Posts: 2
CA
Ever since I dusted off my Cougar last October I've had a handful of issues. A recent re-install of Win10 64bit has resolved all but one. I'm unable to do anything with the microstick in TARGET. Mapping axes to it does nothing and attributing keys to it does occasionally cause a single input of the character bound to the peak of Y-axis. The microstick works fine when I bind axes to it in CCP. I haven't messed with FOXY but I think it would work.

I've read on some forums that there is an error in one of the TM provided tmh files that gets included (either defines.tmh or hid.tmh) which causes issues with the microstick. I've attempted those proposed solutions with no luck. I'm hoping someone will have some insight to this issue.

Interesting post-Win10 re-install note, the "combined" device no longer shows up in device analyzer when running the config in TARGET. My Saitek pedals and 360 controller show up in DA. The "combined" device does show up in other applications.

PS I would like to use TARGET over learning FOXY since I have the TM MFDs too.

Regards,
SupeRaven

Inline advert (2nd and 3rd post)

#4256830 - 05/06/16 02:33 AM Re: Microstick Blues [Re: SupeRaven]  
Joined: Sep 2010
Posts: 2
SupeRaven Offline
Junior Member
SupeRaven  Offline
Junior Member

Joined: Sep 2010
Posts: 2
CA
Corresponding with the new Thrustmaster hardware, there is an update version of T.A.R.G.E.T. out now. I'm going to give this a try.

Update:Device analyzer is working again and I've now seen that RDR_Y and Ant_Elev appear to share an axis when TARGET creates the config/script.

Last edited by SupeRaven; 05/06/16 02:56 AM.
#4262042 - 05/20/16 01:36 PM Re: Microstick Blues [Re: SupeRaven]  
Joined: May 2010
Posts: 6
Marcocom Offline
Junior Member
Marcocom  Offline
Junior Member

Joined: May 2010
Posts: 6
United States
possibly the TARGET config. good idea. but i did have the same problem when i did a fresh install of DCS for 2.0 - turned out to be how i was mapping the axis specifically (and the shift keys) in DCS. i had to reapply that axis to get it working right. just an FYI

specifically the SLEW-X and Y settings in DCS

Last edited by Marcocom; 05/20/16 01:37 PM.

Moderated by  RacerGT 

Quick Search
Recent Articles
Support SimHQ

If you shop on Amazon use this Amazon link to support SimHQ
.
Social


Recent Topics
Carnival Cruise Ship Fire....... Again
by F4UDash4. 03/26/24 05:58 PM
Baltimore Bridge Collapse
by F4UDash4. 03/26/24 05:51 PM
The Oldest WWII Veterans
by F4UDash4. 03/24/24 09:21 PM
They got fired after this.
by Wigean. 03/20/24 08:19 PM
Grown ups joke time
by NoFlyBoy. 03/18/24 10:34 PM
Anyone Heard from Nimits?
by F4UDash4. 03/18/24 10:01 PM
RIP Gemini/Apollo astronaut Tom Stafford
by semmern. 03/18/24 02:14 PM
10 years after 3/8/2014
by NoFlyBoy. 03/17/24 10:25 AM
Copyright 1997-2016, SimHQ Inc. All Rights Reserved.

Powered by UBB.threads™ PHP Forum Software 7.6.0