-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Halo Infinite Insider (1240410) #5032
Comments
Same behaviour on my system, using proton-experimental
Log: |
Reporting the same issue with Proton Experimental |
For this current build of Halo Infinite, there is a known issue on Windows where the first time it loads it will be seemingly stuck on a black screen. Some people have reported having to wait up to 10 minutes for it to load the main menu. My best guess is that it is compiling shader cache during the black screen. |
Just tested in on Windows for an hour. The game takes 10 minutes to load to the main menu on every start for me. AMDGPU (RX6800). |
Was hoping for a miracle since this build just crashes on my desktop in Windows. Got a very similar looking log to d10sfan on Proton Experimental, failing to load Arbiter.dll. CPU: Ryzen 7 2700X |
I tested it on Proton Experimental and also hit a similar issue with Arbiter.dll not loading, but also hit several exceptions beforehand (RTX 2060S): |
Latest Insider for 9/23/2021 beta. Does not boot with Proton Experimental. |
+1, does not boot |
F2P client now up on Steam for everyone to fail their proton packs at. |
Compatibility Report
System Information
5.13.6-zen1-1-zen #1 ZEN SMP PREEMPT Thu, 29 Jul 2021 00:21:08 +0000 x86_64 GNU/Linux
I confirm:
Symptoms
The game fails to launch on all versions of Proton tested, including the GE version. On some versions, it hangs, but on others, it crashes after a short period of time.
Reproduction
Install the game through Proton and try to launch it.
Log Files
Proton 6.13-GE-1 Log
Proton-6-3-5-steam-1240410.log
proton-experimental-steam-1240410.log
The text was updated successfully, but these errors were encountered: