Issue Description:
after hitting play in the launcher and loading the shader cache the loading screen appears then game crashes
Platform:
Steam
[PC] Paste Crash Report, or Upload Console Log & darktide_launcher.log:
darktide_launcher.log (318.6 KB)
Same here. Seems to be around a lot. Fatshark just saying the usual “try wumbo”
Could you also share your console logs, or a crash report with us please?
copy pasting from my own thread where I have this issue
fixed it
open RUN by pressing windows key + R
type in %appdata%
navigate to fatshark and open the folder
delete darktide folder completely
launch game
it should pop up and tell you that you meet minimum requirements (see photo attached)
I expected the same crash as usual but it worked fine
console-2023-10-13-21.53.13-435134c2-3eff-4d14-93ed-363aaada042e.log (6.9 KB)
darktide_launcher.log (390.3 KB)
Since I see it is crashing after printing
21:53:17.147 [d3d12 pipeline state] creating pipeline state for #ID[94b534d7]
I would delete the these files
in %APPDATA%/Fatshark/Darktide
shader_cache.hans
shader_library.pso_lib
state_stream_library.pso_lib
But from the info I can see in our crash is that it could be related to your drivers so my suggestion is to see if a clean re-install of latest driver helps.
You can delete those files again after updating the driver, since updating the driver will make them invalid and we need to re-create the data in there.
Keep us updated if this helps or not.
also Steam Gameoverlay is in the callstack of the crash.
crashes caused by it, are usually fixed by disabling game overlay in steam. We can’t sadly not do anything here if that’s the case.
console-2023-10-29-03.34.35-1ada11ad-420b-4372-902f-6cab82dc0546.log (6.9 KB)
darktide_launcher.log (313.7 KB)
the crash still occurs. here are the logs
you crash inside DiscordHook64.dll
Sadly we can’t investigate it further. So my best tip is to sidable to discord overlay if possible.
let me know if you still have issues with discord overlay disabled.
console-2023-11-04-01.37.07-d6ec51f3-5726-4660-8777-a71263f61e5b.log (12.7 KB)
darktide_launcher.log (646.3 KB)
still happens after turning off the Discord overlay
| |dxilconv.dll!hlsl::DxbcConverter::DxbcConverter(void)|Unknown|Non-user code. Symbols loaded.|
|---|---|---|---|
| |dxilconv.dll!hlsl::DxbcConverter::Alloc<>(struct IMalloc *)|Unknown|Non-user code. Symbols loaded.|
| |dxilconv.dll!CreateDxbcConverter(struct _GUID const &,void * *)|Unknown|Non-user code. Symbols loaded.|
| |dxilconv.dll!DxcCreateInstance(struct _GUID const &,struct _GUID const &,void * *)|Unknown|Non-user code. Symbols loaded.|
| |D3D12Core.dll!CShaderBytecode::FinalConstruct(struct CShaderBytecode::TConstructorArgs const &)|Unknown|Non-user code. Symbols loaded.|
| |D3D12Core.dll!CLayeredObject<class CShaderBytecode>::CreateInstance(struct CShaderBytecode::TConstructorArgs const &,void *,void *,struct _GUID const &,void * *)|Unknown|Non-user code. Symbols loaded.|
| |D3D12Core.dll!CDevice::CreateLayeredChild(unsigned int,void const *,unsigned __int64,struct ID3D12LayeredUseCounted *,struct _GUID const &,void * *)|Unknown|Non-user code. Symbols loaded.|
| |D3D12Core.dll!CBridgeImpl<struct ID3D12LayeredDevice,struct ID3D12LayeredDevice,class CLayeredObject<class NDXGI::CDevice> >::CreateLayeredChild(unsigned int,void const *,unsigned __int64,struct ID3D12LayeredUseCounted *,struct _GUID const &,void * *)|Unknown|Non-user code. Symbols loaded.|
| |D3D12.dll!00007ffaf0275b77()|Unknown|Non-user code. Symbol loading disabled by Include/Exclude setting.|
| |D3D12Core.dll!CDevice::CreateShaderBytecode<4>(struct D3D12_SHADER_BYTECODE const *,void const *,bool)|Unknown|Non-user code. Symbols loaded.|
| |D3D12Core.dll!CDevice::CreatePipelineStateImpl(struct CD3DX12_PIPELINE_STATE_STREAM2 &,struct SPipelineLibraryReference const &,struct _GUID const &,void * *)|Unknown|Non-user code. Symbols loaded.|
| |D3D12Core.dll!CDevice::CreateGraphicsPipelineState(struct D3D12_GRAPHICS_PIPELINE_STATE_DESC const *,struct _GUID const &,void * *)|Unknown|Non-user code. Symbols loaded.|
| |Darktide.exe!Create_Bink_shaders(void * pcreate) Line 1216|C++|Symbols loaded.|
You have a crash now inside bink video player which I assume would crash more often for other players. Not sure how to proceed. But I would on your side do.
Let me know if it still occurs.
console-2023-11-09-22.29.51-458ecec3-f5a0-414a-8e7f-87ffa9e662d0.log (22.3 KB)
darktide_launcher.log (31.6 KB)
it still happens
I’ve forward this issue to Nvidia and see if they have any ideas. Next step would be to check if there is any updates for bink that could fix this.
Would switching to the studio driver preference instead of the game ready driver possibly fix the issue?
@FatsharkJulia I see some similar issues on the troubleshooting forum (not starting / crashing after shader cache ect) I’ve the same / similar problem of no boot / launcher not opening.
Have checked most of these and done all the recommended fixes but had no luck this far, Last ticket said about a Win10 repair but unsure what the users steps where.
Q) is it worth submitting the same with my logs or should I just wait for the master incident to be resolved? dont wanna waste your time with duplicate tickets.
Regards
Sebastian H
@Seb_Cz just because it’s after shader cache doesnt mean it’s the same issue. We always launch the shader cache first so that’s what ppl remember.
In many cases shader cache succeded and we can clearly see in the crash that it’s the game process that failed. They are 2 seperate processes so in theory we should be fine running the game regardless of shader cache status.
Sadly I can’t answer that but it’s worth a try. But in this case I would say that any driver that nvidia experiance gives you should be fine.
What’s happening in your case (what we could see before atleast) was that bink crashed when generating d3d12 shaders, these shaders are inbuilt in the exe and same for all users meaning that I expect same behaviour for all users unless something is wrong on the user side.
Since this code is likely not HW related but perhaps more linked to your OS a driver update might not help here.
Also pretty sure all of the crashes above has all been in d3d12 dlls
| > | dxilconv.dll!00007ff80f9a09c8() | Unknown |
|---|---|---|
| dxilconv.dll!00007ff80f9bb74e() | Unknown | |
| dxilconv.dll!00007ff80f9b80e1() | Unknown | |
| dxilconv.dll!00007ff80f9918db() | Unknown |
meaning my thoughts is something is wrong in there
These are the dlls I would try repair
dxilconv.dll
D3D12Core.dll
D3D12.dll
Too be honest I have no idea how you repair those, I would assume they are part of the windows installation.
Do you play alot of other d3d12 games on this PC? I would expect similar issues with them
I ran a SFC scan and it fixed the issue. thanks for all the help o7
great 