I can navigate the galaxy map with the joystick of my Saitek X52. I can select different tabs in the info window, move the cursor. I think it's doable but, most of the time, I type the name of the system I want to go to.
The Joystick/Controller discussion thread
I can navigate the galaxy map with the joystick of my Saitek X52. I can select different tabs in the info window, move the cursor. I think it's doable but, most of the time, I type the name of the system I want to go to.
Thank you for your reply. With all the buttons / modes with available with CH Pro throttle and Fighter stick there may be some way for me to emulate a mouse click (with the mini joystick on the throttle perhaps). I like to explore so don't really have a system name for which I want to go. I am sure there is a workaround I am trying to get away from switching to and from keyboard / mouse can stick with it for now.
Last edited:
I picked up a Thrustmaster stick last week, but didn't get the HOTAS since I still have the throttle from my old one and have wired it using an arduino (just need to find a way to get the mini breadboard inside the housing 
)
Anyway, in the meantime I thought I'd use the stick as my primary device and an xbox controller in my left hand to operate the thrusters using the analog stick.
The drawback for me is that I've lost all the button mapping power I had with the ABXY buttons changing the state of the DPad.
I know there's at least one other person doing a joystick/gamepad flight combo. How do you organize your controls?
)Anyway, in the meantime I thought I'd use the stick as my primary device and an xbox controller in my left hand to operate the thrusters using the analog stick.
The drawback for me is that I've lost all the button mapping power I had with the ABXY buttons changing the state of the DPad.
I know there's at least one other person doing a joystick/gamepad flight combo. How do you organize your controls?
I just got mine, and am trying to figure out where to put what on the buttons. (since I'm not a flight sim person, no pedals) I'm not quite sure yet which functions are entirely mode-dependent and can be overloaded on the hat switches. I may need a cheap USB numberpad for the overflow..
Last edited:
ALERT !
X52 Pro owners get rid of the bump thing on your throttle, it will break and cause trouble. Extensive vids on Utube disassembling throttle.
Had to do it myself, because throttle failed. very easy to do. Elsevise nice stick and throttle, used for 1344 hours.
Cheers Cmdr's
X52 Pro owners get rid of the bump thing on your throttle, it will break and cause trouble. Extensive vids on Utube disassembling throttle.
Had to do it myself, because throttle failed. very easy to do. Elsevise nice stick and throttle, used for 1344 hours.
Cheers Cmdr's
As an alternative to a number pad, try Roccat Power Grid. Download the PC version onto your Desktop or Laptop and the Android version onto your tablet or phone. Then use the latter in place of the number pad. There are a load of grids available for ED. I prefer ED Horizontal as I like to see my controls in landscape. Simple to follow the instructions and fun to use. In my opinion more immersive than a number pad. See: https://forums.frontier.co.uk/showthread.php?t=15616
I find that I can easily see the control options within my field of vision without having to move my eyes from the monitor screen which is a great advantage over finding keys on a keyboard. I can't claim this over a number pad as I don't have one.
The ED Grids are free as are the software and you get a couple of slots for free. You can also use this software for many other games and applications, even as a remote for your TV.
I also recommend Joystick Curves to tame your joystick, throttle etc.
If you use the shift feature of CH products and CH Control Manager, every button will be available for two binds. With the CH Pro Throttle and Fighter Stick this seems to be more than enough to cover ED's controls.
Here's my basic Control Manager map file which has the pinky button of the joystick as shift and every other button (except for diagonal buttons on hats iirc) available shifted. Once you've opened and 'downloaded' that map to your devices, you'd then assign controls in-game on a custom basis. The map file uses the pedals, so I'm not sure if you'd need to remove that part of it before 'downloading' to the devices.
Last edited:
Great idea! Have some rep!
Only other thing missing on the throttle is an analogue mini-stick.
How did you make the keycap decals?
Great idea! Have some rep!
Only other thing missing on the throttle is an analogue mini-stick.
Cheers
Totally in agreement there, would make thruster use a lot easier!Decals are tweaked versions of Hairstair's Roccat Power Grid template buttons, edited in Photoshop to fit what I needed - In actual fact, I've uploaded them and you can pull them down from here.
They were printed at the right dimensions on sticker paper - this is what I used but non-gloss would work just as well. The first attempt had the ink rubbing off on to my fingers after a few hours of use, so a reprint and cover with sticky back plastic before cutting out and sticking down to the number pad did the job. Of course, muscle memory is now there so I know exactly what each of the buttons does, but still adds a little touch
This is the number pad I used. Request Docking and Set Destination are controlled by Autohotkey macros which I can share if you want them too.
So far totally satisfied with the X52 Pro, but should it defect I'll think about full CH Products setup.Cheers
Decals are tweaked versions of Hairstair's Roccat Power Grid template buttons, edited in Photoshop to fit what I needed - In actual fact, I've uploaded them and you can pull them down from here.
They were printed at the right dimensions on sticker paper - this is what I used but non-gloss would work just as well. The first attempt had the ink rubbing off on to my fingers after a few hours of use, so a reprint and cover with sticky back plastic before cutting out and sticking down to the number pad did the job. Of course, muscle memory is now there so I know exactly what each of the buttons does, but still adds a little touch
This is the number pad I used. Request Docking and Set Destination are controlled by Autohotkey macros which I can share if you want them too.
Thanks for the images!
My X55 starting to deteriorate, stick developing dead zones and one 4-position hat almost dead, so I decided to move on warthog. Now can't really play with it. Missing rz-axis terribly, pedals wont help. Also non-fix switches on throttle base work better due to game logic, saitek shines in that department also. As much as I love coolness of warthog, its just not space-sim material for me.
Worth noting that ED handles shifts natively so no need to use mapping software for this particular case.
It actually recognises any number of individual and combined shifts, which is pretty cool. More useful for game pads than HOTAS as the former usually have fewer buttons, but handy nevertheless. I use 3 different shifts on my HOTAS, for example, to do things like allowing flight controls even when I'm in UI mode.
Logitech 3Dpro joystick and Belkin n52te setup
As a newcomer, I started by analyzing the various functions that can be bound and grokking how to fit it onto my existing setup - a Logitech Extreme3Dpro joystick and my trusty, old n52te.
It was quickly obvious that there is no real need for an expensive HOTAS
Using a simple setup with modifiers, I've managed to fit everything I consider relevant onto the two devices - with plenty of room to spare, should I need to bind more functions.
This is how my n52te is configured. The keys are mostly bound to the numerical keypad, like (1), (2), etc. Green is modified with LeftShift, red is modified with LeftAlt.
I have used LeftAlt for combat related functions (Altercation), and LeftShift for navigation and sensors. I've (so far) left most of the "standard" keybinds in place as alternates. Toggle UI on the main keyboard, has been moved to NumLock.
I have not used the two other keymaps on the n52, which are set up in much the same way, respectively bound to "1".."0" + "+" and F1..F11.
The joystick is bound like this: (Here green signifies functions modified with LeftAlt)
(Image by mcdee.net/elite)
As you may have guessed from the cropped image, I have no intention of using anything on the base of the joystick (Joy_7..Joy_12 keys and miniature throttle). The throttle has been moved to the (mouse) scroll wheel on the n52, using 12,5% increments.
I intend to use the mouse for the maps. I may later want to supplement with a power grid display, or two, for the less used functions, or for immersion.
Now, have I forgotten anything significant?
As a newcomer, I started by analyzing the various functions that can be bound and grokking how to fit it onto my existing setup - a Logitech Extreme3Dpro joystick and my trusty, old n52te.
It was quickly obvious that there is no real need for an expensive HOTAS
Using a simple setup with modifiers, I've managed to fit everything I consider relevant onto the two devices - with plenty of room to spare, should I need to bind more functions.
This is how my n52te is configured. The keys are mostly bound to the numerical keypad, like (1), (2), etc. Green is modified with LeftShift, red is modified with LeftAlt.
I have used LeftAlt for combat related functions (Altercation), and LeftShift for navigation and sensors. I've (so far) left most of the "standard" keybinds in place as alternates. Toggle UI on the main keyboard, has been moved to NumLock.
I have not used the two other keymaps on the n52, which are set up in much the same way, respectively bound to "1".."0" + "+" and F1..F11.
The joystick is bound like this: (Here green signifies functions modified with LeftAlt)
(Image by mcdee.net/elite)
As you may have guessed from the cropped image, I have no intention of using anything on the base of the joystick (Joy_7..Joy_12 keys and miniature throttle). The throttle has been moved to the (mouse) scroll wheel on the n52, using 12,5% increments.
I intend to use the mouse for the maps. I may later want to supplement with a power grid display, or two, for the less used functions, or for immersion.
Now, have I forgotten anything significant?
Last edited: