A very low number of players (3 to date out of thousands) are reporting a crash while loading a specific region of our game, built with Unity 2023.3.30 and latest HDRP. It happens on different machines with different compute shader capable GPUs (two Nvidia, one AMD) with decent amount of vram (>3gb). We ruled out a memory crash as we asked players to try very low memory settings and it is still happening.
The log throws a lot of d3d11 errors such as the ones below, and then crashes:
d3d11: failed to create buffer (target 0x1 mode 0 size 3072) [0x887A0005]
d3d11: failed to create buffer (target 0x21 mode 0 size 6144) [0x887A0005]
d3d11: failed to create buffer (target 0x2 mode 0 size 3960) [0x887A0005]
d3d11: failed to create buffer (target 0x25 mode 0 size 85160) [0x887A0005]
d3d11: failed to create buffer (target 0x1 mode 0 size 17032) [0x887A0005]
d3d11: failed to create buffer (target 0x21 mode 0 size 8516) [0x887A0005]
d3d11: failed to create buffer (target 0x2 mode 0 size 20472) [0x887A0005]
D3D shader create error for vertex shader [0x887a0005]
D3D shader create error for pixel shader [0x887a0005]
d3d11: failed to create staging 2D texture w=128 h=1 d3dfmt=10 [887a0005]
d3d11: failed to create 2D texture id=612 width=128 height=8 mips=1 dxgifmt=10 [D3D error was 887a0005]
d3d11: failed to create 2D texture shader resource view id=612 [D3D error was 80070057]
d3d11: failed to create 3D texture id=5663 s=4x1x1 mips=1 d3dfmt=2 [887a0005]
d3d11: failed to create 3D texture view id=5663 [80070057]
d3d11: failed to create 3D texture id=5665 s=4x1x1 mips=1 d3dfmt=2 [887a0005]
d3d11: failed to create 3D texture view id=5665 [80070057]
d3d11: failed to create 3D texture id=5667 s=4x1x1 mips=1 d3dfmt=2 [887a0005]
d3d11: failed to create 3D texture view id=5667 [80070057]
The dump seems to point to VFXReadbackCountBuffer / AsyncGPUReadbackRequest in the initialize class. But there is not much more helpful info.
Any known issue about this? Idea where this can come from?
Hi!
Could you share some logs and dumps? It would help us with the investigation.
However, without a repro it is very difficult that we can find something.
Thanks!
The loading seems to go infinite, but ends up crashing
The log seems to start bugging when we deactivate an enemy game object after warming it up (that means we activate it so that initialization of everything kicks in, then deactivate it. To avoid some stalls further in the game).
The game object in question has some VFX on it, and some are controlled via OnPlay events
We are still trying to blindly debug this, as we have no computer to reproduce the issue, but so far this happened on:
Hi Alexandre,
I didn’t have time to look at it in detail, it will take some time due to other priorities.
From what you describe, it could be a gpu hang. It then crashes when the graphics device gets disconnected after some time not responding.
You could ask your users to update to latest gpu drivers, to discard any problem on that side.
If the issue persists, it will be easier to track if you report a bug, attaching this data and the VFX that you suspect may be causing this.
In any case, I downloaded the files, and I’ll take a look when I have a chance.
Thanks!
Thanks for responding. We already discarded the graphics drivers. It most likely won’t be possible to send a bug report, knowing how Unity is strict in term of project size (ours is 250gb), and that we cannot ask these players to test builds for us. What we will try to do is deactivate some VFXs in a build and if that solves their issue, see what we can do to not lock the GPU in their initialization, it could be something in the graph that these devices don’t like.
Any word on this issue? I appear to have the same in my project as well, only happens in a release build, never in the editor. Unity 2023.2.15f1, HDRP 16.0.5.
Final player log entries when the entire game just freezes indefinitely and doesn’t actually crash ,which means there’s no .dmp created: