New SRV controls

dreampage · Feb 18, 2019

From today's patch notes:

Controls

Updated 'Classic Context' control scheme to allow the SRV boost button to work correctly once again, and to remove the conflict between handbrake and cycle fire groups

Note - we have had to reassign and in some cases remove some shortcuts. The full list of changes are:

- Moved headlights and cargo scoop to the Y/Triangle button and d-pad directions
- Moved open discovery and camera suite to X/Square button and shoulder buttons
- Moved cycle fire group to Y/Triangle and right d-pad
- Removed galaxy map and system map shortcuts (can still be accessed from left hand panel)

I'm puzzled here. What was wrong with the previous shortcuts? I haven't had any problems with the SRV boost button (it's left click if I interpret it correctly). There was also no conflict between handbrake (B) and cycle fire groups (X+LB/RB). I don't understand why it had to be changed and almost everything put to a new bind.

Do these changes affect the in-ship shortcuts as well? So no instant galaxy map access from the ship or what? Or do these only apply to the SRV? I haven't changed my custom binds (which are not related to this at all) so I just left it as they were before. I tried and still don't have any problems with the SRV. But the options menu stated I have conflicts with the old fire group cycle method (X+LB/RB). But I don't. But if I ever need to change back to the default scheme, the default will be completely unfamiliar to me. Again. So someone please enlighten me why this change was necessary. Thank you.

Bennoj61 · Feb 18, 2019

I have always used the default bindings, and this morning I used my SRV for a bit and absolutely nothing was different. I had installed the update and applied the binding changes. I had never experienced any conflicts.

Clanky Munge · Feb 18, 2019

My mate was on classic, his srv wouldn't boost as the context menu interfered with his thrusters, I'm also on classic and experienced the same problem ages ago, but somehow managed to sort it.

go figure

dreampage · Feb 19, 2019

I'm a bit confused here but the "Classic" setup is different to the "Default" setup? Because in this case I'm not affected at all, yet I don't know why I got the conflict warning at the start screen after the update.

MrJames1944 · Feb 20, 2019

Just to inform. I have not been able to use the boost button (B) on my SRV since the last major update. I've applied the changes shown above but to no avail. The conclusion I draw from this is that further development work is needed, so I'm going to be without a boost button for the foreseeable future. I hate updates!!!

Rebel Yell · Feb 20, 2019

MrJames1944 said:
Just to inform. I have not been able to use the boost button (B) on my SRV since the last major update. I've applied the changes shown above but to no avail. The conclusion I draw from this is that further development work is needed, so I'm going to be without a boost button for the foreseeable future. I hate updates!!!

My boost function was on R-thumbstick (button down), have to check what's not my setting.

Sunyavadin · Feb 22, 2019

dreampage said:
I'm puzzled here. What was wrong with the previous shortcuts? I haven't had any problems with the SRV boost button (it's left click if I interpret it correctly).

You do. I know for a fact that's one control I never altered from the default.

dreampage said:
There was also no conflict between handbrake (B) and cycle fire groups (X+LB/RB). I don't understand why it had to be changed and almost everything put to a new bind.

That seems utterly nonsensical, and completely breaks consistency between ship and SRV controls, surely?

dreampage said:
I haven't changed my custom binds (which are not related to this at all) so I just left it as they were before. I tried and still don't have any problems with the SRV. But the options menu stated I have conflicts with the old fire group cycle method (X+LB/RB). But I don't.

Yep. I got the exclamation on my cycle fire group controls, just confirmed I wanted them to stay as they are and it went away, as usual.

dreampage said:
But if I ever need to change back to the default scheme, the default will be completely unfamiliar to me. Again. So someone please enlighten me why this change was necessary. Thank you.

This is why I keep a list of all my custom binds, so if I ever lose them, it'll only take a minute or so to set it all back to a sensible, intuitive layout.

Mr Cynical · Feb 22, 2019

This only affects the.'classic' control set, so if you run default, or a customised default, it won't (shouldn't!) affect yours.

Sunyavadin · Feb 22, 2019

What's the difference between "Classic" and "Default"?
Just curious, since I created a custom set of binds within 10m of first playing, after my first attempt to launch ended with me blowing up on the pad, so I have no experience of anything but my controls, and had no idea there was more than one preset available.

Also - surely a "Classic" set of binds would be one that never gets existing binds changed, just added to, no? While the "Default" one would change certain binds over time to try and make it more efficient/user-friendly?

Sunyavadin · Feb 22, 2019

It is a nuisance that when they adjust one of the presets, it flashes up the warning on our custom binds, even though they are unaffected, until we save them again. Honestly it should be fairly simple to have the game check which binds the player is using on launch, and if it's not one anything has changed for, not display the warning flags.
If nothing else it's potentially confusing to newer players who suddenly have a big exclamation next to the controls they have selected for something, implying that they have to change them because of some kind of conflict, when there is in fact no issue at all.

Rebel Yell · Feb 22, 2019

Rebel Yell said:
My boost function was on R-thumbstick (button down), have to check what's not my setting.

Quoting me self LOL... all right on me kart, workin' as befoar!

Mr Cynical said:
This only affects the.'classic' control set, so if you run default, or a customised default, it won't (shouldn't!) affect yours.

^^ this! Me use custom layout! Aye!

dreampage · Feb 22, 2019

Mr Cynical said:
This only affects the.'classic' control set, so if you run default, or a customised default, it won't (shouldn't!) affect yours.

OK, this is the piece of info that actually matters to me, thanks.

I've always used the default system with just very few modifications so I'm not affected at all in the end.

Sunyavadin · Feb 22, 2019

Yeah, you're good, like many of us.

As I said, the real nuisance, and potentially a confuser for new players, is that it flags your control scheme no matter which one you use, and new players don't necessarily know that all you need to do is go into your custom controls and just save them again, to make the big warning flags go away. It really shouldn't notify you if you're not using an impacted control scheme.

Mr Cynical · Feb 22, 2019

Yea they could probably have made it clearer. But all is good (apart from all the stuff still broken... Shhhhh

)

MashdTaytuz · Feb 24, 2019

MrJames1944 said:
Just to inform. I have not been able to use the boost button (B) on my SRV since the last major update. I've applied the changes shown above but to no avail. The conclusion I draw from this is that further development work is needed, so I'm going to be without a boost button for the foreseeable future. I hate updates!!!

I was having the same issue...no boost in my SRV. If I remember correctly, I had to undo the binding that allowed me to check the codex while in my SRV. For whatever reason, it was interfering with my ability to boost.

I don't know how your controls are set, but maybe give that a look and see if it isn't what's causing you trouble.