http://bugs.winehq.org/show_bug.cgi?id=33330
Bug #: 33330 Summary: Guild Wars 2: Some graphics options are greyed out in wine 1.5.22. Product: Wine Version: 1.5.22 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 AssignedTo: wine-bugs@winehq.org ReportedBy: zdbiohazard2@gmail.com CC: julliard@winehq.org Classification: Unclassified Regression SHA1: 62f22dd4e3ab4f4b21f8e6b571fd7f9ba3547020
Guild Wars 2 has a few options in the graphics configuration that can only be enabled if the system meets some unstated requirements (High-quality world and character textures). In wine 1.5.21, they work as expected, and the game itself runs remarkably well at maximum quality on my system. Starting with wine 1.5.22, the options are greyed out, and the game runs terribly even at low quality.
I have a hunch that the game is not detecting my 64-bit system and is falling back to 32-bit, as the options in question are known to only be available in 64-bit Windows.
I bisected the regression down to commit 62f22dd4e3ab4f4b21f8e6b571fd7f9ba3547020, and reverting that commit makes it work fine in both 1.5.22 and 1.5.27 (didn't test other versions.)
Note: Guild Wars 2 requires the Awesomeium patch to function completely (unrelated to graphics options), and I made sure to do the testing without it, just in case.
Also, I ran across a this forum thread while working on this, so it's not just me seeing this problem: http://forum.winehq.org/viewtopic.php?f=8&t=18172
http://bugs.winehq.org/show_bug.cgi?id=33330
--- Comment #1 from Alexandre Julliard julliard@winehq.org 2013-04-04 03:51:18 CDT --- Probably it depends on HighestUserAddress, which can potentially change. You could try reverting just that part.
http://bugs.winehq.org/show_bug.cgi?id=33330
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
http://bugs.winehq.org/show_bug.cgi?id=33330
--- Comment #2 from Ryan Turner zdbiohazard2@gmail.com 2013-04-04 13:25:35 CDT --- Created attachment 44090 --> http://bugs.winehq.org/attachment.cgi?id=44090 Switch GetSystemInfo back to using SystemBasicInformation for HighestUserAddress
It's definitely HighestUserAddress. The attached patch switches GetSystemInfo back to using SystemBasicInformation for HighestUserAddress, and the problem goes away.
The patch also adds a call to FIXME() to show what SystemBasicInformation and system_info are when GetSystemInfo is called, and as this log snippet shows; SystemBasicInformation always has 0x7FFEFFFFFFFEFFFF, and system_info changes all over the place, including being zero sometimes.
fixme:reg:GetSystemInfo HighestUserAddress: sbi:0x7FFEFFFFFFFEFFFF system_info:0x7B8B60000033F370 fixme:reg:GetSystemInfo HighestUserAddress: sbi:0x7FFEFFFFFFFEFFFF system_info:0x0 fixme:reg:GetSystemInfo HighestUserAddress: sbi:0x7FFEFFFFFFFEFFFF system_info:0x7B82000000000001 fixme:reg:GetSystemInfo HighestUserAddress: sbi:0x7FFEFFFFFFFEFFFF system_info:0x7B86A1273556DD18 fixme:reg:GetSystemInfo HighestUserAddress: sbi:0x7FFEFFFFFFFEFFFF system_info:0xF6E00010F7587676 fixme:reg:GetSystemInfo HighestUserAddress: sbi:0x7FFEFFFFFFFEFFFF system_info:0x0 fixme:reg:GetSystemInfo HighestUserAddress: sbi:0x7FFEFFFFFFFEFFFF system_info:0xF768C9C2355612F8 fixme:reg:GetSystemInfo HighestUserAddress: sbi:0x7FFEFFFFFFFEFFFF system_info:0xF6E00010F7587676 fixme:reg:GetSystemInfo HighestUserAddress: sbi:0x7FFEFFFFFFFEFFFF system_info:0xF6E00010F7587676 fixme:reg:GetSystemInfo HighestUserAddress: sbi:0x7FFEFFFFFFFEFFFF system_info:0x1100003B5BF7B0 fixme:reg:GetSystemInfo HighestUserAddress: sbi:0x7FFEFFFFFFFEFFFF system_info:0x7B87E9BB3556D4C8 fixme:reg:GetSystemInfo HighestUserAddress: sbi:0x7FFEFFFFFFFEFFFF system_info:0x0 fixme:reg:GetSystemInfo HighestUserAddress: sbi:0x7FFEFFFFFFFEFFFF system_info:0x7B8200007B8B76A8 fixme:reg:GetSystemInfo HighestUserAddress: sbi:0x7FFEFFFFFFFEFFFF system_info:0x7BC383373556D7C8 fixme:reg:GetSystemInfo HighestUserAddress: sbi:0x7FFEFFFFFFFEFFFF system_info:0xF6E00010F7587676 fixme:reg:GetSystemInfo HighestUserAddress: sbi:0x7FFEFFFFFFFEFFFF system_info:0xF6E000100001EA78
http://bugs.winehq.org/show_bug.cgi?id=33330
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |9181b7e8763e9070f6a1d636aeb | |882db829867d8 Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #3 from Alexandre Julliard julliard@winehq.org 2013-04-04 13:56:05 CDT --- Should be fixed by 9181b7e8763e9070f6a1d636aeb882db829867d8.
http://bugs.winehq.org/show_bug.cgi?id=33330
--- Comment #4 from Ryan Turner zdbiohazard2@gmail.com 2013-04-04 18:22:12 CDT --- Just built commit f50e6495785f367d0203201c709ded732c1ca1d1 (which includes cd03a51e7ddcafb3cf98b6c1dd5469bb92b8adcd and 9181b7e8763e9070f6a1d636aeb882db829867d8). Sure enough, the problem is fixed.
Thanks for the awesomely fast fix! :)
http://bugs.winehq.org/show_bug.cgi?id=33330
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #5 from Alexandre Julliard julliard@winehq.org 2013-04-12 13:46:31 CDT --- Closing bugs fixed in 1.5.28.
-
wine-bugs＠winehq.org