X55 rhino modifier issue
-
Can you try the attached key file and see how it works? It’s the one I use after I stripped out the duplicate DX commands at the bottom that were causing weird things to happen. I think you’ll have to select it in the BMS UI as well as it’ll probably using the BMS Full key still. The key file should be dropped into D:\Falcon BMS 4.33\User\Config.
-
Hi Tektolnes I wil thanks. I’ll let you know what happens.
Tried it, no joy again. It totally baffles me why it does recognise the key presses in the BMS setup UI but not in the 3d world!!
-
I have been thinking and testing a bit in other games. In Battle of Stalingrad I have the same issues but a WOII plane doesnt require that many buttons so I use the game UI to program the stick and not the Saitek software.
Because of this I was wondering if the issue is not generated by the way keypresses are read by my pc. I have been tinkering with the standard in Windows10 available settings for keyboard repeat speeds etc. That didn’t help either but I wonder if the solution could be found in the BIOS settings?
-
I had issues with BOS as well and ended up using the UI like you. But DCS works totally fine for me using SST - though I found I had to use advanced commands in the repeat macro box and zero time delay for commands using shift as the X-55 just seems to have a problem with these in every sim. Falcon was a total nightmare to set up using SST but eventually got there using the method mentioned before. I’m using Win 10 as well so really not sure why it’s working for me and not for you.
Where do you have your X-55 plugged in to? I originally had it plugged into USB ports at the front of my PC and it caused all kinds of wonkiness but when I switched them to the USB ports at the back of the PC things were fine. Though I guess if you have it working ok for BOS that’s probably not the issue…
-
Well I suffered at first from the ghost button pushing Gremlin so I bought a powered USB hub and that problem is gone. When this issue started up I tried to put them back in the back of my pc (2.0 ports) but the ghost returned. Facons Gremlin likes to drop the gear in midflight. Nice effects at 550 knots!
-
Go DX (directX ) all the way. No more buggy SST Suffering.
-
DX is nice but not sufficient for some advanced bindings (delays, repeats, etc.) and the dreaded non-DX functions on the stick (cursor for example that I’m successfully using with key bindings).
BTW for the thread starter, have you upgraded to the latest saitek driver/software 7.0.41?
-
Hi b4dshot,
I did and there is some improvement. Radar cursor up doesnt stop moving now, which is better then no movement at all I supose! On the trigger I have ‘2nd trigger detent’ (alt /) but it generates ‘contol alt /’ for van some reason in the test of the hud software. In game one pull and gun keeps firing. Still trying to figure it out. Also dropped a ticket at Saitek. Will see.
-
DX is nice but not sufficient for some advanced bindings (delays, repeats, etc.) and the dreaded non-DX functions on the stick (cursor for example that I’m successfully using with key bindings)
The mini cursor sucks anyway, unusable. If you can make it functions in DX why using the buggy SST?
-
The mini cursor sucks anyway, unusable. If you can make it functions in DX why using the buggy SST?
I’m not aware of a way to bind the mini-stick via DX (it’s not a stick with two axis and not 8 directional DX buttons either afaik).
Using key callbacks I can use it no problem for cursor activities (I need the other two hats for comms and defensive)
The Saitek software works without flaws over here YMMV
-
I’m not aware of a way to bind the mini-stick via DX (it’s not a stick with two axis and not 8 directional DX buttons either afaik).
The Saitek software works without flaws over here YMMVWhat I ment was that the minicursor just sucks due to it’s nature, better explained here http://forums.eagle.ru/showthread.php?t=141754
Profiles bring extra features (realistic or not), yes, but extra problems, and extra things to go wrong with. As poster has problems it seems logical to try a DX setup also. -
I have been thinking and testing a bit in other games. In Battle of Stalingrad I have the same issues but a WOII plane doesnt require that many buttons so I use the game UI to program the stick and not the Saitek software.
DX (directx) programming is excactly the same as what you refer to, in BMS you can program all HOTAS function in DX. I posted my DX profile here
-
I’m not aware of a way to bind the mini-stick via DX (it’s not a stick with two axis and not 8 directional DX buttons either afaik).
Please ignore my post if you might already know - but it is possible to convert the mini stick into DX axis.
Works great for me with windows 10.
https://www.reddit.com/r/EliteDangerous/comments/2rudl0/xpost_rhotas_how_to_turn_x55_mouse_ministick_into/ -
Please ignore my post if you might already know - but it is possible to convert the mini stick into DX axis.
Works great for me with windows 10.
https://www.reddit.com/r/EliteDangerous/comments/2rudl0/xpost_rhotas_how_to_turn_x55_mouse_ministick_into/EDIT: It seems that the X-axis for the ministick is inverted this way. I’ll see if there’s another registry entry that can fix this.
What about being inverted? -
EDIT: It seems that the X-axis for the ministick is inverted this way. I’ll see if there’s another registry entry that can fix this.
What about being inverted?No problem for BMS, since you can “re-invert” the x-axis directly in the setup (Controllers - Advanced - Avionics)
-
Please ignore my post if you might already know - but it is possible to convert the mini stick into DX axis.
Works great for me with windows 10.
https://www.reddit.com/r/EliteDangerous/comments/2rudl0/xpost_rhotas_how_to_turn_x55_mouse_ministick_into/didn’t know, can’t believe I missed that (don’t see it in any profile discussed in the forum but I’m blind at times too)
The reg file to import for anyone else
Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_A215\Axes] [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_A215\Axes\6] "Attributes"=hex:01,81,00,00,05,00,24,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_A215\Axes\7] "Attributes"=hex:01,81,00,00,05,00,26,00
Still not the best stick in the world but it does have a tad of a min to max throw now at least.
I’m still stuck on non-DX for
- mode switch - I use it for 3 key presses
- speed break slider
In case I’m missing more stuff
bad
-
Under DX it goes acceptable and it shows some nice feature as well: a variable speed which I think comes from the amount of pressure applied.
Finding directions is a bit touchy so to speek, I often go the wrong direction with the mini stick, I 'll get used to it I guess.
At least worth giving it a try