PDA

View Full Version : Stepmania Issue

4ny0n3
March 20th, 2008, 07:39 PM
Hi there everyone, new one here, and a newbie as well. I recently installed the Hardy Alpha 6 (had Gutsy before). I had a problem with stepmania in gutsy which was the keyboard or any input device not responding after some time of playing, and now in Hardy my input goes unresponsive whenever I set the resolution of the game to one matching the desktop's. The game doesn't crash at all, it's just the input that dies.

Do you know of any possible fix to this problem? or could it be because of Hardy? in the case that I had to go back to Gutsy, would there be a fix for it too?

thx for your patience. Any help will be appreciated.
4ny0n3
March 21st, 2008, 06:25 PM
neh.. after endless rebooting, uninstalling and resintalling of Nvidia drivers.. I decided to give Envy a go, and that seemed to have done it, now when the resolution matches that of the desktop the input won't die... :D
atari130xe
July 17th, 2008, 07:49 AM
neh.. after endless rebooting, uninstalling and resintalling of Nvidia drivers.. I decided to give Envy a go, and that seemed to have done it, now when the resolution matches that of the desktop the input won't die... :D

Hey Guy! I dunno what happened with you installation, I got the same problem as you, and cant play Stepmania 4 on Ubuntu Hardy 8.04.1. Like you my keyboard does not respond to the second "ok" to keep going and playing this game. I have installed the graphic drivers with EnvyNg and none of my other programs fails. so.... it's a mistery! anyone to give me a hand?:confused:
Cappy
July 17th, 2008, 09:26 AM
Kill Compiz from ubuntu's special effects manager or
compiz --replace &
OR
turn off your screensaver
(they both are solutions to the same problem)
stealthc
October 31st, 2008, 01:53 AM
Kill Compiz from ubuntu's special effects manager or
compiz --replace &
OR
turn off your screensaver
(they both are solutions to the same problem)

I turned off both, problem seems to be solved. I turned compiz back on, seems to still work ok.

Why on earth would the screen saver do this? Is there a way that this can be fixed or a means of automating turning the screen saver off and on like this?