Still Having Radar Cursor Issues
-
Ive been trying to save another thread but I havent found anything so far.
When I first started flying again I had an issue where the cursor took off uncontrollably across the MFDs but that was just one time and I havent seen it again since. But the last 2 weeks has become rather frustrating with this radar cursor and now seems to be getting worse.
It doesnt matter if Im running in Campaign mode, Instant Action, or Dogfight. Everything starts out normal, take off, weapon and TGP pod setup, and ingress all go smooth. Everything works fine including the cursor in both radar and TGP. But usually right before time to drop, sometimes after the first drop if I miss with the first bomb, I lose a cursor direction on my stick, usually cursor down first. Up, left, and right will continue working normally, but nothing on down. A couple of times I have tried to limp through the mission but if I screw around long enough I will start losing other directions. Usually cursor right follows, and then up later if I keep going.
Im pretty sure its not sim related, using the function keys still operates the cursor normally. That leads me to believe its either a hardware issue with the sticks themselves, or software related to the programming. I didnt notice it as much until I started using an Android tablet for the MFDs, but this could simply be coincidental. But now it doesnt matter if I run the tablet software or not, I still lose the functions.
I recently found a thread where Logitech had released a new programming software update so I scrapped the MadCatz software, which is also about the same time all this started. Should I go back to the MadCatz software and give that a shot? It seemed pretty clear in that thread that most people were having better results with the Logitech software.
-
I think its either a rotary that’s open or a key file conflict - when ever I get strange things happen on an otherwise stable set up its usually a rotatory that’s not centred - which sticks do you use ?
-
I also have had problems 2-3 times with the cursor. It blocks while aiming with the TGP/radar but being an extremely rare event to me (I fly regularly two times a week with my wing and also train offline) I can not circumstantiate the causes.
I have an X-52 mainly via DirectX: I just use the software to convert the mouse cursor.
And I also know of another pilot who experienced it, altough I don’t know his setup.
-
Swap out your Direct X functions for key file commands - keep your existing HOTAS profile - change all direct X commands for once using key board input from you key file and save under a different profile name - then try it with new profile on HOTAS - I bet that cures it ;0)
-
My sticks are X52 Pro, using Flounder’s profile I got from a thread here.
I’ll see if its DX programmed or keys, don’t remember seeing key bindings while looking at the profile so I’m pretty sure it’s DX.
-
My sticks are X52 Pro, using Flounder’s profile I got from a thread here.
I’ll see if its DX programmed or keys, don’t remember seeing key bindings while looking at the profile so I’m pretty sure it’s DX.
Cursor slew is Keys …. the only thing in the profile that is Saitek SST programmed. I gave up.
Switched the slew stick to axes and assigned them in BMS. Lost the rudder … which for me was OK because I don’t have a dedicated rudder and the warthog stick doesn’t have a twist rudder. Assigned ‘roll linked steering’ and haven’t looked back. One could discard the twist rudder on the X52/52 Pro and do the same thing.
-
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.
-
I think its either a rotary that’s open or a key file conflict - when ever I get strange things happen on an otherwise stable set up its usually a rotatory that’s not centred - which sticks do you use ?
Just getting back from work, 21 day rotation, I will test this theory. It seems pretty logical, though 3 directions generally work fine. Its always the cursor right that goes first, sometimes the other 3 will fall off over time but I normally get POed and back out before it gets to that point.
-
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.
I haven’t programmed anything, I’m running a profile someone else built. I haven’t had the guts to try the profile editor out for myself. I’m afraid I would wind up screwing up the profiles of everyone on this forum. That’s just how my luck goes.:oops:
-
I haven’t programmed anything, I’m running a profile someone else built. I haven’t had the guts to try the profile editor out for myself. I’m afraid I would wind up screwing up the profiles of everyone on this forum. That’s just how my luck goes.:oops:
save the one that works ok’ish then try editing and save under a different name - that way you can revert - its the way we all do it ;0)
-
I have throttle dpad set up as a cursor slew and in a shifted mode as a CMS. To me a similar issue happens (cursor moving until stopped) most often in an air combat when I switch between controlling FCR and using countermeasures. As if the last command on that dpad gets stuck. My setup is purely through XLS file, no SST (or rather an empty SST profile). Any solution?
-
I have throttle dpad set up as a cursor slew and in a shifted mode as a CMS. To me a similar issue happens (cursor moving until stopped) most often in an air combat when I switch between controlling FCR and using countermeasures. As if the last command on that dpad gets stuck. My setup is purely through XLS file, no SST (or rather an empty SST profile). Any solution?
This forum is littered with SST problems. Do you use SST on other games? If not, uninstall it. If you do, you have to have very deliberate key presses. The stuck keys issue is almost always something to do with a “shifter” key such as SHIFT, CTRL, ALT being released prior to the actuator key. It can be painful in SST to do it correctly, and just as painful to be deliberate in the game. I uninstalled all SST related software and use the ministick for the cursor, never have any issues at all. You have to give up one of the other axes to do it, but if you own an xbox, you can easily plug in an xbox controller to get the extra axis back (and then some). For instance, I disable the twist rudder and use one of the sticks on an xbox controller for rudder/NWS steering. The up side being I also get an additional 8 buttons, 4 axes, and a hat (D-Pad) by using the XBox Controller. The key is to set it up so that having your hand on the XB controller instead of the throttle isn’t detrimental. So things like toe break, steering, and Parking Break are good options to shift to the xbox controller, because you will rarely be using those things in time critical situations where you need a hand on the throttle.
-
Well, I’m not real sure what I just found out.
Made sure all my rotaries were centered in neutral positions and went into Instant Action just for a quick test. Right off the bat I had no right cursor, not even a wiggle. Tested the other directions and everything worked normally to start with until I tried to use the F13 to pull the cursor back to center. Worked fine until I used the stick again. At that point right AND up no longer worked. Played the keyboard keys again and the cursor took off sliding down until my radar was at minimum range. Used the keyboard to recenter again and the next time I used the stick control the cursor took off to the left, ALL other directions were locked out.
Crazy, right? Well it didn’t stop there. Closed out the sim, opened my Firefox browser to update the thread. As soon as I clicked on the address bar the browser screen starts jumping as if I was repeatedly pressing the F10 button, kept flashing the File/Edit/View toolbar at the top of the window. Unplugging the sticks from the USB port had no effect. I could get it to stop by pressing F11 but as soon as I clicked the address bar again the F10 would start jumping again. Closed Firefox to reset it, as soon as I opened it back up it all started again, sticks still disconnected. Finally decided to restart my computer, even that was being affected. I watched the ‘working’ icon spin for several minutes before I finally hard reset it.
-
This forum is littered with SST problems. Do you use SST on other games? If not, uninstall it. If you do, you have to have very deliberate key presses. The stuck keys issue is almost always something to do with a “shifter” key such as SHIFT, CTRL, ALT being released prior to the actuator key. It can be painful in SST to do it correctly, and just as painful to be deliberate in the game. I uninstalled all SST related software and use the ministick for the cursor, never have any issues at all. You have to give up one of the other axes to do it, but if you own an xbox, you can easily plug in an xbox controller to get the extra axis back (and then some). For instance, I disable the twist rudder and use one of the sticks on an xbox controller for rudder/NWS steering. The up side being I also get an additional 8 buttons, 4 axes, and a hat (D-Pad) by using the XBox Controller. The key is to set it up so that having your hand on the XB controller instead of the throttle isn’t detrimental. So things like toe break, steering, and Parking Break are good options to shift to the xbox controller, because you will rarely be using those things in time critical situations where you need a hand on the throttle.
This is about the only thing I run the SST software on. I also have DCS Blakshark but haven’t flown it since getting BMS back up.
The idea of using other controllers is interesting. I’ve been curious about such ideas, just never tried it. I’m going to need more USB ports. LOL
-
Well, I’m not real sure what I just found out.
Made sure all my rotaries were centered in neutral positions and went into Instant Action just for a quick test. Right off the bat I had no right cursor, not even a wiggle. Tested the other directions and everything worked normally to start with until I tried to use the F13 to pull the cursor back to center. Worked fine until I used the stick again. At that point right AND up no longer worked. Played the keyboard keys again and the cursor took off sliding down until my radar was at minimum range. Used the keyboard to recenter again and the next time I used the stick control the cursor took off to the left, ALL other directions were locked out.
Crazy, right? Well it didn’t stop there. Closed out the sim, opened my Firefox browser to update the thread. As soon as I clicked on the address bar the browser screen starts jumping as if I was repeatedly pressing the F10 button, kept flashing the File/Edit/View toolbar at the top of the window. Unplugging the sticks from the USB port had no effect. I could get it to stop by pressing F11 but as soon as I clicked the address bar again the F10 would start jumping again. Closed Firefox to reset it, as soon as I opened it back up it all started again, sticks still disconnected. Finally decided to restart my computer, even that was being affected. I watched the ‘working’ icon spin for several minutes before I finally hard reset it.
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?
-
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.