https://bugs.winehq.org/show_bug.cgi?id=57207
Bug ID: 57207 Summary: Fallout 3: Regression spams console with errors Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: opengl Assignee: wine-bugs@winehq.org Reporter: m1m1k4tz@protonmail.com Distribution: ---
Created attachment 77108 --> https://bugs.winehq.org/attachment.cgi?id=77108 OpenGL
It might introduce some more micro stutters from what I can tell. Reverting e64f35368e8ee831a968a1e5999dfeb227e2d3be fixes this
https://bugs.winehq.org/show_bug.cgi?id=57207
m1m1k4tz m1m1k4tz@protonmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |e64f35368e8ee831a968a1e5999 | |dfeb227e2d3be
--- Comment #1 from m1m1k4tz m1m1k4tz@protonmail.com --- Forgot to mention I tested this with the new wow64 mode
https://bugs.winehq.org/show_bug.cgi?id=57207
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression, wow64
https://bugs.winehq.org/show_bug.cgi?id=57207
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #2 from Fabian Maurer dark.shadow4@web.de --- What exactly does it spam?
https://bugs.winehq.org/show_bug.cgi?id=57207
--- Comment #3 from m1m1k4tz m1m1k4tz@protonmail.com --- 0148:err:d3d:state_undefined Undefined state UNKNOWN_STATE(0) (0). I pruned it but it goes on forever in game
https://bugs.winehq.org/show_bug.cgi?id=57207
Rémi Bernon rbernon@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rbernon@codeweavers.com
--- Comment #4 from Rémi Bernon rbernon@codeweavers.com --- Does it help if you run it with WINEDEBUG=err-d3d,fixme-d3d environment variable?
https://bugs.winehq.org/show_bug.cgi?id=57207
--- Comment #5 from Rémi Bernon rbernon@codeweavers.com --- Nvm, it most likely does. I thought that it was the change that enabled WOW64 GL debug callbacks, but it's a later one.
https://bugs.winehq.org/show_bug.cgi?id=57207
Chiitoo chiitoo@gentoo.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |chiitoo@gentoo.org
--- Comment #6 from Chiitoo chiitoo@gentoo.org --- It seems I may have been ever so slightly too much in haste when adding the links to PlayOnline Viewer, and the game it is used to launch, Final Fantasy XI Online.
For these, the flood gates appear to open with commit 9313c14c63a [1].
At worst, the
err:d3d:state_undefined Undefined state UNKNOWN_STATE(0) (0).
is printed about 10,000 lines per second for Final Fantasy XI, and somewhat less for PlayOnline Viewer.
Running with an "old-style wow64" mingw build of Wine here ("new-style wow64" build runs the launcher application at about 0.5 FPS... haven't tried getting to the actual game with it yet).
I'm not sure if I've seen an impact on performance yet, aside from the terminal emulator where the application is printing into using more CPU. :]
Thank you!
1. https://gitlab.winehq.org/wine/wine/-/commit/9313c14c63a9b941b66ea367b72f0f9...
https://bugs.winehq.org/show_bug.cgi?id=57207
--- Comment #7 from Chiitoo chiitoo@gentoo.org --- As a side'ish note, I noticed some interesting effects while using
WINEDEBUG="err-d3d"
which has pretty much the opposite effect from what I had expected: big FPS drops and about 100% more CPU usage (going by default view of 'top').
First noticed my CPU fans being more active than usual... then the FPS drops from 29 (Final Fantasy XI is limited to ~30) to <10-20.
Was chasing kernel and mesa and other changes I had been making until I realised it was the /not/ printing those lines. :]
Not sure if normal...
https://bugs.winehq.org/show_bug.cgi?id=57207
Rémi Bernon rbernon@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1|e64f35368e8ee831a968a1e5999 |fd2fd541be88c8702e61ab5e632 |dfeb227e2d3be |82acdbfd09fa5
--- Comment #8 from Rémi Bernon rbernon@codeweavers.com --- I took a look at that, and the debug callbacks that seem to be pointed out from the bisected commit are simply never called. I then don't see how they can have any impact on performance or console output.
After redoing the bisect with the console output as a symptom, I found that it is coming from fd2fd541be88c8702e61ab5e63282acdbfd09fa5 instead. The output might indicate an issue with that commit but I don't see anything apparently broken, nor any particular performance impact.
-
WineHQ Bugzilla