https://bugs.winehq.org/show_bug.cgi?id=46118
Bug ID: 46118 Summary: d3d:wined3d_debug_callback 0x1464f0: glBlitFramebuffer and glDrawElementsBaseVertex has generated an error Product: Wine Version: 3.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: version2013@protonmail.com Distribution: ---
Created attachment 62755 --> https://bugs.winehq.org/attachment.cgi?id=62755 log.txt
Game "FlatOut" * has minor graphically glitches since wine-3.9. Car windows and shadows periodically blink, or disappear and reaper rapidly. A minor annoyance.
* FlatOut 1, even though my log.txt says 2.1. That is just the game installer version number from gog.com
Regression test: 0db4d1c251d293333e2721a78d6156008a90ff6f is the first bad commit commit 0db4d1c251d293333e2721a78d6156008a90ff6f Author: Henri Verbeet hverbeet@codeweavers.com Date: Wed May 23 16:14:13 2018 +0430
wined3d: Default to OpenGL 4.4 contexts.
Signed-off-by: Henri Verbeet hverbeet@codeweavers.com Signed-off-by: Alexandre Julliard julliard@winehq.org
:040000 040000 b5834b97e8655f7a879c3ebb830f88c10521dd6a d3cd9af46880f4cffcfe39f89e3f66da119edabd M dlls
https://bugs.winehq.org/show_bug.cgi?id=46118
--- Comment #1 from Nathan version2013@protonmail.com --- This bug report appears to have the same first bad commit: https://bugs.winehq.org/show_bug.cgi?id=45486
https://bugs.winehq.org/show_bug.cgi?id=46118
Nathan version2013@protonmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |0db4d1c251d293333e2721a78d6 | |156008a90ff6f
https://bugs.winehq.org/show_bug.cgi?id=46118
--- Comment #2 from Nathan version2013@protonmail.com --- (In reply to Nathan from comment #0) Typing too fast, instead of 'reaper', I meant 'reappear'.
https://bugs.winehq.org/show_bug.cgi?id=46118
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|d3d:wined3d_debug_callback |FlatOut has graphical |0x1464f0: glBlitFramebuffer |glitches |and | |glDrawElementsBaseVertex | |has generated an error | Component|-unknown |directx-d3d Keywords| |regression
--- Comment #3 from Matteo Bruni matteo.mystral@gmail.com --- I think the glBlitFramebuffer() error is "new", the glDrawElementsBaseVertex() errors are probably the same as bug 45486.
https://bugs.winehq.org/show_bug.cgi?id=46118
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Depends on| |45486
--- Comment #4 from Matteo Bruni matteo.mystral@gmail.com --- FWIW I can't reproduce either of those errors with current Wine (bug 45486 should be fixed since Wine-4.0-rc3).
https://bugs.winehq.org/show_bug.cgi?id=46118
--- Comment #5 from Nathan version2013@protonmail.com --- Wine-4.0-rc4
Testing with a previous FlatOut install. The graphical glitches still appear. Subjectively, they appear less frequent, but they still exist on my system.
After exiting game, among the other terminal messages, the following continuously repeats: 002a:err:d3d:wined3d_debug_callback 0x156280: "glDrawElementsBaseVertex has generated an error (GL_INVALID_OPERATION)".
https://bugs.winehq.org/show_bug.cgi?id=46118 Bug 46118 depends on bug 45486, which changed state.
Bug 45486 Summary: Byond 512.x dreamseeker will crash on loading into a ss13 station that uses shaders if run on wine 3.9 or later, but will run fine if you use 3.8 https://bugs.winehq.org/show_bug.cgi?id=45486
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
https://bugs.winehq.org/show_bug.cgi?id=46118
--- Comment #6 from Henri Verbeet hverbeet@gmail.com --- Can this be reproduced with the demo? I don't seem to be able to reproduce this bug, but that may be because it only happens with specific versions of the game. Which GPU and graphics drivers are you using?
https://bugs.winehq.org/show_bug.cgi?id=46118
Nathan version2013@protonmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |https://archive.org/details | |/FlatOutDemo
https://bugs.winehq.org/show_bug.cgi?id=46118
--- Comment #7 from Nathan version2013@protonmail.com --- The minor graphical glitches can be reproduced with a demo.
command: dmidecode ...snip... Processor Information Version: AMD A10-9600P RADEON R5, 10 COMPUTE CORES 4C+6G
command: fglrxinfo display: :0 screen: 0 OpenGL vendor string: Advanced Micro Devices, Inc. OpenGL renderer string: AMD Radeon R7 Graphics OpenGL version string: 4.5.13399 Compatibility Profile Context 15.201.1151
https://bugs.winehq.org/show_bug.cgi?id=46118
--- Comment #8 from Henri Verbeet hverbeet@gmail.com --- (In reply to Nathan from comment #7)
The minor graphical glitches can be reproduced with a demo.
Ok, so in principle I should be seeing these as well.
command: dmidecode ...snip... Processor Information Version: AMD A10-9600P RADEON R5, 10 COMPUTE CORES 4C+6G
command: fglrxinfo display: :0 screen: 0 OpenGL vendor string: Advanced Micro Devices, Inc. OpenGL renderer string: AMD Radeon R7 Graphics OpenGL version string: 4.5.13399 Compatibility Profile Context 15.201.1151
Hmm, maybe this is specific to fglrx/Catalyst. I think most people are either using something Mesa-based or proprietary NVIDIA. It may be interesting to see whether anyone else can reproduce this, either with or without fglrx. If it's easy for you, it may also be interesting to know whether the issue goes away for you when switching to Mesa/radeonsi.
As for debugging this, in principle what you'd do would be to enable something like WINEDEBUG="+d3d9,+d3d,+tid,+seh", disable csmt if possible, and force a backtrace on GL_DEBUG_TYPE_ERROR_ARB in wined3d_debug_callback(). Chances are that that will either make the issue go away though, or result in a log that's too large to attach here.
https://bugs.winehq.org/show_bug.cgi?id=46118
--- Comment #9 from Nathan version2013@protonmail.com --- (In reply to Henri Verbeet from comment #8) Disabling csmt, via regedit, stopped the graphical glitches. https://wiki.winehq.org/Useful_Registry_Keys
csmt enabled, with wine-3.8 *, fails to display the graphical glitches. csmt enabled, with wine-3.9 and later, displays the graphical glitches.
* - and previous versions all the way back to 3.3, when csmt was enabled by default https://www.winehq.org/news/2018030201
https://bugs.winehq.org/show_bug.cgi?id=46118
Nathan version2013@protonmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|FlatOut has graphical |FlatOut has graphical |glitches |glitches with csmt enabled
https://bugs.winehq.org/show_bug.cgi?id=46118
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #10 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with wine-5.22?
https://bugs.winehq.org/show_bug.cgi?id=46118
--- Comment #11 from Nathan Bennett version2013@protonmail.com --- (In reply to joaopa from comment #10) Yes.
https://bugs.winehq.org/show_bug.cgi?id=46118
--- Comment #12 from Henri Verbeet hverbeet@gmail.com --- (In reply to Nathan Bennett from comment #11)
(In reply to joaopa from comment #10) Yes.
Are the error messages from wined3d_debug_callback() also still present? In case they still are, it looks like I forgot to ask this in reply to comment 9, but does disabling csmt also make the error messages go away, or only the glitches?
https://bugs.winehq.org/show_bug.cgi?id=46118
--- Comment #13 from Nathan Bennett version2013@protonmail.com --- wine-6.0-rc5
csmt enabled (0x1 or 0x3) graphical glitches still present error messages from wined3d_debug_callback() still present
csmt disabled (0x0) both the error messages and graphical glitches go away.
https://bugs.winehq.org/show_bug.cgi?id=46118
--- Comment #14 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with wine-6.23?
https://bugs.winehq.org/show_bug.cgi?id=46118
--- Comment #15 from Nathan Bennett version2013@protonmail.com --- (In reply to joaopa from comment #14) With some quick testing, bug still occurs with wine-6.22 bug seems to be absent with wine-6.23 bug reappears with wine-7.0-rc1 and 7.0-rc2
https://bugs.winehq.org/show_bug.cgi?id=46118
--- Comment #16 from joaopa jeremielapuree@yahoo.fr --- Can you perform a regression test to pinpoint the bad commit between wine-6.23 and wine-7.0-rc1? Thanks in advance
https://bugs.winehq.org/show_bug.cgi?id=46118
--- Comment #17 from Nathan Bennett version2013@protonmail.com --- (In reply to joaopa from comment #16) My attempt at this regression test:
# cd /opt # git clone git://source.winehq.org/git/wine.git wine-git/ # cd wine-git/
# git bisect start # git bisect good wine-6.23 # git bisect bad wine-7.0-rc1
# CC="gcc -m32" ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --libdir=/usr/lib32 CFLAGS="-O2 -march=i686 -mtune=i686" --verbose --disable-tests && make compilation fails with bug https://bugs.winehq.org/show_bug.cgi?id=51862 applied patch https://bugs.winehq.org/show_bug.cgi?id=51862#c7 # patch -p1 < patch.diff patching file dlls/ntdll/unix/system.c Hunk #1 succeeded at 253 (offset 6 lines). # CC="gcc -m32" ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --libdir=/usr/lib32 CFLAGS="-O2 -march=i686 -mtune=i686" --verbose --disable-tests && make # make DESTDIR=/opt/temp/winegit install
boot into main distro for game testing. boot into distro for compiling.
# git bisect good displayed error and aborting. skipping this step on further run-throughs, assuming I will get this same error about the patch. delete winegit directory, and copy fresh winegit directory to /opt.
repeat more run-throughs, with last run-through having all the git commands:
# git bisect start # git bisect good wine-6.23 # git bisect bad wine-7.0-rc1 # git bisect good # git bisect bad # git bisect good # git bisect bad # git bisect good # git bisect good # git bisect good # git bisect bad 194b47b4fd92dda8ebf24e88ca7a14fc926c84ab is the first bad commit commit 194b47b4fd92dda8ebf24e88ca7a14fc926c84ab Author: Henri Verbeet hverbeet@codeweavers.com Date: Thu Dec 9 17:45:15 2021 +0100
wined3d: Use the access flags used to create the bo for persistent maps in wined3d_bo_gl_map().
Signed-off-by: Henri Verbeet hverbeet@codeweavers.com Signed-off-by: Alexandre Julliard julliard@winehq.org
:040000 040000 c9ea4a669cc3935e6bb8fa1daf4dd3b6c7dda3bf 3ada434c4d24aeab5412cfa7cfab95c59911d96c M dlls
https://bugs.winehq.org/show_bug.cgi?id=46118
--- Comment #18 from Henri Verbeet hverbeet@gmail.com --- Created attachment 71507 --> https://bugs.winehq.org/attachment.cgi?id=71507 patch
That's interesting. Does the attached patch make a difference?
https://bugs.winehq.org/show_bug.cgi?id=46118
--- Comment #19 from Nathan Bennett version2013@protonmail.com --- (In reply to Henri Verbeet from comment #18) Used a recent winegit and compiled with patch. A quick test and it appears the issue is resolved. Thank you.
https://bugs.winehq.org/show_bug.cgi?id=46118
--- Comment #20 from Nathan Bennett version2013@protonmail.com --- I thought it would be appropriate to say thanks to all that contributed along the way to the bug being fixed.
Thank you.
https://bugs.winehq.org/show_bug.cgi?id=46118
--- Comment #21 from Henri Verbeet hverbeet@gmail.com --- (In reply to Nathan Bennett from comment #19)
Used a recent winegit and compiled with patch. A quick test and it appears the issue is resolved.
Does that also make the "glDrawElementsBaseVertex" error messages go away?
https://bugs.winehq.org/show_bug.cgi?id=46118
--- Comment #22 from Nathan Bennett version2013@protonmail.com --- (In reply to Henri Verbeet from comment #21) Yes. I fail to see those error messages now.
https://bugs.winehq.org/show_bug.cgi?id=46118
Henri Verbeet hverbeet@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #71507|0 |1 is obsolete| |
--- Comment #23 from Henri Verbeet hverbeet@gmail.com --- Created attachment 71533 --> https://bugs.winehq.org/attachment.cgi?id=71533 patch
Revised version of the previous patch. If this version also works, I'll submit it for upstream inclusion.
https://bugs.winehq.org/show_bug.cgi?id=46118
--- Comment #24 from Nathan Bennett version2013@protonmail.com --- (In reply to Henri Verbeet from comment #23) This patch also works. Thanks.
https://bugs.winehq.org/show_bug.cgi?id=46118
temp82@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |temp82@luukku.com
--- Comment #25 from temp82@luukku.com --- (In reply to Nathan Bennett from comment #24)
(In reply to Henri Verbeet from comment #23) This patch also works. Thanks.
the patch went in wine 7.0rc5.
https://bugs.winehq.org/show_bug.cgi?id=46118
--- Comment #26 from Nathan Bennett version2013@protonmail.com --- (In reply to temp82 from comment #25) wine 7.0-rc5
I fail to see the previously mentioned: - "glDrawElementsBaseVertex" error messages - graphical glitches.
Thank you.
https://bugs.winehq.org/show_bug.cgi?id=46118
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com Resolution|--- |FIXED Status|NEW |RESOLVED Fixed by SHA1| |1908cb9501b3bdd87b211735f58 | |6eedb8b98a01a
--- Comment #27 from Zebediah Figura z.figura12@gmail.com --- Marking fixed by https://source.winehq.org/git/wine.git/commitdiff/1908cb9501b3bdd87b211735f586eedb8b98a01a, thanks for testing!
https://bugs.winehq.org/show_bug.cgi?id=46118
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #28 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 7.0-rc6.