Finally! Solved it.
So here are the steps I took.
- Set the gpu crash report to “1” in LocalPrefs file.
GpuCrashReportingMode "1"
-
Watched install dir for a crash report/log of some kind. Noticed it was generating _FenrisDebug-# (0-6) which it kept overwriting. Timestamps didn’t quite line up, but definitely were changing. So opened up the file with the most recent timestamp.
-
Looked through the log and found this:
...
I 2023.10.16 15:22:23.071503 [CTelemetry] Application initialization completed in 4.77s
I 2023.10.16 15:22:23.072678 [Game] Initializing ChromaCorsair
I 2023.10.16 15:22:23.072754 [Game] Initializing ChromaRazer
I 2023.10.16 15:22:23.074352 [Game] ChromaRazer dll found (2.9.0.12|2.10.4.0)
I 2023.10.16 15:22:23.074637 [Game] ChromaRazer Init failed with error 0x426
I 2023.10.16 15:22:23.074910 [Game] ChromaEffects failed to initialize
...
Haven’t had a razer keyboard in over a year, so not sure why this popped up and only staretd failing in the last couple of months, but sure, whatever. Also, this isn’t a gpu crash report so not sure if #1 did anything.
There is also a FenrisDebug file which I found later which may always have “latest” and explain why the suffix files didn’t seem to line up with timestamp (e.g. old files get rolled up and not outright deleted - keeping a 7 file history).
- Went back to the LocalPrefs file and found this:
DisableChromaEffects "1"
I set it from 0 to 1.
Boom game now launches.
No amount of uninstall, reinstall, modify install, low res assests, whatnot had solved it.
So if I had to guess, Blizzard has a bug that causes the game client to crash when it detects chroma software but cannot initialize it. I have razer synapse stuff installed, but configured to not start with windows.
Would have been nice if someone from Blizzard had helped me debug their app or at least pointed me to the debug/error file without having to just “figure it out”.