Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
TL;DR - It's mixing up keyboard layouts in creative ways now, and I can't get it to stop.
It's easy to replicate: just install a Dvorak keyboard layout (included in Windows) and try to play the game. The bug is the same regardless of which keyboard layout you use. This behavior is also not standard among other games; it's a Frostpunk-specific issue that I've never seen anywhere else.
Still a problem, exact same setup of a US International keyboard and a Dvorak keyboard layout. However, using windows 8.1.
I use Dvorak on a QWERTY keyboard and shift the camera controls one step to the right, so WASD is ESDF on the physical keyboard and mapped in Dvorak to be <period>OEU.
I found that when remapping keys, I had to press the key that in Dvorak emits the QWERTY of the key I wanted to remap, but then also the camera control remapping had one fewer redirect and it took some trial and error to figure out what I needed to do.
I have the panels mapped to YIXK, going down the right side of the camera controls. Using Y as an example, on the QWERTY layout that's physically the T key, so I actually needed to make it remap the T key, so I pressed K on the QWERTY keyboard as that's what emits T in Dvorak. This took a lot of trial and error but what are there, twelve-fifteen keys to map? Not onerous (but losing the generator panel is annoying). I seem to recall the camera controls were a bit different but again, trial and error will get you there even if they keymap showing up in the UI is effectively nonsense.
I found on restarting the game the next day that the keys listed in the controls screen show that the camera controls are mapped to the QWERTY version of the keys and everything else shows the Dvorak mapping. Unfortunately I can't easily run through this setup again as it's on a different computer (my current setup has a keyboard that switches so Windows doesn't know about it... I still lost the generator panel though but maybe that's broken in general? I seem to recall it working when I first installed the game but then didn't play for a long time.)
My current Controls UI shows this:
Camera Forward E
Camera Backward D
Pan Left S
Pan Right F
Rotate Left R
Rotate Right W
Zoom In A
Zoom Out ;
Toggle World `
Camera Center C
Construction Panel Y
Book Of Laws I
Technology Tree K
Economy Panel J
Tutorial Summary Q
Generator Panel ' (doesn't seem to work)
...but I think for most of those I had to demap them myself for initial entry. Camera controls show QWERTY but I think I had to type the Dvorak key that mapped to that, e.g. the D physical key makes E appear. For the panels I think it was the same problem but with another step, Construction being Y, but that's on the physical T key so I had to figure out what Dvorak key makes T (which is K) and then type the key which actually makes K (which is V).
...anyway I hope that FP2 gets some love in keyboard remapping. I've never found it too hard to program when you do it up front but of course bolting something like this into an existing game is tough due to all of the hard coding that takes place. I'm a little surprised that a European company got this wrong though with what I assume is a proliferation of keyboard maps, language packs, etc. on the development team but the game itself is a triumph and this keyboard stuff is a minor challenge.
I also hope this helps someone. It was a lot of trial and error to pick up this game again after buying it long ago and only now trying to play it on a laptop where I make Windows remap keys for me. (I also wish the touchpad worked better in the game but camera controls on the keyboard are good enough.)
I was able to get to a point where the game was using default mappings (e.g. pressing the physical key labeled "O" on your keyboard to open the Temperature Overlay) and everything was working as expected.
If you want to replicate the default key bindings of a Qwerty keyboard without these issues, your key mappings should look like this in the UI:
Now when playing the game, you should be able to press the default keys and get the expected UI elements. (The one exception - you will have to press the "J" key to open Tutorial Summary. This can't be remapped to the "H" key with this workaround.)
It seems like there are two problems:
adjustments accordingly within the game, so when I try to play the game in a Qwerty layout, it's reverse-mapping the keys. (Example: I press "X" on the keyboard - in Dvorak, the "X" character is generated by the "B" key - the game interprets this as pressing the "X" key and receiving the "B" character.)
It's very wonky, and I hope this isn't a problem in Frostpunk 2. But hopefully the above solution can help some other folks.
Verify the following suggestions:
1) Confirm your keyboard is set to the English language.
Go to Control panel. Click on the "Region and Language" icon.
If the setting appears to be in a foreign language, change it to English/U.S.
Click on Keyboards and Language, verify the keyboard language is set to English.
Click on the Change Keyboard and on the General tab, verify you have the correct language.
2) Check if your number lock key is on. If so, depress the key to disengage it.
3) Run a character key test by using the Microsoft Keyboard Diagnostics (MSKEY) program. While in the MSKEY program, hit several keys to make certain that they are the same keys that are identified in the MSKEY window.
To run the diagnostic MSKEY test, go to Start button. In the start search box, type in mskey and hit enter.
Then start typing the keys that are not typing correctly and see what is returned in the test.
try this it worked for me