Microstick Mouse Control In-game

[Martin_Lee]

I am not entirely sure if I should be posting this on Cougar sub-forum or here, since I am trying to use Cougar with TARGET software. It seems that the problem I am having isn’t so much a problem with what hardware I use but with the TARGET Software.

I am having the same problem as WeakLink is having in his post:
https://www.benchmarksims.org/forum/showthread.php?15799-Microstick-Question&highlight=TARGET+Microstick

I have been trying to use microstick to control the mouse in the shifted layer (S3 held). It seems that when in the 3D world, the mouse speed is extremely fast, to the point that if I set a sensitivity that is useful in 3D world, it would become too slow to be useful in 2D or in Windows. This problem isn’t hard to solve, I just need to change to a different sensitivity with another button.

The main problem, however, is what is described in the above link. Whenever I do a mouse click with the joystick (doesn’t seem to matter which button I map the mouse click to), the cursor jumps. This jump occurs before the mouse click command is done, meaning you could not click any buttons with it.

Whilst I could, and don’t actually mind or have any trouble what so ever to, use a mouse or other pointing devices, I am just a bit lazy sometimes to move my hand :oops: I am just wondering if this is a universal problem or isolated case, and that if anyone had found a workaround for it?

p.s. I could still use the Cougar Drivers, actually, and they work just fine. I just brought a T16000M for when I am in college. That’s why I started to learn using TARGET software.

[AV8R]

I have found that the Cougar TQS cursors will drift or jump if:
a. They aren’t calibrated near perfectly in the CCP calibration routine, and use manual not auto calibrate mode when using/flying
b. Sometimes the cursor 4-way pot and switch go bad. Nothing in software will fix it.

In the BMS Control avionics page, where you assign the cursor X & Y axes, you can set a dead zone, try different settings to make the cursor less sensitive to touch or calibration error. See if that helps any.

I use a Cougar FCC3 using only the CCP to calibrate, and BMS contol GUI to assign axes, and modified BMS key file to assign callbacks. No need for TARGET unless I’m using a WartHog where I want to program the LEDs or combine controllers into one virtual controller.