http://www.saitekusa.com/usa/down/drivers.htm
Just a friendly reminder.
On my x45 Vs the last stable ones, the differences I notice are better rudder centering and on the sst the mouse emulation sensibility range is quite different, the same settings I've had are faster now. Backing up a few steps obviously fixes it.
http://www.saitekusa.com/usa/down/drivers.htm
Just a friendly reminder.
On my x45 Vs the last stable ones, the differences I notice are better rudder centering and on the sst the mouse emulation sensibility range is quite different, the same settings I've had are faster now. Backing up a few steps obviously fixes it.
well, I guess I found a SST problem. Can anyone with an x45 and the old software confirm this? (I posted this on their forums too).
As an example, in il2 I have the hat1 set to work as a normal hat, and while shifted it acts as a mouse emulation.
The problem occurs if I'm emulating mouse (pressing hat+shift) and then release ONLY shift, keeping the hat pressed that way even if for a very short while. By this way, the mouse movement will stuck the previous movement and the only way to stop it is using mouse emulation again.
A simple way to show this behaviour (in an inverse shift state way) is creating a new profile (care only for mode1) and map a hat (no matter wich) button as a mouse with sensib at very low to show this better, then map that hat as buttons if shifted in the same mode (no mouse emulation if shifted).
Run the profile, put your mouse cursor at the left border of the screen and then press that hat right (you'll see the cursor going right off course) and while keeping the hat pressed to the right, hold shift and then you can even release the hat while shifting. This should disable mouse emulation, but instead, mouse movement will be stuck with the previous movement! Trust me, this can lead to disasters while dogfighting.
SST v3.2.0.11 doesn't do that, but Dhauzimmer's drivers (3rd party) do. It may be that the basic structure of the driver has changed to add more features, as D's drivers offered options that my current SST drivers don't.
Thanks for the input, well the only ones I've used before were 3.2.0.18's, I really don't know if they exibited this problem.
Btw, this this driver set still has that aux bug. Per example, if setting the aux as an advanced command (in this case press/release del) if you shift and then unshift the pinky, this command will be repeated on it's release (as when I exit a game too!). Setting it for these kind of commands isn't a problem, but for toggling ones might be.
I'd like to set a command to toggle combat flaps on and off when you press the "C" button. How do you set up a toggle w/the SST software?
I'm a PC gamer. Any comments I make that don't specifically state a platform you can bet I'm referring to PC.
3Sqn Forums
[url=http://teambsr.com
I can only think of a solution that is to assign C to "V", then shift C as "F".
I prefer to use the throttle hat with up/down to control flap positions.
On a side note, if you're using the 3.2.0.18 software would you mind testing the above behaviour? Thanks.
PS: Tully, glad to see your new sig
<BLOCKQUOTE class="ip-ubbcode-quote"><font size="-1">quote:</font><HR>Originally posted by BSR_RuGGBuTT:
I'd like to set a command to toggle combat flaps on and off when you press the "C" button. How do you set up a toggle w/the SST software? <HR></BLOCKQUOTE>
The version of SST that I'm using doesn't support toggles, unless the lates version has additional features you'd have to do it the way Marek_Steele suggested.
Even then it'd depend on flaps being in the "raised" or "combat" state when you chose the relevant button. You could make it independant of start conditions by assigning:
Fire C = F F F V
Shift - Fire C = F F F
Just to add one thing I just checked, the older 3.2.0.18 drivers don't suffer from this too.
Posting Permissions
Marek_Steele
Reply With Quote
