[Bug 33413] Diablo III: Random non-responding UI elements

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=33413

--- Comment #3 from Felipe Gustavo de Oliveira <felipe.nemesis at gmail.com> 2013-04-20 20:34:25 CDT ---
Are you using setarch i386 -3 wine diablo3.exe to lunch the game?

When warden its active on server side playing the game without setarch in a
x86_64 enviroment always brings gui corruption, low fps and gui elements
stopping to response. Also Auction house stops to work.

Lunching the game with  setarch i386 -3 fix the insue, however the performance
decreases a little.

(In reply to comment #2)
> (In reply to comment #1)
> > Bug happens in any Wine version from 1.5.0 and up, while using proprietary
> > FGLRX driver
> 
> I'm using nVidia blob, and it only started happening with the specified
> regression commit (somewhere between 1.5.27 and 1.5.28)
> 
> > In early Diablo 3 versions this bug didnt occurs, prior the patch 1.0.2 the bug
> > started to happen.
> 
> Unfortunately one can only test with the latest Diablo 3 version, due to the
> way the game is designed.

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.