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
https://drive.google.com/open?id=1nutxin1t--usvYJQyPgFKRtghqwWqw8A
I'm still baffled by this issue, the controls seems to be affected by at least two files: 'Settings.ini' and 'Highscores', both are located in the following folder: C:\Users\Username\My Games\Pinball Arcade.
When I rebind the keys in-game both files are updated with matching time stamps, if I replace these files with my backup copies my previous control scheme is also restored.
Still, a real fix would be appreciated !
I've got the same issues with the UI for choosing keys not even responding to new key inputs. I couldn't actually find any manual for this, I assume the process is to go into options, double-click on an entry (which will turn yellow), then press the new key you wish to map to?
This is now 4 months old, any progress on the bug? I'd be glad to work with the programmer if they're unable to reproduce the issue - it's 100% repeatable for me.
Can someone please post an example settings.ini?
Deleting it resets the controls to default, however you sacrifice all local scores, camera, lighting, sound adjustments and table goals.
The current exe (1.71.25) seems to be incapable of writing binding changes to that file - My suspicion is those changes are supposed to be written to a specific line number but there is a mismatch, hence the corruption (null) error.
The previous exe (1.71.23) doesn't have that issue and can correctly write the binding lines or reset them to default. If you try to edit them with the current exe you'll have to rollback again to fix it.
Cool...seems to work just fine. Thanks