Its relatively a minor issue, but its annoying. Game runs well, but it can crash occasionally when what you said happens. This has only happened to me with graves from other players, not the default graves built into the game.Ĭan confirm.
When holding B to summon, the game will sometimes crash when the gauge is full. * Summoning from Bloody or Benevolent graves. I've managed to play for up to three hours without a crash a single time, but in most cases the game seems to crash around the one or two hour mark. * Seemingly crashes routinely in intervals of thirty minutes /one hour, but not every time. * When receiving a Steam chat message, the game is minimised immediately to display the chat window and proceeds to crash 100% of the time. As soon as a level load is complete and you hit the button to start the level from the Tips / level information loading screen, the game may crash. As soon as a weapon or armor item is selected and the button is pressed to equip the item, a crash may occur. Otherwise the game may remain running and is detected by Steam as still being played. Other than that, when exiting the game via the in-game quit option, many times the game fails to fully close and must be killed via either Steam's stop button or a process manager / terminal. This has only happened to me with graves from other players, not the default graves built into the game. Summoning from Bloody or Benevolent graves.Seemingly crashes routinely in intervals of thirty minutes /one hour, but not every time.When receiving a Steam chat message, the game is minimised immediately to display the chat window and proceeds to crash 100% of the time.Most frequently I notice crashes happen at the timing of several events: However, at least on my system, the game is highly unstable and just loves to crash at any given opportunity. In reference to GE's comment about just being able to use the conf file with "ferSurfaceCreation = True" set, that definitely does the trick and no other launch options appear to need to be set. The broken videos seem to have been a thing in the original Nioh as well, would be neat if someone maybe has an idea for a fix there. the intro cutscene or videos that showcase skills do not work at all), ingame cutscenes do work fine. Performance seems as expected, I have a crash every 1-2h so far. PROTON_NO_ESYNC=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 DXVK_CONFIG_FILE="/home/username/nf" %command% Add the launch command: DXVK_CONFIG_FILE="/home/username/nf" %command% in your home directory (nf) with the line: ferSurfaceCreation = TrueĤ). Force Large Address Aware in launch options (PROTON_FORCE_LARGE_ADDRESS_AWARE=1)ģ). Disable Esync in launch options (PROTON_NO_ESYNC=1)Ģ). Once at this point I was able to get the game playable with the same fixes that worked for the original Nioh:ġ). ReproductionĪt this point, the mouse cursor changes to the in-game cursor and you can hear menu sounds if clicking, or pressing direction buttons on a game pad. At this point, the mouse cursor changes to the in-game cursor and you can hear menu sounds if clicking, or pressing direction buttons on a game pad. After switching several time back and forth, the window will sometimes maximize and display a completely black screen. Attempting to switch to the minimized game window, the window appears to open, but then immediately minimizes again. If given enough time, there will be some initial menu audio. Under Proton-6.1-GE-1, the same window will appear, and immediately minimize. Under Proton 5.13-5, the game launches a window and then immediate closes / crashes most of the time, but will sometimes launch full screen and just behave as below with Proton GE. that I have checked whether there are updates for my system available.Īttempted to launch with Proton 5.13-5, Proton-6.1-GE-1at first.that I haven't found an existing compatibility report for this game.Link to full system information report as Gist:.Name of the game with compatibility issues: Nioh 2 - The Complete Edition.