Guild Wars 2 - Crash at startup #82
Comments
|
Indeed the trace is not useful. It would be better to have a trace with gallium nine disabled if replaying the trace with nine does cause the same crash. |
|
Is there a way for me to determine if the mesa build I have installed has it enabled? I'm using mesa-git from lcarlier's arch repo. I've run the trace again with the NINE_DEBUG=all set (with and without gallium nine enabled). In hopes that my mesa version has debug enabled. Both traces should be in here:
|
|
The trace on wined3d replays fine on gallium nine. So there are some difference in the game's behaviour between the two for some reasons. If you set NINE_DEBUG=all the log produced would be useful (in your terminal before the assertion failure you would have infos that could be used to deduce which call failed). |
|
I have generated the log file and placed it in the same share as above. |
|
looks like the game tries to create a D3DFMT_INTZ render target after wrongfully being told it can create such a render target. |
|
I've prepared a small patch that should fix the issue. Would you test it ? Would you rather like a mesa branch to test ? Or would you rather wait it gets into the next mesa release. |
|
I should be able to test it. It will be my first time compiling mesa but I will give it a shot. I think I could apply your patch from this state and then proceed with compiling? |
|
Ok, here it is git am thefile.patch |
|
Ok - I hope I built this right. There is a new log file in the share. (I don't see any reference to D3DFMT_INTZ in this new one) They have released a couple patches since I opened this issue here. I'll re-install the mesa-git from aur and run another log to see if there is any difference between the patched version and the one released to aur. So there is something to compare using the latest release of the game (Unfortunately, I can't stop the game from receiving patches :/) Edit: Both files are uploaded: gallium-errror = patched mesa, gallium-error-aur = mesa-git from lcarlier's arch repo (this is assuming i've successfully installed the patched mesa I compiled manually) Doing a diff on the 2 files shows a lot of differences but that's anecdotal. |
|
Thanks. |
|
Alright, I can roll back to a previous wine version if you would like to see those logs. |
|
@axeldavy the mesa patch looks like a nice little bugfix, merge it? |
|
I have updated mesa to the mesa-9e5e3be4122 commit and have the latest version of wine-nine. It doesn't appear the mesa commit i'm on has the patch @axeldavy created, but it is working correctly now. |
|
I'm still getting a crash as described in the initial bug report with the patch applied to mesa master and 20.3 branch. Here's a trace |
|
Thanks for the the report. |
Without the proposed check, some apps will decide to use depth buffers as render targets. Bug found investigating: iXit/wine-nine-standalone#82 Signed-off-by: Axel Davy <davyaxel0@gmail.com>
|
For what it's worth, the game is still running great for me. I'm currently on the following wine and mesa versions: wine-6.1 (Staging) |
Thanks for the reply, I've not tried the mesa-git yet, but even with a fresh wine prefix I'm getting the same crash. My mesa is standard issue from arch testing repo. I'm also on wine-6.1 staging, but this has been going on for a number of wine versions now. |
Guild Wars 2 just released a new patch and now with Gallium Nine enabled i'm unable to get into the game. There is a d9d12pxy that Windows users use that was affected as well.
Previous to the patch they released yesterday the game was working fine for me with Gallium Nine enabled.
When Gallium Nine is disabled, the game works again.
I launch the game, receive the login screen, once I click Play to load into the character screen it crashes before ever displaying the characters.
I believe the important piece is this line:
Here is a trace file, I don't think it's much help though.
https://drive.google.com/file/d/10ntosQ01HpRr2v7ax2X-XQ6UzM4Jxwyz/view?usp=sharing
The text was updated successfully, but these errors were encountered: