How Heavy is Impact on Control Bindings for New Release (beta)?

I have not tried the beta, as I prefer waiting for the live release; however, curious how heavy the impact for the new release is on current live control bindings? I assume it will be fairly major given the new exploration and other features, thus for my x52 Pro HOTAS custom and VoiceAttack profiles, assume some major rework to get everything working based on new changes?
 
yup, there's a whole slew of new keybinds.
it will likely take a while to figure out and tweak to your liking.
 
I had to start using a modifier button on my setup. It's now better than before and includes all the new functionality, but it definitely took some time and effort to setup and acclimate to.
 
While there's a huge number of new bindings, most of them are specific to the FSS and DSS mode. They do not collide with the existing bindings. So you can just bind them without any problems.
.
There are only two exceptions:
- Switching between combat mode and analysis mode. You definitely want to bind a button to that.
- Activating the FSS is a new key binding.
.
So actually you have to squeeze two new buttons into your setup. The rest, while being plenty, are in their own world and don't collide with your existing key bindings.
.
 
The rest, while being plenty, are in their own world and don't collide with your existing key bindings.

Assuming you have enough unbound controls.

Most people using a HOTAS won't have anything unbound and many will already have made concessions to get what they have now, bound.

I had to adjust over a dozen command inputs and my HOTAS setup has more buttons than most. My backup controls will need to be almost completely redone.
 
I have not tried the beta, as I prefer waiting for the live release; however, curious how heavy the impact for the new release is on current live control bindings? I assume it will be fairly major given the new exploration and other features, thus for my x52 Pro HOTAS custom and VoiceAttack profiles, assume some major rework to get everything working based on new changes?

Just a few changes on my part, keep in mind that many of the bindings are SC specific, so you can have multi bindings for the same thing. Read beta reports expecting it to be hassle, had it all sorted in minutes. Also keep in mind your X52 has multiple modes.
 
I use a hotas, mouse and sometimes even some keys on the keyboard. I control the camera ouside the ship with keyboard and mouse for example.
I think it's 3 new keys you need for the stuff in beta while flying.

1. FSS (that's the new discovery scanner) mode. I switch to mouse for that one. Activation is on mouse as well, but I tune with a rotary axis on my throttle.
2. Night Vision on/off, though that's also controllable via ship functions on the right panel, just inconvenient.
3. Combat/analysis mode toggle

The rest of the bindings are for use within the modes. There are lots of bindings for the FSS and a few more for the probe launcher (which activates via trigger specified in firegroups). You can also bind one for squadrons and one for the codex I think, but I guess that's not really necessary.
 
Bare minimum of TWO keys/buttons need to be globally mapped for normal flight - the rest can share bindings as they are tied to specific mode(s) - or activatable via other means.

Valorin has covered this already though. :D
 
Last edited:
I have not tried the beta, as I prefer waiting for the live release; however, curious how heavy the impact for the new release is on current live control bindings? I assume it will be fairly major given the new exploration and other features, thus for my x52 Pro HOTAS custom and VoiceAttack profiles, assume some major rework to get everything working based on new changes?

There are a number of new binds, beyond just having to bind the usual pitch/yaw to new features. All in all it took me about five minutes.
 
The most important ones are, as have been mentioned above, mode switching and FSS activate/deactivate.

Mode switching I've bound to the < key (to the left of Z on my keyboard) for easy access, while activating the FSS is bound to SHIFT + R. Deavtivating FSS is bound to SHIFT + F. Exiting probe/DSS mode is bound to TAB.
 
Assuming you have enough unbound controls.

Most people using a HOTAS won't have anything unbound and many will already have made concessions to get what they have now, bound.

I had to adjust over a dozen command inputs and my HOTAS setup has more buttons than most. My backup controls will need to be almost completely redone.
.
You confuse me. Why did you have to change so many things? I mean, i also had no unbound buttons. But i already before, for some less important functions, use a modifier. For me, it's the FAOff button. When i press that button by itself, i am only in FAOff. When holding the button and then moving one of the 4-way switches, it activates that function.
.
That means that yes, when i switch between combat and analysis mode, i am in FAOff for a moment. When i activate FSS, i theoretically would be in FAOff, but as that one only can be done in supercruise, it doesn't even happen. All the other bindings are additional to my existing bindings. I can zoom in/out with the same four way in FSS, which i use to move in the left and right hand panel in the cockpit. I select target with the fire button, etc. It does not collide with the normal controls.
.
So i really am confused why you had to change so much. There's a lot of negative said about the FSS and DSS being completely different screens and not connected to the normal cockpit. But it has the one positive side, the controls are also not connected, so buttons can freely be used again.
.
Edit: Added my keybindings. While edrefcard is an awesome tool, i still edited the image to also include what is bound via the joystick software.
.
1qzz2TX.jpg
 
Last edited:
The key combos on my xbox controller became a little exotic, but in all honesty it took no more than a day or two to grow accustom to them. It wasn’t a big deal for me. Do you guys have more options on a Hotas, or fewer?
 
Question would saving keybindings before update alleviate problems or reduce the amount of tedious work it takes to rebind everything?

If so, does anyone know how to do this?
 
Good question, as I saw bindings file for beta have same location as usual ones.

I will just save beta ones, and see what happen if I bring them back when the patch hits.
 
When the patch goes live, you will see a yellow (!) next to options > controls.

In the bindings screen, you will see a yellow (!) next to every new unbound control. There aren't that many, but you won't know what each one of them actually does until you bind it and/or try to do stuff and need to trigger something. I'd expect there to be a lot of people asking for and sharing control bindings. One thing I'd suggest, if you haven't done it already, is attaching a gamepad of some description and using that for the FSS and the like. I found it to be the most natural way to bind the controls - some of them, such as the zoom functions, work much better on, say, an Xbox controller.
 
When the patch goes live, you will see a yellow (!) next to options > controls.

In the bindings screen, you will see a yellow (!) next to every new unbound control. There aren't that many, but you won't know what each one of them actually does until you bind it and/or try to do stuff and need to trigger something. I'd expect there to be a lot of people asking for and sharing control bindings. One thing I'd suggest, if you haven't done it already, is attaching a gamepad of some description and using that for the FSS and the like. I found it to be the most natural way to bind the controls - some of them, such as the zoom functions, work much better on, say, an Xbox controller.

Sweet mother of pearl , i never even bothered with assigning camera controls due to the plethora of new keybinds. Ah well guess i kinda have to as im eager to try out some deep space exploration mining once the test build goes live.
 
Good question, as I saw bindings file for beta have same location as usual ones.

I will just save beta ones, and see what happen if I bring them back when the patch hits.

from what I remember (and it was a long time ago) the changed keybinds in Beta transfered to Live when it happened.

You can check this by changing a keybind in Beta and see if it is also changed in live (I think)

But don't quote me on that :D
 
Back
Top Bottom