Keybinds not working after winter update/patch

jeff92k7 · December 2017

My keybinds are not working since the patch yesterday for the winter update. NONE of my keybinds from my keybind file are working. The only custom key commands that are working are the ones I manually set in options>keybinds. if I try to reload my keybind file (/bind_load_file) it appears to work, but the keybinds never actually take effect. I can sit here all day and mash on a custom bound key and nothing happens.

The keybinds were working fine yesterday morning before the winter update.

Is there something I'm doing wrong? or is this a bug in the winter update? It literally makes the game unplayable for me since I have used keybinds in space for almost as long as I have been playing this game.

jeff92k7 · December 2017

I can't even get force verify to work. I have closed down the game repeatedly, restarted, selected force verify, and then logged in, but the game just loads normally. It never verifies anything. when I restart the game, my force verify check is gone (as if it completed), but nothing ever gets verified. What the heck happened in yesterday's update to kill my game like this?

tedgrodzki · December 2017

My binds are non functional as well, in my case I had binds in a subdirectory of the live folder, the "\" is no longer recognized to be able to use that subdirectory.

ie "CombatLog 0$$bind_load_file \subset\combatlog0.txt$$PlayerSay CombatLog Suspended"

daviddxx · December 2017

Check your STO files.. in the " Live " once.. there are 2 new .. x64 / x86 .. copy your Keybind files into these. It should be going after that.

jeff92k7 · December 2017

I was able to get them working again by rebuilding the keybind file (with exactly the same contents) and saving it with exactly the same name in the live folder (exactly the same place).

Not sure what happened to break the keybinds with the update, or why it wouldn't reload the old file with the /bind_load_file command. It just stinks to have to redo the keybinds on all my different characters again - as well as fix the other unrelated keybinds under options/keybinds in-game that get broken when I load the keybind file.

admrenlarreck · December 2017

I had the same issue, What worked for me was going to a character that my keybinds worked on then going into the options and then HUD at the bottom was SAVE UI. I clicked that hen switched to the one where they did not work, and then OPTIONS then HUD then LOAD UI. After two map changes it worked.

toiva · December 2017

After the patch, my display setting were TRIBBLE up, but it seems keybinds and other settings are fine.

frtoaster · December 2017

jeff92k7#4958 wrote: »

if I try to reload my keybind file (/bind_load_file) it appears to work, but the keybinds never actually take effect. I can sit here all day and mash on a custom bound key and nothing happens.

daviddxx wrote: »

Check your STO files.. in the " Live " once.. there are 2 new .. x64 / x86 .. copy your Keybind files into these. It should be going after that.

Daviddxx is correct. See my explanation (highlighted in green) below.

64-bit Game Client

frtoaster wrote: »

More than three weeks ago, I posted this question:

Technical question: What's the purpose of x64\d3dcompiler_47.dll and x86\d3dcompiler_47.dll?

See also: https://www.reddit.com/r/sto/comments/7byvw8/technical_question_whats_the_purpose_of/

It seems that ruinthefun's guess was correct, and everyone who thought otherwise, including me, was wrong. When you select the Tribble shard in the launcher, there is now an option called "Use 32-bit Client" in the "Options" menu. And there are two different game-client executables in the Playtest directory.

Playtest\x64\GameClient.exe
Playtest\x86\GameClient.exe

The old executable Playtest\GameClient.exe has been removed. If you select "Use 32-bit Client" in the launcher, the 32-bit client will run; otherwise, the 64-bit client will run. I have confirmed this in the Windows task manager.

Other changes

Path of UI files

I was highly confused at first, because the keybind that I used to load my custom UI file stopped working. I was ready to report a bug when I realized the problem. It turns out that the path of the commands /ui_load, /ui_save, /ui_load_file, and /ui_save_file is relative to the location of the game-client executable. I was using a relative path instead of an absolute path, and because GameClient.exe was moved, the command /ui_load_file could no longer find my file.

Voice Chat

The "Voice Chat" tab has been removed from the "Options" window in the 64-bit client. It remains in the 32-bit client.
Update 1: Some people have been reporting that they've been unable to run the 64-bit client. They're getting the error message "Unable to start game client: The operation identifier is not valid." It may possibly be related to the Windows 10 Fall Creators Update. See the links below.
https://www.reddit.com/r/sto/comments/7hn50n/64bit_game_client/dqt1k51/

http://forum.arcgames.com/startrekonline/discussion/comment/13302276/#Comment_13302276

http://forum.arcgames.com/startrekonline/discussion/comment/13302278/#Comment_13302278

http://forum.arcgames.com/startrekonline/discussion/1236677/unable-to-launch-tribble

Update 2: The latest Tribble patch has removed the option "Use 32-bit Client" from the launcher. As of December 6, 2017, the launcher starts the 32-bit client even if PrefEntry Launcher.Use32 is set to 0 in the gameprefs.pref file. Both Playtest\x64\GameClient.exe and Playtest\x86\GameClient.exe are still present.[color]

jeff92k7#4958 wrote: »

I can't even get force verify to work. I have closed down the game repeatedly, restarted, selected force verify, and then logged in, but the game just loads normally. It never verifies anything. when I restart the game, my force verify check is gone (as if it completed), but nothing ever gets verified. What the heck happened in yesterday's update to kill my game like this?

I reported this a week ago.

Holodeck ticket 4,626,730: "Force verify" no longer works

Keybinds not working after winter update/patch

Comments