X55 rhino modifier issue
-
Hello folks,
I am having a problem I have failed to solve. I am using an X55 and have it all programmed for falcon. For some reason I cannot figure out any Shift, Control or Alt modifiers I am using do not work in game. In the Rhino testing option everything works. When I go into BMS setup and press the programmed buttons they work as well. Sometimes the modifier button doesn’t show but I figure it should work some of the time in game. The problem seems mostly located to the shift modifier.
Any ideas would be appriciated.
I am suspecting it might be in the programming software because when I assining the commands via BMS UI it works fine.
RedeyeStorm
-
Suggest to share your pr0 file for review. Are you key sequences (that’s what you’re binding to the buttons, right?) nicely timed? Maybe your modifier press/release timings are too short?
-
Hi,
I am using Tektolnes profile. I only changed the layout to my preferences. I wil append my profile when I get back home.
Thanks
-
I don’t have any issues myself - I did find that when using shift modifiers you have to enter both the button press and button release. If you check the advanced command in SST can you see that the one you’re using has both? I’ve attached a jpg showing what it should look like. It took me a while and some experimentation to figure out how to get those to work so it’s possible there’s some duplicate commands in the pro file with one version done the correct way and one done incorrectly. I can take a look later today when I get back home.
-
Hi Tektolnes,
The settings are the same as in your pic. I have appended my profile for comparison.
-
This profile has no delay between key-presses (SHIFT-0-UP-0-up-0-shift-0) - I’m not sure this is THE issue but my bindings always have a natural delay (about 100ms) as typed between key events. I’ve had a problem with some applications not reading such artificial key presses.
Just for testing, right click on those key markers, select wait, add 100ms in between. Try in BMS. YMMV
-
The settings are the same as in your pic. I have appended my profile for comparison.
Yep they look ok alright. What keyfile are you using? It’s possible there might be a conflict with some DX key info at the bottom of the file that’s causing issues (this was something that I had a problem with initially)? I use my profile ok and the time delay set to zero doesn’t cause any issue for me at least. It’s what I always use with the X-55 across all sims when working with advanced commands as it helped eliminate some ghosting. Might be worth testing anyway as b4dshot mentioned.
-
hi b4dshot,
I tried it but no joy. In the tester of the HUD software it no longer detects the key press. I tried with the radar cursor up (shift+UP_arrow). With the adding of the 100ms delay for each key press the combo no longer is recognised int the Setup UI of BMS. The ‘original’ key presses by Tektolnes registered fine. But in game nothing happens. When I press the keys on my keyboard the radar cursor moves fine.Tektolnes, I am using the ‘BMS full’ key. I did notice that when loading no profile in the Rhino the BMS Full key set does register certain commands of certain keys of my joysticks. They work fine in the cockpit. Yesterday I added radar cursor movement commands to the same buttons as are ‘programmed’ in BMS Full key. Could this be causing a conflict? If so how can I delete the allready registered commands for my joystick button?
Thanks for the help guys.
-
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