wine users - May 2011 - Input slowdown with Mass Effect in git

This usually occurs to me after about 15-20 minutes of playing Mass Effect in
git and the latest xorg-server for gentoo (1.10.2). Overrides are d3dx9_36 and
dinput8 (http://bugs.winehq.org/show_bug.cgi?id=16822).

After some time, the input response from the keyboard slows to about 1000 ms,
hence making the game unplayable. The mouse input however remains sharp. When I
quit the game, the keyboard input remains slow when I type in Konsole or browse
the web. When I go to full screen console (CTRL+ALT+F1) and type, the keyboard
input is fine. From what I understand, this could be a wine-x11 or a xorg-server
bug.

The output from the game reveals nothing to really show the problem. I would
like to have some input from the devs on how to find out what's wrong. How
could I find if it's a wine-x11 or a xorg-server issue? Any other folks
experiencing this too?

Thanks!

On 5/30/11 6:17 PM, Das Letzte Einhorn wrote:
> This usually occurs to me after about 15-20 minutes of playing Mass Effect
in git and the latest xorg-server for gentoo (1.10.2). Overrides are d3dx9_36
and dinput8 (http://bugs.winehq.org/show_bug.cgi?id=16822).
>
> After some time, the input response from the keyboard slows to about 1000
ms, hence making the game unplayable. The mouse input however remains sharp.
When I quit the game, the keyboard input remains slow when I type in Konsole or
browse the web. When I go to full screen console (CTRL+ALT+F1) and type, the
keyboard input is fine. From what I understand, this could be a wine-x11 or a
xorg-server bug.
Here is something you can try next time this happens:

Open the full screen session and type in:

ps -ef | grep wine

This should give you a listing of processes running under Wine with the 
game functional.

Switch back to the game's console and stop the program.

Switch back to the full screen session and repeat the command.  There 
should be NO Wine processes running.  If there are, type in wineserver 
-k (this kills the Wine server and should stop all Wine processes.)

Check if a windowed keyboard session now displays the problem.  If it 
does then this might be an xorg problem.  If it does not, this does not 
mean that Wine is the cause.

Try to get the problem to occur again, but do NOT stop the wine 
processes.  Now go to a windowed session and see if the problem is 
present and then stop the Wine processes.  If the problem goes away, it 
is very likely, but not 100% that the problem is with Wine.

Others may add to troubleshooting procedures.

James McKenzie

Hmm, in today's git I have been able to play for more than two hours
straight with no keyboard input slowdown issues. I will continue to test this
during the week and see if it happens again.