Tech help for 4.33 - Left cursor button continually scrolling - help!
-
Hey guys,
I am having a problem with 4.33. Please note, 4.33 NOT 4.32 (which does not have this issue).I am using an X52 with the cursor slew mapped to the mini stick via key presses (in bands) on the X/Y axis of the mouse stick. Again, this works fine in 4.32.
Also note that I have a completely re-written key file as I have a customised helios/X52/VAC set up. Under Zipguns instructions, I copied my 4.32 key profile (which worked fine in 4.32) into my 4.33.
However, in 4.33 the left cursor slew (left only) simply moves the cursor slew left continually. Inputting up/down/right will not stop this. The only way to stop it is to short press the left slew and then move the cursor in any direction. However, if you move it left (or even tap it a tiny bit left) it again just keeps slewing the cursor left.
I have tried pressing the key (F10) in game to see if its an issue with the stick - same problem (which at least proves my stick is fine - phew)!
Bands have been set at 20/60/80 and 33/33/33 and 40/20/40 no change.
I have turned off the (is it called DirectX function) in teamspeak, where buttons on the stick can be mapped directly to a key press. and swapped the drop down under ‘hotkeys’ to “keyboard and mouse only” - no effect.
I have tried to see if the button I have set for cursor slew left (F10) is clashing with any new keys - it seems not.
Can anyone help?
-Sharpe
-
Hi Sharpe,
I had the same problem mapping one of my Saitek X65F Hats for radar cursor.
What I did to fix it was to setup a “New Advanced Command” for a button (this allows you to explicitly define push down, repeat and release keys) when using the Saitek programming software. I’m using the default keys for radar cursor control (shift + arrow button) and what you need to do is RELEASE the direction key BEFORE the modifier key (in this case SHIFT).
So… for PRESS section you would have [SHIFT]
Repeat section is empty.
RELEASE section you would have [SHIFT]If you don’t release the direction key before the modifier then the cursor continuously slews.
This might give you some clues about how to solve your issue or it might not (since you moved away from default bindings and using F10 instead).
Best of luck.
-
Hi Zelegend,
Thanks for your comment. I suspect that this will not apply for me as my key press has no modifier (its F10), also pressing the F10 key itself causes the same problem. As the profile works in 4.32 and not in 4.33 I suspect it is something to do with the 4.33 crossover, but given your comments above I might just try removing the key press and adding it again to see if that helps.-Sharpe
-
Hi everyone,
A VFS member has solved this (or rather, got a work around) for this problem. The outcome was this:
It transpired that the F10 key, when pressed, was in a constant state of being pressed whether used via the HOTAS or via the keyboard. We moved F10 to the trim wheel and the effect was 1 key press (from the keyboard) resulted in the trim wheel moving all the way round (ie, resulting in a continual press).
We swapped the radar cursor slew button to a different key press (‘0’, not the num pad zero) that happened to be free in my key - this worked perfectly.
Analysis:
X52 profile, key file and F10 work perfectly fine in 4.32 and other games.F10 appears to be in a constant state of being pressed when touched once and will only stop ‘pressing’ if you tap the F10 button again, when it stops.
I therefore suspect that something is that matter with either my install of 4.33 or with 4.33 in general. While I am sure other people would have noticed this before if F10 (or other keys) were behaving like this all the time, I suspect a bad install or something very specific to do with my setup/PC/profiles. But I wanted to alert the DEV team to this in cease they see it, and for other people to view in case they randomly see this issue somewhere.
-Sharpe
-
I am having this issue with my x65 as well so thanx for the ideas.
-
You consider losing the rudder axis and using the ministick with directx Mower?
-
I am having this issue with my x65 as well so thanx for the ideas.
Mower, I am happy to meet you on the FO teamspeak and talk you through my troubleshooting process. However, I am sure someone in the 185th (who has an X65) referred to a similar problem. I shall try and find out who it was and report back to you.
In the mean time, one of the other things I was told to try (which didn’t work for me, but may for you) was to disable the Directx functions within TeamSpeak. Do this by going to settings, hotkeys, then a drop down box near the bottom right that says something like ‘act as mouse and keyboard’ rather than default (or something like that) and clear any maps you have for using a TS push to talk on your keyboard, mouse and HOTAS.
-Sharpe
-
Kolbe has stated in a thread that this is a problem in 4.33 and will be fixed in an upcoming update. In the mean time he said to use Shift Y, meaning to change the cursor enable to those keys. I have tried it in an early key file and it works fine using the shift y and the arrow keys to move the cursor. It takes two hands as you have to continually hold the shift and Y down as you move the cursor around with the arrow keys however. It’s not the best solution but at least it works.
-
Hi Zelegend,
Thanks for your comment. I suspect that this will not apply for me as my key press has no modifier (its F10), also pressing the F10 key itself causes the same problem. As the profile works in 4.32 and not in 4.33 I suspect it is something to do with the 4.33 crossover, but given your comments above I might just try removing the key press and adding it again to see if that helps.-Sharpe
Sharpe, My admittedly low tech approach was to reassign the cursor key commands to single entry (not combination) . It worked. BTW, a LTA(low tech approach) to using the microstick is to set it up as a x and y banded control. Put 3 bands or each and leave the center band unprogrammed.
-
This post is deleted! -
Hi Sharpe,
I had the same problem mapping one of my Saitek X65F Hats for radar cursor.
What I did to fix it was to setup a “New Advanced Command” for a button (this allows you to explicitly define push down, repeat and release keys) when using the Saitek programming software. I’m using the default keys for radar cursor control (shift + arrow button) and what you need to do is RELEASE the direction key BEFORE the modifier key (in this case SHIFT).
So… for PRESS section you would have [SHIFT]
Repeat section is empty.
RELEASE section you would have [SHIFT]If you don’t release the direction key before the modifier then the cursor continuously slews.
This might give you some clues about how to solve your issue or it might not (since you moved away from default bindings and using F10 instead).
Best of luck.
Hi all,
Thanks for the tip.
Anyway, I tried the trick for the TRIM keys but nothing went good.
There is something which has to do with the time you hold the keys.
In game, if you press [CRTL][UP ARROW] and relase both keys, or [CTRL][UP ARROW], relase [UP ARROW[ and [UP ARROW] again, the trim wheel advance by steps and hold.
if you you press [CTRL][UP ARROW] for a little more time, the trim wheel start rotate and stop ap the end of the course, resulting in an abnormal pitch….
You definitively has to release both keys, as you explained, but I am not able to replicate the behaviour inside the Saitek programming software.also tried
press [CTRL][UP ARROW] + release [UP ARROW]
repeat = void
release [CTRL]No joy.
Better to stay with the keyboard for the moment
Kind regards -
I’m experiencing the same thing with my Cougar. My cursor slowly drifts “upward” and I’m not able to slew it. I’m using Dunc’s profile foe 4.33 and have the settings as per the manual. Anyone having this problem with the Cougar?
-
For the x65f you have to create a new advanced command.
Enter the keystroke this will create 4 boxes. shft, arrow, shft, arrow.
select the 2 last boxes and click “cut”
and “paste” those in the release box and then click “OK”. Done… -
@usafpga:
I’m experiencing the same thing with my Cougar. My cursor slowly drifts “upward” and I’m not able to slew it. I’m using Dunc’s profile foe 4.33 and have the settings as per the manual. Anyone having this problem with the Cougar?
Yes that’s two of us! I have the same problem with my TQS using TUSBA. The cursor drifts to the left all the time… I tried to solve the problem by set ‘‘medium’’ in settings, but nothing changed. Any solutions please?
-
The problem with the Cougar mouse-stick, the CH throttle joystick, etc. is compound - for one, these devices do not center well, so as/when they are calibrated they don’t return to or maintain a stable, repeatable zero. Things that can help -
-
when calibrating the input watch the output numbers and try to return the stick to as close to a repeatable zero/nominal value as possible before hitting “finish” for the calibration - do this a few times, and check with both the Windows and device control panels that you’ve got something fairly repeatable.
-
once you’ve accomplished #1) to satisfaction, then look at setting deadband in both the control panel and/or BMS to cover any slop in your zero.
-
lather, rinse, repeat until you get something you can use.
I’ve ended up doing the above multiple times, and every time I unplug and move my Cougar to another machine or setup. It’s a PITA, but it seems to work for me.
-
-
-
Give up, buy an FCC-3 or FSSB R2
-
Fly
-
???
-
Profit!?!
-