After accessing the debug menu, the S and T keys stop responding. The screen lags out, the sound cuts out, and the S only yields a tiny move backward and the T eventually opens chat. **Also, I notice that it looks like it has to load every chunk every time I turn.
It takes a client reboot to reset this. And I found out this morning that it affects the 1.6 prerelease too.
This is what shows in the launcher every time either key is pressed:
(Not sure where it stops and starts, so I copied a few times)
Client> Starting up SoundSystem... Client> Initializing LWJGL OpenAL Client> (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org) Client> OpenAL initialized. Client> Client> 2013-06-24 18:00:41 [CLIENT] [SEVERE] ########## GL ERROR ########## Client> 2013-06-24 18:00:41 [CLIENT] [SEVERE] @ Pre render Client> 2013-06-24 18:00:41 [CLIENT] [SEVERE] 1281: Invalid value Client> 2013-06-24 18:05:49 [CLIENT] [INFO] Reloading ResourceManager: Default Client> Client> SoundSystem shutting down... Client> Author: Paul Lamb, www.paulscode.com Client> Client> Client> Starting up SoundSystem... Client> Initializing LWJGL OpenAL Client> (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org) Client> OpenAL initialized. Client> Client> 2013-06-24 18:05:51 [CLIENT] [SEVERE] ########## GL ERROR ########## Client> 2013-06-24 18:05:51 [CLIENT] [SEVERE] @ Pre render Client> 2013-06-24 18:05:51 [CLIENT] [SEVERE] 1281: Invalid value Client> 2013-06-24 18:07:29 [CLIENT] [INFO] Reloading ResourceManager: Default Client> Client> SoundSystem shutting down... Client> Author: Paul Lamb, www.paulscode.com Client> Client> Client> Starting up SoundSystem... Client> Initializing LWJGL OpenAL Client> (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org) Client> OpenAL initialized.
I tried changing the controls so that R is walking backward and Q is chat. These seem to work. I tried changing them back to default, but they still don't work. I changed them back to R & Q, and accidentally hit S by habit and the same error/response occurred.
This does not seem to be a problem on my 0.9.5 on my windows 7 pc, only the mac, though I've not intentionally tried to replicate it, it hasn't happened yet.