Console new FSS and new Keybinds topic

What are folks doing with the controls ?

Im seeing a fair few unhappy folks with regards to mapping the new controls. There isn't even that many to be bound and some of the new controls can be bound to keys already bound to other things so they share the key.
It seems folks are making it more complicated for themselves than it ever needed to be.
 
WE NEED KEYBOARD SUPPORT ASAP!!!!

Seriously but with all the new keybindigs, it's time that FDEV implements keyboard support for the XB, as MS has just released in game Keyboard support and we MUST be able to use them here in Elite now. Actually we must miss so many functions we want to map to a keys and we can't as the controller has to less key combinations to get that all.
 
WE NEED KEYBOARD SUPPORT ASAP!!!!

Seriously but with all the new keybindigs, it's time that FDEV implements keyboard support for the XB, as MS has just released in game Keyboard support and we MUST be able to use them here in Elite now. Actually we must miss so many functions we want to map to a keys and we can't as the controller has to less key combinations to get that all.

Again, i have everything mapped to the controller.

What do you miss?
 
What are folks doing with the controls ?

Im seeing a fair few unhappy folks with regards to mapping the new controls. There isn't even that many to be bound and some of the new controls can be bound to keys already bound to other things so they share the key.
It seems folks are making it more complicated for themselves than it ever needed to be.

oh I definitely am. But that's out of the lack of experience with binding. I literally turned the game on and accepted the control scheme as it is. I turn my game on today and see an exclamation mark in my control settings option. If it's possible for me to belay that and play my game to the new capability standards, I will. But if I absolutely HAVE to bind the new keys in order to use the new capabilities, then I might need a step by step or video tutorial... Hell, just a screen shot of someone else's bindings will do. I'm just lacking the scope needed to view key-binding with a simplified mind-set.
 
oh I definitely am. But that's out of the lack of experience with binding. I literally turned the game on and accepted the control scheme as it is. I turn my game on today and see an exclamation mark in my control settings option. If it's possible for me to belay that and play my game to the new capability standards, I will. But if I absolutely HAVE to bind the new keys in order to use the new capabilities, then I might need a step by step or video tutorial... Hell, just a screen shot of someone else's bindings will do. I'm just lacking the scope needed to view key-binding with a simplified mind-set.

Option 1 will bind all the stuff you need to the controller:

Just in case someone misunderstands

1. Classic Default - old but if changed it becomes custom
2. Default - new but if changed becomes custom
3. Custom - only one custom keybind can exist regardless


afterwards you might want to adjust some stuff to your own preferences, but this will help you out.
 
oh I definitely am. But that's out of the lack of experience with binding. I literally turned the game on and accepted the control scheme as it is. I turn my game on today and see an exclamation mark in my control settings option. If it's possible for me to belay that and play my game to the new capability standards, I will. But if I absolutely HAVE to bind the new keys in order to use the new capabilities, then I might need a step by step or video tutorial... Hell, just a screen shot of someone else's bindings will do. I'm just lacking the scope needed to view key-binding with a simplified mind-set.

I'd have no problem broadcasting my binds for you or sending you screen shots, although screenshotting all those pages, woosh.
I never post pics on the forum unfortunately. I cant be bothered learning how to do it.
 
Last edited:
What are folks doing with the controls ?

Im seeing a fair few unhappy folks with regards to mapping the new controls. There isn't even that many to be bound and some of the new controls can be bound to keys already bound to other things so they share the key.
It seems folks are making it more complicated for themselves than it ever needed to be.



I think whats happening is people are just logging in with their old custom loadout which doesnt have any of the new bindings bound so its extra confusing since when you load the help screen it shows 'not bound' instead of instructions and you cant move the cursors since the movement isnt bound. Thats what I did initially but I just went to options and loaded the default binding to see what the new bindings are, then reloaded my custom bindings and copied the default bindings for the FSS, DSS and set a key for hud mode switch.
 
Last edited:
Again, i have everything mapped to the controller.

What do you miss?

There are many functions missing on the Pad. Using Staff, Heatcooling, set throttle to a % value (25%,50%,75%,100%) and many more. Using staff or heat cooling in an infight is a pain if we must switch the fire group to activate it. This should be accessble with a single key. There are so much other thing we miss on consoles as of limited keybindings! As MS has released Keyboard support for ingame use on the XB, it shouldn't be a big deal to implement it. If we get Keyboard support, this will be the biggest thing ever in the console version of this game!!!
 
There are many functions missing on the Pad. Using Staff, Heatcooling, set throttle to a % value (25%,50%,75%,100%) and many more. Using staff or heat cooling in an infight is a pain if we must switch the fire group to activate it. This should be accessble with a single key. There are so much other thing we miss on consoles as of limited keybindings! As MS has released Keyboard support for ingame use on the XB, it shouldn't be a big deal to implement it. If we get Keyboard support, this will be the biggest thing ever in the console version of this game!!!

then why don't you bind it to a controller? I mean, it all fits in my binding configuration. Not all the throttle value indeed, but I bound the 50% to LB + RB. I bound chaff, SCB, and Heatsinks as well under my ships control bindings.. (think i have all ship systems under A)

Honestly, try it. Use default classic, bind some stuff you miss, and ur good to go.. there is really no need for a keyboard.. I understand if its a preference, but there is no need.
 
I'd only just got round to binding the camera suite controls recently, since I had no desire to delete my custom binds to load a default set for those.
And with the advent of this patch I think the only thing which I had any issues with was finding a bind for night vision which was consistent in which buttons it used with the binds I had set for lights, etc. but also didn't accidentally enable handbrake on my SRV. But it only took about 3 attempts to get that right and I still haven't had to bind any combos of 3 or more buttons yet.
 
I've been away from elite for roughly a year so coming back and trying to remember the normal controls was a mission but wrapping my thick noggin around the new mode gave me a proper challenge .
With some tips I've picked up here I think I'm ready to go so thanks to all the helpful cmdrs on here.
Oh and nice to see there are quite a few names I recognise still here. as well.
 
What i'm wondering is why not just enable keyboard support ? blank key bindings? it is using the UWP. keyboard map the functions to it, and bam you're golden. Problem is, we've ran out of buttons on the controller to map things too.
 
then why don't you bind it to a controller? I mean, it all fits in my binding configuration. Not all the throttle value indeed, but I bound the 50% to LB + RB. I bound chaff, SCB, and Heatsinks as well under my ships control bindings.. (think i have all ship systems under A)

Honestly, try it. Use default classic, bind some stuff you miss, and ur good to go.. there is really no need for a keyboard.. I understand if its a preference, but there is no need.

There are not enough key-combo bindings on the controller. I have already bind many of them but still laking some usefull ones. I can't see anymore combos wich will get me additonal functions on the layout, whitout to break something else. The bindings are completly overloaded actually and some of them trigger 2 function instead only one. I have also tried to map X/B/Y-LS Click but this will not work as it is not correctly handled and activates the normal X press too. A-LS Click works but B-X-Y LS Click not. There are many more such combinations, which do not work as expected or activating 2 commands, than only the one we want.

What's the problem for FDEV do implement the Keyboard support, which is now part of MS XB SDK? Everyone will be happy to get this (except you) and get a better and cleaner key bindings. Actually it is so much like a hack than a good solution.
 
Last edited:
I'd only just got round to binding the camera suite controls recently, since I had no desire to delete my custom binds to load a default set for those.
And with the advent of this patch I think the only thing which I had any issues with was finding a bind for night vision which was consistent in which buttons it used with the binds I had set for lights, etc. but also didn't accidentally enable handbrake on my SRV. But it only took about 3 attempts to get that right and I still haven't had to bind any combos of 3 or more buttons yet.

Loading the default set doesnt delete your custom set as long as you dont save any changes to the default.You can toggle back and forth between them in the drop down menu at the top.
 
Last edited:
What i'm wondering is why not just enable keyboard support ? blank key bindings? it is using the UWP. keyboard map the functions to it, and bam you're golden. Problem is, we've ran out of buttons on the controller to map things too.

Depends on how you have things mapped. In my old custom loadout I still had at least four of the default binding open that I had never used. (for me it was the LB and RB combination buttons like X+RB, X+LB) you can also use combinations of other buttons that work for one functionality things. Like I have my hud switch mapped to X+A which works well it never randomly pushes only one of them.
 
Loading the default set doesnt delete your custom set as long as you dont save any changes to the default.You can toggle back and forth between them in the drop down menu at the top.

Yeah, but that's a toggle, not simply populating the values for the newly added controls within my existing customs with the defaults, isn't it?
And anyway, usually defaults are super unintuitive for me, so I change most things.
 
Yeah, but that's a toggle, not simply populating the values for the newly added controls within my existing customs with the defaults, isn't it?
And anyway, usually defaults are super unintuitive for me, so I change most things.

Right but you can at least see what they are and copy them down to enter into your custom loadout. The FSS and DSS modes have their own binds that dont overwrite the same keys mapped in the other mode so you can use the same binds twice once in each mode. My custom loadout is a lot different than the default too but I just copy pasted the default FSS and DSS to learn to use them. The only things you really have to add are open hud switch, night vision, open discovery, FSS and DSS. The rest of your binds can stay the same.
 
Last edited:
What i'm wondering is why not just enable keyboard support ? blank key bindings? it is using the UWP. keyboard map the functions to it, and bam you're golden. Problem is, we've ran out of buttons on the controller to map things too.

Because that’s would be worse...in essence you’d have a situation where an Xbox one game REQUiRES a keyboard just to play it.

Ideally...keybinds Options help buy everything doesn’t need to be a button to press. Some thing just should be automatic
 
Back
Top Bottom