The Joystick/Controller discussion thread
I only know about it because I mistakenly mapped them to my throttle when I started playing!Well I'll be damned ... just went to check in the Options/Controls list because I confess I didn't believe you and there they are: Thrust Forward & Thrust Backward. I apologise and yes, you're right - it does indeed reinforce your point. Have some rep
Wow, so many questions. If you're running from an attack at full thrust would applying forward thrust give you an extra little bit of speed?
As for your question - it's a good one. I'll check next time I log on.
Kislany, you can safely leave the thrusters bound to the keyboard where they are - I can't think of a situation where delicate throttle control won't achieve the exact same results with less hassle.
Last edited:
Well I'll be damned ... just went to check in the Options/Controls list because I confess I didn't believe you and there they are: Thrust Forward & Thrust Backward. I apologise and yes, you're right - it does indeed reinforce your point. Have some rep
Wow, so many questions. If you're running from an attack at full thrust would applying forward thrust give you an extra little bit of speed?
Not sure, but I often use the lateral ones while moving quite fast to manoeuvre, adds an extra smidge of control. It's great when approaching a station, for example, for tidying up angles lazily.
The way I have forward and back thrust configured is I use them in the Landing/Docking override section of the Controls config, as I don't really see a use for them otherwise.
I have buttons 7 & 8 (the top and bottom rightmost buttons on the left side of the stick) set to forward and reverse. As the name implies, those buttons have other functions when the gear are up, though.
Since with this setting you have to have your landing gear down it might not be as useful to you, but to me this makes the most sense, as I'm only using forward and reverse in situations where I need precise control like scooping or mining or docking, and having the gear down, which also lowers my max speed and makes boost impossible helps with situations with those a lot.
One other thing you might consider are shift states using the left hand buttons. This is what I do. In the Control Options you can press more than one button at the same time and get multiple functions out of a single button.
In my case I use the 4 way hat for 24 functions. Pressing (and holding down) 9 and using the hat sets my power allocation, for example, while button 6 and the hat controls the scoop, gear, and scanner resolution, while button 7 and the hat controls boost, heatsinks, silent running, and FSD/SC engage. The pro of this is you are using the same hand you use for the throttle to push buttons so you're getting more out of that hand. The con of this is you have to use two hands on the stick, if you're controlling throttle some other way than the stick's throttle or using the keyboard with any frequency this won't work as well for you.
But in general that kind of setup (any multi-button combo, not just the hat) might work for you with reverse and forward if you see the need for it.
I have buttons 7 & 8 (the top and bottom rightmost buttons on the left side of the stick) set to forward and reverse. As the name implies, those buttons have other functions when the gear are up, though.
Since with this setting you have to have your landing gear down it might not be as useful to you, but to me this makes the most sense, as I'm only using forward and reverse in situations where I need precise control like scooping or mining or docking, and having the gear down, which also lowers my max speed and makes boost impossible helps with situations with those a lot.
One other thing you might consider are shift states using the left hand buttons. This is what I do. In the Control Options you can press more than one button at the same time and get multiple functions out of a single button.
In my case I use the 4 way hat for 24 functions. Pressing (and holding down) 9 and using the hat sets my power allocation, for example, while button 6 and the hat controls the scoop, gear, and scanner resolution, while button 7 and the hat controls boost, heatsinks, silent running, and FSD/SC engage. The pro of this is you are using the same hand you use for the throttle to push buttons so you're getting more out of that hand. The con of this is you have to use two hands on the stick, if you're controlling throttle some other way than the stick's throttle or using the keyboard with any frequency this won't work as well for you.
But in general that kind of setup (any multi-button combo, not just the hat) might work for you with reverse and forward if you see the need for it.
Last edited:
Oh gosh...so I'm learning the way of the joystick, and honestly now i realize that setting the controls was the easy way. Because I can't even dock now anymore, I'm flying all over the place, no idea what the heck I'm doing *sigh*. I guess it will take me time to adjust to playing with a joystick, something that I've never touched before in my 20 years of gaming...
It will come with time. Once it clicks, it will quickly seem mind-boggling that you ever did without it.
Man, I hope so. Just before the servers went offline, I did my second trial with the docking training - and failed miserably, ending at the deep end of the station, upside down, hitting everything that can be hit inside, lol. I see it's potential, it's just right now my hand movements using the joystick don't follow what my brain is trying to relay...
Last edited:
Howdy CMDRS
I have a Flightmaster T-Flightstick X and this is how I mapped:
Twist is yaw, up/down pitch and left/right roll on the joystick x/y axis
The slider throttle is my forward/backwards throttle.
The hat switch is my up/down left/right thrusters and in the UI is the navigate menu
1 is my primary fire and my select when in the UI
2 is my secondary fire and my back button inside UI
3 is my select target, UI next button
4 is my boost, UI previous button
5 is next target, 6 is highest threat
7 is Flight Assist, 8 is Landing Gear
9 is UI select, 10 is Chaff
11 is Supercruise, 12 is SC to Hyperspace
All the switch mapping is toggle
I use the keyboard of course for the rest. This mapping has worked out well for me so far.
I can use the stick, mouse or keyboard for UI menus and Galaxy/System maps
I'm now mapping to a Logitech gamepad to give that a try too.
Good Luck OP!
I have a Flightmaster T-Flightstick X and this is how I mapped:
Twist is yaw, up/down pitch and left/right roll on the joystick x/y axis
The slider throttle is my forward/backwards throttle.
The hat switch is my up/down left/right thrusters and in the UI is the navigate menu
1 is my primary fire and my select when in the UI
2 is my secondary fire and my back button inside UI
3 is my select target, UI next button
4 is my boost, UI previous button
5 is next target, 6 is highest threat
7 is Flight Assist, 8 is Landing Gear
9 is UI select, 10 is Chaff
11 is Supercruise, 12 is SC to Hyperspace
All the switch mapping is toggle
I use the keyboard of course for the rest. This mapping has worked out well for me so far.
I can use the stick, mouse or keyboard for UI menus and Galaxy/System maps
I'm now mapping to a Logitech gamepad to give that a try too.
Good Luck OP!
Last edited:
The defaults for the Roll anf Pitch are backwards by default by my way of thinking. You can reverse them in the configMan, I hope so. Just before the servers went offline, I did my second trial with the docking training - and failed miserably, ending at the deep end of the station, upside down, hitting everything that can be hit inside, lol. I see it's potential, it's just right now my hand movements using the joystick don't follow what my brain is trying to relay...
1.1 Update...joystick no longer detected
I've got to be doing it wrong...
My CH fighterstick and throttle, along with my Saitek pro rudder peddals were working great last night, pre 1.1. Now with 1.1, they are not detected.
I also have a Thrustmaster TM1600 plugged in, but don't use it for ED.
Like I said, this set up was working last night. Now it is not after the 1.1 update. I've tried to remap the controls with the CH and Saitek, but nothing happens when I hit the button or axis on them.
Ideas?
I've got to be doing it wrong...
My CH fighterstick and throttle, along with my Saitek pro rudder peddals were working great last night, pre 1.1. Now with 1.1, they are not detected.
I also have a Thrustmaster TM1600 plugged in, but don't use it for ED.
Like I said, this set up was working last night. Now it is not after the 1.1 update. I've tried to remap the controls with the CH and Saitek, but nothing happens when I hit the button or axis on them.
Ideas?
Um...no. Why in the world would I have to do that? I did it anyway. Still borked.
Last edited:
I think they borked joysticks with 1.1. Here's why:
I have:
Thrustmaster T1600M (used for Battlefield 4).
Cougar MFD (two of them, used for DCS A10C flight sim).
CH Pro throttle (used for ED).
CH Fighterstick (used for ED).
Saitek Pro rudder pedals (used for ED).
As I said, this worked perfectly last night. Now with 1.1, only the Thrustmaster T1600M is seen by the game.
Note the list above is how they are ordered in Control Panel / Devices and printers. Right clicking on any one of them, then "game controller settings" shows this list. I know Windows sets an order (priority) to each controller. Apparently, with the 1.1 patch to ED, it only detects the controller set with priority 1, which you have no control over in Windows.
There's no way for me to fix this. Using 3 controllers at once was fine pre 1.1 and now it appears not.
I have:
Thrustmaster T1600M (used for Battlefield 4).
Cougar MFD (two of them, used for DCS A10C flight sim).
CH Pro throttle (used for ED).
CH Fighterstick (used for ED).
Saitek Pro rudder pedals (used for ED).
As I said, this worked perfectly last night. Now with 1.1, only the Thrustmaster T1600M is seen by the game.
Note the list above is how they are ordered in Control Panel / Devices and printers. Right clicking on any one of them, then "game controller settings" shows this list. I know Windows sets an order (priority) to each controller. Apparently, with the 1.1 patch to ED, it only detects the controller set with priority 1, which you have no control over in Windows.
There's no way for me to fix this. Using 3 controllers at once was fine pre 1.1 and now it appears not.
Finally completed my CH setup with the pedals. Having everything mapped out is great. Though I never expected how hard it would be for my brains to coordinate the whole setup. Ah well, I'll learn and adapt.
1.1 update - can't use joystick
Hey gys,
I posted this in the support forum, but I thought I am more likely to get a response from someone who has/has had the same issue by posting it here.
I have lost my key bindings and am unable to rebind any of the buttons or axis on my joystick. I am using the Madcatz(Saitek) Cyborg FLY 5.
I have checked the training missions and the mapping for the joystick is working fine, so this points to it being broken in the 1.1 update.
Anyone got any suggestions? has this happened during the BETA and there is an old workaround I can try?
Many thanks!
-Kiblams
Hey gys,
I posted this in the support forum, but I thought I am more likely to get a response from someone who has/has had the same issue by posting it here.
I have lost my key bindings and am unable to rebind any of the buttons or axis on my joystick. I am using the Madcatz(Saitek) Cyborg FLY 5.
I have checked the training missions and the mapping for the joystick is working fine, so this points to it being broken in the 1.1 update.
Anyone got any suggestions? has this happened during the BETA and there is an old workaround I can try?
Many thanks!
-Kiblams
switch your computer off and back on again
Did that, and no joy. (I work in IT so that was my first troubleshooting step)
If it works in the training missions and not in the latest game update for Multiplayer, they just broke it...
Seriously, no one else having this issue?