Controls settings still not saved when in limbo menu (patch 4.24.14)


(Ashog) #1

Even though the save settings bug has been generally fixed in-game, under certain circumstances it is not.

For example, after updating, I have connected to a server and, while still having not joined a team, in limbo menu, started editing my keybinds. After I finished, I clicked join button. After I spawned for the first time, I discovered that all my binds were reset to defaults (or still defaults, meaning my editing of them in limbo wasn’t saved). Of course I had to rebind everything in a hurry while in a team (and being scared of an imminent auto-kick for inactivity from a full server). The situation of course can happen only once before one finally rebinds the keys in in-team menu and they get saved. But still it’s a bug that might get visible again after a new patch is released and controls get reverted.

Also, the controls binding menus in limbo and in team are different. For example, the limbo binding menu doesn’t have a “walk” option. Also the default buttons for voice chat are different for both menus (in limbo the default was empty while in in-team menu it was X).

Other controls bugs include long promised but never implemented solution for being able to bind backspace in menu. As of now, pressing backspace only deletes the current binding leaving the box empty. Many people prefer to be able to actually bind backspace button because of its size and convenient location.

Another yet old bug is chat and teamchat swallowing first letters of sentences when bound on rightcrtl, rightshift and rightalt. Very annoying.

Hope that a person responsible for menu and UI finally takes a look at these older bugs.


(Mustang) #2

If you’re talking about editing settings in the frontend then it’s a known problem, tbh just don’t bother with it atm and setup all your things whilst actually in-game (hopefully quickly enough not to get kicked for idling, oh the irony).


(Ashog) #3

Well, ofc it is known! It was supposed to be fixed (as claimed in patch notes) but is not, because tbh for me, I don’t care if it’s a how you call it “frontend” (or limbo) or an in-team menu - all of it is in-game for me, not a launcher anymore. As far as I understand, the known issues thread isn’t followed anymore, correct me if i’m wrong.


(Mustang) #4

The game being able to read ini files and the frontend menu not saving changes are two completely different bugs, I guess they could have described it a bit better though.

(It’s all “in-game” for me also, but I try to use the terms the devs use to avoid confusion and ensure clear communication)


(Ashog) #5

[QUOTE=Mustang;496014]The game being able to read ini files and the frontend menu not saving changes are two completely different bugs, I guess they could have described it a bit better though.

(It’s all “in-game” for me also, but I try to use the terms the devs use to avoid confusion and ensure clear communication)[/QUOTE]

Well, isn’t the frontend using same ini and if not then why? Are we facing the same config mess as in all idtech engine games (the apogee was ETQW with ubermegamessy config locations/system etc). Even though it was flexible, it was hell to debug, unless your configs were of a 1st grader complexity.

Regarding terminology, sorry, I have abandoned the megachan long time ago :wink:
So they call the first menu when u r on a server (aka spec) a frontend menu, and the one after you join a team - a limbo then? Let me know, I want too to be ubersmart and megaconforming :slight_smile:


(Violator) #6

Its a bit annoying to start binding keys then limbo ends or map changes and you are booted out of the bind screen without it saving.


(Mustang) #7

Yea it should at least do some sort of session save so when you go back into settings everything you were halfway though setting up is still there, and you can just click save to apply it or carry on editing from where you got to.