Anyone having the issue where the X55 Rhino Profiler takes a good amount of CPU? (half of one of my cores)
Is anyone else having trouble with there X55 bindings??
When ever I start ED with previously saved bindings have gone & I have to do it all over again, which is a damn chore.
Any help on this would be appreciated
^^^what he said
You don't need to use the saitek profiler at all unless you want to program a button to do something not provided for in the game.
I started with the X55 option under controls in the game and then changed the buttons I wanted to and it automatically saves it as a custom profile. I did however use the Saitek software to assign f9 and f12 to the pinky switch on the throttle to pause and recenter my TrackIR, as I tend to only use track IR in combat and prefer the hat switch for the consoles during normal trade runs.
Is anyone else having trouble with there X55 bindings??
When ever I start ED with previously saved bindings have gone & I have to do it all over again, which is a damn chore.
Any help on this would be appreciated
Is anyone else having trouble with there X55 bindings??
When ever I start ED with previously saved bindings have gone & I have to do it all over again, which is a damn chore.
Any help on this would be appreciated
I've just mapped buttons 25 & 27 on my X55 (the ones on the lower hat on the throttle) to Left & Right on the UI panels and they work fine, for whatever that's worth.
Wish I could be more help but I'm stumped.
I've been fiddling with the software that comes with this stick to see whether I can use it to assign some ED 'macros' to buttons and switches. I offer here a prototype 'Docking Request' HUD profile, containing a macro bound to the SW6 switch.
To make it work with your Rhino there are few constraints.
- It sends key presses to the game to open the targets panel, tab to Contacts, then issue the docking request
- It assumes that when you open the targets panel, that the Navigation tab is active
- When the macro ends, it makes the Navigation tab active again (so it will work the next time you use it)
- It 'toggles'. If you already have permission to dock, it cancels the request.
- The keys used in the macro must be bound in your ED custom.binds file. I have used the default Keyboard UI controls Q,W,E,A,S,D,<space> that display in the game help screens.
- To work properly, you need to have the X-55 'HUD' software installed and running, with the profile loaded
At the link, there is a copy of the X-55 HUD profile, ED custom.binds file that includes the key bindings so the HUD macro works, and an HTML file that shows the other bindings used by the stick/throttle. All 3 files are also in a zip file if you prefer to download that.
Hope some people find it useful, I'd welcome feedback. Currently the profile has a 0.2 second delay between key presses so you can see it working.
To use it, you must have the station set as your target. Then hold down the SW6 switch until the docking request is sent. Releasing the switch then resets the target panel back to the Nvigation tab, and closes the tab.
https://drive.google.com/folderview?id=0B_b1val4v4WBckJTWnRPVFRKY0U&usp=sharing
(I think you may need a google account to use that link).
thanks for this, was trying to find out if this was possible & how, you've done the leg work for me![]()
Yes, that is why I would have liked to go the easy road.
I intend to master the Saitek software eventually, because I watched a youtube video by a guy called Frooglesim in which he demonstrated the customization power that is in the software. You can do very cool stuff with rotaries for example.
https://www.youtube.com/watch?v=Hr9Oi1jc4wg
In the Saitek software, you can program it to do other things than mousing, although it's super sensitive and frequently will trigger up, say, when you want to go right. I've had some success mapping one axis of it to next UI panel/previous UI panel in the user interface using the bands, with a giant (like 60%) dead zone in the middle.
Another option that might work would be to set every direction on it to the same key, again, with a large deadzone. Something like Boost or Hyperdrive where you just need another button under your thumb, but you don't really care about left vs. right or up vs. down.
And now that I think of it, you could actually do something really slick using the randomness: set each direction to a juke macro, such as "thruster up for 1 sec, thruster right 1 sec, thruster left and down 1 sec" or something, with each direction being a different order of thrusting. Then just tap the stick in any direction in combat to jink a bit if someone's shooting at you.
I've revised my bindings a bit based on more experience with the game, as well as new features introduced. I've also built an EDTracker so the various ways of looking around are no longer that important to me in the X55 bindings, but even without EDTracker I found that I was never using the POV hat to look around, but only the mouse nipple. So I've changed the POV hat to be used for targeting, and moved the subsystem targeting to the lower throttle hat. (I considered using it for lateral thrusters, but it becomes problematic in a dogfight if you want to apply thrusters and shoot at the same time, hence lateral thrusters remain on the throttle hat.)
Anyhow, as before, the mouse nipple on the throttle needs to be configured to a mouse in order to be used for analogue headlook, and the slide switch on the throttle should be bound to caps lock held down when enabled, and caps lock release when sliding back. This way it can be used to toggle throttle reverse (the capslock key was chosen because it does not spam into any text boxes or trigger shortcuts, but it does toggle caps). Both bindings can be ignored without affecting other usage, e.g., EDTracker users may simply disable mouselook an ignore the mouse nipple on the throttle.