https://bugs.winehq.org/show_bug.cgi?id=43322
Bug ID: 43322 Summary: Regression in Test Drive Unlimited 2, visual artifacts Product: Wine-staging Version: 2.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: qptainnemo@gmail.com CC: erich.e.hoover@wine-staging.com, michael@fds-team.de, sebastian@fds-team.de Distribution: ---
Has been happening for some time now, probably coincidental with when the active work on DirectX 10+ began. The game previously rendered normally, at least without visible artifacts. Now there are visual artifacts in the form of random polygons popping from the horizon to the camera. If you need a visual reference, here's a video. https://youtu.be/75Gd9iHFPWI Here is a single screenshot. https://i.imgur.com/FHPchhb.png
Changing graphics quality settings doesn't affect it. CSMT doesn't affect it either. I'm using Arch Linux, an NVidia GPU with proprietary drivers. The prefix is 32 bit with .NET 2.0, 3.5 and 4.0 installed (3.5 is required to run the game).
https://bugs.winehq.org/show_bug.cgi?id=43322
--- Comment #1 from Sebastian Lackner sebastian@fds-team.de --- Is this bug Wine Staging specific or also present in the development version? And do you know a bit more exactly which Wine or Wine Staging release is the first one affected by this issue?
Please also attach terminal output, it might contain a hint what is going wrong.
https://bugs.winehq.org/show_bug.cgi?id=43322
--- Comment #2 from qptain Nemo qptainnemo@gmail.com --- I only use Wine Staging but okay, I'll try to test it with vanilla Wine and earlier Staging versions and report the earliest version.
I'll also provide complete terminal output but I already noticed the terminal was full of the following message repeated over and over "err:d3d:wined3d_debug_callback 0x44e43c0: "GL_OUT_OF_MEMORY error generated. Failed to allocate CPU address space mapping for texture (consider building 64-bit app).".
https://bugs.winehq.org/show_bug.cgi?id=43322
--- Comment #3 from qptain Nemo qptainnemo@gmail.com --- Created attachment 58666 --> https://bugs.winehq.org/attachment.cgi?id=58666 terminal log
https://bugs.winehq.org/show_bug.cgi?id=43322
--- Comment #4 from qptain Nemo qptainnemo@gmail.com --- Also at some point the game begins to massively leak memory at a rate of about 500 mb per second. Of course if I find that this behavior isn't unique to this game I'll file another bug.
https://bugs.winehq.org/show_bug.cgi?id=43322
--- Comment #5 from qptain Nemo qptainnemo@gmail.com --- It's worth pointing out that the memory leaking behavior is new to this version of Wine as far as I'm aware and it's unlikely to be caused by the game itself since it's 32 bit, while the leaks can easily reach up to 16 gigabytes. Also the leaked memory strangely enough is not traced to any particular process in task managers, only the fact that it is in use is detectable.
https://bugs.winehq.org/show_bug.cgi?id=43322
--- Comment #6 from qptain Nemo qptainnemo@gmail.com --- Okay, it definitely affects vanilla Wine 2.14. and 2.13. Verifying earlier versions is proving to be difficult as I'm having trouble with running steam while going backwards in wine versions in this prefix.
https://bugs.winehq.org/show_bug.cgi?id=43322
qptain Nemo qptainnemo@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |-unknown Version|2.12 |2.14 Product|Wine-staging |Wine
https://bugs.winehq.org/show_bug.cgi?id=43322
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #7 from Fabian Maurer dark.shadow4@web.de --- If you're compiling wine yourself, you can make the changed needed for steam to work yourself, and thus continue regression testing. You'll need a bit knowledge with coding though:
https://github.com/wine-compholio/wine-staging/commit/996d9ab307d102399c0014... Line 20 of that patch is enough to make steam work. Just copy the "total = sizeof(void *);" at the right place in the source file. At least that's how I did it.
https://bugs.winehq.org/show_bug.cgi?id=43322
sebastien lacsebastien@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lacsebastien@gmail.com
--- Comment #8 from sebastien lacsebastien@gmail.com --- wine 3.14 staging, i have the same bug
nvidia 960, driver 396.54
https://bugs.winehq.org/show_bug.cgi?id=43322
--- Comment #9 from qptain Nemo qptainnemo@gmail.com --- I've done some pretty extensive testing and I can add the following things with certainty: This manifests as early as Wine 2.8. I was so far unable to make earlier versions of Wine to function well and run the game on my system even by compiling them manually. They either don't run the game or show a black screen or crash in .net code. It's unlikely to be caused by Nvidia drivers, because I've launched the game using software rendering of mesa (using Xephyr) and it renders with exactly the same issues. I have screenshots of the game running perfectly well dated 28th of October 2016. I was most likely using wine-staging. Which suggests that at least wine staging 1.9.21 is a version of wine staging that is guaranteed to not contain that issue.
I wanted to do regression testing as suggested but it's incredibly hard due to how those earlier versions function on current systems and the game's reliance on .net. As far as I can tell, the game runs just fine using standard mono in recent versions of wine but not in the old ones where you need to install .net 3.5.
https://bugs.winehq.org/show_bug.cgi?id=43322
--- Comment #10 from qptain Nemo qptainnemo@gmail.com --- To be clear I have succeeded at installing .net for older versions of Wine that need it but that even combined with manually compiling wine (without which the old versions can't even open GUI windows properly) didn't let me push past 2.8 and reach the state of the game where the issue doesn't manifest.
https://bugs.winehq.org/show_bug.cgi?id=43322
--- Comment #11 from sebastien lacsebastien@gmail.com --- also, my xbox 360 controller does not work with this game
https://bugs.winehq.org/show_bug.cgi?id=43322
--- Comment #12 from Fabian Maurer dark.shadow4@web.de --- (In reply to sebastien from comment #11)
also, my xbox 360 controller does not work with this game
That's a different issue that doesn't belong into this bugreport.
https://bugs.winehq.org/show_bug.cgi?id=43322
zzzzzyzz@hacari.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zzzzzyzz@hacari.org
https://bugs.winehq.org/show_bug.cgi?id=43322
qptain Nemo qptainnemo@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED
--- Comment #13 from qptain Nemo qptainnemo@gmail.com --- As far as I can tell this is fixed in Wine 4.0. I love you guys.
https://bugs.winehq.org/show_bug.cgi?id=43322
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #14 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 4.1.
-
wine-bugs＠winehq.org