http://bugs.winehq.org/show_bug.cgi?id=17402
Summary: Battlefield 2 runs unplayably slow (and mission loading takes longer) on ATi with GLSL Product: Wine Version: 1.1.15 Platform: PC-x86-64 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: ben@atomnet.co.uk
When trying to play Battlefield 2 with an ATi card and GLSL enabled, the mission loading takes far, far longer than it should (several minutes) when it reaches the "Loading Geometry" stage. When it finally loads it runs at about 0.2fps and has odd graphics corruption (mainly on remote hills and the far right part of the screen, unfortunately print screen is black).
Disabling GLSL fixes both these issues but that in turn locks the game to all low quality settings.
ATi driver is 2.1.8395 (9.1) although was present with 8.11 and 8.12 as well (only started using ATi at 8.11).
http://bugs.winehq.org/show_bug.cgi?id=17402
--- Comment #1 from Ben Hodgetts (Enverex) ben@atomnet.co.uk 2009-02-15 10:43:09 --- Created an attachment (id=19475) --> (http://bugs.winehq.org/attachment.cgi?id=19475) Log cropped to the first 3 million lines (+d3d log 1.7GB uncompressed)
Original too large to attach here so uploaded off-site: http://filebin.ca/vyaddg/bf2-d3d.log.tar.lzma (6.7MB).
http://bugs.winehq.org/show_bug.cgi?id=17402
--- Comment #2 from Ben Hodgetts (Enverex) ben@atomnet.co.uk 2009-02-15 10:43:17 --- Created an attachment (id=19476) --> (http://bugs.winehq.org/attachment.cgi?id=19476) Log cropped to the first 3 million lines (+d3d log)
Original too large to attach here so uploaded off-site: http://filebin.ca/vyaddg/bf2-d3d.log.tar.lzma (6.7MB).
http://bugs.winehq.org/show_bug.cgi?id=17402
Ben Hodgetts (Enverex) ben@atomnet.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #19475|Log cropped to the first 3 |Ignore description|million lines (+d3d log | |1.7GB uncompressed) | Attachment #19475|0 |1 is obsolete| |
http://bugs.winehq.org/show_bug.cgi?id=17402
--- Comment #3 from Ben Hodgetts (Enverex) ben@atomnet.co.uk 2009-02-15 11:15:13 --- Ok, the slowdown seems to be caused by the vehicles in some way. Facing them and the game runs 0.2fps, face away and it runs fine.
While facing anywhere else the game just prints:
"fixme:d3d:state_pscale >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from glPointSize(...); @ state.c / 1457"
About 500 times a second but runs ok. But when it slows down the output changes to:
fixme:d3d9:Direct3DShaderValidatorCreate9 stub fixme:d3d_shader:shader_glsl_select >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glUseProgramObjectARB @ glsl_shader.c / 3584 fixme:d3d_shader:shader_glsl_load_constantsF >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glUniform4fvARB() @ glsl_shader.c / 384 fixme:d3d:state_pscale >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from glPointSize(...); @ state.c / 1457 fixme:d3d:state_pscale >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from glPointSize(...); @ state.c / 1457 fixme:d3d:state_pscale >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from glPointSize(...); @ state.c / 1457 fixme:d3d_surface:surface_load_ds_location (0x181130) Not supported with fixed up depth stencil fixme:d3d:state_pscale >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from glPointSize(...); @ state.c / 1457 fixme:d3d_surface:surface_load_ds_location (0x181130) Not supported with fixed up depth stencil
With the "fixme:d3d9:Direct3DShaderValidatorCreate9 stub" message printed about 20 times at the top and this whole sequence is printed out many times each second.
http://bugs.winehq.org/show_bug.cgi?id=17402
--- Comment #4 from Ben Hodgetts (Enverex) ben@atomnet.co.uk 2009-02-15 11:15:48 --- Also the graphical corruption seems unrelated to the slowdown so that can be ignored as I think it may just confuse matters.
http://bugs.winehq.org/show_bug.cgi?id=17402
--- Comment #5 from joaopa jeremielapuree@yahoo.fr 2009-02-15 11:57:31 --- For a seek of performance, any application should be launched with:
WINEDEBUG=-all wine.application.exe
Does this improve the framerate?
http://bugs.winehq.org/show_bug.cgi?id=17402
--- Comment #6 from Ben Hodgetts (Enverex) ben@atomnet.co.uk 2009-02-15 13:08:30 ---
I'm not a newbie, its not a console output issue.
http://bugs.winehq.org/show_bug.cgi?id=17402
--- Comment #7 from Austin English austinenglish@gmail.com 2009-08-26 13:24:32 --- Is this still present in current (1.1.28 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=17402
--- Comment #8 from Austin English austinenglish@gmail.com 2010-09-07 15:10:10 CDT --- Ben, ping.
http://bugs.winehq.org/show_bug.cgi?id=17402
--- Comment #9 from Benjamin Hodgetts ben@xnode.org 2010-09-07 16:42:45 CDT --- I'll test when I get a chance, I don't have access to the games at the moment.
http://bugs.winehq.org/show_bug.cgi?id=17402
Robert Walker robert_mt_walker@yahoo.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |robert_mt_walker@yahoo.co.u | |k
http://bugs.winehq.org/show_bug.cgi?id=17402
Vitaliy Margolen vitaliy-bugzilla@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |debu66er@gmail.com
--- Comment #10 from Vitaliy Margolen vitaliy-bugzilla@kievinfo.com 2012-01-28 12:33:31 CST --- *** Bug 29729 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=17402
Jarkko K jarkko_korpi@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jarkko_korpi@hotmail.com
--- Comment #11 from Jarkko K jarkko_korpi@hotmail.com --- This bug is so old...
Drivers, kernel and wine has improved since.
COuld you report your status on this now?
http://bugs.winehq.org/show_bug.cgi?id=17402
--- Comment #12 from Robert Walker bob.mt.wya@gmail.com --- (In reply to Jarkko K from comment #11)
This bug is so old...
Drivers, kernel and wine has improved since.
COuld you report your status on this now?
Hi,
I am busy running some tests on BF2 and BF2142 at present. My laptop has an AMD Radeon w/AMD4650. I'm using Arch with the latest kernel (13.x) and Mesa 10.x.
There are various rendering bugs. However these appear to be totally equivalent between AMD (w/Radeon driver) and Nvidia (w/Nvidia driver) GPUs.
Landscape textures have to be set to LOW to avoid seeing flickering hexagonal black polygons on ground surfaces.
Lighting has to be set to LOW. All additional lighting sets have to be toggled OFF. With lighting higher than LOW and/or additional light effects turned ON the game simply hangs at the initial map screen.
I've played the game with other settings at HIGH. Including online play - as Punkbuster now works with a downloadable updater utility. I played on a remote hosted multiplayer map for ~30 minutes. FPS is OK (slow ~20-30 FPS) @1366x768 (native) on my (relatively weak) AMD card.
@Jarkko
I would close this bug - it is no longer valid. I'll refile more specific bugs against the textures issues (which was closed recently I notice). Also the Lighting problem (which affects all GPUs) will need to be opened as a "more specific" bug. The priority of fixing problems, affecting both BF2 & BF2142, IMHO needs to be raised - as extended online play is now working for both games.
Thanks Robert
https://bugs.winehq.org/show_bug.cgi?id=17402
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID
--- Comment #13 from Ken Sharp imwellcushtymelike@gmail.com --- As above. Please remember to link new bugs to the AppDB so that other can find them easily. Thanks.
https://bugs.winehq.org/show_bug.cgi?id=17402
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |FIXED
https://bugs.winehq.org/show_bug.cgi?id=17402
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #14 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.7.47.