[Bug 59380] New: Nioh: The Complete Edition fails to reach the main menu
http://bugs.winehq.org/show_bug.cgi?id=59380 Bug ID: 59380 Summary: Nioh: The Complete Edition fails to reach the main menu Product: vkd3d Version: 1.18 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: vkd3d-shader Assignee: wine-bugs@list.winehq.org Reporter: andrey.goosev@gmail.com CC: fcasas@codeweavers.com Regression SHA1: 0dabfdee6393eb777dd025ff3d37968fb385f026 Distribution: --- Movie folder should be renamed due to bug 54682. vkd3d:08d4:err:vsir_dst_operand_io_normalise ../vkd3d/libs/vkd3d-shader/ir.c:4693: Unreachable code reached. vkd3d-1.18-295-gc121e9b1 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=59380 --- Comment #1 from Francisco Casas <fcasas@codeweavers.com> --- I ran the Steam version of the game on a Wine prefix. Did this bug appear on the Steam version of the game or another one? After renaming the movie folder, I could start the game properly and menus were working. However, after enabling/maxing all graphic settings and restarting, I couldn't see the menu again. I couldn't retrieve offending shaders though, I set VKD3D_SHADER_DUMP_PATH but I only got cs_5_0 shaders and all of them compile with vkd3d-1.18-295-gc121e9b1. Can you try the same and attach the shaders in a ZIP? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=59380 --- Comment #2 from Andrey Gusev <andrey.goosev@gmail.com> --- Created attachment 80373 --> http://bugs.winehq.org/attachment.cgi?id=80373 shaders -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=59380 --- Comment #4 from Henri Verbeet <hverbeet@gmail.com> --- (In reply to Francisco Casas from comment #3)
I am not sure this counts as a vkd3d-shader regression though since I am seeing the same behavior in several older vkd3d versions I tested.
I can only speak for myself, but personally I'm not keeping score like that. In any case, hitting a vkd3d_unreachable() is a problem by definition, and I think that's the minimum we should address for the 1.19 release. Ideally we'd also get this shader to compile correctly, but perhaps that's too ambitious given how close we are to the release. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=59380 Andrey Gusev <andrey.goosev@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Fixed by SHA1| |4ef2bae8168c5343f7f97446623 | |57ec69d6c18dc --- Comment #5 from Andrey Gusev <andrey.goosev@gmail.com> --- Fixed by 4ef2bae8168c5343f7f9744662357ec69d6c18dc -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla