http://bugs.winehq.org/show_bug.cgi?id=23643
Summary: America's Army 3.0 goes black after about ten minutes of play Product: Wine Version: 1.2-rc7 Platform: x86 OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: dank@kegel.com
I installed Steam with rm -rf ~/.wine sh winetricks sandbox gecko corefonts steam After disabling in-game notifications and chat in the Steam settings as usual, I downloaded AA3 with Steam successfully.
Running crashed immediately because it needed msvcp80.dll; winetricks vcrun2005 worked around that.
It then crashed quickly anyway (bug 19885); running it outside Steam with cd ~"/.wine/drive_c/Program Files/Steam/steamapps/common/america's army 3/Binaries" wine AA3Game.exe worked around that.
It then started, but screen went black right after game prompted for username. Setting a virtual desktop in winecfg worked around that.
It then ran fine for ten minutes, and then seemed to hang. There were still sounds, so it wasn't completely hung. This happened both times I tried it. There was nothing suspicious on the console.
(The game suffers from The Mouse Bug, so you have to scrub the mouse around to compensate. I haven't tried any patches or settings for this yet. Tips for newbies: in the third part of the initial obstacle course, you can't turn, you have to sidestep and backstep to get through the maze. In the weapons training, use Space to pick up the weapon.)
http://bugs.winehq.org/show_bug.cgi?id=23643
--- Comment #1 from Dan Kegel dank@kegel.com 2010-07-13 20:14:40 --- It seems to happen after the game loses focus while I'm trying to look something up on the web...
http://bugs.winehq.org/show_bug.cgi?id=23643
--- Comment #2 from Dan Kegel dank@kegel.com 2010-07-13 20:19:24 --- ( more newbie tips at http://www.americasarmy.com/downloads/files/AA3_Quickstart_Guide.pdf )
http://bugs.winehq.org/show_bug.cgi?id=23643
--- Comment #3 from Dan Kegel dank@kegel.com 2010-07-13 23:30:07 --- I'm starting to think this is the same bug as is worked around by using a virtual desktop. If I run without a virtual desktop, I reliably see this black screen right after the login prompt.
http://bugs.winehq.org/show_bug.cgi?id=23643
--- Comment #4 from Austin English austinenglish@gmail.com 2010-07-15 00:53:26 --- Works fine for me in 1.2-rc7 / nvidia 9800 gtx+ / 256.25 / metacity.
I didn't use a virtual desktop, alt tabbed between AA3/xchat/firefox several times, and still finished the first few tutorials. I had a black screen for a second or two when starting a tutorial, but the video showed soon after (load lag, I presume).
http://bugs.winehq.org/show_bug.cgi?id=23643
--- Comment #5 from Dan Kegel dank@kegel.com 2010-07-15 12:59:10 --- Maybe the window manager matters then - I'm on Gentoo with KDE 4.
http://bugs.winehq.org/show_bug.cgi?id=23643
--- Comment #6 from Matteo Bruni matteo.mystral@gmail.com 2010-09-14 12:36:23 CDT --- Created an attachment (id=30754) --> (http://bugs.winehq.org/attachment.cgi?id=30754) Don't invalidate context if we couldn't get DC obj
I've got something similar here. Can you try this patch and see if it helps?
http://bugs.winehq.org/show_bug.cgi?id=23643
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |matteo.mystral@gmail.com
--- Comment #7 from Matteo Bruni matteo.mystral@gmail.com 2010-10-02 13:21:29 CDT --- A clarification is due. The patch I attached is just a hack which makes things work for me but doesn't solve the underlying issue. The game uses D3D9 to draw its graphics, but it also makes some use of DDRAW, mainly to get informations on the available video memory and to set the display mode. AA3 calls D3D9 functions from one thread but in the meantime it uses DDRAW from another thread. Currently there is no synchronization between D3D9 and DDRAW on the access to wined3d, so hilarity ensues. My patch is just a workaround for one of the possible problems happening because of this issue. A proper solution would be to fix DDRAW locking, replacing the current DDRAW lock with the wined3d one.
http://bugs.winehq.org/show_bug.cgi?id=23643
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Blocks| |24650
http://bugs.winehq.org/show_bug.cgi?id=23643
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #8 from Austin English austinenglish@gmail.com 2011-05-04 15:13:20 CDT --- I suspect this was fixed by 77face22d5365d94b9bfe614ed202692e1523593, I noticed similar issues in Bulletstorm/Mass Effect 2, and they work after that commit.
http://bugs.winehq.org/show_bug.cgi?id=23643
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #9 from Alexandre Julliard julliard@winehq.org 2011-05-13 13:32:50 CDT --- Closing bugs fixed in 1.3.20.