-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
black screen in guild wars 2 #344
Comments
How long have you waited? Does the menu music start after a while? It's possible that the game is just compiling shaders at the start and will work fine after that. It takes two minutes for me but that will vary depending on your CPU. I've already filed a bug about the shader cache apparently not working here: iXit/wine-nine-standalone#19 |
Here is the relevant line from the very end of the log.
That assert doesn't make sense, e.g. Try disabling the check and see if there are some issues - hangs, visual glitches, etc. |
|
Now it seems obvious. @logan001, could you try recording an apitrace that reproduces the issue. |
I can confirm that this also happens on stable Mesa (19.0.2-4), with Rayman Origins (and in fact any game I try). I think it's an issue that appeared somewhere in the Mesa 19 branch, affecting the combination of the direct3d state tracker with the nouveau driver. I can set I would imagine that the population of gamers attempting to use nouveau on the GM107 GPU is vanishingly small, which is why only two people seem to have reported this so far… |
@PluMGMK, two people are plenty. Would you try recording an apitrace (using wined3d or always_software) that can reproduce the problem with Nine. If you think it is regression, then finding the commit that broke it could also turn out useful. |
Okay, I did an apitrace with always_software, and when I play it back on nouveau (using
Followed by a crash, "assertion failed in 32-bit code" (as opposed to a silent hang, which is what I get from the game itself). I don't know about tracking down the commit that caused it. If I get a bit more time, I might try it. |
If it is nouveau issue, it would make sense to open a bug report to the nouveau component of mesa on freedesktop's bugzilla, linking to this bug report. |
Yeah, I might just do that. FWIW, commenting out the offending assert within Mesa fixes the issue and doesn't (seem to) break anything else, if anyone's looking for a quick fix. |
Its first time i've tried this version of wine/nouveau/mesa so i'm not sure if i missed some things.
I'm trying to play/test Guild Wars 2 (x64) on linuxmint 19.1 cinnamon
the launcher starts but when the actuall game is suppose to start i'm getting only a black screen.
i've install wine/mesa with the help of https://wiki.ixit.cz/d3d9_tutorial
i've also try the NINE_DEBUG=all csmt_force=0 method to get a better output from wine which you can find it here
$ glxinfo | grep "OpenGL version"
OpenGL version string: 4.3 (Compatibility Profile) Mesa 19.1.0-devel (git-9bb63e9 2019-03-15 bionic-oibaf-ppa)
The text was updated successfully, but these errors were encountered: