https://bugs.winehq.org/show_bug.cgi?id=37912
Bug ID: 37912 Summary: Shadowgrounds - rendering issues Product: Wine Version: 1.7.34 Hardware: x86 URL: http://www.gamershell.com/download_12409.shtml OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs@winehq.org Reporter: gyebro69@gmail.com CC: hverbeet@gmail.com Regression SHA1: c6232e1d111ae8929c53c02211cde4a9777311fd Distribution: ---
Created attachment 50495 --> https://bugs.winehq.org/attachment.cgi?id=50495 terminal output
Shadowgrounds and the sequel Shadowgrounds:Survivor have serious rendering issues due to a recent commit:
c6232e1d111ae8929c53c02211cde4a9777311fd is the first bad commit commit c6232e1d111ae8929c53c02211cde4a9777311fd Author: Henri Verbeet hverbeet@codeweavers.com Date: Thu Jan 15 17:19:06 2015 +0100
wined3d: Create GL sampler objects for wined3d sampler objects.
:040000 040000 bc3c73c3d3e26f93417066a5fb249c5c881c6091 0d3e3196edd01a246315bd6d5458217334d044c5 M dlls :040000 040000 cb5a94b6d6d6f6aff0cd35355cb6dd26435ff02e 349d57093d37299200af4e9aa178084ac15bcdaf M include
Reverting the commit fixes the problem.
In the launcher you can set detail level ranging from 'very low' to 'very high': the problem occurs with any settings.
Fedora 21 Nvidia binary drivers 340.65
https://bugs.winehq.org/show_bug.cgi?id=37912
--- Comment #1 from Béla Gyebrószki gyebro69@gmail.com --- Created attachment 50496 --> https://bugs.winehq.org/attachment.cgi?id=50496 screenshot
https://bugs.winehq.org/show_bug.cgi?id=37912
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian@fds-team.de
https://bugs.winehq.org/show_bug.cgi?id=37912
--- Comment #2 from Sebastian Lackner sebastian@fds-team.de --- I also experienced the same rendering issues with FarCry 1 (needs a recent kernel, otherwise it crashes because of a kernel bug). Unfortunately it was not possible to reproduce the issue reliable, it only seems to happen with some specific probability, and after playing a while.
When comparing the terminal output I noticed a huge amount of fixmes like the following one, which were not present before:
fixme:d3d:wined3d_debug_callback 0x788ac90: "Program undefined behavior warning: Sampler object 3 has depth compare enabled. It is being used with non-depth texture 66, by a program that samples it with a regular sampler. This is undefined behavior.".
These tests were done a couple of days ago, so I don't have the full terminal output anymore. I'll try to repeat the tests and attach more logs, probably it helps.
https://bugs.winehq.org/show_bug.cgi?id=37912
--- Comment #3 from Sebastian Lackner sebastian@fds-team.de --- Created attachment 50521 --> https://bugs.winehq.org/attachment.cgi?id=50521 Rendering issues with FarCry 1
It seems like the issue with FarCry 1 happens when the game loads the next level. In the first loaded level everything looks fine, but as soon as you enter the next level the rendering looks terrible (see attached screenshot). Workaround: Restart the game after each level and then load the savegame... ;) After reverting the regression commit on top of current HEAD the issue is gone.
Attaching logs is not possible unfortunately, the game printed several GB of FIXMEs (reverting reduces that to about 1MB). The log contains huge amounts of
fixme:d3d:wined3d_debug_callback 0x181a30: "Program undefined behavior warning: Sampler object 0 does not have depth compare enabled. It is being used with depth texture 451, by a program that samples it with a shadow sampler. This is undefined behavior.".
and
err:d3d:wined3d_debug_callback 0x181a30: "GL_INVALID_OPERATION error generated. Not a valid sampler name.". err:d3d:sampler >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glBindSampler @ state.c / 3745
Tested with wine-1.7.34-74-gcf92569.
https://bugs.winehq.org/show_bug.cgi?id=37912
Johannes Dewender wine@JonnyJD.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wine@JonnyJD.net
--- Comment #4 from Johannes Dewender wine@JonnyJD.net --- I have what looks like the same problem on Diablo III (Reaper of Souls).
git bisect led to the same first bad commit c6232e1d111ae8929c53c02211cde4a9777311fd (wine-1.7.34-58-gc6232e1). Previous commits work fine.
In Diablo I have sometimes red dots and black areas all over the place and always striped ground textures. After ALT+Tabbing I also can't see the health globe: it looks empty, although it is not. Making at least hardcore mode impossible to play.
The message that is in the logs *a lot* is:
err:d3d:wined3d_debug_callback 0x3eecf590: "GL_INVALID_OPERATION error generated. Not a valid sampler name.". err:d3d:sampler >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glBindSampler @ ../../../wine-git/dlls/wined3d/state.c / 3745
At the end I have 3-6 of these: err:d3d:device_leftover_sampler Leftover sampler 0x3ef9d620.
I have a GeForce GTX 750 TI (2048 MB) with the 343.22 nvidia driver. Running in XP-mode, no overrides. I have to screens and I am playing on the second screen. Arch Linux.
https://bugs.winehq.org/show_bug.cgi?id=37912
--- Comment #5 from Johannes Dewender wine@JonnyJD.net --- Created attachment 50522 --> https://bugs.winehq.org/attachment.cgi?id=50522 Diablo III striped ground and red dots (scaled down)
This is a screenshot of Diablo III with the striped ground, which occurs at some, but not all places. Possibly an issue where it works first, but not for subsequent loads after ALT+tabbing.
ALT+tabbing seems to be a trigger for problems starting to happen after the regression commit. Before that ALT-tabbing worked completely fine.
In that screenshot the health globe is still in working condition.
https://bugs.winehq.org/show_bug.cgi?id=37912
--- Comment #6 from Johannes Dewender wine@JonnyJD.net --- Created attachment 50523 --> https://bugs.winehq.org/attachment.cgi?id=50523 Diablo III lots of blackness, empty globes (scaled down)
After more ALT+tabbing it gets worse. In this shot I only see black and the minimap. The helth/ressource globes appear empty.
After running around the blackness sometimes goes away, but the globes still don't show and I do get the stripe problem again.
https://bugs.winehq.org/show_bug.cgi?id=37912
--- Comment #7 from Johannes Dewender wine@JonnyJD.net --- I did more extensive testing and Alt-Tabbing seems to be a requirement for the rendering issues. If I play 10 minutes straight without ever switching to anything else (= always having the game displayed on the screen) I don't see any problems. Only after Alt-tabbing I get the error messages and the rendering problems.
On the other hand: If I do have problems with a black "landscape" and I ALT-tab it does get better sometimes. Better in the sense that I only get the stripes (sometimes cirles centered at the char), empty globes, red dots, but not everything is black anymore.
Playing on my first or second screen doesn't seem to make a difference. I also tried on my first screen now and I do have the same issues when ALT-tabbing.
So my guess would be that some "ressources" are flushed when switching context and not accessible when switching back to the game. This is possibly also what happens when loading a new level in FarCry: some ressources from the previous level are expected to be accessible, but are not.
I am running with WINEDEBUG=fixme-all. I can happily change that to give a better log. With that setting I only get a few usual Diablo errors and the ones I mentioned in comment 4. So I didn't attach a separate log yet.
https://bugs.winehq.org/show_bug.cgi?id=37912
--- Comment #8 from Béla Gyebrószki gyebro69@gmail.com --- Changing screen resolution in a game also results in texture corruption in many games.
https://bugs.winehq.org/show_bug.cgi?id=37912
--- Comment #9 from Henri Verbeet hverbeet@gmail.com --- http://source.winehq.org/patches/data/108696 is supposed to help for this.
https://bugs.winehq.org/show_bug.cgi?id=37912
--- Comment #10 from Johannes Dewender wine@JonnyJD.net --- (In reply to Henri Verbeet from comment #9)
http://source.winehq.org/patches/data/108696 is supposed to help for this.
That patch seems to help. I could not recreate the problem after applying the patch on current git (wine-1.7.34-74-gcf92569).
https://bugs.winehq.org/show_bug.cgi?id=37912
--- Comment #11 from Sebastian Lackner sebastian@fds-team.de --- (In reply to Henri Verbeet from comment #9)
http://source.winehq.org/patches/data/108696 is supposed to help for this.
The patch also helps for FarCry 1. Thanks for your effort :)
https://bugs.winehq.org/show_bug.cgi?id=37912
Béla Gyebrószki gyebro69@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |525696fe6c4c54888255783cd1b | |e4439ae700fc8 Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #12 from Béla Gyebrószki gyebro69@gmail.com --- Fixed by 525696fe6c4c54888255783cd1be4439ae700fc8
https://bugs.winehq.org/show_bug.cgi?id=37912
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #13 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.7.35.
-
wine-bugs＠winehq.org