Windows Build crashing silently during scene switching

EDIT: Solution has been found. After much trial and error, the game no longer crashes during our loading screen, even with steam running. The issue with the graphics driver DOES NOT OCCUR if the graphics API being used is OpenGL. Adding that as an graphics API option to the build, and adding this launch parameter:
-force-glcore32
fixed the issue (though for this player's driver, it still didn't like some of the Standard Assets shaders for post-processing).



Hi. I've made a StandaloneWindows64 build of the game. It works completely fine in the editor, and the windows build works with 99% of players, however a few are reporting it crashes when switching scenes.

Attached is the Player.log and a crash dump. Windows 10 Pro 64-bit
The application just silently crashes/quits when going from my Splashscreen scene (which is a loading screen) to my main menu scene. It may happen during of an LoadSceneAsync operation or during an UnloadSceneAsync, but I'm not completely sure. I've added some more Debug statements in a newer build to find out. Scene switching code below:

Code (CSharp):

1.  
2.     IEnumerator Async_Load_Level()
3.     {
4.         UIManager.ui_manager.loading_icon.SetActive(true);
5.         UIManager.ui_manager.loading_text.gameObject.SetActive(true);
6.         string active_scene = UnityEngine.SceneManagement.SceneManager.GetActiveScene().name;
7.         DestroyImmediate(UnityEngine.EventSystems.EventSystem.current.gameObject);
8.  
9.         AsyncOperation AO = UnityEngine.SceneManagement.SceneManager.LoadSceneAsync(level_to_load);
10.         AO.allowSceneActivation = false;
11.         int progress = (int)(AO.progress * 100f);
12.         while (AO.progress < 0.9f)
13.         {
14.             progress = Mathf.Max(progress, (int)(AO.progress * 100f));
15.             UIManager.ui_manager.loading_text.text = progress + "%";
16.             yield return null;
17.         }
18.         AO.allowSceneActivation = true;
19.         while (AO.progress < 1f)
20.         {
21.             progress = Mathf.Max(progress, (int)(AO.progress * 100f));
22.             UIManager.ui_manager.loading_text.text = progress + "%";
23.             yield return null;
24.         }
25.         UIManager.ui_manager.loading_text.text = "100%";
26.         yield return 0;
27.         UIManager.ui_manager.loading_icon.SetActive(false);
28.         UIManager.ui_manager.loading_text.gameObject.SetActive(false);
29.  
30.         UnityEngine.SceneManagement.SceneManager.UnloadSceneAsync(active_scene);
31.     }
32.  

I noticed the VRAM for this player is very low - 480mb. Could it be unable to allocate enough memory? This could explain why for most players it works, but for a few it doesn't.

 

Thanks for the suggestions. For crash dump, do you mean stuff located at: %TMP%\CompanyName\ProductName\Crashes ? I'll try to get that from the player.

I tried adding the "-force-feature-level-10-0" command line argument, and it still worked for me. Player.log file confirming forcing of D3D11 to 10.0 below:

Code (CSharp):

1. Mono path[0] = 'C:/Builds/steamworks_sdk/tools/ContentBuilder/content/KaijuWars_Windows/KaijuWars_Data/Managed'
2. Mono config path = 'C:/Builds/steamworks_sdk/tools/ContentBuilder/content/KaijuWars_Windows/MonoBleedingEdge/etc'
3. Initialize engine version: 2020.1.0b7 (6cfebb967dcd)
4. [Subsystems] Discovering subsystems at path C:/Builds/steamworks_sdk/tools/ContentBuilder/content/KaijuWars_Windows/KaijuWars_Data/UnitySubsystems
5. GfxDevice: creating device client; threaded=1
6. d3d11: QueryInterface(IDXGIFactory5) failed (80004002).
7. Direct3D:
8.     Version:  Direct3D 11.0 [level 10.0]
9.     Renderer: NVIDIA GeForce GTX 1070 (ID=0x1b81)
10.     Vendor:  
11.     VRAM:     8046 MB
12.     Driver:   27.21.14.6109
13. VirtualTexturing requires compute shaders
14. Begin MonoManager ReloadAssembly
15. - Completed reload, in  0.186 seconds
16. D3D11 device created for Microsoft Media Foundation video decoding.

 

Attached is a crash dump.

 

Thanks for the excellent suggestions. We tried having the player run the game without steam running at all (running the .exe. directly). Attached is the crash dump without steam. Strangely, the game gets past the loading screen about HALF the time.

We also tried running it separately with and without the following launch options:
-force-d3d11-bltblt-mode
-force-feature-level-10-0
But the game still crashed.

We agree this seems to have something to do with the graphics driver, but it's strange it only happens SOMETIMES and not EVERY TIME.

 

Thanks for the suggestions - looks like I submitted the wrong crash dump where steam was running.

However after much trial and error, we did find a solution - even WITH steam running. The issue with the graphics driver DOES NOT OCCUR if the graphics API being used is OpenGL. Adding that as an graphics API option to the build, and adding this launch parameter:
-force-glcore32
fixed the issue (though for this player's driver, it still didn't like some of the Standard Assets shaders for post-processing).