Stop the Cursor Movement

[jc1]

There is a new callback for Cougar owners called SimCursorStopMovement. It’s described in 4.33 BMS Callback Updates.pdf on page 12. From the description it seemed to me that it would re-center the radar cursor. That’s a problem I got with CH Products Pro Throttle. My radar cursor drifts on my Pro Throttle microstick. So I tried this new callback for my throttle, hoping it would stop my drift, but it didn’t do anything. Is it possible to get a callback like SimCursorStopMovement for CH Products Pro Throttle microstick?

[Tiffy]

It’s only a call-back so it’ll work with CH products, how were you triggering it?

This is also probably the wrong place for this as it’s more a Tech Support or Joystick question.

[jc1]

@jc1:

There is a new callback for Cougar owners called SimCursorStopMovement. It’s described in 4.33 BMS Callback Updates.pdf on page 12. From the description it seemed to me that it would re-center the radar cursor. That’s a problem I got with CH Products Pro Throttle. My radar cursor drifts on my Pro Throttle microstick. So I tried this new callback for my throttle, hoping it would stop my drift, but it didn’t do anything. Is it possible to get a callback like SimCursorStopMovement for CH Products Pro Throttle microstick?

@Tiffy:

It’s only a call-back so it’ll work with CH products, how were you triggering it?

This is also probably the wrong place for this as it’s more a Tech Support or Joystick question.

I triggered it by assigning it to one of my DX buttons, like this: SimCursorStopMovement 263 -1 -2 0 0x0 0. If you have another way to make it work, please let me know.

I thought “Documentation” would be a good forum because my post is about some new documentation. But I don’t mind if you want to put it anywhere else.

[Icarus]

Funny thing. I had a wandering cursor in 4.32 that was fixed with a medium deadzone. 4.33 fixed it somehow with no deadzone applied??? No more wandering cursor.

[Tiffy]

No that should have worked. Do you have other shifted buttons and do they work (I’m assuming here you don’t have 9 USB Games Controllers attached to your system).

[jc1]

@jc1:

There is a new callback for Cougar owners called SimCursorStopMovement. It’s described in 4.33 BMS Callback Updates.pdf on page 12. From the description it seemed to me that it would re-center the radar cursor. That’s a problem I got with CH Products Pro Throttle. My radar cursor drifts on my Pro Throttle microstick. So I tried this new callback for my throttle, hoping it would stop my drift, but it didn’t do anything. Is it possible to get a callback like SimCursorStopMovement for CH Products Pro Throttle microstick?

@Tiffy:

It’s only a call-back so it’ll work with CH products, how were you triggering it?

This is also probably the wrong place for this as it’s more a Tech Support or Joystick question.

@jc1:

I triggered it by assigning it to one of my DX buttons, like this: SimCursorStopMovement 263 -1 -2 0 0x0 0. If you have another way to make it work, please let me know.

I thought “Documentation” would be a good forum because my post is about some new documentation. But I don’t mind if you want to put it anywhere else.

@Icarus:

Funny thing. I had a wandering cursor in 4.32 that was fixed with a medium deadzone. 4.33 fixed it somehow with no deadzone applied??? No more wandering cursor.

I use “Large” deadzone but that doesn’t eliminate drifting. I’m still hoping Tiffy will respond. BTW, do Tiffy and Icarus use CH Pro Throttle?

[jc1]

@Tiffy:

No that should have worked. Do you have other shifted buttons and do they work (I’m assuming here you don’t have 9 USB Games Controllers attached to your system).

Yes, I have other shifted buttons that work. I don’t have 9 USB Games Controllers, just Fighterstick, Pro Throttle, Pro Pedals, running with CH Products software Control Manager 4.55a.

Edit:
Also tried it with an unshifted button and it didn’t work that way either.

[Icarus]

@jc1:

I use “Large” deadzone but that doesn’t eliminate drifting. I’m still hoping Tiffy will respond. BTW, do Tiffy and Icarus use CH Pro Throttle?

No, sorry, I have a Cougar.

My system has 10 controllers and I use shifted commands fine.
4x CH MFP
Cougar
TUSBA throttle
2x MFD
BU0836A
BU0836X

Edit
BMS supports up to 16 DX devices
https://www.benchmarksims.org/forum/showthread.php?24018-Have-to-unplug-DirectX-devices-to-get-BMS-to-run-feedback-requested&p=343469&viewfull=1#post343469

[jc1]

@Icarus:

No, sorry, I have a Cougar.

My system has 10 controllers and I use shifted commands fine.
4x CH MFP
Cougar
TUSBA throttle
2x MFD
BU0836A
BU0836X

Edit
BMS supports up to 16 DX devices
https://www.benchmarksims.org/forum/showthread.php?24018-Have-to-unplug-DirectX-devices-to-get-BMS-to-run-feedback-requested&p=343469&viewfull=1#post343469

I realize it supports up to 16 devices. I only need and use 3, stick, throttle and pedals. I have no problem with all other shifted or unshifted keys. The documentation says SimCursorStopMovement was developed for Cougar, but Tiffy says it shouldn’t matter if the callback is used with CH Products equipment. My experience is that SimCursorStopMovement doesn’t work with the CH Throttle or CH Stick. I hope someone with CH equipment can demonstrate that it should work.

[Tiffy]

@jc1:

I realize it supports up to 16 devices. I only need and use 3, stick, throttle and pedals. I have no problem with all other shifted or unshifted keys. The documentation says SimCursorStopMovement was developed for Cougar, but Tiffy says it shouldn’t matter if the callback is used with CH Products equipment. My experience is that SimCursorStopMovement doesn’t work with the CH Throttle or CH Stick. I hope someone with CH equipment can demonstrate that it should work.

Have you check in the setting page that the button is firing the call-back. Go to SETUP/CONTROLLERS and press the button. You should see BUTTON: 263 and the call-back name shown. If this isn’t working but other shifted button on the same controller do then I’m out of ideas.

Unfortunately I’m all TM kit so I can’t test this either.

[Icarus]

@jc1:

I realize it supports up to 16 devices. I only need and use 3, stick, throttle and pedals.

Sorry that part was for Tiffy

[jc1]

@Tiffy:

Have you check in the setting page that the button is firing the call-back. Go to SETUP/CONTROLLERS and press the button. You should see BUTTON: 263 and the call-back name shown. If this isn’t working but other shifted button on the same controller do then I’m out of ideas.

Unfortunately I’m all TM kit so I can’t test this either.

At your suggestion I did check. What I found was that the callback name returned was “BMS - Full”. All my other buttons return the correct callback name. If you look at the file named “BMS - Full.key” in the Falcon BMS 4.33\Docs\Key Files & Input directory, you will see that the first callback is SimDoNothing, and its description is “BMS - Full”, exactly what’s returned when I followed your suggestion. The callback SimCursorStopMovement is described in 4.33 BMS documentation, “Callback Updates.pdf” on page 12, as designed specifically for Cougar owners. What I suspect going on is that if the device is not a Cougar, then the programming logic detects that it’s not a Cougar and will not recognize SimCursorStopMovement. At that point the programming logic will default to the callback SimDoNothing. Great for Cougar owners but not anyone else. Hopefully there’s a better explanation that would satisfy the CH owners because it appears from other threads that the drifting cursor is a real nasty problem. I can eliminate the drifting cursor by selecting “keyboard” for the X/Y axes in Setup/Controllers/Advanced and then assign the cursor callbacks (up, down, left, right) to DX buttons, but that just doesn’t have the same feel as the microstick.

As I was checking into this matter I came across another situation which may be nothing more than a typo, but may be more significant. In the BMS 4.33 documentation “BMS Keystrokes - old vs new. pdf”, there is a SimCursorStopMovement callback with the keystroke combo Shift Z. Shift Y is not listed in the “BMS Keystrokes - old vs new. pdf”. In the BMS 4.33 documentation “BMS Keystrokes - Defaults.pdf” there is a SimCursorStopMovement callback with the keystroke combo Shift Y, and that is in my keyfile as "SimCursorStopMovement -1 0 0x15 1 0 0 1 “TQS: RDR CURSOR - Toggle Stop Movement”. My DX entry was “SimCursorStopMovement 263 -1 -2 0 0x0 0” But even when I use the keyboard Shift Y, nothing happens.

[Guest]

We screwed it up. We implemented it (commands.h, commands.cpp) but forgot to expose it (findfunc.cpp). It will be fixed in next update.

[Predator]

@Switch:

We screwed it up. We implemented it (commands.h, commands.cpp) but forgot to expose it (findfunc.cpp). It will be fixed in next update.

I have the same problem with my TUSBA TQS cursor… Drifting to the left all the time… Hope to solve my problem with your next update???

[Jeast]

Lol I first read the topic title like it was propaganda for a new political movement. Sorry for the offtopic.

[Bolt-1]

@Predator:

I have the same problem with my TUSBA TQS cursor… Drifting to the left all the time… Hope to solve my problem with your next update???

I HAD !!! that problem with my TUSBA R2 TQS cursor. It can be corrected using the RS_HID_DEV_TOOL.

[roccio]

@Bolt-1:

I HAD !!! that problem with my TUSBA R2 TQS cursor. It can be corrected using the RS_HID_DEV_TOOL.

Can you specify, prese?

[Stevie]

The problem with the cursor is that the controller doesn’t return to a repeatable zero - you can sort of “help” it manually during calibration, then you can set your deadband and help it more…but it takes some fiddling.

If you really want to go full-geek, you can note that the for the Cougar the controller acts as a mouse and describes a Lissajous in output…for a converted Cougar TQS that I use with FAF Mac I developed a ControllerMate scrip that determines which quadrant the controller is in and then outputs the appropriate Arrow key command for cursor control - this kills my drift very nicely, and also is very controllable. I still had to do some deadband setting. I’m pretty sure you can/could do the same thing using Foxy (and probably to an even finer extent), but that’s only for the Cougar.

BTW - I have a TUSBA R2 and was able to get the drift out by just adjusting deadband in a combination of places - R2 setup, BMS, CCP, Windows…again fiddly trial and error, but it can be done.

[roccio]

Thank you Stevie, I have TUSBA R1 and have not installed any probram for setup the device. I use only Windows(10) control panel. I will download and try the tools from RealSimulator.

[Ninja]

Moved to tech support as documentation was wrong place