to complete informations :
kernel : 4.15.0-34-generic

and the log :
steam-485510.log

My bad, i did not see that requirement, thanks !
Well now : ulimit -Hn does return me 1048576
But i do still have crash at launch here is my log :

steam-485510.log

@kisak-valve i also had to use that tutorial => https://phpsolved.com/ubuntu-16-increase-maximum-file-open-limit-ulimit-n/ to increase the ulimit, with your link it not was enough to unlock max number of files open.

I just experienced the exact same problem, Ive set my ulimits to the recommended, and I dont see the too many open files error. My system details:

Arch Linux
4.18.9-arch1-1-ARCH
Ryzen 7 2700X
32GB DDR4
Nivida GTX970
Nvidia driver version 396.54`

Here is my log
steamlog-nioh-09222018.log

Nioh needs ID3D11Multithread which might never be implemented. At least it's not in DVXK yet as far as I know and the game won't run without it.

It eventually did get implemented, and it seems like it was pulled in, in 3.16-6 beta. But I get a black screen instead of it crashing on launch
steam-485510.log

Kubuntu 18.04
Intel Core i5-4690K
Radeon RX 580 Series
16Gb DDR3

kernal: 4.15.0-43-generic

Yeah, I would love to see that person's setup, if it really works, there must be something they forgot to tell us.

Crashes for me with Proton and has the black screen issue with plain WINE + DXVK 1.0. Alt tab or not doesn't make a difference. Tested on AMD RX 580.

Do the game works now with 4.2-1? I havent install the game yet yo try

Do the game works now with 4.2-1? I havent install the game yet yo try

I tested it but still getting black screen while music is playing and I can navigate menus with gamepad :(

I just tried and it's the same :(

@vjr2 @ap4y hello! Can you please test this game with config file? Just create config file with this line dxgi.deferSurfaceCreation = True then add this to game launch options:
DXVK_CONFIG_FILE="/path/to/config/file.conf" %command%
Keep in mind that movies doesn't work. Thank you!

Wow it works with dxgi.deferSurfaceCreation = True. Thanks a lot for the tip @arzardk! Cutscenes don't work but this happens with other koei tecmo games, might be related to #1464.

Confirmed it works! However if you activate a red tomb the game will crash. Also after a death, the engine somehow slows down until it can't take it anymore and it crashes. Also death light from enemies who died makes the game crash. PROTON_NO_ESYNC=1 wont fix anything. I tried to upload the log but it's above 10 mb

Well yeah, I know movies can be fixed. But my aware are the crashes. It crashes for me when killing with critical hit, it crashes at activating a blood tomb and once it crashes for me for no reason. When I'm back home I Will try ti upload the log. Can anyone confirm if the game crashes for you at that situations?

@vjr2 can confirm that the game crashes for me after killing enemy.

Yeah. I'm in the university right now, but when I'm back home i can actually make a video of gameplay with the things that crashes the game. For me were

1. Activate Bloody Grave: 100% confirmed crash for me
2. Kill Enemies: Happened just once. I think aftter a critical hit
3. Random = Pretty erratic, but I have a theory

As I said I can't go back home now, but all of those situation was when the game tried to load the "tornado-like" animation that appears when you activate a bloody grave or when the enemy drops legendary items. But that's just a theory. When I'm back I will upload a video and the log.

Also somebody also have this issues?

It does work here too with the "dxgi.deferSurfaceCreation = True" but the game randomly crash.

My log file before crash.
steam-485510.zip

Edit: I don't know if it strange or not, but it seems like the game does not generating DXVK cache but only Nvidia specific cache and "steamapp_pipeline_cache"
Edit 2: i found DXVK cache for Nioh not in /steamapps/shadercache/485510 folder but in /steamapps/shadercache/0. Very strange.

But that means that there has to be a workaround to force or to guide DXVK to generate cache (?). I'm just speculating. I'm going home now, so later I will upload my log

Edit: I've just read a bit of DXVK documentation and it says it's possible to manipulate state cache and it's destination folder. I'm crossing my fingers so that workaround works

But that means that there has to be a workaround to force or to guide DXVK to generate cache (?). I'm just speculating. I'm going home now, so later I will upload my log

Edit: I've just read a bit of DXVK documentation and it says it's possible to manipulate state cache and it's destination folder. I'm crossing my fingers so that workaround works

It seems like i found another solution but i need you to test this. Put this line into DXVK config file and try to kill some enemies, activate bloody graves and other things: d3d11.maxFeatureLevel = 11_1

Edit: this option doesn't help because my game just crashed after i killed enemy, but before that i tried around six times and nothing happened. This game have a very strange behavior.

Interesting. I'm like 300 meters from home. I Will test that ASAP. I'm pretty hopefull about this

@arzardk I just tried your command and nothing, I had a crash but at the 4th enemy killed. Also the performance was so much worse with that command. I will show you the log file
steam-485510.zip

UPDATE: 100% playable when also add: PROTON_FORCE_LARGE_ADDRESS_AWARE=1 to the command line. I've been played for almost half an hour with no issue

Edit: definetly seems to avoid crashes

Ok i can reproduce the crash at 100% during the training using the bow and making a critical damage to an enemy (headshot ).
I added PROTON_FORCE_LARGE_ADDRESS_AWARE=1 but it didn't help in my case.
here is my log :
steam-485510.log

kernel : 4.18.0-17-generic
OS : Ubuntu 18.10
Driver : Nvidia 415.27 ( GTX 1070ti )
Proc : Intel Core i5 2500k@4Ghz
Memory : 12Go
Desktop : Lxqt with openbox as WM

Ok, the game just now crashed for me. As @darkpumpkins said the command didn't help that much. Maybe I was just lucky

steam-485510.zip

What does my log mean? I don't know what it means

What does my log mean? I don't know what it means

Your log file is way much bigger than mine. My log file is 1.6 MB and your is 62.1 MB and it is full of d3dcompiler:skip_dword_unknown 0x00000000 and d3dcompiler:d3dcompiler_shader_reflection_GetDesc iface 0x17544140, desc 0x1650f700 partial stub! messages. I don't know exactly but maybe something wrong with your Proton installation or with your GPU driver because i can't find any of these messages in my log.

Yeah it's weird, i dont't know, I'm using nvidia's property drivers

Can confirm same thing happening on RX 580. PROTON_FORCE_LARGE_ADDRESS_AWARE prevents instant crashing on killing first enemy but game still will crash later. Somehow I only crashed once in tutorial area yesterday.

Wait, is this actually a 32-bit game?

how could we know if it's a x86 or x64 process ?
I don't know if that process capture could help ( cf joined picture ).

If that is gnome-system-monitor, you can right-click -> memory-maps and see if there are 32-bit libraries linked into the process. You can also just run file on the nioh.exe in a terminal. That said, the steam store page says it needs a 64bit OS and I think it is extremly unlikely to be acutally 32bit. That also means that PROTON_FORCE_LARGE_ADDRESS_AWARE won't have any effect.

In that case it seems to be a 64 bits binary for Nioh. I join my memory map capture.

The crash pattern it's pretty errátic. I tried again today and it crashed when activating a bloody grave. This case it's turning weird

Seems like all cutscenes are encoded using wmv3 codec, you can find them in the movies folder. I tried mfplat workaround and wmv9vcm from winetricks but cutscenes still don't work and still getting crashes.

Crash log with mfplat and codecs in the prefix, looks like wine segfaults

steam-485510.tar.gz

Played a bit more with codecs and noticed that after native mfplat installation wine still had errors related to quartz, so I installed native version of it and started getting errors related to DirectShow apis from dx9. I tried to use faked3d and all errors disappeared from the log but movies still don't play. Another thing I noticed is that with faked3d dxgi.deferSurfaceCreation = True is no longer necessary, I forced it to False and game still works, crashes still there though.

I also noticed there is an ini file under steamapps/compatdata/485510/pfx/drive_c/users/steamuser/My\ Documents/KoeiTecmo/NIOH/nioh.ini with:

[MOVIE]
bUseRecommendedCodec=1
nUseDXVA=1

But flipping those flags didn't result in significant changes in log. Nioh also has it's own log file in the same folder but content is not super useful:

Revision : 56546w
CreateSystem : SUCCESS
MemAlloc( MEM 1 ) : SUCCESS
MemAlloc( MEM 2 ) : SUCCESS
AnalysisDeveiceCaps : SUCCESS
Boot Path : Z:\home\ap4y\games\steam\steamapps\common\Nioh
My Document Path : C:\users\steamuser\My Documents
Boot Path : Z:\home\ap4y\games\steam\steamapps\common\Nioh
My Document Path : C:\users\steamuser\My Documents
CreateGraphicsDevice : SUCCESS
ResetGraphicsDevice : SUCCESS
DirectInput8Create : SUCCESS
SoundSystem : SUCCESS

As proton 4.2-3, the game still crashes :(

I re-tried nioh again today and was able to finish first mission (island not the starting jail) without crashes, previously it was constantly crashing upon killing first enemy. I played about 4 hours across 2 sessions and had no crashes. I have a theory that it's somehow related to steam input, I had to force it off today (along with steam controller profiles) because gamepad was having issues and noticed that crashes disappeared, turning playstation controller profile on caused crash to re-appear. I also switched to amd gpu and manjaro recently, that might have affected this crash too.

I re-tried nioh again today and was able to finish first mission (island not the starting jail) without crashes, previously it was constantly crashing upon killing first enemy. I played about 4 hours across 2 sessions and had no crashes. I have a theory that it's somehow related to steam input, I had to force it off today (along with steam controller profiles) because gamepad was having issues and noticed that crashes disappeared, turning playstation controller profile on caused crash to re-appear. I also switched to amd gpu and manjaro recently, that might have affected this crash too.

Just tested three times with forced off Steam Input, and on the third try, game is crashed again. Maybe this is somehow related to Steam Input but I highly doubt it. I think that the root of all problems here is Wine or GPU driver. Also, we need some peoples with AMD GPU to confirm effectiveness of your workaround.

I've played for over an hour on AMD RX 580, amdgpu driver, in a more advanced mission (something around level 82). No crashes, even when doing headshots with the bow or waking up revenants. Used a DS4 controller as input, with "Steam Controller Configuration" disabled.

I will try to finish this and the next mission at some point, that should be ~ 2 hours of testing.

I played 8 hours in total on PC with rx580 with radv driver and had no crashes. I tested on another PC today with vega 56 and it was crashing as always. On top of that radv driver with vega has severe visual glitches for shadows and reflections, it's pretty much unplayable. amdvlk doesn't have visual glitches with vega but still has usual crashes. I wonder why rx580 works so well.

I have very few issues with RX 580 and amdgpu overall, I think maybe the older architecture it uses is better understood and more fully implemented in the amdgpu driver? So that might indicate it's something in the driver that causes the crash. I first thought it's one particular shader that crashes all cards, but that doesn't seem to be the case if RX 580 works.

Please give me a few days to verify stability with Nioh, I will try to produce many critical hits, wake up many revenants and do all sorts of things that seem to provoke the crash on other configurations.

@kisak-valve configs of both PCs are here

Visual glitches on Vega 56 with radv (a bit hard to show with still image, it's actually constantly flickering in the game):

Vega 56 with amdvlk:

Hi folks,

I can reproduce the problem on Vega10 and RADV with mesa-19.0.3/LLVM 8 and mesa-git/LLVM 8.
Note that the problem is NOT present with 19.0.2/LLVM 8, it also works fine with LLVM 9.
It's actually similar to https://bugs.freedesktop.org/show_bug.cgi?id=110573
I'm working on a fix.

Here's the fix https://patchwork.freedesktop.org/series/60252/

Awesome, I'll try to test it this weekend. Thanks @hakzsam !

I pushed the fix, it should be in the 19.0.4 and 19.1 releases.

I was wrong, I get the crash on amdgpu with RX 580 as well now. I switched to a normal sword, one combo in particular triggers the crash a lot (after e.g. 5 minutes).

glxinfo:

Extended renderer info (GLX_MESA_query_renderer):
    Vendor: X.Org (0x1002)
    Device: Radeon RX 580 Series (POLARIS10, DRM 3.26.0, 4.18.0-18-generic, LLVM 9.0.0) (0x67df)
    Version: 19.1.0
    Accelerated: yes
    Video memory: 8192MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.5
    Max compat profile version: 4.5
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2

Padoka version string: 19.1 git190409002900.50f3535 c padoka0

Steam logfile: steam-485510.log

Not sure if this is at all related to Mesa or the fix above. I'll delete this if it's just noise.

@hakzsam can confirm, radv from master fixes visual glitches. thanks!

@psy-q What crash are you talking about?
The fix I pushed last week is only related to GFX9 (ie. Vega).

I believe mine is the same seen in https://github.com/ValveSoftware/Proton/issues/1287#issuecomment-478248432 and https://github.com/ValveSoftware/Proton/issues/1287#issuecomment-478294021, it still seems to be happening for me. I played for over an hour without issues, but another time it can crash after 5 minutes already on killing/fighting an enemy.

What do you mean by crash? GPU hang?

No, an unhandled exception:

Unhandled exception: page fault on read access to 0xffffffff960b0694 in 64-bit code (0x00000001401c6600).

There's a logfile attached to my original comment https://github.com/ValveSoftware/Proton/issues/1287#issuecomment-489190569, I can provoke the crash again and provide more files if it's interesting.

Hmm, I'm really not sure if that's related to RADV.
Can you reproduce the same crash with AMDVLK?

This crash is not driver specific, it happens on both amd drivers on polaris and vega gpus, nvidia gpus are also affected. It could be either wine or dxvk related, though I see nothing dxvk related in the logs. I have opened a ticket for the crash in wine's bugzilla, if someone has additional information please add to that ticket.

Thanks for confirming, that makes sense to me.

Got the same crash on killing enemies in the first mission on island. But it happened not at the beginning of the mission, it happened after I reached the nearest shrine, saved the game on it, leveled up, exit game and after a short break returned to it. And from that point the first killed enemy follows to game crash. Only kills with quick attacks raise exception, not skill attacks, not finishing enemy on the ground - they doesn't crash the game. I also tried to load my old saves - they worked well, but I didn't test them long enough.

UPDATE: Played a bit more. Crashes are absolutely random. Sometimes I can finish all mission without any problem, sometimes game crashing on random enemy without any logic.

steam-485510.log Proton 4.2-9
steam-485510.log Proton 4.11-2

Fedora 30
Gnome 3.32
16Gb RAM
GeForce GTX 960/PCIe/SSE2

I've got interesting bug in the second mission. I can walk on air, but I don't remember this part of the level and I felt and game just didn't resurrect me. Did anyone know how to fix it?

Anyone know if there's been any progress on fixing the game crashing when you kill an enemy?

Does anyone own the censored version of the game from asia? The crash on enemy kill looks fairly common on Windows as well based on Steam forum reports, with no one particular fix for it. I'd noticed are that a lot of the reports were from users on Windows 7 and a few that it crashed specifically on dismemberment or critical hits. I tried changing the version of Windows in winecfg some months back when looking for a workaround with no luck. Apparently the Japanese version of the game doesn't include dismemberment though, so I was curious if anyone was experiencing crashes there as well.

Game still crashes in the tutorial mission when killing an ennemy with a ranged weapon (even without a headshot). Seems consistent, it crashed all 6 times I tried so far.

logfile.txt

This is with PROTON_NO_ESYNC=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 DXVK_CONFIG_FILE="/home/gyscos/nioh.conf" %command%, and dxgi.deferSurfaceCreation = True in the nioh.conf, running Borderless and using proton 4.11-5.

Archlinux
Gnome 3.32
Nvidia GTX-970 (nvidia 435.21)

I discovered that changing the the version from windows 7 to windows 10 in winecfg solved the issue of the game crashing on critical headshots. I tested this a few weeks back so it could be that it started working sometime after @HungOverOnATues tested it.

However the game crashes at random times when clashing steels with some human enemies when I'm using strong attack with tonfas. So that hampered my progression.

Later on I decided to play through the game on windows 10 because I wanted to see the cutscenes, and it turns out the game crashes fairly often there too, especially if there are a lot of yokai enemy effects blasting the screen. Never with lightening effects though, but more so with the dark shadowy effects.

The game also crashes at times when selecting and loading up a stage

So essentially the game is just an extremely broken pc port all around even on windows 10 with maybe 11 crashes in total in my 80 hours windows playthrough.

It seems to me that even if we reach parity with native windows version at some point, we will still end up being stuck with a lot of crashes that are just inherit to the game itself and something one has to put up with if one wants finish the game

How do I change the windows version for nioh?

How do I change the windows version for nioh?

First you need to download protontricks https://github.com/Matoking/protontricks

Then after downloading you need to open winecfg. You can do this by using this command in a terminal
protontricks 485510 winecfg

Then you only need to change the windows version from 7 to 10 and click apply

How do I change the windows version for nioh?

First you need to download protontricks https://github.com/Matoking/protontricks

Then after downloading you need to open winecfg. You can do this by using this command in a terminal
protontricks 485510 winecfg

Then you only need to change the windows version from 7 to 10 and click apply

Thank you!

So essentially the game is just an extremely broken pc port all around even on windows 10 with maybe 11 crashes in total in my 80 hours windows playthrough.

For me this wasn't the case. No crashes on Windows 10, tested with an Nvidia GTX 960 and 1060, AMD RX 580 and Vega 64 on two different PCs, 81 hours playtime.

It's very hard to pin down the exact Windows versions though because that playtime was spread from about October 2018 to July 2019. Could be that something introduced to Windows later brought on the crashes.

I just found out I could also solve the headshot crash in the tutorial by enabling all graphics options (Ambient Occlusion, ...). Haven't bisected yet to know which one solves the problem.
Though now it crashes just a bit later when I need to use the Guardian Spirit skill. :S

I just found out I could also solve the headshot crash in the tutorial by enabling all graphics options (Ambient Occlusion, ...). Haven't bisected yet to know which one solves the problem.
Though now it crashes just a bit later when I need to use the Guardian Spirit skill. :S

what other launch options do you have set? Even with the extra effects on, the game still crashes for me.

For me this wasn't the case. No crashes on Windows 10, tested with an Nvidia GTX 960 and 1060, AMD RX 580 and Vega 64 on two different PCs, 81 hours playtime.

It's very hard to pin down the exact Windows versions though because that playtime was spread from about October 2018 to July 2019. Could be that something introduced to Windows later brought on the crashes.

@psy-q It seems the issues with this game dates back to the release of the game with either amd or nvidia, as seen in this thread on crashes https://steamcommunity.com/app/485510/discussions/0/1482109512305893676/

The game just crashes for a multitude of reasons for different people and setups. Some people however reportedly don't experience any crashes.

Also the game having the very specific issue of stuttering when not having a controller connected further illustrates the fact that the finished binary for this game might just be spaghetti code.

I just found out I could also solve the headshot crash in the tutorial by enabling all graphics options (Ambient Occlusion, ...). Haven't bisected yet to know which one solves the problem.
Though now it crashes just a bit later when I need to use the Guardian Spirit skill. :S

what other launch options do you have set? Even with the extra effects on, the game still crashes for me.

@DigitalDevilSummoner You could actually try to disable dynamic reflections and the other effects and turning everything down to its lowest settings to see if that changes things for you.

Btw would also like to point out again that the "changing windows 7 to windows 10 winecfg fix" only fixed the headshotting enemies crash, for me at least. So I don't know if it fixes other crashes, like for instance random enemy kills

I thought to try D9VK, and it worked ONCE, but I couldn't test the head shot bug because the controls weren't working, specifically square and right trigger. so I exited the game, and loaded back in, and it went back to crashing like usual.

I thought to try D9VK, and it worked ONCE, but I couldn't test the head shot bug because the controls weren't working, specifically square and right trigger. so I exited the game, and loaded back in, and it went back to crashing like usual.

@DigitalDevilSummoner When you get the issue where for instance square/x on a controller doesn't work, you have press the mouse + keyboard equivalent of those inputs to get them working again. In the case of square/x I believe you have to press the right or left mouseclick. That's what worked for me.

Seems like not only does the game crash, but steam as a whole running Nioh with 4.11-6

I discovered that changing the the version from windows 7 to windows 10 in winecfg solved the issue of the game crashing on critical headshots. I tested this a few weeks back so it could be that it started working sometime after @HungOverOnATues tested it.

I gave it another try with proton 4.11-7 and crashing still persists for me. Are you certain that it fixed the issue with headshots? I've found that headshots with the matchlock will crash 4 times out of 5, but I have been able to complete the tutorial, a few times in a row even, by chance. Setting windows version compatibility is a fix that windows players use, but as far as I can tell it doesn't work for everyone there either, so perhaps the same is true in Linux?

As far as stability on Windows 10 goes, for what it's worth I'd only had one or two crashes in almost 200 hours with the game.

Seems like not only does the game crash, but steam as a whole running Nioh with 4.11-6

I've been experiencing the same with 4.11-7.
edit: I played some more on Win 10 recently and Steam would often crash when exiting the game normally. Based on that, I'm guessing that the Linux Steam client crash isn't a proton bug.

I discovered that changing the the version from windows 7 to windows 10 in winecfg solved the issue of the game crashing on critical headshots. I tested this a few weeks back so it could be that it started working sometime after @HungOverOnATues tested it.

I gave it another try with proton 4.11-7 and crashing still persists for me. Are you certain that it fixed the issue with headshots? I've found that headshots with the matchlock will crash 4 times out of 5, but I have been able to complete the tutorial, a few times in a row even, by chance. Setting windows version compatibility is a fix that windows players use, but as far as I can tell it doesn't work for everyone there either, so perhaps the same is true in Linux?

As far as stability on Windows 10 goes, for what it's worth I'd only had one or two crashes in almost 200 hours with the game.

Seems like not only does the game crash, but steam as a whole running Nioh with 4.11-6

I've been experiencing the same with 4.11-7.
edit: I played some more on Win 10 recently and Steam would often crash when exiting the game normally. Based on that, I'm guessing that the Linux Steam client crash isn't a proton bug.

Switched my compatibility to windows 10, seems the crash is back to
being random rather than after shooting an enemy in the head. Been searching through the forums for similar issues and it seems like it might be the same bug. Needless to say, there's no new info sadly, but at least the problem isn't linux specific.

After updating my driver to Nvidia 440.82, I was able to play a good hour without any crash. The next day at the first enemy killed the game crashed again. I tried several time with the same result.
I remembered that cache files were tied to nvidia driver version so I tried to remove cached file into

/steamapps/shadercache/485510/nvidiav1/GLCache/

or

/steamapps/shadercache/485510/DXVK_state_cache

Sometimes I'm able to play the game without any crash ... sometimes it crashed again. It seems something related to shader compilation ...
Are all the cache files related to Nioh are located into : "/steamapps/shadercache/485510/ " ?

I actually can't reproduce at 100% ... sometimes I do remove the "nvidiav1" folder content, sometimes the "fozpipelinesv4" content and sometimes the file "nioh.dxvk-cache".

On my last attempt I was able to play removing the "nioh.dxvk-cache" file. If the first enemy killed with a normal move does not make crash, the game won't crash on the others enemies death. It seems to be a particular effect. If i do execute an enemy with a particular move unlocked with competence ( Y when enemy no longer has stamina ) the crash will never occur.

edit : a Nioh log joined
nioh_60.log

Distribution:Ubuntu 19.10 (64 bits)
Noyau:5.3.0-46-generic
RAM:16 GB
Pilote GPU:NVIDIA 440.82
GPU:NVIDIA GeForce GTX 1070 Ti
CPU:AMD Ryzen 7 3700X 8-Core

Since you mentioned shaders, I thought I would try it on AMD with the ACO shader compiler since that is pretty mature now, just to see. But same result, it crashed on the first enemy I killed (no critical hit).

Okay, I tried several things, delete all shader cache, run the game with the DXVK_STATE_CACHE=0 option, in the end it's a random crash ... at start I thought my actions had a consequence on the game but it has not. Like someone said the game crash 4 / 5. I'm able to play the game but I have to make it crash a couple of time before. If the first enemies are killed without any crash then the game will let me play for hours ...

Since the game was playable just after an update of my Nvidia driver and it was the same for a guy on protonDB ... I thought that things were related to shader cache :/.

So, I've been playing Nioh with almost no crashes for like 100h using Proton-5.9-GE-4-ST and suddenly started crashing 100% on killing yokai with normal attack, headshots and blood grave activation. No idea why, maybe following a Steam update. I thought I fixed it by adding RADV_DEBUG=llmv to the launch arguments to disable the ACO shader compiler, but it worked for one play session, then starting crashing more and more until it again 100% on the actions I mentioned above.

Removed the RADV_DEBUG argument and it worked for a short while again, but now it seems that adding or removing it doesn't change anything. I figured the shader cache was getting corrupted so deleted the folders for Nioh under steamapps/shadercache and in steamapps/compatdata, but it didn't work.
I'm a Linux newbie, so I don't think I can provide a solution, but maybe this can help someone more knowledgeable finding one.

[System]
OS: Pop!_OS 20.04 focal
Arch: x86_64
Kernel: 5.4.0-7642-generic
Desktop: pop:GNOME
Display Server: x11

[CPU]
Vendor: AuthenticAMD
Model: AMD Ryzen 5 3600X 6-Core Processor
Physical cores: 6
Logical cores: 12

[Memory]
RAM: 15.6 GB
Swap: 20.0 GB

[Graphics]
Vendor: X.Org
OpenGL Renderer: AMD Radeon RX 5700 XT (NAVI10, DRM 3.35.0, 5.4.0-7642-generic, LLVM 10.0.1)
OpenGL Version: 4.6 (Compatibility Profile) Mesa 20.3.0-devel (git-9e5e3be 2020-08-22 focal-oibaf-ppa)
OpenGL Core: 4.6 (Core Profile) Mesa 20.3.0-devel (git-9e5e3be 2020-08-22 focal-oibaf-ppa)
OpenGL ES: OpenGL ES 3.2 Mesa 20.3.0-devel (git-9e5e3be 2020-08-22 focal-oibaf-ppa)
Vulkan: Supported

Has anyone gotten this to work recently?
Game still always crashes for me when using the bow/gun in the tutorial, even when using the below and borderless mode. Also tried windowed mode 1080p only and windows 7 setting. (deleted shader cache folder also)

AMD Radeon RX Vega (VEGA10, DRM 3.40.0, 5.11.11-144-tkg-upds, LLVM 11.1.0) Mesa 21.0.0 (git-1896a0674f)

DXVK_STATE_CACHE=0 RADV_DEBUG=llmv PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command%
log from proton 6.3-2:
steam-485510.log.zip

Same of @BillFleming with proton 6.3-2, AMD rx 480, Mesa 21.0.3

please, is there a fix for the game crashing after killing a enemy?

I have possibly a good (or really bad) update on the crashing issue. So the crash may be related to DRM/Steam somehow or achievements.
In addition there is a separate log file created (nioh_2xx.log) for some nvidia crap that fails to run.

2021-06-06T23:15:28.557[I]: Core.cpp:29 	#0 Creating GfeSDK Version 1.0.132.d2f5f552
2021-06-06T23:15:28.566[I]: TaskRunner.cpp:42 	#1 Start TaskRunner thread
2021-06-06T23:15:28.578[I]: FactoryImpl.cpp:17 	#0 Creating default MessageBus wrapper
2021-06-06T23:15:28.580[E]: MessagebusWrapper.cpp:34 	#0 Error creating message bus interface
2021-06-06T23:15:28.581[E]: Core.cpp:122 	#0 Unexpected exception during NVGSDK_Create
2021-06-06T23:15:28.582[E]: CoreCInterface.cpp:90 	#0 Error: failed initializing SDK -1020
2021-06-06T23:18:32.172[E]: HighlightsCInterface.cpp:57 	#0 Invalid Handle!
2021-06-06T23:18:32.180[E]: HighlightsCInterface.cpp:79 	#0 Invalid Handle!
2021-06-06T23:19:45.183[E]: HighlightsCInterface.cpp:90 	#0 Invalid Handle!
2021-06-06T23:19:45.192[E]: CoreCInterface.cpp:109 	#0 INVALID HANDLE

Also note in D3D11 log from DXVK 1.8.1 we also get
err: D3D11: CreateGeometryShaderWithStreamOutput: Rasterized stream not supported

Anyway so if you get stuck in the tutorial you can actually use an item to quit it, then return to the menu where you select your character stuff. From that menu you can then start the game.
You will then appear on a shore and the very first enemy you kill will crash the game no matter the settings. Very reproducible.

I have attached a save right here at the beginning. The sword is already equipped so just wander around the corner towards the shack/fire and press X or Y to nail the first enemy to repro the crash. You may need to rename the sub folder to your steam account number.
485510/pfx/drive_c/users/steamuser/My Documents/KoeiTecmo
KoeiTecmo.zip

Anyway though by applying a crack v1.21.06 and specifying my steam account ID number in the INI file it uses the same normal save folder path and the game no longer crashes when killing that first enemy.
This was on Proton 5.21-GE-1 with the following command line: "PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command%"
However I didn't get a bow yet in the area past the tutorial. Will provide a bow save later.
But the game was able to run even with high graphics settings so it might be playable this way minus the videos.

Any tips specifically on getting proton logs related to Steam API stuff?

Edit: I was able to beat the first level this way and there were no crashes. No crashes using bow, no crashes fighting that first real boss on the ship, no crashes activating the red sword things on the ground.

So I believe I have this figured out now and/or they fixed it in the latest surprise patch.
The key to making it work without using a crack is to disable NVAPI which will disable geforce experience from trying to load.
I just tested successfully using the current proton experimental with the following launch options and the game didn't crash when I killed an enemy and it activated an achievement. I then head-shot another enemy with the bow and it also didn't crash.

WINEDLLOVERRIDES="nvapi,nvapi64=" PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command%

Note that they updated the launcher application so you need a newer proton build since it requires updated VS library or .net to run. So for example the old proton 5.21 GE build no longer works.
Note that e-sync probably does work in this game but you might need to increase the FD limit to a huge amount. (similar to Yakuza and Trails of Cold Steel 3)
So now we are just waiting on proper Quartz video playback to put this game on a whitelist someday. I will test some other levels in the game later this week to confirm it doesn't crash anymore. (in particular the tutorial and the first level)

Now the only problem is I am over level 200 and missing a few dozen achievements, lol.

Edit: I have played more through the game and completed the first level again, the tutorial, and leveled up about 100 times without experiencing any crashes.

I can now play Nioh Coplete Edition without any additional configurations on Proton Experimental.
I defeated the first boss in the prison, watched the cutscene, as well as completed the dojo tutorial, and with no crashes so far!

The only remaining issue is that pre-rendered videos are not playing. Is there really no way to make them play?

My system:
Arch Linux
AMD Ryzen 7 2700X
Radeon RX 580
mesa 21.2.2-1

It seems the dev team has fixed the bug, I can also play without any crash with the last version.

My system:
Ubuntu 21.04
AMD Ryzen 7 3700X
Nvidia GTX 1070ti
Driver version 470.63.01
Proton 6.3-6

Proton 7.0 just released and I tried this game. It still does not play video cutscenes (they're .wmv files).

Another 'pre-rendered videos not playing' reply. I tried to install mf and wmp11 but the game crashed with this error in my terminal:

wine: Call from 000000007B0124BE to unimplemented function mfplat.dll.MFTRegister, aborting
wine: Unimplemented function mfplat.dll.MFTRegister called at address 000000007B0124BE (thread 0168), starting debugger...

[jtfen@jfpc1 movie]$ ffprobe -v error -show_format -show_streams EV0001.wmv
[STREAM]
index=0
codec_name=wmv3
codec_long_name=Windows Media Video 9
profile=Main
codec_type=video
codec_tag_string=WMV3
codec_tag=0x33564d57
width=1920
height=1080
coded_width=1920
coded_height=1080
closed_captions=0
film_grain=0
has_b_frames=0
sample_aspect_ratio=N/A
display_aspect_ratio=N/A
pix_fmt=yuv420p
level=-99
color_range=unknown
color_space=unknown
color_transfer=unknown
color_primaries=unknown
chroma_location=left
field_order=unknown
refs=1
id=N/A
r_frame_rate=30000/1001
avg_frame_rate=30000/1001
time_base=1/1000
start_pts=0
start_time=0.000000
duration_ts=108975
duration=108.975000
bit_rate=10000000
max_bit_rate=N/A
bits_per_raw_sample=N/A
nb_frames=N/A
nb_read_frames=N/A
nb_read_packets=N/A
extradata_size=5
DISPOSITION:default=0
DISPOSITION:dub=0
DISPOSITION:original=0
DISPOSITION:comment=0
DISPOSITION:lyrics=0
DISPOSITION:karaoke=0
DISPOSITION:forced=0
DISPOSITION:hearing_impaired=0
DISPOSITION:visual_impaired=0
DISPOSITION:clean_effects=0
DISPOSITION:attached_pic=0
DISPOSITION:timed_thumbnails=0
DISPOSITION:captions=0
DISPOSITION:descriptions=0
DISPOSITION:metadata=0
DISPOSITION:dependent=0
DISPOSITION:still_image=0
TAG:language=jpn
[/STREAM]
[FORMAT]
filename=EV0001.wmv
nb_streams=1
nb_programs=0
format_name=asf
format_long_name=ASF (Advanced / Active Streaming Format)
start_time=0.000000
duration=108.975000
size=113925831
bit_rate=8363447
probe_score=100
TAG:WM/ToolName=TMPGEnc Video Mastering Works 6 Version. 6.2.2.29
TAG:WMFSDKVersion=12.0.14393.1198
TAG:WMFSDKNeeded=0.0.0.0000
TAG:IsVBR=0
TAG:DeviceConformanceTemplate=MP@HL
[/FORMAT]

Trying to run the game with Proton 7.0-3 gives me the same error described above (Failure to play movie. (RTM_ID_EV0001)). The cutscene is then skipped and I can continue to the main menu. However, on Experimental I get a different issue. After the Koei Tecmo splash screen, a window titled ActiveMovie Window pops up and the game doesn't proceed, even if I close the window. I couldn't find anything of interest in the log file (other than maybe err: D3D11: CreateGeometryShaderWithStreamOutput: Rasterized stream not supported, but that shows up before it tries playing the cutscene and looking it up it doesn't seem like it should prevent you from playing).

• GPU: RX 6600
• Driver/LLVM version: Mesa 22.0.1
• Kernel version: 5.17
• Full system information report: https://gist.github.com/Heliozoa/aab90ac35e7224006e71e1d452161022
• Proton version: Experimental

Log: https://github.com/ValveSoftware/Proton/files/9116500/steam-485510.log

@Heliozoa Could you try this game again and see if you still get the error? I believe this should be fixed now with current experimental. If you still see the error, please try uninstalling/reinstalling the game to trigger the necessary video files to download and see if that fixes the problem :)

@alasky17 After changing the Proton version back to Experimental, I no longer get either error and the pre-rendered cutscenes play as expected. :tada: Thanks!

I can confirm that the game is much more playable now that the pre-rendered videos work.
However, I sometimes still see the placeholder instead of the real video. Can I trigger the download of the correct videos somehow which does not require me to re-download the entire game?

@adoa Proton-GE can use your local gstreamer libraries.

If you're seeing placeholder videos it means you're one of the first people to ever see that cutscene on Proton, and eventually it will get transcoded remotely.

@adoa Proton-GE can use your local gstreamer libraries.

Proton-ge does show the videos indeed, but the embedded tutorial videos in the dojo tutorial are played too fast by proton-ge.
Proton Experimental only shows the placeholder, so I guess I will wait for the transcoding before I start to seriously play this game.

Great work! Anyone know which developer/commit was responsible for the fix so I can buy them a coffee?

Any news, fixes and or workarounds for the videos playing too fast? Its not just the tutorial videos, cutscenes also finish too quickly. Only noticed after playing for 16 hours that its been skipping 90% of every cutscene, I'll look these up on YouTube or something so I can catch up but I don't think I want to continue playing until I can watch the remaining videos in-game.

@subanz Could you give some more info? Which Proton version? Also, which hardware? (Please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.). If you are playing on Proton GE, could you try using Proton Experimental too to confirm it has the same problem?

@alasky17

I've tried both Proton Experimental and GE-Proton7-42, deleted the existing compatdata proton folder each time to start clean.

In both cases the initial cutscene that plays before starting the game plays fine all the way through, starting a new game however the first cutscene ends after about 20 seconds soon after the yellow crystal shows up before the dialogue starts in the full version of the cutscene.

I'm not 100% sure but I think the audio plays at normal speed but eventually gets cut off when the video ends. In some cutscenes later in the game the audio continues to play for a short time after the video ends before the prompt to continue appears.

Also the tutorial videos that can be viewed on the Learn Skills page and also in parts of the tutorial play extremely fast.

https://gist.github.com/subanz/35dbcf436174c53d42c7f2b4ac76b88e

Small edit: Most of the tutorial videos in the Learn Skills page are still placeholders, only a few work. I'm guessing most players don't watch these at all.

@subanz Thank you so much for the details! I can see the same problem that you are seeing with the first cutscene when starting a new game. I went ahead and filed a bug for this. Unfortunately I don't have an estimate on how long it will take to fix - these kinds of video playback issues can be very tricky. I appreciate you bringing this to our attention :)

@alasky17 Thank you, thats understandable. Helps to know that its not just something on my end. Guess I'll have to play something else for a while.