Unable to close in-game console
Product: Battlefield 1
Platform:PC
Summarize your bug When the keyboard key above the tab key ("tilde" (~) on US keyboards) is pressed in-game while using Japanese keyboard input (IME), the game becomes bricked until it is restarted.
How often does the bug occur? Every time (100%)
Steps: How can we find the bug ourselves? Use Japanese keyboard input (IME) as the default input before launching the game. Press the tilde key to open the console, then press the tilde key again to attempt to close it. I do not think that you need a Japanese keyboard to test this.
What happens when the bug occurs? The in-game console does not close when the tilde key is pressed. There is no way to recover without losing progress. When this happens during an online match, the user is forced to abandon the match and close the game using Alt-F4.
Please select your region Europe
In what game mode did the bug occur? Conquest
AMD or Nvidia Model Number
Enter RAM memory size in GB
I consider the described issue to be a bug because I have found no built-in way to recover from the "bricked" state without restarting the game. I was however able to work around this.
This is an issue that is important to resolve because one frequently uses the the keys that surround the tilde key, which increases the chances of accidentally pressing it.
Please also note that the tilde key on a US keyboard (layout) is not the tilde key on a Japanese keyboard (layout), but instead that special key switches between alphanumeric and Japanese character input. I just call it the tilde key here so that we all know which it is we talk about.
Workarounds:
- Switch to a non-Japanese keyboard input before launching the game. You will not get stuck this way.
- When stuck, switch to a non-Japanese input using Win-Space (Windows key and spacebar key), then close the console using the "tilde" key. Alt-Shift does not work for switching in-game. Make sure to add another keyboard input along with your Japanese input, e.g. English/US keyboard. If you have this problem on Windows 7 then this workaround will not help.
