Updated logs from PROTON_LOG=1%command% and Proton 3.16-1-beta, native library, without gamepad connected: Naruto Shippuden: Ultimate Ninja Storm 2 Naruto Shippuden: Ultimate Ninja Storm Full Burst standard Naruto Shippuden: Ultimate Ninja Storm Full Burst HD Naruto Shippuden: Ultimate Ninja Storm 4 All games here are tested and found to be running near perfectly under Lutris Wine Steam runner with Wine staging-3-17 and esync-staging-pba-3.18 EDIT: Its have a high possibility of upstream bug. I tested Storm 4 using Lutris and wine 3.16 crashes with page fault error, and wine 3.7 crashes with dx11 error. Storm 3 Full Burst is the sole one I own and it still crashes for me. The HD version still manages to go up to the Bandai screen at the start, but crashes.

Indonesia: Cara Mengatasi Naruto Shippuden: Ultimate Ninja Storm 4 Crash. To Boruto DLC) OS. Aug 22, 2018 - Naruto Shippuden: Ultimate Ninja Storm 4 Crash on Startup #1533. I'm a bit confused since this bug is for 4 titles. And it is broken. Turns out wine-staging had a more complete 32bppRGBA patch, let's use that one then.

The default non HD version reports missing mono, but the general solution used of setting OS to Windows XP to cause.NET Framework to install, or even installing it with winetricks, generates other crashing reasons. • GPU: Intel HD Graphics 630 (i7-7700K) • Driver/LLVM version: mesa 18.2.3 • Kernel version: 4.18.16 • Proton version: 3.16-4 • ArchLinux.

Storm 3 Full Burst is the sole one I own and it still crashes for me. The HD version still manages to go up to the Bandai screen at the start, but crashes. The default non HD version reports missing mono, but the general solution used of setting OS to Windows XP to cause.NET Framework to install, or even installing it with winetricks, generates other crashing reasons. * GPU: Intel HD Graphics 630 (i7-7700K) * Driver/LLVM version: mesa 18.2.3 * Kernel version: 4.18.16 * Proton version: 3.16-4 * ArchLinux Any log file for Storm 3 HD crash?

Another page fault at Unhandled exception: page fault on read access to 0x3fe46000 in 64-bit code (0x00007fec17cb8cb3). Some good news! I've have regained control of my controller and Storm 1 input works perfectly without DirectInput prompt screen, without any crashes.

But when I go to battle mode it crashes. 👎 For now I can't verify whether all button input works, but if it doesn't crash, Proton is better than upstream Wine in this case The page fault error still persist though I've noticed that now the page fault error comes from 1 0x00007fec13a51248 MSVCRT_memcpy+0x57() in msvcrt (0x3ee7d0) instead of dxvk. All games in this bug report have the same page fault problem, so if one of the game crashes all of the games crashes. I say that because with me testing multiple Wine versions in Lutris either all of them works or none of them works I also noticed that all of upstream Wine versions that I have compiled by myself also have the same segfault problem, but with wine-staging patch it doesn't, after I've finished compiling wine 3.21-staging I can give you the Lutris versions where the games runs nearly perfectly and where the games crashes EDIT: staging-3.16 from Lutris doesn't crash Storm 4, while vanilla 3.16 crashes Storm 4 with page fault. Current workaround for running all Naruto games: Install Wine 3.21-staging and Windows Steam, and use x360ce to bypass ingame dodgy DirectInput setting screen. The staging is important, as even Wine 3.21 without staging patch doesn't work, it crashes with the same page fault error. I think one of those staging patches fixes it, but I don't know which one, as wine staging changes the makefiles and it makes git bisect doesn't work as it will fail to compile I've tried all Naruto games in this bug report and if the necessary patches are in, I think that these games are whitelist ready.