Graphics Corruption

When I build to Windows platform I see graphics corruption.

The output log file shows a few warnings that might be related, i.e. "WARNING: Shader Unsupported: 'Standard' - Pass 'META' has no vertex shader". But from past experience I believe the "no vertex shader" warning may be ignored. For example, the standard shader also throws this warning.


Unity 2018.3.12.f:

Player (Standalone PC):


Editor:


Log File:

Code (CSharp):

1. Initialize engine version: 2018.3.12f1 (8afd630d1f5b)
2. GfxDevice: creating device client; threaded=1
3. Direct3D:
4.     Version:  Direct3D 11.0 [level 11.1]
5.     Renderer: NVIDIA GeForce GTX 1060 (ID=0x1c20)
6.     Vendor:  
7.     VRAM:     6054 MB
8.     Driver:   23.21.13.9140
9. Begin MonoManager ReloadAssembly
10. - Completed reload, in  0.113 seconds
11. <RI> Initializing input.
12.  
13. <RI> Input initialized.
14.  
15. <RI> Initialized touch support.
16.  
17. WARNING: Shader Unsupported: 'Standard' - Pass 'META' has no vertex shader
18. WARNING: Shader Unsupported: 'Standard' - Pass 'META' has no vertex shader
19. WARNING: Shader Unsupported: 'Standard (Specular setup)' - Pass 'META' has no vertex shader
20. WARNING: Shader Unsupported: 'Standard (Specular setup)' - Pass 'META' has no vertex shader
21. UnloadTime: 0.566800 ms
22. WARNING: Shader Unsupported: 'Legacy Shaders/Diffuse' - Pass 'Meta' has no vertex shader
23. WARNING: Shader Unsupported: 'Custom/Dissolve' - Pass 'Meta' has no vertex shader
24. WARNING: Shader Unsupported: 'Custom/Respawn' - Pass 'Meta' has no vertex shader
25. Resource Cache Size: 0
26.  
27. Fallback handler could not load library PC-Mono/xxx_Data/Mono/libc
28. Fallback handler could not load library PC-Mono/xxx_Data/Mono/libc.dll
29. Fallback handler could not load library PC-Mono/xxx_Data/Mono/libc

Has anyone seen this before or have any thoughts on where I might look to fix?

 

I'm struggling to understand what could cause this behavior at runtime. In the past, I've had trouble with assets in \resources not being included in the build, such as shaders.

 

Thanks Tautvydas -- this is useful advice. It appears the same with D3D12. I'm just not sure where to tweak to test this better. The ship shown to the right is the standard Unity shader, which I think might help me rule out store assets that somehow have legacy or unsupported shaders. Maybe post-processing V1 is causing this, I don't know. I'll try disabling that next.

D3D12 Log

Code (CSharp):

1. Initialize engine version: 2018.3.12f1 (8afd630d1f5b)
2. GfxDevice: creating device client; threaded=1
3. d3d12: loaded!
4. Direct3D:
5.     Version:         Direct3D 12 [level 12.1]
6.     Renderer:        NVIDIA GeForce GTX 1060 (ID=0x1c20)
7.     Vendor:        
8.     VRAM:            6054 MB
9.     App VRAM Budget: 5145 MB
10.     Driver:          23.21.13.9140
11. Begin MonoManager ReloadAssembly
12. - Completed reload, in  0.179 seconds
13. <RI> Initializing input.
14.  
15. <RI> Input initialized.
16.  
17. <RI> Initialized touch support.
18.  
19. WARNING: Shader Unsupported: 'Standard' - Pass 'META' has no vertex shader
20. WARNING: Shader Unsupported: 'Standard' - Pass 'META' has no vertex shader
21. WARNING: Shader Unsupported: 'Standard (Specular setup)' - Pass 'META' has no vertex shader
22. WARNING: Shader Unsupported: 'Standard (Specular setup)' - Pass 'META' has no vertex shader
23. UnloadTime: 10.177300 ms
24. WARNING: Shader Unsupported: 'Legacy Shaders/Diffuse' - Pass 'Meta' has no vertex shader
25. WARNING: Shader Unsupported: 'Custom/Dissolve' - Pass 'Meta' has no vertex shader
26. WARNING: Shader Unsupported: 'Custom/Respawn' - Pass 'Meta' has no vertex shader
27. Resource Cache Size: 0
28.  
29. (Filename: C:\buildslave\unity\build\Runtime/Export/Debug.bindings.h Line: 45)
30.  
31. Fallback handler could not load library C:/Users/stons/GitHub/-New/Builds/PC-Mono/_Data/Mono/libc
32. Fallback handler could not load library C:/Users/stons/GitHub/-New/Builds/PC-Mono/_Data/Mono/libc.dll
33. Fallback handler could not load library C:/Users/stons/GitHub/-New/Builds/PC-Mono/_Data/Mono/libc
34. WARNING: Shader Unsupported: 'FORGE3D/Planets HD/Sun Corona' - Pass 'Meta' has no vertex shader
35. WARNING: Shader Unsupported: 'FORGE3D/Planets HD/Sun' - Pass 'Meta' has no vertex shader
36. WARNING: Shader Unsupported: 'FORGE3D/Planets HD/Oceanic' - Pass 'Meta' has no vertex shader
37. WARNING: Shader Unsupported: 'FORGE3D/Planets HD/Atmosphere' - Pass 'Meta' has no vertex shader
38. WARNING: Shader Unsupported: 'FORGE3D/Planets HD/Ring Transparent' - Pass 'Meta' has no vertex shader
39. WARNING: Shader Unsupported: 'FORGE3D/Planets HD/Gas' - Pass 'Meta' has no vertex shader
40. Setting up 4 worker threads for Enlighten.
41.   Thread -> id: 4d1c -> priority: 1
42.   Thread -> id: 17e4 -> priority: 1
43.   Thread -> id: d80 -> priority: 1
44.   Thread -> id: 2880 -> priority: 1
45.  

 

Not D3D11 vs D3D12.
Not post-processing.
Not caused by two cameras with different depth layers.
Not IL2CPP vs .NET scripting backend.
Not Static Batching, Dynamic Batching, GPU Skinning, Graphics Jobs.
Not Development vs Release Build

 

Tautvydas -- I believe this is the likely culprit and the graphics corruption looks similar: https://forum.unity.com/threads/bug-4gb-limit-to-textures-in-standalone-build.441116/

I'll update the thread here once I break up my assets into smaller bundles. I'm completely surprised the build process allows a bugged player to be created.