https://bugs.winehq.org/show_bug.cgi?id=52116
Bug ID: 52116 Summary: World of Warships: garbled textures and GL_INVALID_OPERATION errors due to invalid PBO access Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: janbraun@gmx.net CC: jsikorski@codeweavers.com Regression SHA1: bb285f56f9ca843c58ee37328027c9611f2587d0 Distribution: ---
World of Warships has graphical artifacts: (seemingly random) textures turn into weird colors and stay that way until game restart. This makes for an over time increasingly psychedelic game experience. ;) The console log spits out the following message from time to time (with varying hexvalues): 0430:err:d3d:wined3d_debug_callback 0x245380: "GL_INVALID_OPERATION in glCompressedTexSubImage2D(invalid PBO access)".
Reverting commit bb285f56f9ca843c58ee37328027c9611f2587d0 "wined3d: Avoid stalling the pipeline on 3D blits." fixes both.
re-tested with current git head wine (67d0509f2f5), running Mesa 21.2.5 on amdgpu. Please holler if you need more info.
https://bugs.winehq.org/show_bug.cgi?id=52116
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, regression Component|-unknown |directx-d3d URL| |https://worldofwarships.eu/
https://bugs.winehq.org/show_bug.cgi?id=52116
--- Comment #1 from Jan Sikorski jsikorski@codeweavers.com --- Created attachment 71170 --> https://bugs.winehq.org/attachment.cgi?id=71170 Proposed fix
Looks like we don't always unbind buffers after using them, so we need to make sure nothing is bound to GL_PIXEL_UNPACK_BUFFER before copying data from system memory. Attached patch should fix the issue.
https://bugs.winehq.org/show_bug.cgi?id=52116
aidas957@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |aidas957@gmail.com
--- Comment #2 from aidas957@gmail.com --- I get the same issue in Roblox in Direct3D mode (without DXVK)
Luckily I just saw a patch in the mailing list which should fix this ????
https://bugs.winehq.org/show_bug.cgi?id=52116
--- Comment #3 from Jan Braun janbraun@gmx.net --- That patch fixes it for me. Thanks for the fast turnaround!
https://bugs.winehq.org/show_bug.cgi?id=52116
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Fixed by SHA1| |d2ceed3904b96576ccb370f196b | |f6fe6d77b3537
--- Comment #4 from Matteo Bruni matteo.mystral@gmail.com --- Reported fixed.
https://bugs.winehq.org/show_bug.cgi?id=52116
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #5 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 7.0-rc1.