http://bugs.winehq.org/show_bug.cgi?id=31860
Bug #: 31860 Summary: Guild Wars 2: Raw input is broken Product: Wine Version: 1.5.14 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: sworddragon2@aol.com Classification: Unclassified
After the last known raw input bug with Guild Wars 2 was solved (#31702) I decided to buy it. But on the first start (after my character was created) I got some troubles with the mouselook. If I'm pressing the right mouse button and want to look around this works only up to a maximum of ~90° (even a little less). After this I can't continue looking around in the same direction - but I can go back to the other direction until it stops again after ~90°.
http://bugs.winehq.org/show_bug.cgi?id=31860
Samuel Nelson valczir.darkvein@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |valczir.darkvein@gmail.com
--- Comment #1 from Samuel Nelson valczir.darkvein@gmail.com 2012-10-02 15:19:04 CDT --- (In reply to comment #0)
After the last known raw input bug with Guild Wars 2 was solved (#31702) I decided to buy it. But on the first start (after my character was created) I got some troubles with the mouselook. If I'm pressing the right mouse button and want to look around this works only up to a maximum of ~90° (even a little less). After this I can't continue looking around in the same direction - but I can go back to the other direction until it stops again after ~90°.
Which version of Wine are you using? That is the issue described in #31702, which should be fixed in Wine version 1.5.14. If you are using PlayOnLinux (or PlayOnMac), I *believe* that they haven't quite updated to 1.5.14 yet - so you may just need to wait until they have a 1.5.14-GuildWars2 version (because 1.5.14 still needs the awesomium patch for the trading post to work).
If you are using PlayOn* to run Guild Wars 2, you can tell it to use Wine 1.5.14 instead of 1.5.12-GuildWars2, and then just access the trading post by following this post: https://plus.google.com/u/0/115031774996640834812/posts/bhqrGZDqbEJ
http://bugs.winehq.org/show_bug.cgi?id=31860
--- Comment #2 from sworddragon2@aol.com 2012-10-02 16:05:31 CDT --- I'm using Wine 1.5.14 from the official WineHQ ppa.
http://bugs.winehq.org/show_bug.cgi?id=31860
voidcastr voidcastr@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |voidcastr@gmail.com
--- Comment #3 from voidcastr voidcastr@gmail.com 2012-10-02 16:22:43 CDT --- Are you _sure_? What is the output of wine --version ?
I'm asking because http://bugs.winehq.org/show_bug.cgi?id=31702 was considered fixed... you are the first one reporting the issue since the release of 1.5.14.
If it's really 1.5.14, it might be interesting to know... - if you experience the limit on _every_ attempt of turning the camera - what window manager you are using
http://bugs.winehq.org/show_bug.cgi?id=31860
--- Comment #4 from Samuel Nelson valczir.darkvein@gmail.com 2012-10-02 16:28:09 CDT --- (In reply to comment #3)
Are you _sure_? What is the output of wine --version ?
I'm asking because http://bugs.winehq.org/show_bug.cgi?id=31702 was considered fixed... you are the first one reporting the issue since the release of 1.5.14.
If it's really 1.5.14, it might be interesting to know...
- if you experience the limit on _every_ attempt of turning the camera
- what window manager you are using
In addition, if it really is 1.5.14, is GW2 set to Fullscreen, Windowed Fullscreen, or Windowed?
http://bugs.winehq.org/show_bug.cgi?id=31860
--- Comment #5 from sworddragon2@aol.com 2012-10-02 19:27:23 CDT ---
Are you _sure_? What is the output of wine --version ?
sworddragon@ubuntu:~$ wine --version wine-1.5.14
- if you experience the limit on _every_ attempt of turning the camera
It happens on every try (even the first one).
- what window manager you are using
Openbox 3.5.0
In addition, if it really is 1.5.14, is GW2 set to Fullscreen, Windowed Fullscreen, or Windowed?
I'm playing at fullscreen mode at 1680x1050.
http://bugs.winehq.org/show_bug.cgi?id=31860
--- Comment #6 from voidcastr voidcastr@gmail.com 2012-10-03 02:34:12 CDT --- (In reply to comment #5)
Are you _sure_? What is the output of wine --version ?
sworddragon@ubuntu:~$ wine --version wine-1.5.14
Damn.
- if you experience the limit on _every_ attempt of turning the camera
It happens on every try (even the first one).
Then, most likely, you do not experience the issue described and fixed in http://bugs.winehq.org/show_bug.cgi?id=31702 The problem in there was basically a throttling of the activation of XInput2, which is -- among other things -- responsible for suppressing the cursor movement in certain circumstances. This throttling (avoiding subsequent activations within 1000ms) was applied in unnecessary cases.
To me, it seems like XI2 does not get activated at all for you... i.e. the invisible mouse cursor hits the edge of the screen when turning, instead of remaining in place.
Are you familiar with compiling wine from source? If so, we could check the above theory.
- what window manager you are using
Openbox 3.5.0
I guess that's not a widespread one among GW2 players. If it is somehow related to the problem, this might explain why nobody else reported the issue. To either confirm or refute Openbox being the cause, you could thy another WM... say xfwm.
http://bugs.winehq.org/show_bug.cgi?id=31860
--- Comment #7 from sworddragon2@aol.com 2012-10-03 09:01:26 CDT ---
Are you familiar with compiling wine from source? If so, we could check the above theory.
No, but I can try it. I have now get Wine from git and made my first try. It failed due to missing dependencies and I tried to install them like suggested in the Wiki (I'm using Ubuntu). But resolving the dependencies failed (which is unfortunately not rare on a build-dep with Ubuntu). I will add the log as an attachment. Maybe you can say me what I have to do now.
I guess that's not a widespread one among GW2 players. If it is somehow related to the problem, this might explain why nobody else reported the issue. To either confirm or refute Openbox being the cause, you could thy another WM... say xfwm.
I have now uninstalled LXDE with Openbox and installed Unity with Compiz. After a reboot I have tested this again but the problem still exists.
http://bugs.winehq.org/show_bug.cgi?id=31860
--- Comment #8 from sworddragon2@aol.com 2012-10-03 09:02:14 CDT --- Created attachment 41946 --> http://bugs.winehq.org/attachment.cgi?id=41946 Compiling failure
http://bugs.winehq.org/show_bug.cgi?id=31860
--- Comment #9 from Samuel Nelson valczir.darkvein@gmail.com 2012-10-03 09:38:22 CDT --- Just FYI, I use many different window managers (and a couple of desktop environments), and GW2 works the same across all of them. I don't think it's that.
sworddragon2: I'm curious if it was working any better with any previous versions of Wine. I don't know how ubuntu works these days (they lost my interest when they included networkmanager before it was ready, way back when I was in college), but if it's possible, could you try to install previous versions of Wine through your package manager?
If ubuntu doesn't have packages for earlier versions of Wine, could you install PlayOnLinux and try to download a few different versions of Wine (I'm most specifically interested in 1.5.9 and up, including the -GuildWars2 versions), then try launching GW2 with them and see if anything changes?
Also, try changing to windowed fullscreen or windowed mode and let us know if that changes anything.
http://bugs.winehq.org/show_bug.cgi?id=31860
--- Comment #10 from sworddragon2@aol.com 2012-10-03 10:30:51 CDT --- I have tested now Wine 1.5.13 in all 3 modes (window, windowed fullscreen, fullscreen) and the same for 1.5.14 but there is no difference. At last I have looked if there are any differences with the virtual desktop enabled/disabled and if there are differences between Windows XP and Windows 7 but the bug appears every time with the exact same behavior.
http://bugs.winehq.org/show_bug.cgi?id=31860
--- Comment #11 from voidcastr voidcastr@gmail.com 2012-10-03 10:33:12 CDT --- (In reply to comment #8)
Created attachment 41946 [details] Compiling failure
Though this is really strange (my libsane-dev depends on libtiff4-dev... not v5), this approach won't work anyway on Ubuntu x64.
Instead, you might want to follow the instructions here: http://wiki.winehq.org/WineOn64bit Don't worry, it's really like copy&paste, but it will take some time (mainly for the execution of debootstrap).
AFAIK, this is currently the only way to compile a 32bit wine on a 64bit Ubuntu... and this is exactly what you are trying to achieve.
http://bugs.winehq.org/show_bug.cgi?id=31860
--- Comment #12 from sworddragon2@aol.com 2012-10-03 11:50:58 CDT ---
Though this is really strange (my libsane-dev depends on libtiff4-dev... not v5), this approach won't work anyway on Ubuntu x64.
Maybe because I'm using Ubuntu 12.10 dev.
Instead, you might want to follow the instructions here: http://wiki.winehq.org/WineOn64bit Don't worry, it's really like copy&paste, but it will take some time (mainly for the execution of debootstrap).
The instructions need "apt-get build-dep wine". apt will choose wine1.5 for wine which will result in the same error.
But this remembers me on one thing. With Wine 1.5.13 I have tried out Slender (it was affected by the main Raw Input bug too) to check if it is working fine. I could move the mouse around but it stoped at ~180°. I thought this is the normal behavior but now I think this could be this bug too. I have tested this now with Wine 1.5.14 and the behavior still exists in Slender. Can you test Slender v0.9.7 (it is free) if you can move around 360° with your mouse?
http://bugs.winehq.org/show_bug.cgi?id=31860
--- Comment #13 from voidcastr voidcastr@gmail.com 2012-10-03 12:54:55 CDT --- (In reply to comment #12)
Though this is really strange (my libsane-dev depends on libtiff4-dev... not v5), this approach won't work anyway on Ubuntu x64.
Maybe because I'm using Ubuntu 12.10 dev.
Well... most likely. ^^
Instead, you might want to follow the instructions here: http://wiki.winehq.org/WineOn64bit Don't worry, it's really like copy&paste, but it will take some time (mainly for the execution of debootstrap).
The instructions need "apt-get build-dep wine". apt will choose wine1.5 for wine which will result in the same error.
Well, actually you debootstrap to precise (12.04) according to this guide... you just need a sources.list of precise (preferably containing the wine-dev ppa). I could attach mine if you like.
This will work because with "sudo chroot /var/chroot" you enter the context of the encapsulated 12.04 system you created with debootstrap. Thus, "apt-get build-dep wine" will not be processed by your 12.10 package manager but by the one of the 12.04 (precise) system.
But this remembers me on one thing. With Wine 1.5.13 I have tried out Slender (it was affected by the main Raw Input bug too) to check if it is working fine. I could move the mouse around but it stoped at ~180°. I thought this is the normal behavior but now I think this could be this bug too. I have tested this now with Wine 1.5.14 and the behavior still exists in Slender. Can you test Slender v0.9.7 (it is free) if you can move around 360° with your mouse?
Gonna try it tomorrow if nobody else did it before.
http://bugs.winehq.org/show_bug.cgi?id=31860
--- Comment #14 from sworddragon2@aol.com 2012-10-03 16:04:13 CDT --- I followed the guide and could successfully compile Wine (there were some permission issues after exiting the chroot but I have solved them):
sworddragon@ubuntu:~$ /var/chroot/wine/wine --version wine-1.5.14-142-g730479e
After backing up my old ~/.wine directory, creating a new one and making a symlink to the old "Program Files (x86)" folder I can start the game. I have tested if the bug still exists in the current git and it does. But I'm now able to test any patches after you have an idea.
http://bugs.winehq.org/show_bug.cgi?id=31860
--- Comment #15 from Alexandre Julliard julliard@winehq.org 2012-10-03 16:12:16 CDT --- You should get a +cursor trace to check if XInput 2 is working.
http://bugs.winehq.org/show_bug.cgi?id=31860
--- Comment #16 from sworddragon2@aol.com 2012-10-03 16:15:18 CDT --- I don't know how to make such a trace.
http://bugs.winehq.org/show_bug.cgi?id=31860
--- Comment #17 from Alexandre Julliard julliard@winehq.org 2012-10-03 16:20:48 CDT --- http://wiki.winehq.org/FAQ#head-16da35b6327024d6ea576e3678488b16862d0f5e
http://bugs.winehq.org/show_bug.cgi?id=31860
--- Comment #18 from voidcastr voidcastr@gmail.com 2012-10-03 16:21:40 CDT --- First, try if you can also observe the issue trying to rotate your character in the login screen. If so, this might save you a lot of time on subsequent attempts.
(In reply to comment #16)
I don't know how to make such a trace.
Start the game with WINEDEBUG=+cursor /compiled_wineroot/wine /path/to/Gw2.exe -dx9single &> log.txt
Then try to rotate the character/camera a few times and exit the game.
Now, analyze log.txt. For every rotation attempt you should see - several lines starting with "trace:cursor:enable_xinput2" in the log, directly below each other - one line starting with "trace:cursor:disable_xinput2"
At least that's what I get.
http://bugs.winehq.org/show_bug.cgi?id=31860
--- Comment #19 from sworddragon2@aol.com 2012-10-03 16:50:33 CDT ---
First, try if you can also observe the issue trying to rotate your character in the login screen. If so, this might save you a lot of time on subsequent attempts.
Yes, the bug also appears on the character selection screen.
Start the game with WINEDEBUG=+cursor /compiled_wineroot/wine /path/to/Gw2.exe -dx9single &> log.txt
Then try to rotate the character/camera a few times and exit the game.
In the attachments is the log.
http://bugs.winehq.org/show_bug.cgi?id=31860
--- Comment #20 from sworddragon2@aol.com 2012-10-03 16:51:07 CDT --- Created attachment 41962 --> http://bugs.winehq.org/attachment.cgi?id=41962 Cursor trace
http://bugs.winehq.org/show_bug.cgi?id=31860
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #21 from Alexandre Julliard julliard@winehq.org 2012-10-04 01:01:23 CDT --- warn:cursor:X11DRV_XInput2_Init couldn't load libXi.so.6
You don't have XInput2.
http://bugs.winehq.org/show_bug.cgi?id=31860
--- Comment #22 from voidcastr voidcastr@gmail.com 2012-10-04 01:40:23 CDT --- (In reply to comment #21)
warn:cursor:X11DRV_XInput2_Init couldn't load libXi.so.6
You don't have XInput2.
Hmm, wine does not seem to depend on it (is it supposed to?)... so try sudo apt-get install libxi6
http://bugs.winehq.org/show_bug.cgi?id=31860
--- Comment #23 from sworddragon2@aol.com 2012-10-04 09:27:54 CDT ---
Hmm, wine does not seem to depend on it (is it supposed to?)... so try
Yes, it is supposed to (what I don't like). Wine doesn't even depend on libxcursor1:i386 which will result in corrupted cursor graphics in a lot of games (for example Diablo 3, Guild Wars, Guild Wars 2). I have already opened a ticket for this here: https://bugs.launchpad.net/ubuntu/+source/wine1.4/+bug/960334 Bug the ticket got a "Won't Fix".
sudo apt-get install libxi6
libxi6 is installed but libxi6:i386 was missing. I have installed it now and all is working fine.
http://bugs.winehq.org/show_bug.cgi?id=31860
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #24 from Austin English austinenglish@gmail.com 2012-10-09 13:23:16 CDT --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=31860
Scott Ritchie scott@open-vote.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |scott@open-vote.org
--- Comment #25 from Scott Ritchie scott@open-vote.org 2012-10-19 18:52:47 CDT --- Again, the libraries are already on the recommends list. You are forcing Wine's install by explicitly disabling the installation of recommends, then complaining that the recommended packages are not installed.
The Wine package depends on libraries that are required for it to run (eg glibc). Stuff that Wine dlopens on demand (and degrades gracefully if unavailable) are placed in recommends. This is by Debian/Ubuntu policy, and this policy is entirely sensible: imagine what would happen if you were on a system that needed a Wine app but couldn't, for some reason, use the system-provided version of libxi6.
If I made this a dependency rather than a recommends, apt would refuse to install Wine even though many useful Wine programs would work perfectly (and even then only the animated cursors would not work in the ones that didn't).
This is a problem that only gets created when users who "know what they're doing" explicitly disable the installation of default-installed Recommended packages but actually need them.
-
wine-bugs＠winehq.org