https://bugs.winehq.org/show_bug.cgi?id=46790
Bug ID: 46790 Summary: Witcher 3 hangs shortly after launch; may show 'press space to skip' Product: Wine-staging Version: 4.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: riddervancocagne@hotmail.com CC: leslie_alistair@hotmail.com, z.figura12@gmail.com Distribution: ---
Created attachment 63809 --> https://bugs.winehq.org/attachment.cgi?id=63809 Zip file containing api trace, partial console output and Witcher 3 crash report.
If The Witcher 3 is launched using Wine 4.3 Staging, it will grind to a halt almost immediately.
This is no ordinary black screen, as the game often does display the text 'Press space to skip'. Pressing space has no effect, however.
I have also tried running the game on Wine 3.03 Stable, Wine 4.0 Stable and Wine 4.3 Devel. All three variants launch and run the game.
Attached: partial console output, api trace and Witcher 3 crash report generated by the game itself.
https://bugs.winehq.org/show_bug.cgi?id=46790
Tea_Sencha riddervancocagne@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression Distribution|--- |Ubuntu
https://bugs.winehq.org/show_bug.cgi?id=46790
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be Severity|blocker |normal
--- Comment #1 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Bug triage notification:
Issue with one application is normal, not blocker.
Read the severity definitions here: https://wiki.winehq.org/Bugs#severity
https://bugs.winehq.org/show_bug.cgi?id=46790
--- Comment #2 from Tea_Sencha riddervancocagne@hotmail.com --- (In reply to Olivier F. R. Dierick from comment #1)
Bug triage notification:
Issue with one application is normal, not blocker.
Read the severity definitions here: https://wiki.winehq.org/Bugs#severity
Ah, thanks! I hadn't seen those yet - clicking on 'Importance' leads to the definition 'The importance of a bug is described as the combination of its Priority and Severity'. My assumption then was that 'blocker' referred to the fact that the application could not be used at all.
https://bugs.winehq.org/show_bug.cgi?id=46790
Paul Gofman gofmanp@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gofmanp@gmail.com
--- Comment #3 from Paul Gofman gofmanp@gmail.com --- Could you please attach archived log with WINEDEBUG=+d3d,+d3d_shader from the failing run (not truncated)?
Apart from that, there is usually no point truncating console output, the information from the earlier part of default log could already be interesting.
https://bugs.winehq.org/show_bug.cgi?id=46790
--- Comment #4 from Tea_Sencha riddervancocagne@hotmail.com --- Created attachment 63811 --> https://bugs.winehq.org/attachment.cgi?id=63811 Full console output, generated with command DRI_PRIME=1 WINEDEBUG=+d3d,+d3d_shader wine witcher3.exe
https://bugs.winehq.org/show_bug.cgi?id=46790
--- Comment #5 from Tea_Sencha riddervancocagne@hotmail.com --- (In reply to Paul Gofman from comment #3)
Could you please attach archived log with WINEDEBUG=+d3d,+d3d_shader from the failing run (not truncated)?
Apart from that, there is usually no point truncating console output, the information from the earlier part of default log could already be interesting.
OK, done!
https://bugs.winehq.org/show_bug.cgi?id=46790
--- Comment #6 from Tea_Sencha riddervancocagne@hotmail.com --- The full console output was generated with updated graphics drivers (Padoka versus Ubuntu the 18.10 default drivers).
The symptoms were identical, yet I can downgrade the system if necessary and provide another log.
https://bugs.winehq.org/show_bug.cgi?id=46790
--- Comment #7 from Paul Gofman gofmanp@gmail.com --- Thanks for the logs, I think the issue is clear, I will make a fix.
https://bugs.winehq.org/show_bug.cgi?id=46790
--- Comment #8 from Tea_Sencha riddervancocagne@hotmail.com --- Many thanks!
https://bugs.winehq.org/show_bug.cgi?id=46790
--- Comment #9 from Paul Gofman gofmanp@gmail.com --- Created attachment 63815 --> https://bugs.winehq.org/attachment.cgi?id=63815 Use explicit flag to distinguish between old and d3d10+ constant setting mode
I am attaching the fix (on top of the current Wine-Staging (which has latest own commit 3a1bf0a033f898969f18a31965a865fde43cc15e now) in case anyone wants to test it.
https://bugs.winehq.org/show_bug.cgi?id=46790
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |6260ab9bce5d2152360794b7fc5 | |17813c5150ed2 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #10 from Gijs Vermeulen gijsvrm@gmail.com --- I think it's fair to assume this was fixed by https://github.com/wine-staging/wine-staging/commit/6260ab9bce5d2152360794b7...
If this is not the case, please reopen.
https://bugs.winehq.org/show_bug.cgi?id=46790
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #11 from Zebediah Figura z.figura12@gmail.com --- Closing bugs fixed in wine-staging 4.4.
-
wine-bugs＠winehq.org -
WineHQ Bugzilla