TOPIC:

Haven't been around for a while. Now when I play, the game behaves strangely. Some keyboard shortcuts work (F1-F12, Ctrl+1 - Ctrl+9, Shift+Ctrl+1 - Shift+Ctrl+8, Shift+Ctrl+F1 - Shift+Ctrl+F12) but most others don't - X for transparency, M for map, A for rail contruction.. etc etc.

I use a compiled 1.4.2 BTPro version but when I tried 1.3.3 from Ubuntu packages the behavior was exactly the same.
I didn't make any changes to hotkeys.cfg.

@Ubuntu 14.04

Move it and let it make a fresh one?

Saber wrote: Move it and let it make a fresh one?

This behavior was when I had no hotkeys.cfg. And after I created an empty hotkeys.cfg file, the program filled it with default values but still exactly the same behavior.

I am not sure how the game behaves on Linux but on Windows it creates a folder in My Documents that it uses for storing saves, screenshots and cfg files. If you have multiple clients instaled they will all use this folder unless you create a cfg file inside game instalation folder - then the game will use files from instalation folder and will also store all saves and screenshots in there.

So, maybe you have some corrupted hotkey.cfg in your instalation folder?

Try using the original client or download a fresh zip/unzip and launch.

This has happened to me also quite some patches back.

krawco wrote: I am not sure how the game behaves on Linux but on Windows it creates a folder in My Documents that it uses for storing saves, screenshots and cfg files. If you have multiple clients instaled they will all use this folder unless you create a cfg file inside game instalation folder - then the game will use files from instalation folder and will also store all saves and screenshots in there.

So, maybe you have some corrupted hotkey.cfg in your instalation folder?

in Linux it's in ~/.openttd; I deleted this dictionary and purged all previous installs. I also searched for hotkeys.cfg and there are none except in my new installs in the same dictionary as the executable.

Saber wrote: Try using the original client or download a fresh zip/unzip and launch.

This has happened to me also quite some patches back.

I compiled 1.4.2 original version and 1.4.2 BTPro and tried 1.3.3 from Ubuntu repositories, the same behaviour in all cases.