Still Having Radar Cursor Issues
-
If you’re binding cursor slew keys in SST, you need to bind both the key press AND release, otherwise occasionally the game registers that a slew key is being held down. This should fix most of the slew problems.
Your problem sounds exactly like what might occur if you haven’t done ^this in SST.
Obviously check drivers as well, but I suspect a quick edit in SST will solve your issue
-
What version of the driver are you using? And OS version? Did you pull the “recent” drivers from the logitech site instead of the old unsigned MadKatz drivers?
Running Windows 10, the stick drivers are the Logitech drivers. Actually, I was having fewer problems with the MadCatz software, but the cursor issue was why I swapped to the Logitech. I may go back and try that again.
-
Your problem sounds exactly like what might occur if you haven’t done ^this in SST.
Obviously check drivers as well, but I suspect a quick edit in SST will solve your issue
Took a look at this. The only way I really know how to check that is in the SST test page. I get a black F10 on the button press, then gray when I release, goes to blue repeating if I hold it. So I THINK its registering the release. I remember seeing a setting somewhere while I was vainly trying to program through the SST last month (that doesnt work for BMS anymore), but its going to take some digging to find it again.
I also took the opportunity to expand my dead zone on the ministick. I have had a nagging feeling this could all be a fault in the stick itself but I have also played around with the cursor function outside the sim, as a normal mouse function, and everything seems to function normally. Admittedly, that doesn’t mean much, but so far it runs smoothly.
-
…. I also took the opportunity to expand my dead zone on the ministick. I have had a nagging feeling this could all be a fault in the stick itself but I have also played around with the cursor function outside the sim, as a normal mouse function, and everything seems to function normally. Admittedly, that doesn’t mean much, but so far it runs smoothly.
Hmmm …. you might be on to something.
When I dropped the SST programming from my mini-stick and made it a DX axis, it would continuously scroll … left or left/up, iirc. It still would, except I set the deadzone in BMS to ‘large’. In your case, it would be same as continuously pushing Fxx.
At one point I also had the issue you describe where it would ‘push’ F10 (or F11?) constantly and was giving me fits in misc open widows on the PC.
In the original Flounder keyfiles, I’m pretty sure there were no zones or bands … just F8, F9, F10 and F11 keybind emulation. Later I tried using arrow keys (<-- -->), but those also ‘drifted’ or worked inconsistently.
-
I have come to the conclusion its time to call off the dogs. I’ve been approaching this as an issue limited to BMS and/or the profile but I decided to build a Black Shark profile using the profile editor and give that a shot for a while. Surprise, surprise!! I’m running into nearly identical issues there as well. This has brought me to the conclusion that its something either in the sticks or my computer that’s causing all of this. I had run BS a few times prior to getting BMS up and running and hadn’t seen the issues, but during those runs I was just flying off the sim profile which was very limited in function. Now that I have tried building a more in-depth profile I’m starting to see those bugs. I can’t figure out if its stick hardware, computer hardware (USB ports), logitech software, or something in Windows 10, but whatever it is I don’t see getting to the bottom of it before building my new desktop.
Thanks for everyone’s time and effort in trying to figure this out, I just wish I had figured it out before wasting everyone’s time. Guess its time to start saving up money for that new desktop and set of Cougar sticks.
-
I have come to the conclusion its time to call off the dogs. I’ve been approaching this as an issue limited to BMS and/or the profile but I decided to build a Black Shark profile using the profile editor and give that a shot for a while. Surprise, surprise!! I’m running into nearly identical issues there as well. This has brought me to the conclusion that its something either in the sticks or my computer that’s causing all of this. I had run BS a few times prior to getting BMS up and running and hadn’t seen the issues, but during those runs I was just flying off the sim profile which was very limited in function. Now that I have tried building a more in-depth profile I’m starting to see those bugs. I can’t figure out if its stick hardware, computer hardware (USB ports), logitech software, or something in Windows 10, but whatever it is I don’t see getting to the bottom of it before building my new desktop.
Thanks for everyone’s time and effort in trying to figure this out, I just wish I had figured it out before wasting everyone’s time. Guess its time to start saving up money for that new desktop and set of Cougar sticks.
The issue is with the drivers. Windows (7 and 10) natively sees the ministick as a mouse, and the magic keyboard drivers were garbage to begin with–this driver holds old SST programming and fires at seemingly random intervals, but its really due to the overly sensitive sensors in the stick. This is why I recommended removing the SST altogether. I use a 52 Pro with no issues at all, but using the stock Windows drivers. It is a little involved to completely remove the SST stuff, including the drivers, but the process can be found with a quick google search. The only issue with this in BMS is that you have to have the “Controller” window open in the background while flying BMS to enable all the buttons. Control Panel->Devices and Printers->X 52 Controller Properties Just leave the properties window open behind the game. Doing so will enable you to use the mouse wheel on the back of the throttle (Up/Down and Push), as well as the push button function of the roller by the LCD, and the Mode Selector rotary in the game.
-
The issue is with the drivers. Windows (7 and 10) natively sees the ministick as a mouse, and the magic keyboard drivers were garbage to begin with–this driver holds old SST programming and fires at seemingly random intervals, but its really due to the overly sensitive sensors in the stick. This is why I recommended removing the SST altogether. I use a 52 Pro with no issues at all, but using the stock Windows drivers. It is a little involved to completely remove the SST stuff, including the drivers, but the process can be found with a quick google search. The only issue with this in BMS is that you have to have the “Controller” window open in the background while flying BMS to enable all the buttons. Control Panel->Devices and Printers->X 52 Controller Properties Just leave the properties window open behind the game. Doing so will enable you to use the mouse wheel on the back of the throttle (Up/Down and Push), as well as the push button function of the roller by the LCD, and the Mode Selector rotary in the game.
Would this also cause the LED screen on the throttle to go dark? That’s why I’m thinking its hardware related. Most of the time, about the same time the mini stick starts goofing the backlight on that screen will shut off, the profile notification text will still be there just no back light and I start losing functions on the stick. The MadCatz version included the original stick settings and adjustment pages. I had noticed even then that several of the sliders and knobs would ‘jiggle’, even when the stick wasn’t being touched. I had to set some fairly large dead zones to accommodate for that jiggle. Unfortunately the new logitech package didn’t include that setup page.
-
Would this also cause the LED screen on the throttle to go dark? That’s why I’m thinking its hardware related. Most of the time, about the same time the mini stick starts goofing the backlight on that screen will shut off, the profile notification text will still be there just no back light and I start losing functions on the stick. The MadCatz version included the original stick settings and adjustment pages. I had noticed even then that several of the sliders and knobs would ‘jiggle’, even when the stick wasn’t being touched. I had to set some fairly large dead zones to accommodate for that jiggle. Unfortunately the new logitech package didn’t include that setup page.
Yes, that’s also a part of the driver issue. That’s also the other downside to using the Windows driver, it won’t display the command name in the LCD window when you press a button because you aren’t giving any commands a “name” for it to reference in SST.
-
Did you manage to solve your cursor problem? I have the exact same problem but only if its in window mode. After i put it back to normal and ticked “Disable full-screen optimisations” <<(dont know if that helped)
all works well -
Add a deadzone in the profiler software, then calibrate the stick. Hopefully you’ll have your analog axis return close to zero. The calibration works for analog axis that center automatically (spring, etc.).
Did you manage to solve your cursor problem? I have the exact same problem but only if its in window mode. After i put it back to normal and ticked “Disable full-screen optimisations” <<(dont know if that helped)
all works wellAre you guys talking about the analog MFD cursor axis, or the mouse cursor? I’m confused.
For the mouse cursor you can disable the programmable Saitek pseudo-mouse in Device Manager while still using the profiler software.
-
there is a bug that will cause the cursor to sneak up but I’ve only noticed it in AA mode and it only happens if your stick isn’t centered when you load in, for me was happening because the hardware was defective.
Call logitech , if it’s been less than two years they own saiteks liability.