Ok I have access and tried it earlier and It just immediately closes (nothing appears) status on Steam goes back to "Online" please give me information on how I can gather information to help diagnose.

@kisak-valve Please reopen this, as this is now available to users.

@kisak-valve the beta of Halo Infinite has dropped today under AppId 1240440, so can be reopened now yeah? I have also attached a pair of log files, one each for Proton 6.3-7 and Experimental. In both cases, launching the game causes the button to switch from "Play" to "Stop" for a few seconds before the game exits. I was also using the Steam Client Beta for both attempts.

proton-experimental-log-1240440-15Nov2021.log
proton-637-log-1240440-15Nov2021.log

Like @shagia, insta-death. Here's my console log using konsole --hold -e %command%:

https://gist.github.com/cybik/43b99328f170ca60b3a66f0ef536f8f2 (also contains steam-1240440.log)

Note that my log comes from a GE, not mainline. I'm assuming experimental and mainline are not showing much difference.

I should have clarified the Proton branch I'm using: I'm using the latest experimental (bleeding edge) branch myself in response to the post @cybik is referring to. I'll try mainline later today.

Still no boot on Proton Experimental or Proton-6.21-GE-1.

Noticed this in the log (used Proton GE): steam-1240440.log

53880.430:010c:0110:err:module:LdrInitializeThunk "Arbiter.dll" failed to initialize, aborting

53880.430:010c:0110:err:module:LdrInitializeThunk Initializing dlls for L"Z:\\home\\server\\.local\\share\\Steam\\steamapps\\common\\Halo Infinite\\HaloInfinite.exe" failed, status c0000142 pid 59450 != 59449, skipping destruction (fork without exec?)

Is "Arbiter.dll" anti-cheat?

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-969290284

I suppose so. Tried to attach a debugger to it but it just traps it with an INT3 instruction and immediately quits the game afterwards.

Note that my log comes from a GE, not mainline. I'm assuming experimental and mainline are not showing much difference.

I'm actually getting a different output when running with experimental (mainline). With GE it mentions Arbiter.dll but not with experimental. I'm not sure if it gets stuck earlier or farther ahead than GE.

Edit: Here's my log

I've got some slightly different behavior on Proton 5.0-10.
It doesn't open anything, but it doesn't exit either, it just stays running.
The proton log still has errors about Arbiter.dll though, so maybe just different behavior after exceptions.

Has anyone attempted viewing Arbiter.dll through a program such as Ghidra?

I tried loading it. It doesn't export many functions (entry and two others), and analyzing took up all 32GB of ram so I had to stop it.

Tried with Proton Experimental, no dice.

Gist

steam-1240440.log

Switching to 6.3.7 installing Visual C++ x64 and x86 from here produces a different log, in which arbiter.dll seems to be loading. Now what nsiproxy is I have no idea.
steam-1240440.log

Interesting, it looks like I actually have no problem loading Arbiter.dll:

trace:loaddll:build_module Loaded L"Z:\\home\\aldrenean\\.local\\share\\Steam\\steamapps\\common\\Halo Infinite\\Arbiter.dll" at 0000000180000000: native

These are the error/fail messages I got in my proton log:

err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\nsiproxy": c0000003

fixme:service:scmdatabase_autostart_services Auto-start service L"nsiproxy" failed to start: 87

err:steam:initialize_vr_data Could not load libopenvr_api.so.

err:virtual:virtual_setup_exception stack overflow 1872 bytes in thread 0108 addr 0x7fc8e57c0ed4 stack 0x5408b0 (0x540000-0x541000-0x940000)

This is on Proton Experimental.

What version of Wine is Proton Experimental based on, since the changelog of the recent Wine 6.19 seems to have a lot regarding whatever nsiproxy is. https://www.winehq.org/announce/6.19

I got these errors initially, but after launching it a few times I just get this:

gavin@jeff ~/.s/s/s/c/Halo Infinite> WINEARCH=win64 WINEPREFIX=/home/gavin/.steam/steam/steamapps/compatdata/1240440/pfx STEAM_COMPAT_CLIENT_INSTALL_PATH="$HOME/.steam/steam" STEAM_COMPAT_DATA_PATH=~/.proton/ ~/.steam/steam/steamapps/common/Proton\ -\ Experimental/proton run HaloInfinite.exe
esync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
WARNING: radv is not a conformant Vulkan implementation, testing use only.
WARNING: radv is not a conformant Vulkan implementation, testing use only.
gavin@jeff ~/.s/s/s/c/Halo Infinite> 

No errors (i'm pretty sure that second line is just a warning). It just closes.

But what's also interesting is the fact that a similar issue is being reported on Windows 10, on the Steam page:
https://steamcommunity.com/app/1240440/discussions/0/5963323773768307774/

With ProtonGE on Wine 6.21 and x64 Visual C++ installed the only errors I get are those:

5681.383:0110:0114:err:module:LdrInitializeThunk "Arbiter.dll" failed to initialize, aborting
5681.383:0110:0114:err:module:LdrInitializeThunk Initializing dlls for L"Z:\\home\\ich\\.local\\share\\Steam\\steamapps\\common\\Halo Infinite\\HaloInfinite.exe" failed, status c0000142
steam-1240440.log

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-969635514

I get the same error with GE 6.21

I also tried disabling Arbiter and forcing native

Using Proton 6.3-7 I get:
12473.049:010c:0110:err:virtual:virtual_setup_exception stack overflow 1936 bytes in thread 0110 addr 0x7f49928269a9 stack 0x540870 (0x540000-0x541000-0x940000)
steam-1240440.log

With Proton Experimental I'm getting:
pid 110292 != 110289, skipping destruction (fork without exec?)
With PROTON_USE_WINED3D=1.

steam-1240440.log
system_info.txt

Proton Experimental on 5.15.2-arch1-1 Arch Linux logs:
steam-1240440.log
sysinfo.txt

It appears to load Arbiter but later exits:

110769.084:0104:0108:trace:loaddll:build_module Loaded L"Z:\\mnt\\local\\SteamLibrary\\steamapps\\common\\Halo Infinite\\Arbiter.dll" at 0000000180000000: native
...
110771.494:005c:006c:trace:seh:dump_unwind_info **** func 1ac90-1ad76
110771.494:005c:006c:trace:seh:dump_unwind_info unwind info at 00000002279D4A70 flags 0 prolog 0x8 bytes function 00000002279BAC90-00000002279BAD76
110771.494:005c:006c:trace:seh:dump_unwind_info     0x8: subq $0x160,%rsp
110771.494:005c:006c:trace:seh:dump_unwind_info     0x1: pushq %rbx
110771.494:005c:006c:trace:seh:RtlRestoreContext returning to 00000002279C403A stack 000000000162F740
110771.494:005c:0078:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x226fe2c,4,(nil))
110771.494:005c:007c:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x287fe2c,4,(nil))
110771.494:005c:0080:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x2e8fe2c,4,(nil))
110771.495:005c:0074:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x1c3fe2c,4,(nil))
110771.522:00cc:00e0:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x151fe2c,4,(nil))
110771.522:005c:006c:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\drivers\\winebus.sys" : builtin
110771.523:005c:006c:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\drivers\\wineusb.sys" : builtin
110771.524:005c:006c:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\drivers\\winehid.sys" : builtin
110771.524:005c:006c:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\hidclass.sys" : builtin
110771.525:005c:006c:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x162fe2c,4,(nil))
110771.594:0030:008c:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x336fe2c,4,(nil))
110771.594:0030:0064:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x274fe2c,4,(nil))
110771.594:0030:0054:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x213fe2c,4,(nil))
110771.594:0030:0070:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x2d5fe2c,4,(nil))
110771.594:0030:0118:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x3f8fe2c,4,(nil))
110771.594:0030:0044:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x151fe2c,4,(nil))
110771.594:0030:00d4:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x459fe2c,4,(nil))
110771.594:0030:0038:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0xf0fe2c,4,(nil))
pid 70842 != 70841, skipping destruction (fork without exec?)

I could be wrong here, but I found this talking about the arbiter.dll and maybe explaining a bit about it. This was from 2019 tho, either 343 made their own or they use a version of this one. I submit this as a noob that wants to help if he can. I dont see anything useful on this page but maybe someone else can http://windowsbulletin.com/files/dll/windows-software-developer/third-party-application/arbiter-dll

Ill keep testing and mention anything I find

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-969290284
Is "Arbiter.dll" anti-cheat?

It's most likely an anti-cheat measure for Windows. The VFIO community is currently able to bypass this as they do other anti-cheat with hypervisor.

Has anyone attempted viewing Arbiter.dll through a program such as Ghidra?

Took a good half hour but i am able to load Arbiter.dll into Ghidra. Unfortunately i am very weak with analyzing x86 binaries.

Project File Name: 	Arbiter.dll
Last Modified:	Tue Nov 16 11:34:10 PST 2021
Readonly:	false
Program Name:	Arbiter.dll
Language ID:	x86:LE:64:default (2.9)
Compiler ID:	windows
Processor:	x86
Endian:	Little
Address Size:	64
Minimum Address:	180000000
Maximum Address:	18124f7ff
# of Bytes:	19183668
# of Memory Blocks:	9
# of Instructions:	0
# of Defined Data:	1472
# of Functions:	0
# of Symbols:	83
# of Data Types:	326
# of Data Type Categories:	4
CompanyName:	Copyright (c) 2021 Microsoft
Compiler:	visualstudio:unknown
Created With Ghidra Version:	10.0
Date Created:	Tue Nov 16 11:34:09 PST 2021
Executable Format:	Portable Executable (PE)
Executable Location:	/tmp/something/Arbiter.dll
Executable MD5:	77ebc2639607d6b571686d5758c97973
Executable SHA256:	1f90f72aa741194c98a9c1ada8209e3df5ecb454dab036e8b28f91aa59ff400b
FSRL:	file:///tmp/something/Arbiter.dll?MD5=77ebc2639607d6b571686d5758c97973
FileDescription:	Arbiter Runtime Library
FileVersion:	1.5.0.124
LegalCopyright:	Copyright (c) 2021 Microsoft
PDB Age:	1
PDB File:	loader.pdb
PDB GUID:	922362bf-4ea4-46a7-912b-299d588fc74e
PDB Version:	RSDS
ProductName:	Arbiter Runtime Library
ProductVersion:	1.5.0.124
Relocatable:	true
SectionAlignment:	4096
Translation:	4b00409

edit: Now I see what others were refering to with running out of memory. some of the functions do exhaust 32gb of memory trying to disassemble.

Seems like the problem is vkd3d and vulkan https://github.com/HansKristian-Work/vkd3d-proton/issues/910#issue-1056672939

There seem to be a few different issues going on here.

Proton Experimental and Proton 6.3-8 both crash on launch. The game generates its own crash log, referencing Media Foundation.
steam-1240440.log
crashCABN.txt

pReader->SetCurrentMediaType(dwStreamIndex, nullptr, pType.Get()) failed (HR=0xc00d5212):
0xc00d5212 seems to infer a missing codec playing one of the intro videos. There doesn't appear to be anything particularly special about the videos.

Container: MP4
Stream 0 (Video): H264 - MPEG-4 AVC (part 10) (av1)
Stream 1 (Audio): MPEG AAC Audio (mp4a) 48000Hz 3F2R/LFE 32bpp

This can be bypassed by moving the video mp4s into a folder where the game can't find them. This will get the game launching, albeit not looking right and at 1-2fps presumably due to the vkd3d issue above. There is a relevant branch vkd3d execute-indirect-advanced but it appears to be in a draft state, too early for testing. For me a d3d12.dll compiled from this tree causes the game to crash shortly after launching.

Proton-GE (6.21) seems to have an unrelated issue where it can't initialize Arbiter.dll. Not relevant here but I've attached the log anyway
steam-1240440.log

Can confirm that removing the videos allows me to launch the game, but I have to RMA my card (for separate reasons) and my integrated graphics don't meet minimum specs to run the game so it crashes.

I can also confirm that it now launches with the videos moved. The GPU driver crashed and kinda recovered so I couldn't really do anything. I'll try again :)

The game launches and I can get to the menu(s) however the graphics don't update once I hit the menus and I can't do anything other than make sounds clicking on menu links.

I haven't removed the videos and I'm using an AMD 6900XT on Arch Linux.

For what it is worth: The open radeon vulkan driver loads faster however it has graphics artifacts when trying to close the game (had to restart X) the amdvlk driver seems slower but it doesn't get the artifacts when it closes halo and seems to lock harder than the readon vulkan driver.

Has anybody tried again now that the campaign has been released?

Just launched the game. It loads, and you can get past the Microsoft login, but crashes on menu pages. After the first crash, it now crashing passing the loading page

Just launched the game. It loads, and you can get past the Microsoft login, but crashes on menu pages. After the first crash, it now crashing passing the loading page

:( thanks. Hopefully it's resolved eventually. Too big of a release for Proton to not support it down the line, with Steam Deck coming.

I'll have to boot Windows in the meantime I guess.

Just launched the game. It loads, and you can get past the Microsoft login, but crashes on menu pages. After the first crash, it now crashing passing the loading page

So, some further research. Deleting the video folder is what boots up the game. But then once the video is tried to be fetched, the game crashes. Keeping the videos folder crashing the game at loading.

I still haven't been able to start the game, with or without the videos. On proton experimental, it just does nothing and the log is empty except for the standard header. With proton 6.3-8, it runs for a few seconds and crashed again (no window opens at any time), and I get this log.

Just launched the game. It loads, and you can get past the Microsoft login, but crashes on menu pages. After the first crash, it now crashing passing the loading page

I can confirm that I'm experiencing the same behavior also I noticed that in the main menu the performance is horrible it's like ~2fps and just as it tries to show up the menu the game auto closes no errors or anything.

I also get the "game crashes as soon as I launch it" I get a window that flashes and then goes POOF and then game crashes. I have tried Proton Experimental, Proton 6.3.8, and even GloriousEggroll's latest Proton build, but none work.

Just launched the game. It loads, and you can get past the Microsoft login, but crashes on menu pages. After the first crash, it now crashing passing the loading page

So, some further research. Deleting the video folder is what boots up the game. But then once the video is tried to be fetched, the game crashes. Keeping the videos folder crashing the game at loading.

Out of curiosity has anyone tried replacing the videos with dummy files (e.g. an empty MP4) rather than deleting them?

I tried replacing the videos with blank ones from this repo. Specifically I tried blank.mp4 and blank_AVC.mp4 (the encoding of the original videos) renamed to the original video file names. Both of these formats caused to game to crash on launch like the original videos did.

A AAA game like this needs support

For an RX 590 the game takes most of the system with it, it's responsive, but starting a new session via ssh or recovering the xserver seems unreliable, had to REISUB. Relevant dmesg:

[drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
[drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=285544632, emitted seq=285544634
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process HaloInfinite.ex pid 1887837 thread 00 MAIN pid 1887900
amdgpu 0000:09:00.0: amdgpu: GPU reset begin!
amdgpu: cp is busy, skip halt cp
amdgpu: rlc is busy, skip halt rlc
amdgpu 0000:09:00.0: amdgpu: BACO reset
amdgpu 0000:09:00.0: amdgpu: GPU reset succeeded, trying to resume
[drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
[drm] VRAM is lost due to GPU reset!
[drm] UVD and UVD ENC initialized successfully.
[drm] VCE initialized successfully.
amdgpu 0000:09:00.0: amdgpu: recover vram bo from shadow start
amdgpu 0000:09:00.0: amdgpu: recover vram bo from shadow done
[drm] Skip scheduling IBs!
[drm] Skip scheduling IBs!
amdgpu 0000:09:00.0: amdgpu: GPU reset(2) succeeded!
[drm] Skip scheduling IBs!
[...]
[drm] Skip scheduling IBs!
[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
amdgpu 0000:09:00.0: amdgpu: GPU fault detected: 147 0x00c00402 for process steamwebhelper pid 1857306 thread steamwebhe:cs0 pid 1857308
amdgpu 0000:09:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000218
amdgpu 0000:09:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x04004002
amdgpu 0000:09:00.0: amdgpu: VM fault (0x02, vmid 2, pasid 32780) at page 536, read from 'TC1' (0x54433100) (4)
[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=285544636, emitted seq=285544638
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process steamwebhelper pid 1857306 thread steamwebhe:cs0 pid 1857308
amdgpu 0000:09:00.0: amdgpu: GPU reset begin!

After that the system was in a irrecoverable state.

I tried it after the latest update (with renamed intro videos) and was able to load into a training game, but it was 0 fps and nearly crashed my system (Ryzen 5, GTX 1070, Proton Experimental, Solus Mate). Top showed 100% CPU usage while the game was running. Menus were still at 1-2fps. I tried toggling windowed/borderless, HUD effects, Vsync, esync/fsync all with no effect. The proton log is absolutely massive. There was also a message when first starting the game that said: "Unable to connect to Halo Infinite Lobby Service."

I also managed to capture a couple screenshots, and I was able to hear the audio of the training game, including my inputs.

Edit: tried it a couple more times, and it loads into a training game (map: Live Fire) without crashing. I can hear all inputs as if it is running the game in real time, but the screen is black or stuck on the loading screen. I also noticed that the display adapter option (which should show the GPU, is greyed out and "disabled").

This is the tail of the proton log:

14177.609:0128:012c:trace:seh:dump_unwind_info` **** func 2c9e0-2c9f2 14177.609:0128:012c:trace:seh:dump_unwind_info unwind info at 000000007B63D4DC flags 0 prolog 0x4 bytes function 000000007B62C9E0-000000007B62C9F2 14177.609:0128:012c:trace:seh:dump_unwind_info 0x4: subq $0x28,%rsp 14177.609:0128:012c:trace:seh:RtlVirtualUnwind type 1 rip 000000007BC5E603 rsp 000000000063FE70 14177.609:0128:012c:trace:seh:dump_unwind_info **** func 5e580-5e683 14177.609:0128:012c:trace:seh:dump_unwind_info unwind info at 000000007BC83C8C flags 0 prolog 0x7 bytes function 000000007BC5E580-000000007BC5E683 14177.609:0128:012c:trace:seh:dump_unwind_info 0x7: subq $0x168,%rsp 14177.609:0128:012c:trace:seh:call_stack_handlers found wine frame 000000000063FEA0 rsp 000000000063FFE0 handler 000000007BC68370 14177.609:0128:012c:trace:seh:call_teb_handler calling TEB handler 000000007BC68370 (rec=000000000061ABA0, frame=000000000063FEA0 context=000000000061A0F0, dispatch=0000000000619FC0) pid 39804 != 39803, skipping destruction (fork without exec?)

Riding on the previous comment, I managed to get into the campaign after navigating the slow main menu that now doesn't cause a game crash. As mentioned above, none of the graphics seem to improve this.

Surprisingly though, it seems the main menu is the only place these performance issues exist, from the short period I played. However, almost none of the 3D geometry actually renders, leaving you guessing what's actually happening:

Fortunately, no crashes occured, though while in the main menu my system was very slow (5600X, 3080 Ti, 32GB RAM) which makes almost everything hard to navigate.

On Intel Iris Xe the game complains about not having a compatible direcx12 device and refuses to start. On Windows you are able to get into the game, but with graphical glitches until Intel releases a driver fix. I'll make a log only if there is an interest in improving Intel gaming on Proton.

I’m also getting that DirectX 12 message, and I have an AMD RX 5600 XT.

On Dec 19, 2021, at 1:51 AM, ruineka @.***> wrote:

On Intel Iris Xe the game complains about not having a compatible direcx12 device and refuses to start. On Windows you are able to get into the game, but with graphical glitches until Intel releases a driver fix. I'll make a log only if there is an interest in improving Intel gaming on Proton.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.

Does anyone replying here even read what's written before? Its even pinned right on top with a green border!

Does anyone replying here even read what's written before? Its even pinned right on top with a green border!

Are you sure you are on the right issue thread? There's nothing on this issue with a green border, and people looking for solutions would arrive to this issue from a search engine directly, instead of the issue page.

Not sure if anyone's aware, but the game is available via Xbox Game Pass; can use this for now while we wait.

@braiam my bad, the green border thingy was an add-on (Refined GitHub), but the main complain remains if people even read what's written before.

https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-972565583

i am having fun it seems stable with the d3d12 from here disabling the High res textures, steam overly and disabling winedb.exe once you get into the tutorial that is the main menus love crashing I think its to do with the online services as when its trying to go online it dies but once it switches to offline because you are trying to launch the tutorial it seems to be stable

side note this is on a laptop with a ssd with the game installed on it proton experimental linux tkg and mesa-git with a ryzen 5 2500u and a rx 560x and 16 gb of ram

i am having fun it seems stable with the d3d12 from here disabling the High res textures...

Are you able to provide step by step instructions?

i am having fun it seems stable with the d3d12 from here disabling the High res textures...

Are you able to provide step by step instructions?

Build it using the command provided, which will setup a directory containing a script you can use to install it. Direct it at the wine prefix relevant for your app (so steamapps/compatdata/id/pfx) and use the installer script.

In my experience though, that branch does not seem to make the game any more or less stable - it still kills framerate on the main menu, or when rendering actual level geometry. I'm not sure the indirect rendering fix patch actually improves anything just yet.

i am having fun it seems stable with the d3d12 from here disabling the High res textures...

Are you able to provide step by step instructions?

yes you can use githubs automated checks at the bottom of that PR to download a build here under artifacts. Because I am lazy I just set the prefix to use d3d12 native and shoved the 64 bit d3d12.dll into the games folder. disabling of winedbg will result in no debugging options if it dose crash but in general make games that like to crash less unstable and more performant its a environment variable WINEDLLOVRRIDES=winedbg.exe=d

AMDGPU-pro is less speedy and more unstable then radv in my testing (mesa-git)
the game has issues picking which gpu to use in some laptops and was trying to run with my vega apu
the menus run at 30fps for my system with my settings (all low and 71% res scale)

Any news/movement on this now that upstream VKD3D12 seems to have more of the missing calls that were previously missing? beyond that do we have a working list of what calls were missing previously?

The feature that is supposed to fix most of this(indirect rendering) is still being worked on here and does not appear to have made it to a release yet. The following is on current Proton Expiremental with an i7-12700kf, kernel 5.16.14(zen, arch btw), and a gtx 1070(driver 510.54). After compiling it from the execute-indirect-advanced branch, as @money123451 did, it loads in normally (still with no trees on menu) and after loading into a game, the only thing visible were palm trees (map bazaar, unplayable). On the latest commit on the execute-indirect-advanced-breadcrumbs branch the loading screen stays visible during gameplay, though you can walk around and shoot just like execute-indirect-advanced. I tried a few other commits but was unable to get one that just works. My guess is funny issues with latest proton and earlier vkd3d-proton, but I could've missed something from money123451. Will try playing around with versions.

Is there any news on if they are implementing a DirectX 12 Indirect Rendering equivalent to Vulkan?

and is there any progress being made on Halo Infinite?

It seems to have come a very long way, I just retried on my RTX 3070(as I heard AMD still lack their indirect rendering extensions)
The performance seems perfect, however everything is rendered awfully weird(and it still requires you to rename the videos folder)

EDIT: remembering when it was like 2fps...

That's really great progress actually! nice to see!

as I heard AMD still lack their indirect rendering extensions)

I believe they're WIP. I'm currently caught on some other projects, but if others in this issue with the requisite hardware are ok with building from source, you can enable experimental extensions in AMDVLK (the vulkan driver) manually!

Repo is here:https://github.com/GPUOpen-Drivers/AMDVLK

(Open source 🙏 )

Edit: Reminder that AMD has the older radv driver for Vulkan, as well as the modern, FOSS AMDVLK driver

I believe they're WIP. I'm currently caught on some other projects, but if others in this issue with the requisite hardware are ok with building from source, you can enable experimental extensions in AMDVLK (the vulkan driver) manually!

AMDVLK doesn't seem to want to launch the game at all while RADV launches and hangs my 6800XT. I successfully built AMDVLK with AMDVLK_ENABLE_DEVELOPING_EXT="all" which I hope is what you were referring to

I believe they're WIP. I'm currently caught on some other projects, but if others in this issue with the requisite hardware are ok with building from source, you can enable experimental extensions in AMDVLK (the vulkan driver) manually!

AMDVLK doesn't seem to want to launch the game at all while RADV launches and hangs my 6800XT. I successfully built AMDVLK with AMDVLK_ENABLE_DEVELOPING_EXT="all" which I hope is what you were referring to

From the docs, I believe you need to provide it as a series of CSV's explicitly selecting each extension

From the docs, I believe you need to provide it as a series of CSV's explicitly selecting each extension

The docs states that "all" should work though. I'm not sure if this needs to be exported before building or if it needs to be exported while playing the game... The game doesn't start either way...

What extensions were you thinking about enabling? :)

So the Dev branch seems to get the game running farther than their Master branch but it still hangs my GPU after the initial loading screen just like RADV :/

Did you do the remove video files trick like others in the thread above? (amongst other suggestions to get farther in)

Did you do the remove video files trick like others in the thread above?

Yeah. When I tried with the videos, the game wouldn't even show the loading indicator.

I noticed that I could see some of the menu background with the RADV drivers while the background remained totally black on amdvlk

Edit: Reminder that AMD has the older radv driver for Vulkan, as well as the modern, FOSS AMDVLK driver

Apologies for the off-topic comment, but this is very wrong. Both are FOSS. RADV is slightly older but that doesn't make it any less modern. Both are actively developed.

When I try launch, it just says "Failed to create a DirectX 12 Device for the following adapter:" on Proton Experimental and an RX 6600 XT.

Apologies for the off-topic comment, but this is very wrong. Both are FOSS. RADV is slightly older but that doesn't make it any less modern. Both are actively developed.

Apologies for the mistake, was under the impression that RADV was like the old closed source drivers.

https://gist.github.com/nater1983/da5694196059d6a9d332cd91c0817131

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1163557630

There are 46 subscribers on this issue and none of them want to hear about your takes on AMDVLK, please keep them for Reddit or Youtube comments. Thanks.

Replying to [#5030 (comment)](https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1163557630)

There are 46 subscribers on this issue and none of them want to hear about your takes on AMDVLK, please keep them for Reddit or Youtube comments. Thanks.

sorry about that, I hid it for you
on the topic of radv, does anybody have the issue of a hard gpu reset after reaching the title screen?

So the big one you've all been waiting for.


Single player is NOT yet working due to missing some stuff in VKD3D, but Multiplayer is playable, sometimes the game may hang, but you can easily shut it down and restart it again.
This is played on Arch Linux and NVIDIA gpu, not sure how things are on AMD so if someone can test with PROTON GE - 7.22 as it uses the latest VKD3D from git, don't use any other proton as it may hard freeze your entire system.

Halo Infinite is working over here on Fedora, I just had to enable Glorious Eggroll's Mesa-git COPR repo and switch to GE-Proton7-21.
MP crashes, but SP works just fine.
Will try GE-Proton7-22 shortly.

Same results for me with GE-Proton7-21, SP hangs the game on black screen, MP is working

GE-Proton7-22 doesn't work for me, I am currently compiling proton-ge-custom from source to see if using newer versions of packages will work.

not sure how things are on AMD so if someone can test with PROTON GE - 7.22

Doesn't seem to run on the Steam Deck, it shows the loading icon on the lower left but then returns to Steam.

not sure how things are on AMD so if someone can test with PROTON GE - 7.22

Doesn't seem to run on the Steam Deck, it shows the loading icon on the lower left but then returns to Steam.

you need vulkan-radeon-git to run it probably (which you can't install on a steam deck ... probably)

don't think this looks right but its progress I guess (on AMD with ryzen 4000 series integrated graphics, hopefully its a better story for rdna2 gpus)
specs:
5.18.7 kernel and proton-ge 7-21 with vulkran-radeon-git freshly compiled today on arch linux
multiplayer not working with proton-ge 7-22
https://gist.github.com/Etaash-mathamsetty/cf021d6fa13cc6ab5262a95accbab058

don't think this looks right but its progress I guess

Please share your complete config, including kernel, mesa, vulkan backend, version of wine/Proton etc.

When possible, best to edit a previous post rather than create a new post to help minimize the amount of emails sent to others following this topic.

proton-ge 7-22
yeah so multiplayer only works on proton-ge 7-21
strangely vulkan-radeon-git causes the same bugs to happen as the stable vulkan on the arch repos
mesa 21.1.2: (I'll post the images on the same comment, seems like you guys didn't like me posting two images in two different comments)

(still on amd ofc)

For Halo Infinite to render properly, you need a patched mesa library, Glorious Eggroll maintains one for Nobara that contains the patch:
https://copr-dist-git.fedorainfracloud.org/cgit/gloriouseggroll/mesa-aco/mesa.git/tree/dgc_testing.patch?h=f36&id=f51580996713f185ea8edfba9a294ce643fce5c2

To get into the game, you need to either rename or delete the videos folder inside the game directory.

To get into the game, you need to either rename or delete the videos folder inside the game directory.

Can confirm I can now get into the game with the Deck after doing this, but I'm having the same issue as @Etaash-mathamsetty. Guess I will need to figure out how to use that patched Mesa library...

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1167895886

You can put Fedora onto an SD card (at least 64GB in size), install Halo Infinite to that SD card, and then tweak Fedora so that it includes everything needed, like the COPR repo and whatnot.
You can also dual boot, but I wouldn't recommend doing this just yet until dual boot gets supported on the Deck officially.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1167904617

I have a second fedora parition in case my arch linux install dies for no reason, and I have a 128gb sd card, so let me try this
I will edit this comment if I succeed, so that I don't bother the other 46 people on this thread lol
EDIT:
MARK YOUR CALENDARS, TODAY WAS A BIG DAY !
here is a screenshot of victory from AMD gang

where do we get the COPR repo if we are not on Fedora or Arch????

where do we get the COPR repo if we are not on Fedora or Arch????

You will have to compile from source, with the patch applied, if you're not on a Fedora-based distro or one that uses COPRs.
Until the patch gets applied to upstream, it's going to be a while until you get Infinite working on any other distro (unless you apply the patch yourself)

specs:
5.18.7 kernel and proton-ge 7-22 Slackware 15.0
I upgraded libdrm 2.4.110 and mesa 22.1.2 on my system

I recorded myself playing a little bot match
https://www.youtube.com/watch?v=Iru6IrnEwC4 (random low fps is a obs problem don't worry about it)
basically how to get it working right now
delete all the videos in the videos folder
download proton-ge 7-21 and 7-22
launch with 7-22, if it works leave it
if online does not work
launch with 7-21
on amd you have to download those custom mesa drivers from the legend himself glorious eggroll
and that's it

I managed to play 3 consecutive MP games, no issues, however if you unfocus the game(if you use 2nd monitor or minimize) it might cause it to hang. Other than that no issues, can't wait for the SP to get working as that's what I've been eager to play, MP is just a bonus for me.

EDIT: Just FYI since people think I did something outside of the ordinary, I did NOT, all I did was use NVIDIA driver 515.48.07 and GE-Proton7-22

As far as I can tell this was the commit to finally allow the game to be playable https://github.com/HansKristian-Work/vkd3d-proton/commit/18f1d1c72eb86b4409c9ccd39a5adcb6167eda89

If im not mistaken the feature works ootb on NVIDIA, and requires a Mesa patch due to the AMD drivers not supporting anything like it, would like to be corrected if im wrong, very curious how this was all implemented.

If im not wrong, this is the mesa branch that will enable Execute indirect on AMD https://gitlab.freedesktop.org/themaister/mesa/-/commits/dgc_testing_ultra_bleed

It seems that for many NVIDIA and AMD users Halo Infinite now works with the latest Proton-GE. I updated my vkd3d (as of today) on archlinux and the game successfully launches but freezes at the splash screen where it says "Press Enter" and requires me to turn off the game. Indeed the entire background with all the birds flying also freezes. The game only successfully launched into the main menu once but I couldn't play any game because it said "you need to wait for shaders to finish compiling" What is causing this?

I don't know how to take a screenshot in game

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1168816671

I also had this issue. I'm not sure what causes it, but after a few restarts it works.

You can put Fedora onto an SD card (at least 64GB in size), install Halo Infinite to that SD card, and then tweak Fedora so that it includes everything needed, like the COPR repo and whatnot.

Game works on Deck with Nobara Project, thanks @orowith2os.

Only problem now is I can't figure out how to get the audio working, I think I'll just wait until SteamOS adds the patch to the Mesa drivers.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1168856336

Problem is i have restarted the game numerous times and it doesn't get better and like once in a while freezes on menu.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1168856336

I have tried numerous restarts - nothing helps. Occasionally it loads, most of the time it freezes. Did you install any packages or anything?

Hi,

i am playing the MP for some weeks now with the vkd3d lut index branch and a special radv branch. From graphics side this works fine so far. But:

I can not add/invite friends to my lobby, when i klick on using steam, no window shows up ( tab->friends->search, choose steam)
I can not join to my friends fireteam. He is playing on windows and could send me a steam invite. Klicking on it leads to an error message, "not being able to join fireteam".
The same happens after we added each other via xbox live as friends when i tried to join his team.

Br,
Christian

Halo Infinite runs perfect (in my experience) with the following tweaks:

1. Adding the launch option PROTON_NO_ESYNC=1 %command%
2. Running through GE-Proton7-21 (using a later version may work)
3. Using the patched Mesa libraries from GloriousEggroll's mesa-aco COPR repo (possibly Mesa with LTO enabled will work, also apply the following patch: https://copr-dist-git.fedorainfracloud.org/cgit/gloriouseggroll/mesa-aco/mesa.git/plain/dgc.patch?h=f36): https://copr.fedorainfracloud.org/coprs/gutigen/mesa-aco/
4. renaming the videos folder in the game directory

I suggest using distrobox to make a Fedora container to play Infinite if you are on AMD. This is the most painless way to go about it, and it integrates well with the host, with little risk of breaking it. Also a nice tool for immutable systems like the Steam Deck.

NVIDIA GPUs seem to have occasional hanging, attempt disabling fsync and esync in different combinations if you experience hanging, although I cannot guarantee that this will work.

I can also now load into multiplayer games when i disable esync. This may work for those who cannot load into single player.

Final edit: Infinite is very iffy on my system, with it sometimes working and sometimes not. Will try again when some updates get released for Mesa and VKD3D to allow it to render properly without large modifications

Afraid I cant actually get into any sorta game on my NV gpu, it runs in the background after choosing something like multiplayer or tranining, but is covered by a blackscreen or the load screen.

Edit: Got it to work with no fsync (sometimes) at the cost of performance.

Afraid I cant actually get into any sorta game on my NV gpu, it runs in the background after choosing something like multiplayer or tranining, but is covered by a blackscreen or the load screen.

Edit: Got it to work with no fsync (sometimes) at the cost of performance.

Got the same issue with my 3070. Going to try turning off fsync.

Afraid I cant actually get into any sorta game on my NV gpu, it runs in the background after choosing something like multiplayer or tranining, but is covered by a blackscreen or the load screen.
Edit: Got it to work with no fsync (sometimes) at the cost of performance.

Got the same issue with my 3070. Going to try turning off fsync.

Minor update, did get it working without any fsync or esync toggles, just proton ge 23. but it seems random if it will work or not. Crashes still too, it does "work" but not ready for primetime yet.

Spent more time with it, definitely not for full time, however the progress is huge, comparing to how it was, this is just stunning.
I seriously hope the campaign would be made playable soon.

my game has never crashed interestingly, (i have esync and fsync both on), is this just an nvidia issue?

my game has never crashed interestingly, (i have esync and fsync both on), is this just an nvidia issue?

Pretty sure it's a nvidia problem. I'll see if downgrading driver version does anything different. (I was on 515.48.07)

Compiling mesa-git with this patch worked for me with Proton-GE-23 on Arch. The only issue that I can spot is that the cursor is visible when in-game. Minor bug that doesn't really affect the gameplay

If I’m not mistaken this is the pr that will allow videos to play, https://github.com/HansKristian-Work/vkd3d-proton/pull/1070

Just wait a little longer, they’re doing some amazing work.

I'm going to edit my tinker steps and say this here:
if you want to run Infinite with little to no tinkering, I suggest using distrobox, installing a Fedora image, and use it inside of there.
The above will work for AMD, NVIDIA shouldn't require it since it uses its own Mesa libs included in nvidia-utils.

up and running < 10 mins (had the game downloaded already lol)
black bars are caused by gamescope
edit: can't get past main screen lol
edit2: ping www.google.com works but the game cant connect to servers... interesting
it even lets me sign in lmao

Further testing:
Haven't experienced any crashes when playing the game via gamescope, but will need to do more testing.

EDIT: Nope, still hangs randomly(the picture I mean, as the audio continues normally)

Further testing: Haven't experienced any crashes when playing the game via gamescope, but will need to do more testing.

EDIT: Nope, still hangs randomly(the picture I mean, as the audio continues normally)

yeah then it's probably an nvidia issue

this PR: should fix it for amd once it gets merged
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17269

Edit: merged, anybody running stable mesa >= 22.2 should be good

Further testing: Haven't experienced any crashes when playing the game via gamescope, but will need to do more testing.

EDIT: Nope, still hangs randomly(the picture I mean, as the audio continues normally)

Gamescope doesn't even work properly for me on nvidia 2060, how did you get it to work?

Further testing: Haven't experienced any crashes when playing the game via gamescope, but will need to do more testing.

EDIT: Nope, still hangs randomly(the picture I mean, as the audio continues normally)

Gamescope doesn't even work properly for me on nvidia 2060, how did you get it to work?

That's an Nvidia (or used to be) driver problem so what is your driver version

It's a hit or miss for me, still has some issues, but some titles work ok with it

Compiling mesa-git with this patch worked for me with Proton-GE-23 on Arch. The only issue that I can spot is that the cursor is visible when in-game. Minor bug that doesn't really affect the gameplay

how do you compile mesa-git with the patch on arch? I'm a noob.

@mercifulboss I saved the patch to my home folder as halo-mesa-patch.patch and ran yay --editmenu -S mesa-git in the terminal (make sure to enter "A" when PKGBUILDs to edit? pops up) and added this inside of the prepare function:

cd mesa
git apply ~/halo-mesa-patch.patch

Should look like this:

Maybe not the best solution unlike the already available patching logic above the code but it works :)

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1171756146

I would just git clone [AUR PACKAGE] and then edit the PKGBUILD and then run makepkg -si
your solution is valid too

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1171756146

Thank you for your reply! I tried doing what you suggested by I get "Yay command not found" when trying to run yay --editmenu -S mesa-git

Replying to [#5030 (comment)](https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1171756146)

I would just git clone [AUR PACKAGE] and then edit the PKGBUILD and then run makepkg -si your solution is valid too

How do I edit the PKGBUILD to add the patch to mesa-git? I tried putting the link to the patch in "sources" and got "fatal error"

Edit:

I got it to work using method 1, but I seem to have encountered another error:

This is on my amd machine running garuda since my nvidia machine doesn't work with halo infinite.

With a 2060 this is now loading up pretty consistently on Proton Experimental since the vkd3d update. No more freezing on the splash screen but it crashes after the player badge image loads (presumably the last step of logging in (?)). Don't really know what's happening so I've just attached the tail of the log file from just before the error. Awesome work getting it this far to all those putting in the hard yards.
steam-1240440-tail.log

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1171875106

You edit it in the same way he said to edit it in yay, yay is just editing the PKGBUILD
You also have to install vulkan-mesa-layers-git for it to work

Compiling mesa-git with this patch worked for me with Proton-GE-23 on Arch. The only issue that I can spot is that the cursor is visible when in-game. Minor bug that doesn't really affect the gameplay

I'm begginer, please, explane me step by step how do you apply the patch for Halo?

Linux: Garuda | Arch Linux

Compiling mesa-git with this patch worked for me with Proton-GE-23 on Arch. The only issue that I can spot is that the cursor is visible when in-game. Minor bug that doesn't really affect the gameplay

I'm begginer, please, explane me step by step how do you apply the patch for Halo?

Linux: Garuda | Arch Linux

First you google what a patch is on open source project (if you know this, you'll know how to implement the patch). Then you google what language the patch is in (applied in this case) so you can understand what you are doing. This will make you understand that applying any kind of patch makes it unstable and a developmental stage (if you don't know enough, you shouldn't self patch but do research on the subject first).

If you don't look up what I just said, you won't be able to apply the patches, this is an issue forum not a "how to do it" forum (mentioning the policies this sort of forum it is and where you can get better help and/or help yourself).

So after looking it up you will be able to apply the patch; so my understanding is that in AUR (for Arch Linux derivatives) you can edit the PKGBUILD of said mesa (the package is mesa-git) so you let the PKGBUILD build the mesa with the patch. If you look at the history of this issue they even mention how they did it with AUR specifically.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1173915629

A noob will have a hard time understanding how to apply PKBUILDS just from googling the information. I, myself tried googling how to apply a patch and came up with conflicting and confusing information, none of which made sense to me or worked. That's why I had to ask here.

I believe that such attitudes towards noobs (especially saying that this is "not a how to do it forum" puts off many future linux users and reduces adoption rates)

That being said, thank you for explaining it further on in your comment.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1173915629

I see. Thank you for your reply, I've already figured out how to patch mesa, but...

I got this issue then I trying to apply the patch (mesa-git or vulkan-mesa-layer-git)
error: src/amd/vulkan/radv_device.c: There is no such file or directory
ERROR: There was a failure in prepear()

I have been applyed patch by AUR

I think this problem is related to amd drivers. Don't throw slippers at me :)

Replying to [#5030 (comment)](https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1173915629)
…
I believe that such attitudes towards noobs (especially saying that this is "not a how to do it forum" puts off many future linux users and reduces adoption rates)

Except that he's 110% right that this is not a "how to do it forum". It's an issue tracker/bug report…

Replying to [#5030 (comment)](https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1173915629)
…
I believe that such attitudes towards noobs (especially saying that this is "not a how to do it forum" puts off many future linux users and reduces adoption rates)

Except that he's 110% right that this is not a "how to do it forum". It's an issue tracker/bug report…

I was trying to be nice in the other comment and here you are giving me attitude.

Except that issues tracking goes hand in hand with discussions on how to fix things. There are numerous precedents on other "issue trackers" for this. Where would you rather him go? Not all people know or have access to other communities that can help him fix the issue.

Logically, "'tracking issues" and "help me fix this issue" go hand in hand.

I'm going to take a book out of Glorious Eggroll's book and say this:

Halo Infinite is NOT ready to be played on Linux just yet, there are others working on getting the needed components to function correctly, the game just happens to partially work with some updates and patches.
When Infinite has most of the bugs ironed out, it will most likely be announced on a new version of Proton-GE. I cannot be sure about this, but it's what I am going to assume, so take it with a grain of salt.

That being said, if you want to attempt playing Halo Infinite:

It would be easiest just to go into a Fedora distrobox container, add Glorious Eggroll's mesa-aco COPR, install Steam from RPMFusion, and set the Proton-GE version to GE-Proton7-21 or newer. You may need to disable esync, fsync, or both, not 100% sure at this time. Anything past this, you're on your own.
https://copr.fedorainfracloud.org/coprs/gloriouseggroll/mesa-aco/

I would also not expect support for getting it running UNTIL Halo Infinite has all of the patches it needs included inside Proton-GE, or on Valve's Proton.

performance improvements on the way?
https://github.com/HansKristian-Work/vkd3d-proton/pull/1157
edit: got merged bois

Multiplayer works fine on Deck with vanilla SteamOS and GE-Proton7-26, no need to apply Mesa patches!

I recommend setting the graphics settings to Medium or lower, then setting the refresh rate somewhere between 40-50 Hz (it won't go any higher than 50 FPS at Medium settings at native resolution). Otherwise on default settings the audio stretches and the framerate lags at around 30 FPS.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1190608726

Impossible.........
did valve update the mesa version?
could you check what mesa version you are running?
and also why does it say dxvk, it should be vkd3d?

what mesa version you are running?

22.0.2

what mesa version you are running?

22.0.2

how is it even working, the game crashes on the main menu on proton ge 7-25 and 7-26
lemme try my fedora install with patched mesa
and there's broken rendering on 7-24 with mesa 21.1.3

You should really be using 7-26, that version specifically fixes the vkd3d-proton regression for the game. And make sure the video files are deleted if you haven't done so already.

You should really be using 7-26, that version specifically fixes the vkd3d-proton regression for the game. And make sure the video files are deleted if you haven't done so already.

I am using 7-26 lol and there are no video files
edit: only working on fedora with patched mesa still

Just played a few matches and roamed around for a bit in the campaign (using a save) without any lock-ups on my gtx 1650 mobile (w/ optimus). However I now have very severe stutter which was not present the last time I tried. Not sure if it's caused by my setup or if anyone else is also experiencing this.

Any other nvidia users able to confirm if the lock-ups are gone? I'm using proton-tkg with the proton bleeding edge branch and the latest vkd3d commits.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1190714377

I am also getting some pretty bad stuttering, I just thought it was my hardware tho (I have an igpu)

I should clarify for anyone running the game on Deck to opt in to the beta SteamOS/Deck client update channels, as apparently some on r/SteamDeck can't get the game to run at all on the stable SteamOS branch.

I'm running it on steam deck and performance seems to suffer greatly if you put your deck to sleep, you'll need to restart the deck to gain the performance back. Also changing your uma size in the bios to 4gb seems to help.

@Etaash-mathamsetty On Arch, I am also dealing with it crashing when it reaches the menu, it loads to the menu on Proton GE 7-24 but on 7-26, I get a crash

GE-Proton7-26 seems to have broken a lot of games for people, judging from what I've seen. I would recommend trying 7-25 and versions before that for now.

Games is running but the performance is grap.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1190714377

If that is a dgpu in a laptop with 4gb vram, you are hitting the vram limit of your card so stutter is expected.

The latest Proton GE 27 fixes videos not being able to be played + a bunch of other fixes! https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/GE-Proton7-27

If that is a dgpu in a laptop with 4gb vram, you are hitting the vram limit of your card so stutter is expected.

Same happens in the menus (where vram usage is much lower) so it's unlikely to be that I'm afraid. Seems to be an issue for others as well from what I've gathered.

If that is a dgpu in a laptop with 4gb vram, you are hitting the vram limit of your card so stutter is expected.

Same happens in the menus (where vram usage is much lower) so it's unlikely to be that I'm afraid. Seems to be an issue for others as well from what I've gathered.

On my RTX 3070 - the cpu spikes up to 95% usage and everything seems to flop hard, it wasn't like this a few proton ge versions ago... Furthermore the issue with random screen hanging/freezing on nvidia is still present.

Would love comments from people running an AMD dGPU (aka not a steam deck) on their current experience/needs/workarounds!

Would love comments from people running an AMD dGPU (aka not a steam deck) on their current experience/needs/workarounds!

you need the latest git version of mesa and proton ge 7-27
annnnnnnd you will get lots of stuttering anyway :(
and your mouse won't work properly, but otherwise it's pretty ok

It seems to me that when you approach a 60fps framerate (right around 57-58fps) that's when it freezes (for me a "freeze" is the image remains static, but the game still runs in the background). I think this is why it works on the Deck, because it can't reach that rate.

What seems to work for me: Turn off minimum framerate in the settings and set max framerate to 48 and turn on vsync. You may have to set max framerate to 30fps depending on your monitor (I know, not ideal). I set my graphics settings to low (I don't know if this matters).

This is with GE-Proton-7-26 (27 didn't work at all for some reason for me). I have a desktop with dedicated NVidia graphics (No iGPU though, so idk how it would work with Optimus).

I don't know if this is a solution, and I'd imagine some won't like this workaround, but it made my game go from crashing within 5 seconds of the start of a game to being able to complete a game against bots.

Good luck, I hope this helps someone,
jedi453

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1196933677

The game runs for me without any freezes at 120+ fps on my AMD GPU so maybe it's just an Nvidia issue?

Edit: Specs wanted by @FCLC:
Inxi:
CPU: 8-core AMD Ryzen 7 5800X (-MT MCP-) speed/min/max: 3535/2200/4850 MHz
Kernel: 5.18.14-zen1-1-zen x86_64 Up: 8h 46m Mem: 9586.2/32021.1 MiB (29.9%)
Storage: 3.18 TiB (30.8% used) Procs: 419 Shell: Zsh inxi: 3.3.19

Proton version: Proton 7 GE 27

I've only tested it with RADV due to AMDVLK not supporting dgc

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1196933677

The game runs for me without any freezes at 120+ fps on my AMD GPU so maybe it's just an Nvidia issue?

Thanks for sharing!

Mind editing your post to include current hardware configuration?

Which GPU/CPU/kernel/mesa/proton version?

As well as if you're using AMDVLK vs RADVLK?

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1196996705

Radv is what u need to use
Mesa 22 latest git version
Proton ge 7-27
Cpu : ryzen 7 4700u
Gpu: integrated graphics
5.18 kernel on fedora 36
And with that combo it's stuttering a lot (prob my hardware)
(My bad didn't read the edit your old post part lol, but this is my hardware config in case u need it)

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1196936082

Sounds like it as my ryzen 7 5800x3D paired with rtx 3070 on xorg halo infinite runs just fine but cpu is blasted to 95% and performance is incredibly choppy + random hang.
On wayland(which I main) I have to run the game with logging enabled(PROTON_LOG=1 %command%) just to make it run...
With proton ge 7.22 I can run the game with bearable performance and regular ~50% cpu usage(but the random hang is still present)

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1196933677

First of all I apologize for the double post, with the new proton ge 7.27 the game on xorg session runs fine but does run into the hang after a while, I found that limiting to 55 fps also triggers it so I lowered to 41 which resolved the issue. it seems there's something happening with higher frame rates on NVIDIA specific systems.
Just a quick note - you don't need to run V-Sync on, but if you don't use forcecompositionpipeline or gsync(if single monitor) then I guess it's better to be on.

I know each system is different. but Id like to say that I found that alt-tabbing once or twice removes the cursor in screen for me. I had been playing (vs bots) and never really noticed the cursor after 5m of playing, it wasn't that big of an issue for me. then later I noticed it was gone and I tried testing around a bit.

Idk if this will help anyone, also, I run GE 27 and do experience hangs and freezes like what Jedi453 encountered. Always when starting matches, once im in a bot match I can play for hours and hours. other than that I rarely encounter framerate issues (I only run at 1080 60fps mid setting. havent messed with quality yet) and playing online is fine providing it doesnt freeze. So I dont normally play online, ill wait until its more stable. normally can only play 2-3 matches online before freezing. small note, I am able to also run the game on proton experimental with some better results sometimes, but menu crashing occasionally. Videos file is still moved.

Game is running on my internal HDD. for better testing Ill be moving it to my NVME tonight.

[System]
OS: Ubuntu 20.04 focal
Arch: x86_64
Kernel: 5.15.0-41-generic
Desktop: ubuntu:GNOME
Display Server: x11

[CPU]
Vendor: AuthenticAMD
Model: AMD Ryzen 7 5800X 8-Core Processor
Physical cores: 8
Logical cores: 16

[Memory]
RAM: 62.7 GB
Swap: 2.0 GB

[Graphics]
Vendor: NVIDIA Corporation
OpenGL Renderer: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2
OpenGL Version: 4.6.0 NVIDIA 515.48.07
OpenGL Core: 4.6.0 NVIDIA 515.48.07
OpenGL ES: OpenGL ES 3.2 NVIDIA 515.48.07
Vulkan: Supported
(copied from lutris cuz lazy)

Just wanted to add a bit further report - after playing the game it seems that when limiting framerate to 41fps no hangs/freezes, however the open world section drops framerates like crazy, it's totally not so stable and I'd even say it's quite unplayable at the moment.

Ive never had it crash when capping at 30fps, tho it does just drop to 10fps sometimes, (once or twice) I had an issue like this in arma 3 once and I dont know what causes it. I often start matches capped at 30, then swap to 60 after 10seconds

GE-Proton7-28 disables video playback for now, apparently it's caused a regression. "Currently pending an update from Valve to fix the issue."

GE-Proton7-28 disables video playback for now, apparently it's caused a regression. "Currently pending an update from Valve to fix the issue."

it caused a regression with OTHER GAMES not halo infinite, so continue using GE 7-27 for halo infinite it's not worth the trouble to update (or 7-24 if that works better, you would have to remove the videos for this older version)
unless, somehow, the stuttering issue was resolved somehow

This game is weird every time I play attrition or last spartan standing my whole computer freezes...
In attrition it happens when all our teams respawns are used and in last spartan standing when there is only 5 spartans left my computer just locks up.
Audio still works for about 20 sec after that my friends told me that steam does not report me as playing anything so I guess game crashes at that point.
The weird part is how consistent the freezes are on those game modes.

[System]
OS: Arch Linux rolling n/a
Arch: x86_64
Kernel: 5.18.15-zen1-1-zen
Desktop: KDE
Display Server: wayland

[CPU]
Vendor: AuthenticAMD
Model: AMD Ryzen 9 5900X 12-Core Processor
Physical cores: 12
Logical cores: 24

[Memory]
RAM: 31.3 GB
Swap: 0.0 GB

[Graphics]
Vendor: AMD
OpenGL Renderer: AMD Radeon RX 6800 XT (navi21, LLVM 14.0.6, DRM 3.46, 5.18.15-zen1-1-zen)
OpenGL Version: 4.6 (Compatibility Profile) Mesa 22.2.0-devel (git-36c000484d)
OpenGL Core: 4.6 (Core Profile) Mesa 22.2.0-devel (git-36c000484d)
OpenGL ES: OpenGL ES 3.2 Mesa 22.2.0-devel (git-36c000484d)
Vulkan: Supported

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1200389702

It looks like I have the same problem with attrition (similar specs btw). Lets see if not matchmaking in those gamemodes helps a bit

Haven't seen this commented so thought I'd chime in again, my experience has been stable on Experimental and several of the recent GE version, however the game still consistently closes once the log in is complete (after gamer picture loads) - log file attached. I've also observed a crash after the framerate drops all the way down and have noticed that during that type of crash steam seems to be reloading the game library or something and afterwards I need to reload steam as the library shows "error code -105". Thanks everyone for all the hard work.

New DXVK release is out; "added support for shared fences (PR https://github.com/doitsujin/dxvk/pull/2608). This is needed for videos in Halo Infinite to work, alongside corresponding wine and vkd3d-proton patches."

The game seems to launch and work correctly now using the shared-resources branch of Proton Experimental on my Steam Deck.

I have been playing for a couple hours and haven't noticed any crashes.

the new proton experimental update improved perf a lot (no stuttering!!!!, or audio glitching), nearly runs like native on my 4700u. (well I am assuming native, I actually never tried this game native on this laptop :p)
I am getting random drops to around 20 fps (they stick around for 5-10 secs), but that is probably thermal throttling lol, these apus ain't meant to run at 30w
I am still getting those weird LOD glitching bugs, but when mesa 22.2 comes out, I will test again on arch to see if those bugs are present over there too
edit: perf problems gone when set power plan to balanced, the lod glitching goes away too (for the most part)
edit2: MOUSE HAS BEEN FIXED!

New Proton Experimental update gets me into the game, intro videos work fine and so does the initial 3D environment in the main menu. Once I load into the campaign however, there's a lot of LOD issues. Geometry seems low poly and textures don't quite load in. Performance is also very poor at around 20-25fps. Occasionally, the entire game freezes and crashes to desktop.

Arch Linux
AMD Ryzen 3900x
Nvidia 3090 with 515.65.01 drivers

I have been doing some tests with freezes in this game and I noticed that when I do get the freezes that lock up computer in 5.18 and 5.19 kernels in the 5.17 kernel I have not had a single problem while playing multiplayer.

[System]
OS: Arch Linux rolling n/a
Arch: x86_64
Kernel: 5.17.9-258-tkg-bmq
Desktop: KDE
Display Server: wayland

[CPU]
Vendor: AuthenticAMD
Model: AMD Ryzen 9 5900X 12-Core Processor
Physical cores: 12
Logical cores: 24

[Memory]
RAM: 31.3 GB
Swap: 0.0 GB

[Graphics]
Vendor: AMD
OpenGL Renderer: AMD Radeon RX 6800 XT (navi21, LLVM 14.0.6, DRM 3.44, 5.17.9-258-tkg-bmq)
OpenGL Version: 4.6 (Compatibility Profile) Mesa 22.3.0-devel (git-446d2039cb)
OpenGL Core: 4.6 (Core Profile) Mesa 22.3.0-devel (git-446d2039cb)
OpenGL ES: OpenGL ES 3.2 Mesa 22.3.0-devel (git-446d2039cb)
Vulkan: Supported

The latest

New Proton Experimental update gets me into the game, intro videos work fine and so does the initial 3D environment in the main menu. Once I load into the campaign however, there's a lot of LOD issues. Geometry seems low poly and textures don't quite load in. Performance is also very poor at around 20-25fps. Occasionally, the entire game freezes and crashes to desktop.

Arch Linux AMD Ryzen 3900x Nvidia 3090 with 515.65.01 drivers

Same issues, the only way I could get it to stabilize(further to prevent the NVIDIA GPU hang/freeze of the picture you have to lock fps to 41) is to set minimum fps to 41 as well so that it uses dynamic resolution to somewhat maintain it. That way I have somewhat smooth image but still a lot of geometry issues and problems into the main campaign, multiplayer is mostly fine.

Ryzen 7 5800X3D
RTX 3070
4x8gb ddr4 3000mhz ram
Kernel 5.19 tkg pds

Are people with AMD gpus having this problem (of freezing and crappy perf)?
The game runs at 60 fps for me with an integrated gpu
LOD issues are common among both GPU's however

Are people with AMD gpus having this problem (of freezing and crappy perf)? The game runs at 60 fps for me with an integrated gpu LOD issues are common among both GPU's however

Yeah AMD here and having those problems... atleast on newer kernel versions.

[System]
OS: Arch Linux rolling n/a
Arch: x86_64
Kernel: 5.17.9-258-tkg-bmq
Desktop: KDE
Display Server: wayland

[CPU]
Vendor: AuthenticAMD
Model: AMD Ryzen 9 5900X 12-Core Processor
Physical cores: 12
Logical cores: 24

[Memory]
RAM: 31.3 GB
Swap: 0.0 GB

[Graphics]
Vendor: AMD
OpenGL Renderer: AMD Radeon RX 6800 XT (navi21, LLVM 14.0.6, DRM 3.44, 5.17.9-258-tkg-bmq)
OpenGL Version: 4.6 (Compatibility Profile) Mesa 22.3.0-devel (git-446d2039cb)
OpenGL Core: 4.6 (Core Profile) Mesa 22.3.0-devel (git-446d2039cb)
OpenGL ES: OpenGL ES 3.2 Mesa 22.3.0-devel (git-446d2039cb)
Vulkan: Supported

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1207423126

I am running 5.18.16 (on fedora 36) kernel, so I don't think the "newer" kernel version causes it. (maybe upgrade to 5.18?)

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1207428053

Like I said in my reply before I tested 5.18 and 5.19 kernels (I actually have used 5.18 for few months) and then I just got this crazy idea to use old 5.17 kernel that I forgot to uninstall and haven't had any freezes after that.
If I start game with 5.18 or newer kernel I can play 1-2 matches and then my computer just locks up.

I don't know why 5.17 works for me I just hoped that if I tell about it here someone smarter that me can figure it out.

I would like to use 5.19 kernel if possible (I just have this stupid thing that I want to be on latest and newest on everything).

I just wanted to point out to those using the Steam Flatpak on a machine with AMD graphics. There is a way to get mesa-git working through Flatpak ( I couldn't get it to work through Distrobox or anything. ) This isn't my finding, but here's the link to the original author's post: https://www.reddit.com/r/linux_gaming/comments/v396dt/comment/ib3rhuy/?utm_source=share&utm_medium=web2x&context=3
All thanks should go to jntesteves on Reddit.
Using their method I was able to get it running on Proton Experimental on an AMD iGPU (VEGA 8). I also had to turn settings way down though, and don't expect amazing performance from a VEGA iGPU either. I also get some graphical glitches, but the games I played vs bots were good fun nevertheless.

The game seems to not utilize(at least for NVIDIA) the gpu correctly, it runs at about ~75-85% usage with mostly nothing going on in the workload(and that is if we exclude the random hang/freeze of the screen which occurs if you exceed 41fps). Other than that the game has weird flickers of the graphics even on low settings. CPU utilization is slightly higher as a result to that. Hopefully it'll all be resolved soon.

Hello everyone. Surely I can't be the only one who is seeing a night and day difference in the game due to the most recent updates.

Recent updates through Steam: (last 2 days)

Two Proton Experimental updates
Two Halo Infinite updates
One shader pre-cache (I think that's what it was called) update
And Proton 7.0-4

Launching with either 7.0-4 OR Experimental, I no longer receive the "Please ensure you have a DX12 compatible graphics adapter" warning on game launch (which Infinite is known for, both on Windows and Linux) that I have seen for the last few weeks, which has prevented Infinite from even opening at all.

After these recent updates, using "Experimental, as selected by Valve testing", the game starts right up.

• The main menu, which used to be so laggy I couldn't even navigate, is now smooth as silk. There are some slight audio popping issues.
• I go into campaign, the 3..2..1.. timer counts all the way down. This is where it used to break before. It would just go 3,2,1, then it would stop doing anything.
• Now, however, the loading bar at the bottom appears (pausing just long enough at 54% to make me think it locked up) and goes all the way to 100%. This step never happened before. The menu screen changes to the orange-red "map loading, gameplay tips" screen, then the screen goes black and the cursor appears in the center of the screen.

And that's it. No music. Nothing else. I have to force close at that point.

But its so much closer now.

Thank you to everyone helping to make this work.

Zorin 16.1 Pro
Kernel: Linux 5.15.0-46-generic
Kernel driver in use: nvidia 515.65.01
GTX 1070
i7-6800K OC
16GB RAM
Proton Tricks no longer installed
Wine Tricks installed
I don't use any launch options
Game settings on Medium or lower
Max framerate set to 30

I agree with techs, menu is now buttery smooth and responsive. I could play 5 MP matches without a crash. at 60fps no less. The game doesnt run perfectly yet but we are so close. Huge thank you to the ones helping the project along

I am having an issue where the loading screen that has tips never disappears for custom games even though I can move around and shoot.

I have not tried matchmaking or campaign.

System specs:

                          ./+o+-       gamebuster@gamebuster-Ryzen9-3900X-RTX-3080
                  yyyyy- -yyyyyy+      OS: Ubuntu 22.04 jammy
               ://+//////-yyyyyyo      Kernel: x86_64 Linux 5.15.0-43-generic
           .++ .:/++++++/-.+sss/`      Uptime: 3d 16h 39m
         .:++o:  /++++++++/:--:/-      Packages: 3134
        o:+o+:++.`..```.-/oo+++++/     Shell: bash 5.1.16
       .:+o:+o/.          `+sssoo+/    Resolution: 3840x2160
  .++/+:+oo+o:`             /sssooo.   DE: GNOME 41.7
 /+++//+:`oo+o               /::--:.   WM: Mutter
 \+/+o+++`o++o               ++////.   WM Theme: Adwaita
  .++.o+++oo+:`             /dddhhh.   GTK Theme: Yaru-dark [GTK2/3]
       .+.o+oo:.          `oddhhhh+    Icon Theme: Yaru
        \+.++o+o``-````.:ohdhhhhh+     Font: Ubuntu 11
         `:o+++ `ohhhhhhhhyo++os:      Disk: 670G / 917G (77%)
           .o:`.syhhhhhhh/.oo++o`      CPU: AMD Ryzen 9 3900X 12-Core @ 24x 3.8GHz
               /osyyyyyyo++ooo+++/     GPU: NVIDIA GeForce RTX 3080
                   ````` +oo+++o\:     RAM: 8528MiB / 32007MiB
                          `oo++.      

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1224352567

what's your nvidia driver version?
and you should probably try normal multiplayer or campaign first

Sadly i get game crashes from time to time. Also Using alt+tab when searching for a mp game is troublesome and causes game freezes.

For the game crash, 2 files:

crash_info.txt

And:
https://drive.google.com/file/d/1iQuOBczBUyXjrfh4qGmWyBFUa2imrCYr/view?usp=sharing

For the freeze with al-tab:

Multiplayer->Quick play

While the game is searching for games, alt+tab so that another window is in front of the Halo window. The game will freeze when the final connect happens and the game switches to the loading screen before the actual match starts.

The issue happens on kde here, X11, compositor disabled, Proton Experimental.

on the latest Nvidia vulkan dev driver the game doesn't even launch. It almost instantly hangs
steam-1240440.log
.

something I have noticed, when setting halo infinite to be 'always on top' (alt+space brings up the menu) it reduces hang ups by quite a bit. could be luck ofc but I played around 10 matches without any hangs and then left the game normally. this is while I did also move workspaces to watch videos during loading. so take that as you may.

[System]
OS: Ubuntu 20.04 focal
Arch: x86_64
Kernel: 5.15.0-46-generic
Desktop: ubuntu:GNOME
Display Server: x11

[CPU]
Vendor: AuthenticAMD
Model: AMD Ryzen 7 5800X 8-Core Processor
Physical cores: 8
Logical cores: 16

[Memory]
RAM: 62.7 GB
Swap: 2.0 GB

[Graphics]
Vendor: NVIDIA Corporation
OpenGL Renderer: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2
OpenGL Version: 4.6.0 NVIDIA 515.65.01
OpenGL Core: 4.6.0 NVIDIA 515.65.01
OpenGL ES: OpenGL ES 3.2 NVIDIA 515.65.01
Vulkan: Supported

Shot in the dark but I had Doom Eternal freezing instantly as soon as anything was drawn on top of its window (any app notification popup etc.). No idea if it's fixed now (most probably) but could it be the same for Halo Infinite? Then making the window always on top might fix it I guess.

Unfortunately, I still have freezes when a match ends even with the always on top workaround.

Unfortunately, I still have freezes when a match ends even with the always on top workaround.

I found that for some insane reason, when ending matches. (during loading screen) if I intentionally move workspace to another tab and have (mozilla for example) open, with VLC, then it doesnt freeze as much. bear in mind I am still getting freezes but the number has dropped by a huge % compared to before. It could be anything, I cant understand it but thats why I am sharing these findings. to try to help

Unfortunately, I still have freezes when a match ends even with the always on top workaround.

what wine version are you running? It may be some changes with recent patches that caused this.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1231216001

I was using the latest Proton Experimental at the time of writing.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1231216587

I mean your system WINE, because one MUST have system wine installed and its updates (to my knowledge) do affect proton. I noticed a change since I upgraded from 7.0 to 7.15 (and today to 7.16). I dont know if any big changes occurred tho, just throwing my two sense in

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1231336670

I’m almost certain proton is entirely isolated from system wine very much intentionally.

Replying to [#5030 (comment)](https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1231216587)

I mean your system WINE, because one MUST have system wine installed and its updates (to my knowledge) do affect proton. I noticed a change since I upgraded from 7.0 to 7.15 (and today to 7.16). I dont know if any big changes occurred tho, just throwing my two sense in

That can't be. I am running Steam inside of Flatpak, and it does not have access to my system Wine installation.

Replying to [#5030 (comment)](https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1231336670)

I’m almost certain proton is entirely isolated from system wine very much intentionally.

you're probably correct, I am no expert. but why then does wine need to be installed for proton to function? if some assets arent used

Replying to [#5030 (comment)](https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1231336670)

I’m almost certain proton is entirely isolated from system wine very much intentionally.

you're probably correct, I am no expert. but why then does wine need to be installed for proton to function? if some assets arent used

This is getting off-topic, but no, you should not have to have Wine installed on your system to be able to make use of Proton. Proton is self-contained in that regard.

Having an issue where the game crashes right before loading the menu screen.
SteamHardwareInfo.txt
errorlog - it is a Google Drive link 'cause it's too big to be uploaded by CTRL-C/CTRL-V'ing it into Github

This is on Proton Experimental, the Steam Client Beta, and the Steam Runtime - Soldier Beta, if any of those are relevant.

Having an issue where the game crashes right before loading the menu screen. SteamHardwareInfo.txt errorlog - it is a Google Drive link 'cause it's too big to be uploaded by CTRL-C/CTRL-V'ing it into Github

This is on Proton Experimental, the Steam Client Beta, and the Steam Runtime - Soldier Beta, if any of those are relevant.

I am pretty sure intel gpus are not supported yet
edit: for future readers, mesa 22.2 is required to load into the menu, and in game (on amd), intel cards are probably not working atm

Two things - first of all, thank you email for sending me the first version of your comment 'cause that was more actually useful - I'm on the 22.1.7 kisak ppa version of Mesa, which explains why I can't get in the menu if it requires 22.2.

Second of all, I do have a Radeon RX 5700 XT eGPU plugged into my system that even MangoHud was detecting as the video driver for Halo Infinite when I generated that log.

Two things - first of all, thank you email for sending me the first version of your comment 'cause that was more actually useful - I'm on the 22.1.7 kisak ppa version of Mesa, which explains why I can't get in the menu if it requires 22.2.

Second of all, I do have a Radeon RX 5700 XT eGPU plugged into my system that even MangoHud was detecting as the video driver for Halo Infinite when I generated that log.

that was my bad, I saw that you had a framework laptop with intel and just assumed that you had an intel card (I didn't read the rest)
I forgot egpus existed lol

The hanging/freeze image issue seems to be triggered by fluctuating framerate(which is quite evident by barely using my GPU at least on NVIDIA) so a workaround is to set minimum framerate to 41 and maximum framerate to 41, with that I haven't encountered any freezes/hangs yet in both campaign and multiplayer.

The hanging/freeze image issue seems to be triggered by fluctuating framerate(which is quite evident by barely using my GPU at least on NVIDIA) so a workaround is to set minimum framerate to 41 and maximum framerate to 41, with that I haven't encountered any freezes/hangs yet in both campaign and multiplayer.

this makes sense, I often drop in bot games when bots are joining in for the first time. frame drops probably happen around that time. the rare times I do freeze in MP are during melee moments, and when someone has a kill effect. just my observations mind you. possibly why I can play quite a bit, I have a system that can handle infinite easily so framedrops happen very infrequently

When I join bot games with uncapped frame rate, I can hear sounds such as me firing my own weapon, however the loading screen is frozen onscreen.

Using proton experimental.

                     ./o.                  false@false 
                   ./sssso-                ----------- 
                 `:osssssss+-              OS: EndeavourOS Linux x86_64 
               `:+sssssssssso/.            Host: MS-7C37 1.0 
             `-/ossssssssssssso/.          Kernel: 5.19.4-zen1-1-zen 
           `-/+sssssssssssssssso+:`        Uptime: 5 days, 16 mins 
         `-:/+sssssssssssssssssso+/.       Packages: 1029 (pacman), 5 (flatpak) 
       `.://osssssssssssssssssssso++-      Shell: bash 5.1.16 
      .://+ssssssssssssssssssssssso++:     Resolution: 2560x1440 
    .:///ossssssssssssssssssssssssso++:    DE: Plasma 5.25.4 
  `:////ssssssssssssssssssssssssssso+++.   WM: KWin 
`-////+ssssssssssssssssssssssssssso++++-   Theme: [Plasma], Breeze [GTK2/3] 
 `..-+oosssssssssssssssssssssssso+++++/`   Icons: [Plasma], breeze-dark [GTK2/3] 
   ./++++++++++++++++++++++++++++++/:.     Terminal: konsole 
  `:::::::::::::::::::::::::------``       CPU: AMD Ryzen 7 5800X (16) @ 3.800GHz 
                                           GPU: NVIDIA GeForce RTX 3090 
                                           Memory: 10763MiB / 32018MiB 

with proton experimental bleeding edge and mesa-tkg-git from the chaotic aur with vanilla arch linux on kde wayland
I set the in game frame limit to vary between 35 and 70 hz (I OCd my monitor to 70hz).
With this combination and my 4700u + The iGPU (with medium settings preset), I am getting a flawless experience without any LOD glitching
Unfortunately the mouse has once again been broken (edit: I was using the wrong branch of proton, i was using shared resources rather than bleeding edge, it works with bleeding edge)

not bad considering this system config is a potato by modern standards

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1238665039

Yeah, getting about the same results. Seems like for me the sweet spot is having the fps locked at 41-45 fps, this made the game completely playable (2070 super). Anything higher than that will result in the freeze after a short while of playing. The incredible work that has gone from not getting past the loading screen to this nothing short but awesome.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1238665039

Yeah, getting about the same results. Seems like for me the sweet spot is having the fps locked at 41-45 fps, this made the game completely playable (2070 super). Anything higher than that will result in the freeze after a short while of playing. The incredible work that has gone from not getting past the loading screen to this nothing short but awesome.

That seems to be an Nvidia problem, i later set the min fps to 70 and it never froze or anything

anybody getting textures issues with latest mesa git? I have a feeling that it might be that sparse texture thing that got merged
edit: seems like they are gone after another update to mesa

running okay between 41-45 fps, as seen before. some crashes when opening the challenge/BattlePass menu. Alt-tabbing causes instability. but aside from that, the thing runs pretty much faultlessly as far as I can tell. just waiting on that fix for the fps issue/hang/freeze/whatever

I can't run it for some reason. Maybe somebody know what might be the problem?
I have GTX 1060

@gravit22 the NVIDIA drivers need to be around version 515, afaik. If you're running the Steam Flatpak and your host's drivers are on the 515 series, run a flatpak update and restart Steam completely.

@gravit22 the NVIDIA drivers need to be around version 515, afaik. If you're running the Steam Flatpak and your host's drivers are on the 515 series, run a flatpak update and restart Steam completely.

@orowith2os Thank you for your response. I made changes you mentioned, and this is what I got.

So sad. I have only 3 GB VRAM.

Oh. no. I am sorry, I just pressed continue, and it launched.
Thank you.

Hi

i still can 100% reproduce the mentioned alt+tab hang here. Could anyone at vavle reproduce that ? Are there any logs needed ?

Thx

Hello,
I am playing Halo Infinite on Arch Linux with an AMD GPU using the mesa-git drivers.

I notice a consistent crash for me on any multiplayer game type involving a zone to capture. I seem to crash whenever the graphics for the zone are supposed to appear. For example, in the King of the Hill game mode, I crash as soon as the initial hill is available to capture, if my view in-game is looking towards the area it is in. I can supply any logs if needed.

EDIT:
Wow, I'm sorry I didn't realize there was an update to mesa-git released a few hours ago after not having an update for at least a week or so. This update to mesa-git fixes the issue as far as I can tell! The game runs much smoother for me now although it still stutters quite a lot.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1257131296

What version of mesa-git were you running before, and what version seems to have fixed this issue for you?

Replying to [#5030 (comment)](https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1257131296)

What version of mesa-git were you running before, and what version seems to have fixed this issue for you?

It doesn't seem like the AUR has version numbers, but the previous version I was on was this one released on the 10th, and I just updated to this version released on the 24th.

Ah, ok TIL not all -git AUR packages are locked to a certain commit. Looking at the PKGBUILD for mesa-git I don't see any specific commit linked in the git source...

I will try and see if I can get the specific version from the old version I was using, but using the version I updated on the 24th, glxgears -info shows me:

GL_RENDERER   = AMD Radeon RX Vega (vega10, LLVM 14.0.6, DRM 3.47, 5.19.11-arch1-1)
GL_VERSION    = 4.6 (Compatibility Profile) Mesa 22.3.0-devel (git-e0b7430eae)
GL_VENDOR     = AMD

EDIT: Unfortunately I deleted my pacman cache, so I cannot verify for sure, but based on my best detective work I believe the commit I was playing with before was around 3d4c36a3 on the 14th

I should also mention, today while playing the latest "Fracture" event based around the "Land Grab" gamemode (spawns many capture zones), I did encounter a crash in the same way as before, so it's not completely fixed yet (I encountered only one crash from the many Land Grab games I played).

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1260496543

played some myself, cant say I had those issues, in fact it only crashed after 7 games or so, and only in BTB social. I am on nvidia tho, proton GE or exp work best ive found

'gamemoderun mangohud %command%'

Deleting the games compatdata file (1240440) is a good way to get pretty solid performance. Ive found that sometimes it never loads right and starts crashing far more often, removing this folder is a great way to fix that (tested twice now)

If anyone knows if this is a horrible idea, let me know, but as of typing, my game doesnt crash unless I alt tab too much

Deleting the games compatdata file (1240440) is a good way to get pretty solid performance. Ive found that sometimes it never loads right and starts crashing far more often, removing this folder is a great way to fix that (tested twice now)

If anyone knows if this is a horrible idea, let me know, but as of typing, my game doesnt crash unless I alt tab too much

No harm in deleting the compatdata folder, not sure how it helps, but it's just the prefix location so it will only reset any local configurations / save data and have Steam reinstall game dependencies like visual C++, etc.

As for the unfocusing the Window issue, if you use Gamescope it will prevent this problem, as it runs the game in a containerized display compositor, which will prevent the game from detecting any anomalies like Alt-Tabing, minimizing, etc. I use this myself and it's completely removed that issue for me.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1271714132

my understanding of it is it is a prefix, and I know that wine prefixes break all the time, so I do this occasionally with my base wine prefix to really clean the place up a bit. idk how exactly it helps infinite, but sometimes I crash way too often and removing that helps clear it up a bit

Has anyone been able to join the fireteam in Halo Infinite?

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1272580333

I've been having issues with this too lately.

I've been having issues with this too lately.

Did it work before? With what proton?

I've been having issues with this too lately.

Did it work before? With what proton?

A few months ago but I stopped playing. Just booted it up on my pc a few days ago and my and my friend (also on linux with proton) were both having issues with fireteam

So, we can play online these deathmatches, etc, but can not play campaign with friend... :(

new feature release NVIDIA drivers (520) apparently stop the game from hanging, however have flashing colors and texture issues. source is protondb.

Myself I cannot upgrade to them as my work at the moment is keeping me from risking a driver change. Anyone have anything to report on this matter?

new feature release NVIDIA drivers (520) apparently stop the game from hanging, however have flashing colors and texture issues. source is protondb.

Myself I cannot upgrade to them as my work at the moment is keeping me from risking a driver change. Anyone have anything to report on this matter?

could you post some pictures? (or someone else)

I just tried playing a custom game match with bots using Nvidia driver 520.56.06. I was able to complete the match, but the game still hung during the loading screen after the match.

Maybe check your ram usage when you crash? For me the only time I have crashed was when the linux kernel OOM kicked in and killed the process because I ran out of ram

Maybe check your ram usage when you crash? For me the only time I have crashed was when the linux kernel OOM kicked in and killed the process because I ran out of ram

The game doesn't out-right crash. The graphics locked up, but the sound was still going.

Plus I'd be surprised if Halo Infinite could trigger OOM on 32gb of ram.

Maybe check your ram usage when you crash? For me the only time I have crashed was when the linux kernel OOM kicked in and killed the process because I ran out of ram

well I have 64gb of ram and it has locked up in the past for me too, Id be shocked if it managed to fill that up. Also, Ive had no crashes (5 games at 60fps in BTB) since I moved my steam folder from my HDD to my NVME. I am still running the 515 driver. will be testing more but work stopped that.

Seems like nvidia's new driver 520 has solved most of the issue, performance wise still isn't the great... As for texture flickering on medium settings seems like it doesn't happen.

EDIT: Never mind, I managed to run into a lockup after some time... So the issue is not fully resolved, but rather "improved"

I decided to try Proton Experimental (bleeding-edge), since I was using Proton-GE. Just to be sure I also cleared my compatdata.

To my surprise I was able to play a few MP matches (I tried Fiesta and BTB), and some of the Campaign without any hiccups. The framerate is pretty bad compared to my Windows10 VM, and there's a fair amount of texture flicker once in a while, but It's definitely an improvement.

Driver: 520.56.06
GPU: RTX3060 12GB

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1283585253

Actually yes, playing the game on Proton-GE seems to cause the hangs forgot I used it to compensate with FSR for the poor GPU utilization(which results in poor performance).
On Proton experimental with driver 520.56.06 there doesn't seem to be any hangs.

I have the same issue as well (on proton-ge), that's why I don't play the game using proton-ge (and im using AMD)

Can also confirm with an RTX 3070--got crashes with Glorious Eggroll, but with Experimental no crashes, just texture flickering.

cat /proc/driver/nvidia/version
NVRM version: NVIDIA UNIX x86_64 Kernel Module  520.56.06  Thu Oct  6 21:38:55 UTC 2022
GCC version:  gcc version 12.2.0 (GCC)

Proton Experimental works at 60fps and tested 5 BTB games. Will be testing more but there should have been a hang by that point. slight performance drop on breaker (hate that map) but aside form that it felt pretty good. using the 515 drivers as well and during typing this I have had the game alt-tabbed in another workspace which normally caused it to hang very quickly. I have seen the game drop to 14fps for a second during a loading screen but it did not hang. GE still does cause crashes (tested last night). Will report more if I find anything

OS: Ubuntu 20.04 focal
Arch: x86_64
Kernel: 5.15.0-52-generic
Desktop: ubuntu:GNOME
Display Server: x11

[CPU]
Vendor: AuthenticAMD
Model: AMD Ryzen 7 5800X 8-Core Processor
Physical cores: 8
Logical cores: 16

[Memory]
RAM: 62.7 GB
Swap: 2.0 GB

[Graphics]
Vendor: NVIDIA Corporation
OpenGL Renderer: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2
OpenGL Version: 4.6.0 NVIDIA 515.76
OpenGL Core: 4.6.0 NVIDIA 515.76
OpenGL ES: OpenGL ES 3.2 NVIDIA 515.76
Vulkan: Supported

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1272580333

I too am having this issue... I have tried different versions of Proton and a couple of launch settings from protondb but nothing seems to work. Anyone have any luck?

Never even tried to join a fireteam. I still cant join my friends in the MCC (custom, MP, or campaign) So I will be of no help here xD

I get pretty bad frametimes with GE proton 7-37 and proton experimental.

CPU : 10600k
GPU : 1660ti (515.76 driver)

Display server : X11
Ubuntu 20.04.1 LTS

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1287594151

From what I can tell, my card stutters a bit on that map specifically, and any card that is under a 30 series has performance issues as of recent. (Based on what I am hearing from other users. Users on protondb with 30 series work decently, users with older cards say they get horrible framerate)

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1272580333

I'm having the same issue. I (Ubuntu 22.04, kernel 5.17, Mesa 22.2.2, Proton Experimental) couldn't connect with my friend (Steam Deck) no matter how many times we tried. Tried joining from the Social menu in-game and through invites in Steam chat. Neither of us have any issues with matchmaking, we're just unable to join fireteams.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1287594151

Yes something similar happens on my RTX 3070 as well. The GPU utilization fluctuates between 50-85% totally not how it should be, so in order to tackle it I use the minimum framerate in-game setting set to 82 and it drops down resolution to maintain somewhat higher FPS. Not ideal solution however it gives playable performance.
In regards to fireteam, if you try to join someone it does not work, INSTEAD make them join over you - that in all my tests have always worked.

Yeah other people can join fine it is just not allowing me to join other players, seems odd to me. As far as the graphics thing goes I'm on AMD and get over 70 fps at 4k all Ultra settings. Maybe it is an nvidia issue.

Yeah other people can join fine it is just not allowing me to join other players, seems odd to me. As far as the graphics thing goes I'm on AMD and get over 70 fps at 4k all Ultra settings. Maybe it is an nvidia issue.

It is an Nvidia issue, I've not seen anybody with amd reporting these issues

Yeah other people can join fine it is just not allowing me to join other players, seems odd to me. As far as the graphics thing goes I'm on AMD and get over 70 fps at 4k all Ultra settings. Maybe it is an nvidia issue.

It is an Nvidia issue, I've not seen anybody with amd reporting these issues

Maybe this is an issue with VKD3D that only appears on nvidia cards, or a nvidia driver bug within itself.

Is there any reports about this on the wine project? If not i may open a bug report about that.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1287861332

wine's vkd3d has nothing to do with the vkd3d that proton uses, you should open a bug report at vkd3d-proton, NOT the upstream one

Been playing for a while, no hangs anymore, new proton experimental and nvidia drivers 520 remove hangs.
Has crashed once or twice during menus but never in games. Working okay so far however slight performance problems. frame drops. This should not be happening on my system so anyone with mid specs might suffer far more

I can still encounter random hang + weird performance in this title and went ahead to report it on the NVIDIA forums.

https://forums.developer.nvidia.com/t/poor-halo-infinite-performance-and-random-hang/232202

Hmm I wonder when Nvidia or 343 or even valve them selfs will solve this weird frame timing issue. I'm loving the game just the fps is very weird on Nvidia gpus lol

Hmm I wonder when Nvidia or 343 or even valve them selfs will solve this weird frame timing issue. I'm loving the game just the fps is very weird on Nvidia gpus lol

Have you tried turning on vsync in game. I did that and the frame timing issues went away for me (amd rx6600xt. Might also work on Nvidia though)

Just tested it and vsync off around 40fps to 50fps and frame timing weird af. Vsync on 45fps to 30fps and frame timing is better but seems to have bigger dips so idk. I have a 2060 aswell and I get around 100 to 120fps on windows

Just tested it and vsync off around 40fps to 50fps and frame timing weird af. Vsync on 45fps to 30fps and frame timing is better but seems to have bigger dips so idk. I have a 2060 aswell and I get around 100 to 120fps on windows

It's kinda weird cause some maps make me get 60 to 70 then the rest are like 30 to 40 and texture and shader cache are constantly loading in every match so that's pretty annoying but oh well

these are my frametimes on an APU (it's struggling lol, it's doing pretty well for only 15W of power tho)

For me, the only map I have fps issues with is breaker. Could be the extra effects, no idea if this would help anyone. guessing its the bigass laser in the middle causing that.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1299462562

Its funny that your getting 45 fps there and i get the exact same fps on my rtx 2060...

Can't launch the game after getting the following error when playing with Proton Experimental on an RTX 3070 on the latest Winter Update.

Could not load 'api-ms-win-core-memory-l1-1-6.dll'. It may be missing or corrupted.

It being called "Arbiter" makes me think this is an anti-cheat issue since Arbiter is the name of the anti-cheat in Halo Infinite.

Same here

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1307710200

Okay, deleted arbiterdll and verified game files, same error, will try again with a few other things but at this point game appears broken due to anti-cheat. I will assume it is due to updates with the Co-op and relevant anti-cheat. This is an assumption tho, I can be wrong

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1307710200

This issue has been fixed in wine upstream, at least I think it has (edit: it hasn't, but it's probably a one line patch for upstream wine)
Once I reach home I will thoroughly check
edit: for proton, the patches would be way bigger than one line (it's unfortunate, this is why proton needs to be rebased)

I will assume this puts us into borked mode for several days if not weeks correct? Until it is actually repaired

I will assume this puts us into borked mode for several days if not weeks correct? Until it is actually repaired

no, someone's already working on it apparently, it might take a while for the fix to get merged tho

I will assume this puts us into borked mode for several days if not weeks correct? Until it is actually repaired

no, someone's already working on it apparently, it might take a while for the fix to get merged tho

Then I will continue looking and testing after work, will share what I can if I get anywhere

i hope it gets fixed soon. theres free shop items!

This should hopefully work again now with the just updated "Proton Hotfix". For now "Proton Hotfix" should be manually selected as compatibility tool for the game. If trying right now probably worth restarting Steam so Proton Hotfix gets updated right away.

This should hopefully work again now with the just updated "Proton Hotfix". For now "Proton Hotfix" should be manually selected as compatibility tool for the game. If trying right now probably worth restarting Steam so Proton Hotfix gets updated right away.

you work on proton too, dang, they are all the same same people after all lol
edit: apparently needs a little bit of cleaning up before it can reach experimental, but that's what proton hotfix is for!

It works. I'm playing

On Tue, Nov 8, 2022, 21:45 Etaash Mathamsetty @.***>
wrote:

This should hopefully work again now with the just updated "Proton
Hotfix". For now "Proton Hotfix" should be manually selected as
compatibility tool for the game. If trying right now probably worth
restarting Steam so Proton Hotfix gets updated right away.

you work on proton too, dang, they are all the same devs after all lol

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1308166303,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2MCZEG44Q7RJJLX7IJAR63WHMM6PANCNFSM5BGY6AKQ
.
You are receiving this because you commented.Message ID:
@.***>

Confirm that is working now on steam deck with proton hotfix, also if a warning appears during loading for incorrect windows version

Works and is playing, some stutter on BTB maps but overall great

Forge doesn't seem to be launching, not sure if that's because of Proton or what

https://user-images.githubusercontent.com/71602778/200813417-c714c4f3-3014-4345-9a6a-817e63dd7868.mp4

tried restarting the game several times now but it had no effect

EDIT: just got in after launching a custom game and then exiting. no clue about correlation yet.
Looks like launching a custom game set to local server is required first before Forge works. Not sure if this is Proton-specific or just how the game's behaving on my system.

I've seen this with a lot of games lately, do we know what exactly is causing the GPU to reset when playing games like Halo Infinite? It seems to happen on both AMD and NVIDIA cards and seemingly randomly.

Like, is it an issue with both Nvidia and AMD drivers, is it an issue with the kernel, game, etc? I've heard people blame many thing but no definite answer yet.

I've seen this with a lot of games lately, do we know what exactly is causing the GPU to reset when playing games like Halo Infinite? It seems to happen on both AMD and NVIDIA cards and seemingly randomly.

Like, is it an issue with both Nvidia and AMD drivers, is it an issue with the kernel, game, etc? I've heard people blame many thing but no definite answer yet.

I know one cause is that the high res textures can fill up my vram very quickly, and setting the texture quality to low can help that abit. It still has some crashes after that but they might be related.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1309090818

Seems like just a placebo to me though. Whether I run on the lowest settings with locked 60 FPS, or max settings at 165 FPS (which both run at full speed and never use all my VRAM) I still crash at some point. Infact, 165 FPS seems to last way longer before crashing (which again is probably just a coincidence).

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1309090818

Seems like just a placebo to me though. Whether I run on the lowest settings with locked 60 FPS, or max settings at 165 FPS (which both run at full speed and never use all my VRAM) I still crash at some point. Infact, 165 FPS seems to last way longer before crashing (which again is probably just a coincidence).

When textures were set to high, I would crash before the game would load. After setting it lower, I could get in game and complete a round. It still crashes occasionally though.

Continuing from https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1307710200

Working after applying the hotfix :+1:

Even after setting compatibility to Proton Hotfix, the game still seems to crash right at the part where it seems to have a loading bar. Not sure what is wrong.

Even after setting compatibility to Proton Hotfix, the game still seems to crash right at the part where it seems to have a loading bar. Not sure what is wrong.

you probably need to update your gpu drivers to mesa 22.2+ or any recent version of nvidia drivers

steam-1240440.log

Popup error message "Could not load 'api-ms-win-core-memory-l1-1-6.dll'. It may be missing or corrupted." didn't leaves even after update the game and Proton Hotfix.

OS: Fedora Rawhide
GPU: AMD Radeon 6900XT
GPU driver: Mesa-22.4-dev

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1309380017

I think you have to restart steam

I think you have to restart steam

During this time, I have already managed to restart the computer several times. So the option to restart steam will definitely not work.

Even after setting compatibility to Proton Hotfix, the game still seems to crash right at the part where it seems to have a loading bar. Not sure what is wrong.

Not really sure, I am running the latest Ubuntu LTS kernel with an AMD 6800 XT. I am pretty sure the drivers are proper. IDK.

Even after setting compatibility to Proton Hotfix, the game still seems to crash right at the part where it seems to have a loading bar. Not sure what is wrong.

Not really sure, I am running the latest Ubuntu LTS kernel with an AMD 6800 XT. I am pretty sure the drivers are proper. IDK.

ubuntu LTS's mesa isin't new enough you have to get it from from a ppa (idk which one)

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1309380017

Just to confirm, you selected to use proton hotfix instead of experimental correct. manually

The hotfix worked for me, however I cannot join any friends. If I try to connect to one of my friends parties via a steam invite I always get the messages "You were unable to connect to the fireteam. Please try again later." But if I invite them (and they are a windows user) they can join my party. The same issue occurs for my friend who also uses linux but not my friends who use windows. Linux users can only host a lobby for windows users to join, but linux to linux host cannot connect at all it seems.

The hotfix worked for me, however I cannot join any friends. If I try to connect to one of my friends parties via a steam invite I always get the messages "You were unable to connect to the fireteam. Please try again later." But if I invite them (and they are a windows user) they can join my party. The same issue occurs for my friend who also uses linux but not my friends who use windows. Linux users can only host a lobby for windows users to join, but linux to linux host cannot connect at all it seems.

has been an issue for a while, or at least to me it has been

I have noticed there is a issue that has been here even before the winter update where if you are alt tabbed out while you're in the countdown and if it counts down to one your game instantly freezes and crashes and this such a problem due to the longer then usual queue compared to other games where while playing ranked I have been banned 3 times because of this issue

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1310021068

I have been getting this before the winter update because I like tabbing out a bunch for music and YouTube lol so kinda annoying

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1310041256

Yup, same here. Super annoying.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1310021068

I think you can use gamescope to resolve this
edit: I can reproduce this as well, you can play in windowed mode to use your DE's media player controls or something if you don't want to use gamescope

After updating to Proton Hotfix the game launches and is playable but I'm getting some graphical glitches I didn't have before:

• Missing hands:

• Poor textures (especially the trees)

GPU: AMD RX 5700 XT

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1312248277

Use mesa-git, you are getting the dreaded LOD issues we used to get back when mesa 22.2 was about to get released

Since you weren't having the issue before, try deleting your vkd3d cache for the game

The hotfix worked for me, however I cannot join any friends. If I try to connect to one of my friends parties via a steam invite I always get the messages "You were unable to connect to the fireteam. Please try again later." But if I invite them (and they are a windows user) they can join my party. The same issue occurs for my friend who also uses linux but not my friends who use windows. Linux users can only host a lobby for windows users to join, but linux to linux host cannot connect at all it seems.

Thanks for describing the issue. This should hopefully be fixed now in the just updated Experimental ([bleeding-edge] branch; choose [bleeding-edge] in properties for Proton Experimental tool, BETAS tab and select Proton Experimental as the compatibility tool for the game).

Ive not been able to test it yet, will let people know

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1312343896

Following these instructions fixes the issue for me upon initial load, but after a few seconds it reverts back to the broken textures.

I have noticed there is a issue that has been here even before the winter update where if you are alt tabbed out while you're in the countdown and if it counts down to one your game instantly freezes and crashes and this such a problem due to the longer then usual queue compared to other games where while playing ranked I have been banned 3 times because of this issue !

This should be fixed in the just updated Experimental [bleeding-edge].

I have noticed there is a issue that has been here even before the winter update where if you are alt tabbed out while you're in the countdown and if it counts down to one your game instantly freezes and crashes and this such a problem due to the longer then usual queue compared to other games where while playing ranked I have been banned 3 times because of this issue !

This should be fixed in the just updated Experimental [bleeding-edge].

you are on a roll, nice job

Replying to [#5030 (comment)](https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1312248277)

Use mesa-git, you are getting the dreaded LOD issues we used to get back when mesa 22.2 was about to get released

Since you weren't having the issue before, try deleting your vkd3d cache for the game

Unfortunately installing mesa-git (23.0.0_devel.162811.e63d6ed85e0.d41d8cd98f00b204e9800998ecf8427e-1) and deleting the vk3d cache did not fix it for me. The same issues persist.

Replying to [#5030 (comment)](https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1312248277)

Use mesa-git, you are getting the dreaded LOD issues we used to get back when mesa 22.2 was about to get released
Since you weren't having the issue before, try deleting your vkd3d cache for the game

Unfortunately installing mesa-git (23.0.0_devel.162811.e63d6ed85e0.d41d8cd98f00b204e9800998ecf8427e-1) and deleting the vk3d cache did not fix it for me. The same issues persist.

not sure what it could be, I am not experiencing any LOD issues on AMD

Game is "working" over here for me on Proton Experimental (bleeding edge, I think?).

A few issues I notice are that it needs me to sign in too xbox live every time I start it up, and it shows me as offline.

It is also working for me not jav

Game is "working" over here for me on Proton Experimental (bleeding edge, I think?).

A few issues I notice are that it needs me to sign in too xbox live every time I start it up, and it shows me as offline.

It is also working for me on proton experimental (bleeding edge) Xbox live is working fine and it is not showing offline. Still bad fps on my rtx 2060 :(

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1309380017

Oof, seeing this on a 1080Ti now with Proton-GE-7-41. I've tried restarting, disabling compatibility, setting it to Experimental, and 7.0.4; same thing. Any tips?

So I'm playing Halo infinite using proton hot fix. It seems to work fine until I get into a match. I'm in the match for maybe a minute and then it freezes but I can still hear the audio as if the game was running. But I can't do anything. I can't tab out steam is unresponsive nothing works. I either have to reset the PC or after a while of waiting it will turn off itself.

I have a ryzen 5 and a 6700 Radeon GPU. I am using Nobara Linux. Has anyone else encountered this problem? Is there a fix?

Replying to [#5030 (comment)](https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1309380017)

Oof, seeing this on a 1080Ti now with Proton-GE-7-41. I've tried restarting, disabling compatibility, setting it to Experimental, and 7.0.4; same thing. Any tips?

Same issue here, think it started happening last night.

So I'm playing Halo infinite using proton hot fix. It seems to work fine until I get into a match. I'm in the match for maybe a minute and then it freezes but I can still hear the audio as if the game was running. But I can't do anything. I can't tab out steam is unresponsive nothing works. I either have to reset the PC or after a while of waiting it will turn off itself.

I have a ryzen 5 and a 6700 Radeon GPU. I am using Nobara Linux. Has anyone else encountered this problem? Is there a fix?

Same issue here. I also have an RX 6700, however, this also occurs with my 5700 XT, 6600 XT, and 6650 XT using many different distros and hardware configs.

Seems that the GPU is being reset, and I've seen some others mention this happening on Nvidia GPUs as well so I have no idea what is causing the problem.

Replying to [#5030 (comment)](https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1309380017)

Oof, seeing this on a 1080Ti now with Proton-GE-7-41. I've tried restarting, disabling compatibility, setting it to Experimental, and 7.0.4; same thing. Any tips?

Same issue here, think it started happening last night.

Proton-GE 41 does not have the fix for this, you'll have to use proton HotFix or switch Proton Experimental to the beta (bleeding-edge) branch.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1314388560

Forgot to mention this issue is also happening on proton bleeding edge. I'm on a ryzen nvidia build btw too.

Anyone have any ideas for joining custom games, alot of people are running them lately and being a linux user cuts off most of the paths due to discord not being able to read proton infinite

Anyone have any ideas for joining custom games, alot of people are running them lately and being a linux user cuts off most of the paths due to discord not being able to read proton infinite

You can use an IPC bridge to get it working, maybe it could also be implemented in Proton itself at some point: https://github.com/0e4ef622/wine-discord-ipc-bridge

Anyone have any ideas for joining custom games, alot of people are running them lately and being a linux user cuts off most of the paths due to discord not being able to read proton infinite

You can use an IPC bridge to get it working, maybe it could also be implemented in Proton itself at some point: https://github.com/0e4ef622/wine-discord-ipc-bridge

Attempting to make it work, however at the moment It does not, I can only speculate as to why, Anyone else get this to work with infinite? Could be my own stupidity

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1314736820

Hm, there was one other project I can't name at the moment, but I know that it installed inside of the Wine prefix and would start whenever the prefix does. If I can figure out that name, I'll send it over.

Replying to [#5030 (comment)](https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1314736820)

Hm, there was one other project I can't name at the moment, but I know that it installed inside of the Wine prefix and would start whenever the prefix does. If I can figure out that name, I'll send it over.

something along the lines of 'rpc-wine', found that and it also did not work, would love if anyone else could try because my level of skill with linux is only as high as minor understanding and dumb luck

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1316403105

Are you using the native package of Discord and Steam (using a package manager like pacman, apt, or dnf, not flatpak)? The flatpak of both should work with a tweak.

I just discovered something else as well, now it could be because I am actually running both versions of this, but the game does consistently crash within 2 minutes upon boot when running this discord setup as a command. I am using the downloaded debian for discord and steam, should I be using something else?

Native packages of both should work OOTB with that script, I don't know why it doesn't work. Do you have any logs?

Native packages of both should work OOTB with that script, I don't know why it doesn't work. Do you have any logs?

I will try to find where (if possible) the logs could be. I figured it should work as well, and maybe I am just doing something wrong but I made sure to follow the instructions carefully. when I try to test it, it always says halo infinite is not detected when trying to join people

Halo Infinite is still broken for me (doesn't launch), with a 19MB log. Here's a sample of it on Gist, can upload the full file somewhere if needed, but everything is just repeating what's at the end of the file: https://gist.github.com/orowith2os/dd35a158b52035648107f41a4d9610df

Could it be that I'm running Infinite inside of a podman container? I'm not entirely sure.

Halo Infinite is still broken for me (doesn't launch), with a 19MB log. Here's a sample of it on Gist, can upload the full file somewhere if needed, but everything is just repeating what's at the end of the file: gist.github.com/orowith2os/dd35a158b52035648107f41a4d9610df

Could it be that I'm running Infinite inside of a podman container? I'm not entirely sure.

I remember running halo infinite inside a distrobox (podman) container and it worked fine (it got to the loading screen, but the inputs didn't work), all I needed was mesa 22.2

@Etaash-mathamsetty I'm on an Arch-based container (using Arch repos), with Mesa 22.2.3. What was your container like? I can try to reproduce it over here and see if I have better results.

@Etaash-mathamsetty I'm on an Arch-based container (using Arch repos), with Mesa 22.2.3. What was your container like? I can try to reproduce it over here and see if I have better results.

I used a fedora 36 container with whatever mesa-git was at the time (some time right before the release of 22.2)

Alright, made a Fedora 37 container and set up Steam and whatnot. Turns out Halo Infinite still breaks, this time with a 100MB log.

I resorted to google drive and uploaded my latest log file. https://drive.google.com/file/d/1bY7VwOTPunytnvAzd_a_Qdc3tq9gMTJs/view?usp=sharing

Apologies, cannot find logs and frankly have no clue as to why It will not work. Ill shelve this until someone else is also able to test it

Replying to [#5030 (comment)](https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1316403105)

Are you using the native package of Discord and Steam (using a package manager like pacman, apt, or dnf, not flatpak)? The flatpak of both should work with a tweak.

Halo Infinite is still broken for me (doesn't launch), with a 19MB log. Here's a sample of it on Gist, can upload the full file somewhere if needed, but everything is just repeating what's at the end of the file: https://gist.github.com/orowith2os/dd35a158b52035648107f41a4d9610df

Could it be that I'm running Infinite inside of a podman container? I'm not entirely sure.

Is it crashing on the first "Xbox" splash screen, or not launching at all?

@NjlsShade right when it plays through a bit of the xbox logo in most cases.

@NjlsShade right when it plays through a bit of the xbox logo in most cases.

This might just be my experience with it, but I run a HDD and an NVME, infinite is on the NVME for speed with loading (not that it does shit with this games UI) and when I run steam and then halo with my HDD mounted, I believe steam tries to use the compatdata from the HDD and it always crashes consistently, I have tried many things to fix this but I end up just running it without my HDD mounted and it works just fine. Even switching the game over to my HDD does not fix it, cant know what causes this but there it is, are you running this in a similar way?

It also crashes for me after the Xbox logo on Arch running in Flatpak with Steam and flatpak-beta with proton-hotfix. If I clear the compatdata it lasts longer but eventually crashes again. Could it compiling shaders and when it reaches one it causes a crash?

It also crashes for me after the Xbox logo on Arch running in Flatpak with Steam and flatpak-beta with proton-hotfix. If I clear the compatdata it lasts longer but eventually crashes again. Could it compiling shaders and when it reaches one it causes a crash?

you need mesa 22.2, flatpak has 22.1

It also crashes for me after the Xbox logo on Arch running in Flatpak with Steam and flatpak-beta with proton-hotfix. If I clear the compatdata it lasts longer but eventually crashes again. Could it compiling shaders and when it reaches one it causes a crash?

you need mesa 22.2, flatpak has 22.1

Even if I am using Steam from flatpak-beta and runtime/org.freedesktop.Platform.GL.default/x86_64/22.08beta/?

It also crashes for me after the Xbox logo on Arch running in Flatpak with Steam and flatpak-beta with proton-hotfix. If I clear the compatdata it lasts longer but eventually crashes again. Could it compiling shaders and when it reaches one it causes a crash?

Are you crashing on the Xbox logo (while the first slash screen is playing), or right before the main menu would load? As these both indicate seporent issues.

My apologies. I think @Etaash-mathamsetty was right. Despite me installing mesa 22.2 from flatpak-beta, Steam from flatpak-beta is still showing Driver Version: 4.6 (Compatibility Profile) Mesa 22.1.7 (git-7a3414c4bd). I'll have to figure out how to force it to use Mesa 22.2.

My apologies. I think @Etaash-mathamsetty was right. Despite me installing mesa 22.2 from flatpak-beta, Steam from flatpak-beta is still showing Driver Version: 4.6 (Compatibility Profile) Mesa 22.1.7 (git-7a3414c4bd). I'll have to figure out how to force it to use Mesa 22.2.

Install the mesa-git flatpak runtime extension and follow the Steam flatpak wiki pages to use it.

Is this the wiki you are referring to @orowith2os?

I first installed 23.08beta but wasn't launching flatpak Steam with FLATPAK_GL_DRIVERS. Trying that, Steam says it is on Meas 23.0. However Halo Infinite crashes immediately without even the Microsoft screen.

The wiki says to use 21.08 but when I try 21.08, 21.08beta, 22.08, 22.08beta, Steam doesn't launch at all. It says glXChooseVisual failed.

@wallzero that is indeed the wiki page I'm talking about, and the error you got is related to drivers not working, I think. Reboot and see if it works, maybe your kernel needs an update? What version are you on (uname -r)?

I am on kernel 6.0.8-arch1-1

It seems neither Steam from flathub nor flathub-beta can use runtime 21.08 which I thought has mesa 22.2. If you try the following Steam isn't listed: flatpak list --system --app --app-runtime=org.freedesktop.Platform//21.08

However Steam is listed with 22.08. I removed all mesa installations again and ran flatpak install --system flathub-beta org.freedesktop.Platform.GL.mesa-git//22.08 org.freedesktop.Platform.GL32.mesa-git//22.08. Then, after running Steam successfully with FLATPAK_GL_DRIVERS=mesa-git flatpak run com.valvesoftware.Steam, it shows it is using Mesa 23.0.0-devel (git-6addb8566d).

Halo Infinite crashes immediately and I suspect it's now because of Mesa 23.0. I'm not sure how to get Steam Flatpak to use an older runtime.

AFAIK using an older runtime actually won't work at all, as any Mesa version below 22 can't run VKD3D n newer DXVKs. 21.08 ships with Mesa 21, 22.08 with 22.

Nevermind. Known Issue.

Now is working!, proton experimental bleeding edge

OS: Arch Linux
KERNEL: 6.0.9-arch1-1
CPU: AMD Ryzen 7 5800X 8-Core
GPU: NVIDIA GeForce RTX 3070
GPU DRIVER: NVIDIA 520.56.06
RAM: 32 GB

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1320804384

What is working exactly?

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1320805908

Halo infinite multiplayer...

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1320805973

Oh, were you having the dll issue?

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1320804384

What is this? warn:d3d12_command_list_execute_indirect_state_template: Template requires patching

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1320806211

I don't know, I just know that the game crashed when trying to load a multiplayer game

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1317126194 (topic was Discord RPC)

I found the program I was talking about in my bookmarks, @ZAGON117. https://github.com/openglfreak/winestreamproxy

Replying to [#5030 (comment)](https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1317126194) (topic was Discord RPC)

I found the program I was talking about in my bookmarks, @ZAGON117. https://github.com/openglfreak/winestreamproxy

Thanks mate, I will check this out and see if it works

This is for anyone looking to get into custom games,

What I do, is in mint blitz server for example, friend someone in the game, make sure the game lobby is in friends mode, and then join via my friends within infinities UI. I looked for a good long while for ways to make discord work but alas this is the only way, at least this works

While playing the single player campaign on Steam Deck, I've noticed that the opening cutscene plays in a different language than my selected language (English) and that randomly sized and shaped black artifacts appear from both the Pilot's head and Escharum's head whenever these characters are on screen.

These issues are occurring for me in both proton hotfix and proton experimental and have not occurred in any other game I've tried. I've tried deleting the game's prefix, shader cache, and reinstalling the game, but the issue seems to occur regardless. My system's information is available here.

Hello @Mophead2K, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

they are using a steam deck, I don't think it's nessessary ?

I just tried to run the game again and took a closer look at the logs, it seems to fail with a "Bad file descriptor" error.

I've tried both on the latest Mesa provided by Arch and Mesa-git.

Renaming the videos folder lets me get to the main menu.

The game also tells me I'm offline:

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1327975136

can't reproduce any of that, renaming the videos folder is only required on "old" proton versions, I feel like your system is missing some dependency or something (im on arch too!)

Replyig to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1327977131

If you can toss together a list of everything I should install, I can try that.

I'm also running on the bleeding edge Proton Experimental.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1327977131

I believe they are running in a podman container if this is regarding the same issue they were having before.

@orowith2os bypassing the videos fixed the crashing issue in distrobox, or is this not related to the container issue you were having before?

I don't believe running in a container is related whatsoever, and I am running Steam inside of an Arch-based (Crystal Linux) container.

And yes, skipping the videos by renaming the folder fixed the crashing.

I don't believe running in a container is related whatsoever, and I am running Steam inside of an Arch-based (Crystal Linux) container.

And yes, skipping the videos by renaming the folder fixed the crashing.

I am able to replicate your issue using a fedora 37 container via distrobox. Problem does not occur if I use flatpak or native Steam.

@NjlsShade Interesting. I wonder what it's doing that screws up the networking? I'll go into a toolbox and see if that changes anything.

Okay, Toolbox didn't change anything. I'll get the Steam flatpak installed and see if it's working over there. If not, it might be an issue with my network configuration.

Okay, Toolbox didn't change anything. I'll get the Steam flatpak installed and see if it's working over there. If not, it might be an issue with my network configuration.

Would not be a network configuration issue on your end, as I too have the same issue. Flatpak with the mesa-git beta works just fine (outside of mesa crashes which are an issue everywhere it seems).

Would you be able to test a rootfull container, too? If that doesn't work, then I think an issue can be made on Podman's issue tracker.

Okay, well, Flatpak seems to work... So I guess that's what I'm gonna use from now on.

psssst, Valve, you should really help with maintaining the flatpak, too

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1312248277

Is anyone still getting these LOD issues now?

I am, and I've tried mesa 22.2 and mesa git 23.0.

i am, if you get it fix give me a hand

game works fine on Low graphics, medium to ultra looks terrible, wont load textures

game works fine on Low graphics, medium to ultra looks terrible, wont load textures

This only seem to happen when shader pre-caching is enabled.

https://github.com/Frogging-Family/wine-tkg-git/actions/runs/3596391144

if you are getting LOD problems, try using this, u wont get video play back but textures and performance is very good.
i have been getting some strange crashes so i use xanmod kernel or Linux-lqx kernel, may help also.

https://github.com/Frogging-Family/wine-tkg-git/actions/runs/3596391144

if you are getting LOD problems, try using this, u wont get video play back but textures and performance is very good. i have been getting some strange crashes so i use xanmod kernel or Linux-lqx kernel, may help also.

Thanks. This proton version seems to fix the blurry trees and textures in the main menu.

However now my PC hard freezes when the game loads any map.

Hi. I can't get the game to work. With Proton Experimental and Proton-GE, mouse cursor style changes to Halo and CPU fan blows constantly, but there's no display output whatsoever. Using Proton hotfix, the game launches but has some weird issue. If I get into the game with no internet connection or with a bad connection so it can't get online, it won't crash at all (I can't do anything obviously because I don't own campaign). But, if I get into the game with internet being connected, the game will just crash. It might crash in loading page or main menu so it isn't constant, but it will inevitably crash. Any help would be appreciated.

CPU: Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
Ram : 16GB
iGPU: Intel Mesa Intel(R) UHD Graphics (CML GT2)
dGPU: NVIDIA Corporation NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2
dGPU VRAM: 4GB
dGPU driver: 4.6.0 NVIDIA 525.60.1
OS: "Arch Linux" (64 bit)
Kernel: 6.0.10-arch2-1
Display server: Xorg
Steam version: steam-runtime_0.20221019.0

Steam is installed from Arch repos.
Vulkan is set to use dGPU (iGPU Vulkan drivers aren't even installed).
prime-run, gamemoderun and disabling ESync have no effect.

Currently I can't post the log because it's freaking 64MB! Any way to force Proton to log only useful info?

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1337570137

@iliair, I have a nvidia rtx 3070 and works good on proton experimental bleeding edge, Arch linux, nvidia 525.60.11, so try proton experimental bleeding edge.

Replying to [#5030 (comment)](https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1337570137)

@iliair, I have a nvidia rtx 3070 and works good on proton experimental bleeding edge, Arch linux, nvidia 525.60.11, so try proton experimental bleeding edge.

no changes unfortunately.

This is the output of "cat ~/steam-1240440.log | grep err" with Proton Experimental bleeding-edge:
https://gist.github.com/iliair/1d6ec589c69f38887e875b122edbf5dc

And this one is for Proton Hotfix:
https://gist.github.com/iliair/ddb7ec44aef8a06a7e7f0129688c21a8

For newreaders:
With Experimental, there is no graphical output. just some transparent fullscreen window appears and also my mouse cursor changes to the game-specified one. The game is definitely doing something back there because CPU fan blows like crazy.
With Hotfix, I can't get in game with internet being connected, because it will crash. It is fine in offline mode though. As per the log I provided, I guess it has something to do with NTLM.

https://github.com/Frogging-Family/wine-tkg-git/actions/runs/3596391144
if you are getting LOD problems, try using this, u wont get video play back but textures and performance is very good. i have been getting some strange crashes so i use xanmod kernel or Linux-lqx kernel, may help also.

Thanks. This proton version seems to fix the blurry trees and textures in the main menu.

However now my PC hard freezes when the game loads any map.

use xanmod or linux_lqx Kernel, that fixed it for me

@iliair Can you try VKD3D_DISABLE_EXTENSIONS=VK_KHR_present_id,VK_KHR_present_wait prepended before %command% in launch options with Experimental?

@iliair Can you try VKD3D_DISABLE_EXTENSIONS=VK_KHR_present_id,VK_KHR_present_wait prepended before %command% in launch options with Experimental?

@Saancreed I just did that and the graphics problem with Experimental and Proton-GE is gone, so thanks a lot;
But now I can't test the game for the multiplayer problem because Halo Infinite servers are blocked in my country and for some reason no VPN works today as they impose heavy censorship stuff. I'll keep you informed when I'm able to get it to work. Thanks again.

temp fix for textures not fully loading, go to that folder of which proton you use and delete all the video plugins except
libprotonmediaconverter.so

Folder (/home/xxxxx/.steam/steam/compatibilitytools.d/proton_xxxxxxxx/files/lib64/gstreamer-1.0/)

i believe gstream plugin is stopping it from loading textures which is weird.

@iliair Can you try VKD3D_DISABLE_EXTENSIONS=VK_KHR_present_id,VK_KHR_present_wait prepended before %command% in launch options with Experimental?

@Saancreed So I finally tested the game and unfortunately, nothing changed at all. Both Experimental and Proton-GE crash like Hotfix. In first attempts they just crashed in "Establishing best connection with data centers" loading part, now the main menu loads up but crashes while transitioning from offline to online mode. Logs are pretty the same as the ones I provided earlier. Some errors about OLE, NTLM,LDAP and Kerberos.

So somehow it's working now and I'm impressed because I just did nothing except changing few graphical settings from low to off. It started working and now I switched every option possible to medium except texture quality, and again it is fine! It still freezes occasionally though. Now I have another problem. Some textures flicker and some are just black. Like black walls, black stones or even black lines representing smoky path of a shot rocket.

https://www.youtube.com/watch?v=5eVfrN9ixHg

Check this out, this may be a big problem with halo

Halo Infinite opens and crashes moments after running with an Arc 750 GPU. Here is the log:
steam-1240440.zip

Running with Mesa 22.3.1 - kisak-mesa and kernel 6.0.6-76060006-generic on Pop OS.

Halo Infinite opens and crashes moments after running with an Arc 750 GPU. Here is the log: steam-1240440.zip

Running with Mesa 22.3.1 - kisak-mesa and kernel 6.0.6-76060006-generic on Pop OS.

it might be a driver bug and also do the drivers support VK_NV_device_generated_commands

Apparently not. Video driver issue report: https://gitlab.freedesktop.org/mesa/mesa/-/issues/6883

on older motherboard without resize-able bar we get texture issues, some one told me mesa cant give all gpu vram to videos and thats what causing us to get texture loading issues, cause if i delete video files the texture loads fine or if we shrink the video to 540p the game also works fine but this is what he said to me.

"Regarding enabling the feature
[11:58 AM]
Older boards without reBAR support might still have above 4G decoding
[11:59 AM]
I have that on my Nvidia machine
[11:59 AM]
It doesn't allow for reBAR on Windows, but it's apparently enough for Linux to use it.
Without reBAR, it's 256MB per 256MB, so let's say they are doing an allocation for each video, which would eat 512MB VRAM for nothing
The GPU is left with 7.5GB available instead of 8GB.

It may be halo but when i shrank the videos resolution it worked fine.

Hi there, I'm having a really weird audio issue that I haven't seen posted anywhere. It seems that sound effects only play if I'm looking directly at the source of the sound, but I CAN hear the reverb from the sound effect. For example if I'm getting shot from behind, I can hear my spartan go "oof" as well as the echo/reverb of the weapon (very quietly) but I can't actually hear the weapon being fired unless I turn around and look at the spartan shooting me. Another example is in CTF if someone takes either flag, I can hear the echo/reverb of the flag taken sounds, but I can't hear the effect itself unless I'm looking directly at the flag. This only seems to happen on my Arch install, my Steamdeck with SteamOS does not have this issue. I'm running Proton Hotfix, and I've validated my game files in Steam. Here is my system info:

CPU: Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz
RAM:  15846 MB
GPU: AMD Radeon RX 6800 (navi21, LLVM 14.0.6, DRM 3.49, 6.1.1-arch1-1)
VRAM: 16384 MB
Driver Version:  4.6 (Compatibility Profile) Mesa 22.3.1
OS: "Arch Linux" (64 bit)
Kernel: 6.1.1-arch1-1
Display server: Xorg
Steam version: steam-runtime_0.20221019.0

Here is all the errors in the log file, I poured over it but I couldn't find anything that would cause this, other than a lot of:
err:seh:dispatch_exception unknown exception (code=c0000420) raised
https://gist.github.com/glyndwr-io/b533da7bb92682a1499e29a64d620c66

If anyone has any wisdom that would be much appreciated as I'm not sure what to do next.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1368316401

perhaps try pipewire, pulseaudio has some wierd quirks that make it not so good for gaming (or if you are using pipewire try pulse?)

perhaps try pipewire, pulseaudio has some wierd quirks that make it not so good for gaming (or if you are using pipewire try pulse?)

Perfect! That was the problem. I had both pipewire and pulseaudio installed, but I didn't have pipewire-pulse installed to replace pulseaudio. Installed pipewire-pulse (which removed pulseaudio) and now it works perfectly.

Is it still the same LOD issue if the textures/geometry do eventually load, but they take forever to do so? It's noticably slower than in Windows. One example is the crates in the background of the multiplayer menu. Sometimes textures don't even load in until after a match or two.

Is it still the same LOD issue if the textures/geometry do eventually load, but they take forever to do so? It's noticably slower than in Windows. One example is the crates in the background of the multiplayer menu. Sometimes textures don't even load in until after a match or two.

delete or rename or video folder and your textures will load

delete or rename or video folder and your textures will load

My textures do load though, they just take a significantly longer period of time to do so. In the kill cams, my teamamtes that are far away from me have really bad pop-in. Sometimes they load before I respawn sometimes they don't. Once they do load, if they go far enough away from me the same thing happenes again. It's really bad when I pick up a gun that hasn't been in range for a while. I'm thinking this might be a separate issue because I tried deleting the video folder and that didn't change anything.

https://www.youtube.com/watch?v=5eVfrN9ixHg

Check this out, this may be a big problem with halo

In the main menu, my trees are somewhere between the examples at 2:08 where they don't load at all and 3:28 where they load instantly. Mine can take up to 30sec to load in. This doesn't happen in windows, and it's hard to tell if it happens on my steamdeck since everything is turn down so low to hold 60fps, but I don't think it does.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1371483319

what version of linux do you use, cause on nobara and arch, removing the video files solved my problem, wit nvidia gpu it works just performances is bad, tell me your driver version and os, and if u have an updated pc enable resizeable bar or smart access memory

@kisak-valve
Thank you for the insight. Will check this out. I do have a question: Would not the drivers be corrected when you start Proton for first time? meaning then the Windows files are created?

Maybe it is related to what @massatt212 mentioned.
In December there was a big update from Halo infinite, it might have happened that the video folder was restored after the update. (previously deleted). And I did not erased it again, I did reinstall the game so the folder will still be there.

Will check this out and let you know if I find more information

what version of linux do you use, cause on nobara and arch, removing the video files solved my problem, wit nvidia gpu it works just performances is bad, tell me your driver version and os, and if u have an updated pc enable resizeable bar or smart access memory

In my comment you replied to, I mentioned that I deleted the videos folder and nothing changed. My system details can be found above, but I'm on arch 6.1.4 now. Right now I'm trying to debug a different issue with amdgpu voltage controls so I've been trying out a ton of different kernel versions and this issue seems to be present on all of them. I've tried with Resizable BAR and Above 4G decoding both on, just 4G on, and both off and the issue persists. I'm not super concerned about it as the textures do load, they just take longer than in Windows. The voltage control issue means I can't play stable for more that 30mins so that's my priority right now. I'm going to try a different SSD next, but I'm doubtful this will solve it. My windows install that played Halo Infinite used to live on this drive and didn't have this issue. Besides, I'm pretty sure the textures are loaded into memory once the match starts and aren't read from the drive mid-game, but I'm not certain. Either way I'll report back if this solves it.

@kisak-valve
I bring an update, and a workaround. That might be useful?

1. I did erase the folder that proton creates for the game. Meaning:
   home/deck/.local/share/Steam/steamapps/compatdata/1240440
2. Then I started the game with Proton Hotfix and it worked for the whole session, no freeze or crash. And it felt it ran better.
   However today I started to play and crashed several times in the main menu. After 2-3 tries, I managed to start a match but it again froze in the first 5 seconds.
   The Logfiles are from this moment in time.
   steam-1240440_new.zip

Then I re-did the workaround, and it worked again. No issues.
I think yesterday there was an small update for Halo Infinite. And this might have caused the issue?

Not sure if this is helpful to solve the issue, or could be useful for you but this is what I found. Will post if I find the culprit.
Lastly, would you mind to check with your Expertise if there is any useful information? Thanks!

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1379503961

Try Using proton experimental, It's worked perfectly in my experience

@Etaash-mathamsetty As mentioned before, I tried several verisions before and did not help much :| But at least I have a workaround at the moment

@kisak-valve
Update on the situation. It seems that the GPU is restarting. And so far is only happening to me when there is a highlight area. Like King Of the Hill, when the hill changes color it crashes. I have had less crashes in the last days since the last Proton update but it is still an issue (Wont dare to play Ranked atm).

Edit: I tested this theory, in any landgrab game or king of the hill, the game freezes as soon as the hill or area is on the screen. It can exist, as long as you ignore it nothing happens. the moment you look at it, freeze.

There is a Thread online where this issue is common, However this is only happening to me in Halo. I played GOW recently trying to get the error again, so this might not be the hardware error mentioned here:
https://www.reddit.com/r/SteamDeck/comments/z8kmyl/psa_some_potential_hardware_issues_to_look_out/

These are my log files.

So far I have found 5-6 people in Reddit that had this issue. Meaning I am not an isolated case. I am at the moment talking with Valve for an RMA on my SteamDeck. Would be great if the Proton team is checking this.

My game doesn't even start on ARC 770. I am on the most recent stable mesa drivers and proton-ge or proton experimental.

Have you tried proton experimental (bleeding edge)?

Have you tried proton experimental (bleeding edge)?

Yes

@caniko this game can't currently run on Intel GPUs: https://gitlab.freedesktop.org/mesa/mesa/-/issues/6883

@DanielCardiel It looks very similar to this issue I am experiencing with my Radeon 680M (Ryzen 6800U iGPU).

https://gitlab.freedesktop.org/drm/amd/-/issues/2220#note_1701633

I don't experience the issue with gaming though. It happens whenever I use hardware video acceleration in Firefox + Wayland.

My system was working perfect until the most recent Manjaro updates
Basically when i launch the game the screen turns black for like 15 seconds and then just goes back to the desktop

This update was working fine
https://forum.manjaro.org/t/stable-update-2022-12-24-kernels-xfce-systemd-thunderbird-kde-git/129970

This one killed me
https://forum.manjaro.org/t/stable-update-2023-01-24-kernels-plasma-frameworks-gear-libreoffice-mesa-nvidia-deepin/132381

This one hasnt improved it either
https://forum.manjaro.org/t/stable-update-2023-02-03-kernels-phosh-firefox-thunderbird-systemd-mate-budgie-kodi/133238

(I just updated and here is the latest stuff that still doesnt work)
OS: Manjaro Linux
KERNEL: 6.1.9-1-MANJARO
CPU: AMD Ryzen 7 5800X 8-Core
GPU: AMD Radeon RX 6700 XT (navi22, LLVM 15.0.7, DRM 3.49, 6.1.9-1-MANJARO)
GPU DRIVER: 4.6 Mesa 22.3.4
RAM: 16 GB
PROTON: Proton: 1675282930 experimental-7.0-20230201
SteamGameId: 1240440

steam-1240440.tar.gz

[  265.984729] [drm:gfx_v10_0_priv_reg_irq [amdgpu]] *ERROR* Illegal register access in command stream
[  265.994707] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=343347, emitted seq=343349
[  265.995087] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process HaloInfinite.ex pid 6191 thread 00 MAIN pid 6201

Same issue here with the GPU resetting. My system freezes entirely and I have to switch TTY to kill my display manager to get back in.

Not sure why this happens, 2 days ago I was playing several matches without any crashes. I saw someone mentioned King of The Hill, and that gamemode reset my GPU so maybe it's linked?

It also happens with land grab, as soon as the area is on display the game crashes. you are the 4 person i found it happens the same thing as me. I ended up ins taling windows on an ad card and i am playing like that in the meantime this ia fixed.@VladTheSheep

@kisak-valve
@DanielCardiel
@VladTheSheep

I have a second system with the same motherboard but a different videocard

The AMD Radeon RX 6700 XT fails but the AMD Radeon RX 5700 X works

What videocards are you guys using?

Im thinking of nuking my system and reinstalling it and seeing if that fixes it since the only significant difference between the 2 systems seems to be the video card but they are both AMD

THIS ONE WORKS

OS: Manjaro Linux
KERNEL: 6.1.9-1-MANJARO
CPU: AMD Ryzen 7 3800X 8-Core Processor
GPU: AMD AMD Radeon RX 5700 XT (navi10, LLVM 15.0.7, DRM 3.49, 6.1.9-1-MANJARO)
GPU DRIVER: 4.6 (Compatibility Profile) Mesa 22.3.4
RAM: 16 GB
MOTHERBOARD: Gigabyte X570 AORUS ELITE (rev. 1.0)

THIS ONE DOESNT WORK

OS: Manjaro Linux
KERNEL: 6.1.9-1-MANJARO
CPU: AMD Ryzen 7 5800X 8-Core
GPU: AMD Radeon RX 6700 XT (navi22, LLVM 15.0.7, DRM 3.49, 6.1.9-1-MANJARO)
GPU DRIVER: 4.6 Mesa 22.3.4
RAM: 16 GB
MOTHERBOARD: Gigabyte X570 AORUS ELITE (rev. 1.0)
PROTON: Proton: 1675282930 experimental-7.0-20230201
SteamGameId: 1240440

@Cytomax55

RX 6800 XT
Using open source drivers

Looks like the issue is with the RX6800XT... i wonder what @DanielCardiel is using....
@VladTheSheep you dont by any chance have any spare videocards you can try that arent RX6800xt?

If the problem is 6800XT based ... should we be talking to MESA maybe or is this a Proton issue?
I play other games without issues

Looks like the issue is with the RX6800XT... i wonder what @DanielCardiel is using....
@VladTheSheep you dont by any chance have any spare videocards you can try that arent RX6800xt?

If the problem is 6800XT based ... should we be talking to MESA maybe or is this a Proton issue?
I play other games without issues

Got no spare unfortunately :( You had issues with the 6700XT too? Likely an issue with the 6000 series?

yup thats why i am hoping that @DanielCardiel also has a 6700xt or at least a 6000 series that would help narrow down the problem

yup thats why i am hoping that @DanielCardiel also has a 6700xt or at least a 6000 series that would help narrow down the problem

I have both a 6700 XT and a 6900 XT. What is it we are checking for?

For sure the 6700xt isn't working .. but it IS working with the 5700xt...
I'm thinking the 6700 or at least the 6000 series is having issues if you could try a 6700 first and confirm that the game won't work then you can try the 6900 and see what happens

For sure the 6700xt isn't working .. but it IS working with the 5700xt...
I'm thinking the 6700 or at least the 6000 series is having issues if you could try a 6700 first and confirm that the game won't work then you can try the 6900 and see what happens

Do I have to play the game for awhile to run into the issue or does it happen right away?

In my case the game doesn't even load at all

when you click the game to start the screen turns black and in about 5 seconds it crashes to desktop

Apparently Manjaro ships mesa vulkan drivers with debug symbols and that can cause crashes in some cases, maybe try using stock arch Linux or flatpak
(Yet another reason not to use Manjaro?)

Apparently Manjaro ships mesa vulkan drivers with debug symbols and that can cause crashes in some cases, maybe try using stock arch Linux or flatpak (Yet another reason not to use Manjaro?)

I use arch and have the same issue

 ~ uname -r
6.1.9-arch1-1
 ~ yay -Q | grep vulkan
lib32-vulkan-icd-loader 1.3.240-1
lib32-vulkan-mesa-layers 22.3.4-1
lib32-vulkan-radeon 22.3.4-1
vulkan-headers 1:1.3.240-1
vulkan-icd-loader 1.3.240-1
vulkan-mesa-layers 22.3.4-1
vulkan-radeon 22.3.4-1
vulkan-tools 1.3.240-1
 ~ yay -Q | grep amd
hsa-amd-aqlprofile-bin 5.4.1-1
xf86-video-amdgpu 22.0.0-1
 ~ yay -Q | grep mesa
lib32-libva-mesa-driver 22.3.4-1
lib32-mesa 22.3.4-1
lib32-mesa-vdpau 22.3.4-1
lib32-vulkan-mesa-layers 22.3.4-1
libva-mesa-driver 22.3.4-1
mesa 22.3.4-1
mesa-demos 8.5.0-2
mesa-utils 8.5.0-2
mesa-vdpau 22.3.4-1
vulkan-mesa-layers 22.3.4-1

Apparently Manjaro ships mesa vulkan drivers with debug symbols and that can cause crashes in some cases, maybe try using stock arch Linux or flatpak (Yet another reason not to use Manjaro?)

It works perfectly with Manjaro and same motherboard and a 5700xt...
It crashes with a 6700xt

Make sure you are using proton experimental and make sure resizeable bar or above 4g encoding is enabled in the bios

Last time I played this game (2 weeks ago) it worked perfectly, one of the best working games on my system in fact

@Etaash-mathamsetty
I have two computers with the same motherboard and the only difference is the video card
One has a 6700 XT
The other has a 5700 XT

Both were working perfectly up until the second to last update of Manjaro which I documented in my prior post

I am using proton experimental the latest version

The Manjaro with the 5700 XT is still working perfectly I think the 6700 XT or maybe even the six series AMD cards are having issues

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1418292322

That's why I'm surprised, I have a rx 6800 over here

@Etaash-mathamsetty
Which version of mesa are you running and which OS are you running

@Etaash-mathamsetty Which version of mesa are you running and which OS are you running

it's still working over here, proton exp bleeding edge, mesa 23.1 git, arch linux, rx 6800
resizable bar is ON

I just enabled Above 4G Decoding and still crashes at loading screen
The only other difference i am noting is you are running mesa-git ... i am simply running mesa... im gonna try mesa-git and hope it doesnt destroy my computer since it comes from arch repos and not manjaro.. wish me luck.

i dont know if its a big deal or not but do you think you could run normal mesa and see if you have issues...

HOLY DOG POO IT WORKED....

mesa-git fixed my problems

This must be a mesa bug!

How do I report this?

HOLY DOG POO IT WORKED....

mesa-git fixed my problems

This must be a mesa bug!

How do I report this?

make an issue on gitlab (then they will tell you what to do), but it's most likely that you were missing mesa-vulkan-layers or something

@Etaash-mathamsetty @Cytomax55 : Afaik there was indeed a bug in mesa which caused issues in Halo when you try to get into the maps, this was fixed rather recently. What i still have here is that the game hangs from time to time (gpu hang). This is a longstanding issue for me. I am using a 6900XT.

@Etaash-mathamsetty @Cytomax55 : Afaik there was indeed a bug in mesa which caused issues in Halo when you try to get into the maps, this was fixed rather recently. What i still have here is that the game hangs from time to time (gpu hang). This is a longstanding issue for me. I am using a 6900XT.

Can you try to use the Flatpak version of Steam and let me know if the issue occurs? I was troubleshooting this a few months ago, however, I have not been able to reproduce it on my current system using Flatpak and would like to rule out it being a coincidence on my end.

Also, if you could let me know what distro you are using and the system's kernel + mesa version?

@cytomax55
I am actually playing on a steam deck, will check later this, just not sure how to do it on the Steam Deck

@Cytomax55
@pingubot

mesa-git fixed it for me as well! Though now I'm having issues with blurry textures and random, sudden freezes that clears up after about 15-30 seconds.

@kisak-valve
Seems that the issue has been found and a solution, would you mind to help us report it?

@VladTheSheep
I can play a few games without any stutter and then I'll play another game where it literally freezes for about 20 seconds but I can hear the audio perfectly fine

@Cytomax55 @pingubot

mesa-git fixed it for me as well! Though now I'm having issues with blurry textures and random, sudden freezes that clears up after about 15-30 seconds.

turn resizable bar on

@VladTheSheep I can play a few games without any stutter and then I'll play another game where it literally freezes for about 20 seconds but I can hear the audio perfectly fine

do you get any dmesg entries from amdgpu at that time hinting to a gpu hang ? And does it recover after those 20 secs ?

@Etaash-mathamsetty I turned 4G and resizable bar on yesterday when you told me about that a mesa-git, i have not tried with it off

@pingubot I dont know where to look for dmesg, it does recover after the 20 seconds

@Etaash-mathamsetty I turned 4G and resizable bar on yesterday when you told me about that a mesa-git, i have not tried with it off

@pingubot I dont know where to look for dmesg, it does recover after the 20 seconds

ok, interesting, for me it hangs and i have to reboot. I also play with rebar on. You open a terminal and use the command "dmesg -T" and it will show you kernel messages. Check if there is something with amdgpu at the time you saw the 20 second hang.

looks like dmesg erases after a reboot so i have nothing to offer you
ill play tonight and post my stuff here

[Mon Feb  6 13:07:11 2023] RAMDISK: [mem 0x36df3000-0x376f0fff]
[Mon Feb  6 13:07:11 2023] ACPI: SSDT 0x00000000BC63A000 008CE9 (v02 AMD    AmdTable 00000002 MSFT 04000000)
[Mon Feb  6 13:07:11 2023] ACPI: SSDT 0x00000000BC636000 003D74 (v01 AMD    AMD AOD  00000001 INTL 20190509)
[Mon Feb  6 13:07:11 2023] ACPI: SSDT 0x00000000BC629000 000024 (v01 AMD    BIXBY    00001000 INTL 20190509)
[Mon Feb  6 13:07:11 2023] ACPI: IVRS 0x00000000BC628000 0000D0 (v02 AMD    AmdTable 00000001 AMD  00000001)
[Mon Feb  6 13:07:11 2023] ACPI: VFCT 0x00000000BC61C000 00AA84 (v01 ALASKA A M I    00000001 AMD  31504F47)
[Mon Feb  6 13:07:11 2023] ACPI: PCCT 0x00000000BC619000 00006E (v02 AMD    AmdTable 00000001 AMD  00000001)
[Mon Feb  6 13:07:11 2023] ACPI: SSDT 0x00000000BC614000 004043 (v02 AMD    AmdTable 00000001 AMD  00000001)
[Mon Feb  6 13:07:11 2023] ACPI: CRAT 0x00000000BC613000 000F10 (v01 AMD    AmdTable 00000001 AMD  00000001)
[Mon Feb  6 13:07:11 2023] ACPI: CDIT 0x00000000BC612000 000029 (v01 AMD    AmdTable 00000001 AMD  00000001)
[Mon Feb  6 13:07:11 2023] ACPI: SSDT 0x00000000BC611000 00068E (v01 AMD    QOGIRDGP 00000001 INTL 20190509)
[Mon Feb  6 13:07:11 2023] ACPI: SSDT 0x00000000BC60F000 00150D (v01 AMD    QOGIRTPX 00000001 INTL 20190509)
[Mon Feb  6 13:07:11 2023] ACPI: SSDT 0x00000000BC60E000 000788 (v01 AMD    QOGIRNOI 00000001 INTL 20190509)
[Mon Feb  6 13:07:11 2023] ACPI: SSDT 0x00000000BC60A000 0039F7 (v01 AMD    QOGIRN   00000001 INTL 20190509)
[Mon Feb  6 13:07:11 2023] ACPI: SSDT 0x00000000BC606000 00147F (v01 AMD    QOGIRC   00000001 INTL 20190509)
[Mon Feb  6 13:07:11 2023] AMD-Vi: Using global IVHD EFR:0x0, EFR2:0x0
[Mon Feb  6 13:07:11 2023] smpboot: CPU0: AMD Ryzen 7 5800X 8-Core Processor (family: 0x19, model: 0x21, stepping: 0x0)
[Mon Feb  6 13:07:11 2023] Performance Events: Fam17h+ core perfctr, AMD PMU driver.
[Mon Feb  6 13:07:11 2023] pci 0000:00:00.2: AMD-Vi: IOMMU performance counters supported
[Mon Feb  6 13:07:11 2023] pci 0000:00:00.2: AMD-Vi: Found IOMMU cap 0x40
[Mon Feb  6 13:07:11 2023] AMD-Vi: Extended features (0x58f77ef22294a5a, 0x0): PPR NX GT IA PC GA_vAPIC
[Mon Feb  6 13:07:11 2023] AMD-Vi: Interrupt remapping enabled
[Mon Feb  6 13:07:11 2023] perf: AMD IBS detected (0x000003ff)
[Mon Feb  6 13:07:11 2023] perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank).
[Mon Feb  6 13:07:13 2023] AMD-Vi: AMD IOMMUv2 loaded and initialized

[Mon Feb  6 13:07:12 2023] perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank).
[Mon Feb  6 13:07:18 2023] [drm] amdgpu kernel modesetting enabled.
[Mon Feb  6 13:07:18 2023] amdgpu: Ignoring ACPI CRAT on non-APU system
[Mon Feb  6 13:07:18 2023] amdgpu: Virtual CRAT table created for CPU
[Mon Feb  6 13:07:18 2023] amdgpu: Topology: Add CPU node
[Mon Feb  6 13:07:18 2023] amdgpu 0000:0b:00.0: enabling device (0006 -> 0007)
[Mon Feb  6 13:07:18 2023] amdgpu 0000:0b:00.0: amdgpu: Fetched VBIOS from VFCT
[Mon Feb  6 13:07:18 2023] amdgpu: ATOM BIOS: 113-D5121000_100
[Mon Feb  6 13:07:18 2023] amdgpu 0000:0b:00.0: vgaarb: deactivate vga console
[Mon Feb  6 13:07:18 2023] amdgpu 0000:0b:00.0: amdgpu: Trusted Memory Zone (TMZ) feature disabled as experimental (default)
[Mon Feb  6 13:07:18 2023] amdgpu 0000:0b:00.0: amdgpu: VRAM: 12272M 0x0000008000000000 - 0x00000082FEFFFFFF (12272M used)
[Mon Feb  6 13:07:18 2023] amdgpu 0000:0b:00.0: amdgpu: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF
[Mon Feb  6 13:07:18 2023] amdgpu 0000:0b:00.0: amdgpu: AGP: 267894784M 0x0000008400000000 - 0x0000FFFFFFFFFFFF
[Mon Feb  6 13:07:18 2023] [drm] amdgpu: 12272M of VRAM memory ready
[Mon Feb  6 13:07:18 2023] [drm] amdgpu: 7958M of GTT memory ready.
[Mon Feb  6 13:07:18 2023] amdgpu 0000:0b:00.0: amdgpu: PSP runtime database doesn't exist
[Mon Feb  6 13:07:18 2023] amdgpu 0000:0b:00.0: amdgpu: PSP runtime database doesn't exist
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: STB initialized to 2048 entries
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: Will use PSP to load VCN firmware
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: RAS: optional ras ta ucode is not available
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: smu driver if version = 0x0000000e, smu fw if version = 0x00000012, smu fw program = 0, version = 0x00413900 (65.57.0)
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: SMU driver if version not matched
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: use vbios provided pptable
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: SMU is initialized successfully!
[Mon Feb  6 13:07:20 2023] snd_hda_intel 0000:0b:00.1: bound 0000:0b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
[Mon Feb  6 13:07:20 2023] kfd kfd: amdgpu: Allocated 3969056 bytes on gart
[Mon Feb  6 13:07:20 2023] amdgpu: sdma_bitmap: ffff
[Mon Feb  6 13:07:20 2023] amdgpu: HMM registered 12272MB device memory
[Mon Feb  6 13:07:20 2023] amdgpu: SRAT table not found
[Mon Feb  6 13:07:20 2023] amdgpu: Virtual CRAT table created for GPU
[Mon Feb  6 13:07:20 2023] amdgpu: Topology: Add dGPU node [0x73df:0x1002]
[Mon Feb  6 13:07:20 2023] kfd kfd: amdgpu: added device 1002:73df
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: SE 2, SH per SE 2, CU per SH 10, active_cu_number 40
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 1
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 1
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 1
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 1
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: amdgpu: Using BACO for runtime pm
[Mon Feb  6 13:07:20 2023] [drm] Initialized amdgpu 3.49.0 20150101 for 0000:0b:00.0 on minor 0
[Mon Feb  6 13:07:20 2023] fbcon: amdgpudrmfb (fb0) is primary device
[Mon Feb  6 13:07:20 2023] amdgpu 0000:0b:00.0: [drm] fb0: amdgpudrmfb frame buffer device
[Mon Feb  6 13:47:32 2023] amdgpu 0000:0b:00.0: amdgpu: free PSP TMR buffer
[Mon Feb  6 13:47:33 2023] amdgpu 0000:0b:00.0: amdgpu: MODE1 reset
[Mon Feb  6 13:47:33 2023] amdgpu 0000:0b:00.0: amdgpu: GPU mode1 reset
[Mon Feb  6 13:47:33 2023] amdgpu 0000:0b:00.0: amdgpu: GPU smu mode1 reset
[Mon Feb  6 13:47:35 2023] amdgpu 0000:0b:00.0: amdgpu: RAS: optional ras ta ucode is not available
[Mon Feb  6 13:47:35 2023] amdgpu 0000:0b:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[Mon Feb  6 13:47:35 2023] amdgpu 0000:0b:00.0: amdgpu: SMU is resuming...
[Mon Feb  6 13:47:35 2023] amdgpu 0000:0b:00.0: amdgpu: smu driver if version = 0x0000000e, smu fw if version = 0x00000012, smu fw program = 0, version = 0x00413900 (65.57.0)
[Mon Feb  6 13:47:35 2023] amdgpu 0000:0b:00.0: amdgpu: SMU driver if version not matched
[Mon Feb  6 13:47:35 2023] amdgpu 0000:0b:00.0: amdgpu: use vbios provided pptable
[Mon Feb  6 13:47:35 2023] amdgpu 0000:0b:00.0: amdgpu: SMU is resumed successfully!
[Mon Feb  6 13:47:35 2023] amdgpu 0000:0b:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[Mon Feb  6 13:47:35 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[Mon Feb  6 13:47:35 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[Mon Feb  6 13:47:35 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[Mon Feb  6 13:47:35 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[Mon Feb  6 13:47:35 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[Mon Feb  6 13:47:35 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[Mon Feb  6 13:47:35 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[Mon Feb  6 13:47:35 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[Mon Feb  6 13:47:35 2023] amdgpu 0000:0b:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
[Mon Feb  6 13:47:35 2023] amdgpu 0000:0b:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[Mon Feb  6 13:47:35 2023] amdgpu 0000:0b:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
[Mon Feb  6 13:47:35 2023] amdgpu 0000:0b:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 1
[Mon Feb  6 13:47:35 2023] amdgpu 0000:0b:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 1
[Mon Feb  6 13:47:35 2023] amdgpu 0000:0b:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 1
[Mon Feb  6 13:47:35 2023] amdgpu 0000:0b:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 1

Well i played 2 matches perfectly...
then when it was giving me the match stats it hard froze
this is all i saw

[Mon Feb  6 21:08:25 2023] [drm] amdgpu kernel modesetting enabled.
[Mon Feb  6 21:08:25 2023] amdgpu: Ignoring ACPI CRAT on non-APU system
[Mon Feb  6 21:08:25 2023] amdgpu: Virtual CRAT table created for CPU
[Mon Feb  6 21:08:25 2023] amdgpu: Topology: Add CPU node
[Mon Feb  6 21:08:25 2023] amdgpu 0000:0b:00.0: enabling device (0006 -> 0007)
[Mon Feb  6 21:08:25 2023] amdgpu 0000:0b:00.0: amdgpu: Fetched VBIOS from VFCT
[Mon Feb  6 21:08:25 2023] amdgpu: ATOM BIOS: 113-D5121000_100
[Mon Feb  6 21:08:25 2023] amdgpu 0000:0b:00.0: vgaarb: deactivate vga console
[Mon Feb  6 21:08:25 2023] amdgpu 0000:0b:00.0: amdgpu: Trusted Memory Zone (TMZ) feature disabled as experimental (default)
[Mon Feb  6 21:08:25 2023] amdgpu 0000:0b:00.0: amdgpu: VRAM: 12272M 0x0000008000000000 - 0x00000082FEFFFFFF (12272M used)
[Mon Feb  6 21:08:25 2023] amdgpu 0000:0b:00.0: amdgpu: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF
[Mon Feb  6 21:08:25 2023] amdgpu 0000:0b:00.0: amdgpu: AGP: 267894784M 0x0000008400000000 - 0x0000FFFFFFFFFFFF
[Mon Feb  6 21:08:25 2023] [drm] amdgpu: 12272M of VRAM memory ready
[Mon Feb  6 21:08:25 2023] [drm] amdgpu: 7958M of GTT memory ready.
[Mon Feb  6 21:08:25 2023] amdgpu 0000:0b:00.0: amdgpu: PSP runtime database doesn't exist
[Mon Feb  6 21:08:25 2023] amdgpu 0000:0b:00.0: amdgpu: PSP runtime database doesn't exist
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: STB initialized to 2048 entries
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: Will use PSP to load VCN firmware
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: RAS: optional ras ta ucode is not available
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: smu driver if version = 0x0000000e, smu fw if version = 0x00000012, smu fw program = 0, version = 0x00413900 (65.57.0)
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: SMU driver if version not matched
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: use vbios provided pptable
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: SMU is initialized successfully!
[Mon Feb  6 21:08:27 2023] snd_hda_intel 0000:0b:00.1: bound 0000:0b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
[Mon Feb  6 21:08:27 2023] kfd kfd: amdgpu: Allocated 3969056 bytes on gart
[Mon Feb  6 21:08:27 2023] amdgpu: sdma_bitmap: ffff
[Mon Feb  6 21:08:27 2023] amdgpu: HMM registered 12272MB device memory
[Mon Feb  6 21:08:27 2023] amdgpu: SRAT table not found
[Mon Feb  6 21:08:27 2023] amdgpu: Virtual CRAT table created for GPU
[Mon Feb  6 21:08:27 2023] amdgpu: Topology: Add dGPU node [0x73df:0x1002]
[Mon Feb  6 21:08:27 2023] kfd kfd: amdgpu: added device 1002:73df
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: SE 2, SH per SE 2, CU per SH 10, active_cu_number 40
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 1
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 1
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 1
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 1
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: amdgpu: Using BACO for runtime pm
[Mon Feb  6 21:08:27 2023] [drm] Initialized amdgpu 3.49.0 20150101 for 0000:0b:00.0 on minor 0
[Mon Feb  6 21:08:27 2023] fbcon: amdgpudrmfb (fb0) is primary device
[Mon Feb  6 21:08:27 2023] amdgpu 0000:0b:00.0: [drm] fb0: amdgpudrmfb frame buffer device

@pingubot
I finally got it
i played like 5 matches of halo and then i got to a new map and a few seconds into it the screen froze but i heard all the audio and then the screen turned black and when it came back on i was at the login screen like the session had restarted

It started at 17:35

[Tue Feb  7 16:29:13 2023] [drm] amdgpu kernel modesetting enabled.
[Tue Feb  7 16:29:13 2023] amdgpu: Ignoring ACPI CRAT on non-APU system
[Tue Feb  7 16:29:13 2023] amdgpu: Virtual CRAT table created for CPU
[Tue Feb  7 16:29:13 2023] amdgpu: Topology: Add CPU node
[Tue Feb  7 16:29:13 2023] amdgpu 0000:0b:00.0: enabling device (0006 -> 0007)
[Tue Feb  7 16:29:13 2023] amdgpu 0000:0b:00.0: amdgpu: Fetched VBIOS from VFCT
[Tue Feb  7 16:29:13 2023] amdgpu: ATOM BIOS: 113-D5121000_100
[Tue Feb  7 16:29:13 2023] amdgpu 0000:0b:00.0: vgaarb: deactivate vga console
[Tue Feb  7 16:29:13 2023] amdgpu 0000:0b:00.0: amdgpu: Trusted Memory Zone (TMZ) feature disabled as experimental (default)
[Tue Feb  7 16:29:13 2023] amdgpu 0000:0b:00.0: amdgpu: VRAM: 12272M 0x0000008000000000 - 0x00000082FEFFFFFF (12272M used)
[Tue Feb  7 16:29:13 2023] amdgpu 0000:0b:00.0: amdgpu: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF
[Tue Feb  7 16:29:13 2023] amdgpu 0000:0b:00.0: amdgpu: AGP: 267894784M 0x0000008400000000 - 0x0000FFFFFFFFFFFF
[Tue Feb  7 16:29:13 2023] [drm] amdgpu: 12272M of VRAM memory ready
[Tue Feb  7 16:29:13 2023] [drm] amdgpu: 7958M of GTT memory ready.
[Tue Feb  7 16:29:13 2023] amdgpu 0000:0b:00.0: amdgpu: PSP runtime database doesn't exist
[Tue Feb  7 16:29:13 2023] amdgpu 0000:0b:00.0: amdgpu: PSP runtime database doesn't exist
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: STB initialized to 2048 entries
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: Will use PSP to load VCN firmware
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: RAS: optional ras ta ucode is not available
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: smu driver if version = 0x0000000e, smu fw if version = 0x00000012, smu fw program = 0, version = 0x00413900 (65.57.0)
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: SMU driver if version not matched
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: use vbios provided pptable
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: SMU is initialized successfully!
[Tue Feb  7 16:29:16 2023] snd_hda_intel 0000:0b:00.1: bound 0000:0b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
[Tue Feb  7 16:29:16 2023] kfd kfd: amdgpu: Allocated 3969056 bytes on gart
[Tue Feb  7 16:29:16 2023] amdgpu: sdma_bitmap: ffff
[Tue Feb  7 16:29:16 2023] amdgpu: HMM registered 12272MB device memory
[Tue Feb  7 16:29:16 2023] amdgpu: SRAT table not found
[Tue Feb  7 16:29:16 2023] amdgpu: Virtual CRAT table created for GPU
[Tue Feb  7 16:29:16 2023] amdgpu: Topology: Add dGPU node [0x73df:0x1002]
[Tue Feb  7 16:29:16 2023] kfd kfd: amdgpu: added device 1002:73df
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: SE 2, SH per SE 2, CU per SH 10, active_cu_number 40
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 1
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 1
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 1
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 1
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: amdgpu: Using BACO for runtime pm
[Tue Feb  7 16:29:16 2023] [drm] Initialized amdgpu 3.49.0 20150101 for 0000:0b:00.0 on minor 0
[Tue Feb  7 16:29:16 2023] fbcon: amdgpudrmfb (fb0) is primary device
[Tue Feb  7 16:29:16 2023] amdgpu 0000:0b:00.0: [drm] fb0: amdgpudrmfb frame buffer device


++++++++++++++++++++++++++++++++++++++++++++++++++++++++
THIS IS WHERE THE CRASH STARTED AROUND 17:35 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++



[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32770, for process HaloInfinite.ex pid 4244 thread 00 MAIN pid 4254)
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x00008002028e0000 from client 0x1b (UTCL2)
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301431
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          Faulty UTCL2 client ID: SQC (data) (0xa)
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          MORE_FAULTS: 0x1
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          WALKER_ERROR: 0x0
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          RW: 0x0
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32770, for process HaloInfinite.ex pid 4244 thread 00 MAIN pid 4254)
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x00008002028e0000 from client 0x1b (UTCL2)
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          MORE_FAULTS: 0x0
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          WALKER_ERROR: 0x0
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          RW: 0x0
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32770, for process HaloInfinite.ex pid 4244 thread 00 MAIN pid 4254)
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x00008002028e0000 from client 0x1b (UTCL2)
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          MORE_FAULTS: 0x0
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          WALKER_ERROR: 0x0
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          RW: 0x0
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32770, for process HaloInfinite.ex pid 4244 thread 00 MAIN pid 4254)
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x00008002028e0000 from client 0x1b (UTCL2)
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          MORE_FAULTS: 0x0
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          WALKER_ERROR: 0x0
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Tue Feb  7 17:35:08 2023] amdgpu 0000:0b:00.0: amdgpu:          RW: 0x0
[Tue Feb  7 17:35:18 2023] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32770, for process HaloInfinite.ex pid 4244 thread 00 MAIN pid 4254)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x00008002028e0000 from client 0x1b (UTCL2)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301431
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          Faulty UTCL2 client ID: SQC (data) (0xa)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          MORE_FAULTS: 0x1
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          WALKER_ERROR: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          RW: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32770, for process HaloInfinite.ex pid 4244 thread 00 MAIN pid 4254)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x00008002028e0000 from client 0x1b (UTCL2)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          MORE_FAULTS: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          WALKER_ERROR: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          RW: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32770, for process HaloInfinite.ex pid 4244 thread 00 MAIN pid 4254)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x00008002028e0000 from client 0x1b (UTCL2)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          MORE_FAULTS: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          WALKER_ERROR: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          RW: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32770, for process HaloInfinite.ex pid 4244 thread 00 MAIN pid 4254)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x00008002028e0000 from client 0x1b (UTCL2)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          MORE_FAULTS: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          WALKER_ERROR: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          RW: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32770, for process HaloInfinite.ex pid 4244 thread 00 MAIN pid 4254)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x00008002028e0000 from client 0x1b (UTCL2)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          MORE_FAULTS: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          WALKER_ERROR: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          RW: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32770, for process HaloInfinite.ex pid 4244 thread 00 MAIN pid 4254)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x00008002028e0000 from client 0x1b (UTCL2)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301431
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          Faulty UTCL2 client ID: SQC (data) (0xa)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          MORE_FAULTS: 0x1
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          WALKER_ERROR: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          RW: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32770, for process HaloInfinite.ex pid 4244 thread 00 MAIN pid 4254)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x00008002028e0000 from client 0x1b (UTCL2)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          MORE_FAULTS: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          WALKER_ERROR: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          RW: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32770, for process HaloInfinite.ex pid 4244 thread 00 MAIN pid 4254)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x00008002028e0000 from client 0x1b (UTCL2)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          MORE_FAULTS: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          WALKER_ERROR: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Tue Feb  7 17:35:18 2023] amdgpu 0000:0b:00.0: amdgpu:          RW: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32770, for process HaloInfinite.ex pid 4244 thread 00 MAIN pid 4254)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x00008002028e0000 from client 0x1b (UTCL2)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301431
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          Faulty UTCL2 client ID: SQC (data) (0xa)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          MORE_FAULTS: 0x1
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          WALKER_ERROR: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          RW: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32770, for process HaloInfinite.ex pid 4244 thread 00 MAIN pid 4254)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x00008002028e0000 from client 0x1b (UTCL2)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          MORE_FAULTS: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          WALKER_ERROR: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          RW: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32770, for process HaloInfinite.ex pid 4244 thread 00 MAIN pid 4254)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x00008002028e0000 from client 0x1b (UTCL2)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          MORE_FAULTS: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          WALKER_ERROR: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          RW: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32770, for process HaloInfinite.ex pid 4244 thread 00 MAIN pid 4254)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x00008002028e0000 from client 0x1b (UTCL2)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          MORE_FAULTS: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          WALKER_ERROR: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          RW: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32770, for process HaloInfinite.ex pid 4244 thread 00 MAIN pid 4254)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x00008002028e0000 from client 0x1b (UTCL2)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          MORE_FAULTS: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          WALKER_ERROR: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          RW: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32770, for process HaloInfinite.ex pid 4244 thread 00 MAIN pid 4254)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x00008002028e0000 from client 0x1b (UTCL2)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          MORE_FAULTS: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          WALKER_ERROR: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          RW: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32770, for process HaloInfinite.ex pid 4244 thread 00 MAIN pid 4254)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x00008002028e0000 from client 0x1b (UTCL2)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          MORE_FAULTS: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          WALKER_ERROR: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          RW: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32770, for process HaloInfinite.ex pid 4244 thread 00 MAIN pid 4254)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x00008002028e0000 from client 0x1b (UTCL2)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          MORE_FAULTS: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          WALKER_ERROR: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          RW: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32770, for process HaloInfinite.ex pid 4244 thread 00 MAIN pid 4254)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x00008002028e0000 from client 0x1b (UTCL2)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          MORE_FAULTS: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          WALKER_ERROR: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          RW: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32770, for process HaloInfinite.ex pid 4244 thread 00 MAIN pid 4254)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x00008002028e0000 from client 0x1b (UTCL2)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          MORE_FAULTS: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          WALKER_ERROR: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Tue Feb  7 17:35:28 2023] amdgpu 0000:0b:00.0: amdgpu:          RW: 0x0
[Tue Feb  7 17:35:28 2023] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered
[Tue Feb  7 17:35:38 2023] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=9085805, emitted seq=9085808
[Tue Feb  7 17:35:38 2023] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process HaloInfinite.ex pid 4244 thread 00 MAIN pid 4254
[Tue Feb  7 17:35:38 2023] amdgpu 0000:0b:00.0: amdgpu: GPU reset begin!
[Tue Feb  7 17:35:38 2023] amdgpu 0000:0b:00.0: amdgpu: free PSP TMR buffer
[Tue Feb  7 17:35:38 2023] amdgpu 0000:0b:00.0: amdgpu: MODE1 reset
[Tue Feb  7 17:35:38 2023] amdgpu 0000:0b:00.0: amdgpu: GPU mode1 reset
[Tue Feb  7 17:35:38 2023] amdgpu 0000:0b:00.0: amdgpu: GPU smu mode1 reset
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: GPU reset succeeded, trying to resume
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: RAS: optional ras ta ucode is not available
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: SMU is resuming...
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: smu driver if version = 0x0000000e, smu fw if version = 0x00000012, smu fw program = 0, version = 0x00413900 (65.57.0)
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: SMU driver if version not matched
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: use vbios provided pptable
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: SMU is resumed successfully!
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 1
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 1
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 1
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 1
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: recover vram bo from shadow start
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: recover vram bo from shadow done
[Tue Feb  7 17:35:39 2023] amdgpu 0000:0b:00.0: amdgpu: GPU reset(4) succeeded!
[Tue Feb  7 17:35:39 2023] amdgpu_cs_ioctl: 7 callbacks suppressed
[Tue Feb  7 17:35:39 2023] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
[Tue Feb  7 17:35:39 2023] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
[Tue Feb  7 17:35:39 2023] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
[Tue Feb  7 17:35:39 2023] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
[Tue Feb  7 17:35:39 2023] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
[Tue Feb  7 17:35:39 2023] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
[Tue Feb  7 17:35:39 2023] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
[Tue Feb  7 17:35:39 2023] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
[Tue Feb  7 17:35:39 2023] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
[Tue Feb  7 17:35:39 2023] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

@kisak-valve will do sorry about that

@pingubot I finally got it i played like 5 matches of halo and then i got to a new map and a few seconds into it the screen froze but i heard all the audio and then the screen turned black and when it came back on i was at the login screen like the session had restarted

It started at 17:35

sudo dmesg -T | grep amdgpu

Exact same issue happened to me where it crashes entering a game and puts you back on your desktop login screen. Happened multiple times when streaming last week with my Rx 6700

@pollux56

After the crash please provide the logs

sudo dmesg -T | grep amdgpu

@pollux56

After the crash please provide the logs

sudo dmesg -T | grep amdgpu

Alright ill hope on and try and get the crash again then provide the logs :)

@pollux56
After the crash please provide the logs
sudo dmesg -T | grep amdgpu

Alright ill hope on and try and get the crash again then provide the logs :)

I played halo infinite for 3 hours and I didn't crash so maybe it's fixed now idk 🤷

@pingubot
this is my 2nd crash with halo...
it starts at around 15:38

[Wed Feb 8 15:38:36 2023] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32796, for process HaloInfinite.ex pid 3916 thread 00 MAIN pid 3926)

https://gist.github.com/Cytomax55/68d71940c292e893ae356442cf2f0caf

Looks like i just had a 2nd crash here is the logs
https://gist.github.com/Cytomax55/6fd1e1a75770156031f057be78be5c27

Looks like i just had a 2nd crash here is the logs
https://gist.github.com/Cytomax55/6fd1e1a75770156031f057be78be5c27

What kernel version are you using?

OS: Manjaro 22.0.2 Sikaris
██████████████████ ████████ Kernel: x86_64 Linux 6.1.9-1-MANJARO
██████████████████ ████████ Uptime: 2h 7m
████████ ████████ Packages: 1773
████████ ████████ ████████ Shell: zsh 5.9
████████ ████████ ████████ Resolution: 2560x1440
████████ ████████ ████████ DE: KDE 5.102.0 / Plasma 5.26.5
████████ ████████ ████████ WM: KWin
████████ ████████ ████████ GTK Theme: Breeze [GTK2/3]
████████ ████████ ████████ Icon Theme: breeze
████████ ████████ ████████ Disk: 8.2T / 115T (8%)
████████ ████████ ████████ CPU: AMD Ryzen 7 5800X 8-Core @ 16x 3.8GHz
████████ ████████ ████████ GPU: AMD Radeon RX 6700 XT (navi22, LLVM 15.0.7, DRM 3.49, 6.1.9-1-MANJARO)
RAM: 4169MiB / 15916MiB

MESA: 23.1 mesa-git

News seems to say they are switching to EAC away from the arbiter anti-cheat. this is concerning

News seems to say they are switching to EAC away from the arbiter anti-cheat. this is concerning

yes that is very concerning, hopefully they enable linux support
can't believe I am saying this, but it is microsoft, so I think they will

I guess the upside is direct storage and ray tracing which I guess are going to be added alongside EAC.

where my logs useful in finding out what the problem is?

I forget where I heard it from, perhaps the MCC issue thread but I heard that they were slowly trying to enable EAC for MCC as well so its possible they will do that from the go? then again they don't exactly have alot of development time free... tho... I wonder how much of their tiny playerbase for steam are linux users as well. Time will tell

This game works for me but no textures load is there any fix for this I am using rx560 with Mesa 22.2.5. Last time I tried to update to latest mesa it broke my system so is there any other fix.

This game works for me but no textures load is there any fix for this I am using rx560 with Mesa 22.2.5. Last time I tried to update to latest mesa it broke my system so is there any other fix.

you have 2 options

1. enable rebar or above 4G encoding in your bios, or
2. delete the videos in the game files

Video Works on Nvidia without rebar
Guess its a mesa problem that needs to be addressed

new update causes crash on loading screen, looking into it further.

new update causes crash on loading screen, looking into it further.

send a log pls
can't test atm

new update causes crash on loading screen, looking into it further.

send a log pls can't test atm

not needed, it's a known issue with vkd3d, they are using the only feature of execute indirect in d3d12 that the current solution doesn't support

I have some crash report from my steam deck if any of it is helpful
halobugreport.pdf
halobugreport2.pdf

steam-1240440.tar.gz

System information:
    Wine build: wine-7.0
    Platform: x86_64
    Version: Windows 10
    Host system: Linux
    Host version: 6.1.15-2-liquorix-amd64
30085.782:0110:0290:trace:seh:handle_syscall_fault code=c000001d flags=0 addr=0x7f6795a98c05 ip=7f6795a98c05 tid=0290
30085.782:0110:0290:trace:seh:handle_syscall_fault  rax=ffffffffffffe4e0 rbx=000000009a3fe4e0 rcx=ffffffffffffea40 rdx=ffffffffffffeae0
30085.782:0110:0290:trace:seh:handle_syscall_fault  rsi=0000000000000000 rdi=00007f67940d4457 rbp=0000000000000000 rsp=000000009a3fe5d8
30085.782:0110:0290:trace:seh:handle_syscall_fault   r8=000000009a3fe900  r9=000000009a3feaf0 r10=0000000000000000 r11=0000000000000246
30085.782:0110:0290:trace:seh:handle_syscall_fault  r12=000000009a3feaf0 r13=000000009a400000 r14=000000009a3fe650 r15=0000000000000000
30085.782:0110:0290:warn:seh:handle_syscall_fault backtrace: --- Exception 0xc000001d at 0x7f6795a98c05: /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libc.so.6 + 0x98c05.
30085.782:0110:0290:trace:unwind:dwarf_virtual_unwind function 7f6795a98c05 base 0x7f6795a98bc0 cie 0x7f6795bc7ec8 len 14 id 0 version 1 aug 'zR' code_align 1 data_align -8 retaddr %rip
30085.782:0110:0290:warn:seh:dwarf_virtual_unwind backtrace: 0x7f6795a98c05: /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libc.so.6 + 0x98c05.
30085.782:0110:0290:trace:unwind:execute_cfa_instructions 7f6795a98bc0: DW_CFA_def_cfa %rsp, 8
30085.782:0110:0290:trace:unwind:execute_cfa_instructions 7f6795a98bc0: DW_CFA_offset %rip, -8
30085.782:0110:0290:trace:unwind:dwarf_virtual_unwind fde 0x7f6795bd38d4 len 18 personality (nil) lsda (nil) code 7f6795a98bc0-7f6795a98c0b
30085.782:0110:0290:trace:unwind:execute_cfa_instructions 7f6795a98bc0: DW_CFA_advance_loc 5
30085.782:0110:0290:trace:unwind:execute_cfa_instructions 7f6795a98bc5: DW_CFA_def_cfa_offset 16
30085.782:0110:0290:trace:unwind:execute_cfa_instructions 7f6795a98bc5: DW_CFA_advance_loc 1
30085.782:0110:0290:trace:unwind:execute_cfa_instructions 7f6795a98bc6: DW_CFA_def_cfa_offset 8
30085.782:0110:0290:trace:unwind:execute_cfa_instructions 7f6795a98bc6: DW_CFA_advance_loc 4
30085.782:0110:0290:trace:unwind:execute_cfa_instructions 7f6795a98bca: DW_CFA_def_cfa_offset 16
30085.782:0110:0290:trace:unwind:dwarf_virtual_unwind next function rip=0000000000000000
30085.782:0110:0290:trace:unwind:dwarf_virtual_unwind   rax=ffffffffffffe4e0 rbx=000000009a3fe4e0 rcx=ffffffffffffea40 rdx=ffffffffffffeae0
30085.782:0110:0290:trace:unwind:dwarf_virtual_unwind   rsi=0000000000000000 rdi=00007f67940d4457 rbp=0000000000000000 rsp=000000009a3fe5e8
30085.782:0110:0290:trace:unwind:dwarf_virtual_unwind    r8=000000009a3fe900  r9=000000009a3feaf0 r10=0000000000000000 r11=0000000000000246
30085.782:0110:0290:trace:unwind:dwarf_virtual_unwind   r12=000000009a3feaf0 r13=000000009a400000 r14=000000009a3fe650 r15=0000000000000000
30085.782:0110:0290:warn:seh:dump_syscall_fault backtrace: returning to user mode ip=0000000000000000 ret=c000001d
wine client error:290: write: Bad file descriptor
pid 67046 != 67045, skipping destruction (fork without exec?)

not needed, it's a known issue with vkd3d, they are using the only feature of execute indirect in d3d12 that the current solution doesn't support

Is there an issue we can refer to for more details? I couldn't find anything on vkd3d-proton and dxvk's bug trackers.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1459987282

no, it's known among the developers, I can give more details if anyone is interested

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1460131269

I am interested in learning more.

Replying to [#5030 (comment)](https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1460131269)

I am interested in learning more.

Basically it's ExecuteIndirect with dispatch + state changes
they're doing multi-indirect dispatch with root descriptor changes
it's the one thing VK_NV_device_generated_commands does not support

give them some time, based on what they said it should be possible to work around it

edit: the workaround is apparently extremely painful :/

not sure what most of this stuff is (I don't do graphics programming), but here you go anyways

Has anyone been able to get in game since the update, past loading screens and to a menu? I ask to know if its a system specific thing or something that is borked across the board?

Has anyone been able to get in game since the update, past loading screens and to a menu? I ask to know if its a system specific thing or something that is borked across the board?

it's borked across the board, it's a vkd3d-proton bug, we have to wait for the developers to create that painful workaround I mentioned earlier

Has anyone been able to get in game since the update, past loading screens and to a menu? I ask to know if its a system specific thing or something that is borked across the board?

it's borked across the board, it's a vkd3d-proton bug, we have to wait for the developers to create that painful workaround I mentioned earlier

Thanks for letting me know, Ill stop messing around with things then and just wait for any news on it, is it a similar issue to the previous update causing the game to crash? You mentioned it being a painful thing to workaround. Quite unfortunate. How are you monitoring that situation? because I would like to follow it as well

Not that this needs to be said, after Etaash's advice (thank you for that, btw), but the game stopped working for me too with the Mar 7 update. There was another 58MB update today, but (despite my extreme optimism) that did nothing to change the situation. In fact, the game might crash even sooner than before, after today's update. The loading screen, which used to last ~20 seconds, now only appears for about 500ms before crashing to desktop. Will stay tuned.

Zorin OS 16.2
Linux 5.15.0-67-generic
RTX 3070 Ti (525.85.05)
Proton Experimental / bleeding edge

I saw a report that says it works, but my card is nvidia not AMD. So I cannot test this

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1464440190

I gave this a try on my 7900 XT and it didn't work unfortunatley, this update also added ray-traced shadows so I wonder if that could be an issue as well.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1464440190

Hey, i tested it with an RX 7900 XTX, it didn't work for me, neither. According to @glyndwr-io's post, i assume it's a RDNA 3 related issue.

Radv perf test doesn't work on my 6700xt
Running Manjaro stable KDE
6.1 kernel
Mesa git

Halo Infinite opens, plays the opening video (Xbox, 343 Industries) then crashes on the loading screen after a few seconds.
AMD Radeon RX 6600 XT
Intel i7-12700k (@ 5.1 GHz)
Fedora Linux 37
Kernel 6.1.15

I have the same issue where halo infinite it opens and as soon as it finished loading it crashes

It'd be great if we could get any kind of feedback on this. Should we expect this to be fixed in the near future, or can we expect this to be broken for the foreseeable future? There doesn't even seem to be a github issue open for vkd3d about this.

It'd be great if we could get any kind of feedback on this. Should we expect this to be fixed in the near future, or can we expect this to be broken for the foreseeable future? There doesn't even seem to be a github issue open for vkd3d about this.

cant know, I am blind as you are. I know 343 is making a patch in the next few hours so there may be something progressing there. Considering it is broken on many PC users and some xbox users. No clue if it will help, just guessing really.

I believe this branch is the one for fixing the issue mentionned by @Etaash-mathamsetty. I'm keeping an eye on it or any pull request related to it.
https://github.com/HansKristian-Work/vkd3d-proton/tree/multi-indirect-dispatch

PS: Please keep in mind that Github is basically Hans-Kristian's workplace, it might be preferable to not bother him and keep Halo Infinite related technical discussions in this issue unless he asks for feedback.

I believe this branch is the one for fixing the issue mentionned by @Etaash-mathamsetty. I'm keeping an eye on it or any pull request related to it.
https://github.com/HansKristian-Work/vkd3d-proton/tree/multi-indirect-dispatch

PS: Please keep in mind that Github is basically Hans-Kristian's workplace, it might be preferable to not bother him and keep Halo Infinite related technical discussions in this issue unless he asks for feedback.

I don't think it can run halo yet, but it's a step in the right direction
We still need support for state changes

edit: seems like it got updated again, not sure if halo werks yet (it doesn't)

Alright, well this is odd.
I installed the March 15th "Small Update", and ran the game with PE. Instant crash, like usual.

Decided to try again. On 2nd run... the hex/topgraphical/loading screen actually loaded... and the progress bar got all the way to 100%.

And stayed there. And nothing else happened.

That's where it is right now. Its been like this for 10 minutes. Its a Halo Infinite scrolling landscapes screensaver.

How does a fool implement this? :thinking:

I ask because mine still crashes so I assume its something I need to manually apply, and I would rather not damage the prefix by messing around with it xD

How does a fool implement this? thinking

I ask because mine still crashes so I assume its something I need to manually apply, and I would rather not damage the prefix by messing around with it xD

download the artifact off the PR's CI and then put the x64 d3d12.dll next to the game executable and click play (using proton experimental)
here's the link https://github.com/HansKristian-Work/vkd3d-proton/actions/runs/4430663214

How does a fool implement this? thinking
I ask because mine still crashes so I assume its something I need to manually apply, and I would rather not damage the prefix by messing around with it xD

download the artifact off the PR's CI and then put the x64 d3d12.dll next to the game executable and click play (using proton experimental) here's the link https://github.com/HansKristian-Work/vkd3d-proton/actions/runs/4430663214

Thanks mate

Halo infinite now works with the latest proton-ge 51 from gloriouseggroll :)

Halo infinite now works with the latest proton-ge 51 from gloriouseggroll :)

Can't seem to confirm this working on Steam Deck just yet with 51. I'm in the middle of reinstalling just to try that but I couldn't get it past that loading screen yet.

I've only installed GE7 51 so far. Am I missing something?

@ion070 I haven't gotten it to work either. (Zephyrus G14 2022) With the iGPU enabled, I got garbled intro video and then a crash. With the iGPU disabled and just the dGPU, it would load, then crash when at the "Initalizing Data" part of the sign-in process.

@colemickens I found a post on reddit of someone who got to the main menu on the Deck with 51 here: https://www.reddit.com/r/halo/comments/11sjgqo/does_anyone_know_how_to_fix_not_having_any/?utm_source=share&utm_medium=android_app&utm_name=androidcss&utm_term=1&utm_content=share_button

I left a comment asking how they may have done it.

Halo infinite now works with the latest proton-ge 51 from gloriouseggroll :)

Can't seem to confirm this working on Steam Deck just yet with 51. I'm in the middle of reinstalling just to try that but I couldn't get it past that loading screen yet.

I've only installed GE7 51 so far. Am I missing something?

The reinstall worked!

Is there some other way to clear the game state? I'm in a location where bandwidth is scarce. I can't believe its 2023 and "reinstall" somehow helps. The game content should be roughly immutable, whatever state does Steam maintain per-game?

Halo Infinite now runs on my computer with Proton-GE 7-51 with about 40% of my games crashing out in some way. If I make it all the way through a game I loose server connection after and don't see the full results.

Halo Infinite now runs on my computer with Proton-GE 7-51 with about 40% of my games crashing out in some way. If I make it all the way through a game I loose server connection after and don't see the full results.

Halo infinite is the most stable game on my system never crashes, the second issue you mentioned is something I experience too, will retest with proton tkg 8.3

Odd, I have always had some issues with it, but it was about a 15% crash rate in season 2. What are your specs and launch options? I have no launch options.
Specs:
Intel 12700-K i7
64 GB DDR4 RAM
AMD Radeon 6600XT

Game is on graphics preset medium.

Odd, I have always had some issues with it, but it was about a 15% crash rate in season 2. What are your specs and launch options? I have no launch options. Specs: Intel 12700-K i7 64 GB DDR4 RAM AMD Radeon 6600XT

Game is on graphics preset medium.

on both my systems I never had crashes (with no launch options)
laptop:
ryzen 7 4700u
16gb ddr4

PC:
ryzen 7 7700x
32gb ddr5
RX 6800

Ok. I will do some trouble shooting later today to see if some of my configuration somewhere is messing up stuff. It could be the Intel CPU? I don't know. I assume you are using Proton-GE?

Odd, I have always had some issues with it, but it was about a 15% crash rate in season 2. What are your specs and launch options? I have no launch options. Specs: Intel 12700-K i7 64 GB DDR4 RAM AMD Radeon 6600XT
Game is on graphics preset medium.

on both my systems I never had crashes (with no launch options) laptop: ryzen 7 4700u 16gb ddr4

PC: ryzen 7 7700x 32gb ddr5 RX 6800

What distro/DE are you running and do you have ReBAR enabled?

Fedora 37. I feel dumb, I completely forgot about ReBAR. I can't check right now, but when I get there should I have it on or off?

Removing RADV_PERFTEST=gpl gets me all the way to searching for a game, but then another crash. Still dGPU only.

Fedora 37. I feel dumb, I completely forgot about ReBAR. I can't check right now, but when I get there should I have it on or off?

On

Fedora 37. I feel dumb, I completely forgot about ReBAR. I can't check right now, but when I get there should I have it on or off?

On

See, if I have ReBAR on with my 3700X/6800XT, in-menu load times are insufferable, taking at least a minute or more to load into Customization, MP, or the store. With it off, they're fine 🤔 Any ideas?

System:

• CPU: AMD Ryzen 7 3700X
• RAM: 32GB DDR4 2400
• GPU: AMD RX 6800XT
• Storage: Samsung 970 Evo Plus 2TB
• OS: Fedora Workstation 37
• DE: Gnome (Wayland)

Proton-GE 7-51 enabled me to start the game and play for about a minute and a half (my character had no hands holding the gun and all textures looked terrible) before my whole system crashed, my desktop locked up and I had to power my PC off. Never had such a crash on my system besides a recent VLC issue as described here.

Arch 6.2.6-zen Ryzen 5 5600x RX6600xt Asrock b450m Pro4-CB (newest UEFI version) GNOME 43.3 Wayland 1tb NVME
Resizable BAR and Above 4g are enabled

for textures to look correct ReBAR has to be on, I am tired of saying this over and over again (edit: only on RADV apparently, above 4g encoding works as well)

It's a mesa problem, cause Nvidia without rebar texture work, so the developers of mesa have to fix that problem, so delete your video folder if u want textures to work.

Ple

Proton-GE 7-51 enabled me to start the game and play for about a minute and a half (my character had no hands holding the gun and all textures looked terrible) before my whole system crashed, my desktop locked up and I had to power my PC off. Never had such a crash on my system besides a recent VLC issue as described here.

Arch 6.2.6-zen Ryzen 5 5600x RX6600xt Asrock b450m Pro4-CB (newest UEFI version) GNOME 43.3 Wayland 1tb NVME Resizable BAR and Above 4g are enabled

Please disregard this post, I too was quite sure ReBAR was enabled as I had done so in the past but at some point it went back to disabled. Apologies

How does a fool implement this? thinking
I ask because mine still crashes so I assume its something I need to manually apply, and I would rather not damage the prefix by messing around with it xD

download the artifact off the PR's CI and then put the x64 d3d12.dll next to the game executable and click play (using proton experimental) here's the link https://github.com/HansKristian-Work/vkd3d-proton/actions/runs/4430663214

VKD3D patch works with Proton Experimental. The added CPU overhead is massive, and causes a bit of stutter in game, but it's playable.

Before S3 (winter update): 60-75FPS pinned w/ vsync in game and menus
After: Felt like 30ish, but it was pretty unstable, anywhere from 20 to 75 w/ vsync

Game menus are very slow.

Specs below.
CPU: Intel Core i5-6500
GPU: Radeon RX 6600 (navi23, LLVM 15.0.6, DRM 3.49)
MB: MSI Z270 Gaming PRO Carbon
Mesa: 22.3.3
RAM: 16GB DDR4-3200
Game installed on Crucial MX500 1TB
OS: Debian GNU/Linux bookworm/sid
Kernel: 6.1.0-6-amd64
DE: Cinnamon 5.6.7

ReBAR is off, as my motherboard doesn't seem to support it (last BIOS update was 2018.) Above 4G Decoding is on.

Launch options:
RADV_PERFTEST=gpl mangohud gamemoderun %command%

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1472978205

I also experienced slow menus and slow LOD loading prior to S3 but it's gotten significantly worse in S3. When a game is finished, the loading splash screen takes ages before dumping me back to the multiplayer menu where it says I've disconnected from the game session due to a timeout. Resizeable BAR is enabled.

For me it works!!

Steam beta
PROTON HOTFIX
Mesa-git
REBAR on
4g ON

OS: Manjaro 22.0.5 Sikaris
██████████████████ ████████ Kernel: x86_64 Linux 6.1.19-1-MANJARO
██████████████████ ████████ Uptime: 3h 39m
████████ ████████ Packages: 1777
████████ ████████ ████████ Shell: zsh 5.9
████████ ████████ ████████ Resolution: 2560x1440
████████ ████████ ████████ DE: KDE 5.103.0 / Plasma 5.26.5
████████ ████████ ████████ WM: KWin
████████ ████████ ████████ GTK Theme: Breeze [GTK2/3]
████████ ████████ ████████ Icon Theme: breeze
████████ ████████ ████████ Disk: 8.3T / 110T (8%)
████████ ████████ ████████ CPU: AMD Ryzen 7 5800X 8-Core @ 16x 3.8GHz
████████ ████████ ████████ GPU: AMD Radeon RX 6700 XT (navi22, LLVM 15.0.7, DRM 3.49, 6.1.19-1-MANJARO)
RAM: 4495MiB / 15919MiB

for textures to look correct ReBAR has to be on, I am tired of saying this over and over again (edit: only on RADV apparently, above 4g encoding works as well)

ReBAR was off, so I turned it on, and above 4G was already on.
Proton-GE 7.51

Halo runs very very well. The loading screen before and after the matches is still very long (about 33 seconds on average before and 56 seconds on average after) and about 40% of the matches drop the server connection before I get to the results screen, but the game plays very well.

I will try Proton Hotfix and Proton Experimental later today.

For some of my tests I used the RADV_PERFTEST=gpl %command% launch option, it seemed to shorten the pre and post game loading screens by a few seconds, reduce the amount of dropped games before the results screen, and lengthen the first loading screen a bit.

Also note Halo got a little update in the middle of some of my testing, so that could have messed things up.

This is a reminder to myself to time the loading screens on my brother's Windows 10 laptop just to get an idea of how long they should be.

Proton-GE 7-51 enabled me to start the game and play for about a minute and a half my whole system crashed, my desktop locked up and I had to power my PC off.

I fixed this crash by disabling "XMP Profile 2.0" in UEFI settings. 16GB RAM.
With XMP Profile set to 2.0, my system crashes about 30 seconds into a match.

Proton-GE 7-51 enabled me to start the game and play for about a minute and a half my whole system crashed, my desktop locked up and I had to power my PC off.

I fixed this crash by disabling "XMP Profile 2.0" in UEFI settings. 16GB RAM.
With XMP Profile set to 2.0, my system crashes about 30 seconds into a match.

That is odd. I have had that crash before (very rarely and only in Halo)... I don't know why disabling XMP would fix it.

I don't know much about stuff like this, but I think those whole system freezes are the display server crashing and failing to recover.

I am also able to reproduce, I only get it in certain game modes though

I am also able to reproduce, I only get it in certain game modes though

Same. Fortunately Slayer seems to work and that is me and my friend's favorite mode to play.

Edit 2: MY BAD! I should've scrolled up a bit more. There was someone mentioning this bug already. Sorry for flooding your mail!

I have really odd graphics with Proton GE 51.

It's like the LOD of the game is lower than anything possible. Is this normal? Even the player hands dont show up. The weapons are also really lowpoly/odd looking.

Operating System: Fedora Linux 37
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.18-200.fc37.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15,5 GiB of RAM
Graphics Processor: AMD Radeon RX 6600

Edit:

Seems the issue was my resizable BAR not being enabled: This gave the game only 256mb VRAM, or something like that. Weird. Enabling it fixed the graphical issue but things load much slower now.

Just wanna share that I'm actually able to boot into a Halo Infinite match now when using the current hotfix. However, it's very choppy.

Edit: thanks to y'all working on this

In the issue that Luiqui87 opened above, kisak-valve says the following:
This is a general system config issue and unrelated to the Steam for Linux client. Use another medium.

Does anyone know what kind of system configuration issues would cause load times to increase with ReBAR on? I've can't seem to find anything but I also don't know where to look.

Yeah I would like to know what system config issues it is because I can't think of anything. My menu loading times are also ridiculous.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1475297057

Thanks for the context. The only reason I mentioned it was I was just curious if there are any paths I could go down to see if a config option could fix it. I've been chasing this for quite a while and nothing has really helped, so it very well could be a Proton issue. If there is any debug info that could help pin this down I'd be happy to provide it, as there doesn't seem to be anything useful in Proton or Kernel logs.

The vkd3d-proton work around have been merged upstream

GPU hangs can be prevented using RADV_DEBUG=hang, I don't recommend this because it's only supposed to be used for debugging and the performance is worse (by a lot).

proton experimental bleeding edge beta can play this game now, no need to copy paste DLLs or use proton-ge

The vkd3d-proton work around have been merged upstream

Do we have to wait for Steam to include it? Can we use this latest version manually? How to use it with Steam?
Sorry that's a lot of questions, but information on the subject is sparse.

Been working for me using proton hotfix

Been working for me using proton hotfix

I tried with experimental bleeding edge, hot fix.
The game starts, the cursors changes to the Halo cursor. I can hear the music and trigger menus, but I have a frozen view of my desktop instead of seeing the game.
Has anyone seen something like this?
I'm running Ubuntu 22.10 with Nvidia drivers 530.

@imval give VKD3D_DISABLE_EXTENSIONS=VK_KHR_present_id,VK_KHR_present_wait %command% as launch option a try.

@imval give VKD3D_DISABLE_EXTENSIONS=VK_KHR_present_id,VK_KHR_present_wait %command% as launch option a try.

it might be another nvidia driver bug, this works around it

Do we have to wait for Steam to include it? Can we use this latest version manually? How to use it with Steam? Sorry that's a lot of questions, but information on the subject is sparse.

It is available in Bleeding Edge (a beta branch of Proton Experimental) and should get pulled in on the next proper Experimental update.

I have encountered some crashes with the reBAR on, I've shared my crash here: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7664#note_1829965

Wanted to share it here as well if there are any ideas how to fix this.

The latest bleeding edge actually updated a few hours after my last comment and fixed the issues I had.

The latest bleeding edge actually updated a few hours after my last comment and fixed the issues I had.

yeah that's because they (vkd3d-proton devs) disabled those vulkan extensions (present_wait, present_id) on nvidia GPUs lmao
nvidia moment

I have encountered some crashes with the reBAR on, I've shared my crash here: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7664#note_1829965

Wanted to share it here as well if there are any ideas how to fix this.

I wonder when people without rebar will get video support 😂

I have encountered some crashes with the reBAR on, I've shared my crash here: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7664#note_1829965

Wanted to share it here as well if there are any ideas how to fix this.

Does it crash on any specific gamemode? I noticed mine only crashes when I load into zone-based gamemodes (Total Control, Strongholds, etc) which I usually don't get in matchmaking until after a few games. I've also seen others mention crashes in these modes too. It happens right as you get within draw distance of a zone.
https://gitlab.freedesktop.org/drm/amd/-/issues/2471

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1481932833

I think you might be right! I havent really paid attention to it but it seems anything with capture points can cause crash. Maybe it's some specific shader used for the capture points?

Replying to [#5030 (comment)](https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1481932833)

I think you might be right! I havent really paid attention to it but it seems anything with capture points can cause crash. Maybe it's some specific shader used for the capture points?

I don't have that issue on RDNA 2, so I don't think that's the issue, it's probably RDNA 3 specific

Update from my side. After uninstalling and removing all files, the game works. As it yesterday.
Playing on Steam Deck with Proton Experimental.

I played for a few hours yesterday with no crashes. The long loading screens are annoying though. Sometimes the people I was playing with would already be in the match for a few minutes before I finally got in.

One thing I'm experiencing that I haven't seen mentioned is that the movements keys can be sticky. Sometimes I'll get stuck moving in one direction using WASD keys, and I have to mash the keys again to unstick it. It seems to happen with any direction and I haven't noticed it happen with mouse clicks or other keys.

I've only ever seen this happen in Halo and in daily use those keys never get stuck, so I think it's Halo specific.

Hello @duckbytes, can you check if your system uses ibus 1.5.28? You may have encountered ibus/ibus#2480.

Oh that was it. Thank you. I added

IBUS_ENABLE_SYNC_MODE=1

to my /etc/environment and it's not happening any more.

Replying to [#5030 (comment)](https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1481932833)

I think you might be right! I havent really paid attention to it but it seems anything with capture points can cause crash. Maybe it's some specific shader used for the capture points?

I don't have that issue on RDNA 2, so I don't think that's the issue, it's probably RDNA 3 specific

Along with my 7900 XT I have an RX 6800 that is on it's way out and while it encounters general stability issues, I can also get it to crash under the same circumstances. It also seems that Steam Deck users are reporting this issue as well. From some of the comments in this thread it seems to be a bad sahder cache that once cleared temporarily solves the issue. I was using this trick of deleting my shader cache pre Season 3 with very mixed/limited success with my 7900 XT, but since Season 3 it does not seem to work anymore.
https://www.reddit.com/r/SteamDeck/comments/1086ae9/comment/j8oot9r/?utm_source=share&utm_medium=web2x&context=3

. I was using this trick of deleting my shader cache pre Season 3 with very mixed/limited success with my 7900 XT, but since Season 3 it does not seem to work anymore.

Perhaps they fixed the workaround?

I've been having an issue myself now, It's been mostly fine (save the stupidly long load times) and then on the mission Pelican down it started crashing (I'm currently re-installing it).

Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x0
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:173 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x0
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:173 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x0
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
Apr 02 15:42:27 small-box kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
Apr 02 15:42:28 small-box kernel: Failed to wait all pipes clean
Apr 02 15:42:28 small-box kernel: amdgpu 0000:03:00.0: amdgpu: soft reset failed, will fallback to full reset!
Apr 02 15:42:28 small-box kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Apr 02 15:42:28 small-box kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Apr 02 15:42:28 small-box kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Apr 02 15:42:28 small-box kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Apr 02 15:42:28 small-box kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Apr 02 15:42:28 small-box kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Apr 02 15:42:28 small-box kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Apr 02 15:42:28 small-box kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Apr 02 15:42:28 small-box kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Apr 02 15:42:28 small-box kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Apr 02 15:42:29 small-box kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Apr 02 15:42:29 small-box kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Apr 02 15:42:29 small-box kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Apr 02 15:42:29 small-box kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Apr 02 15:42:29 small-box kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Apr 02 15:42:29 small-box kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Apr 02 15:42:29 small-box kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Apr 02 15:42:29 small-box kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Apr 02 15:42:29 small-box kernel: [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
Apr 02 15:42:29 small-box kernel: amdgpu 0000:03:00.0: amdgpu: MODE1 reset
Apr 02 15:42:29 small-box kernel: amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset
Apr 02 15:42:29 small-box kernel: amdgpu 0000:03:00.0: amdgpu: GPU smu mode1 reset
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset succeeded, trying to resume
Apr 02 15:42:30 small-box kernel: [drm] PCIE GART of 512M enabled (table at 0x00000085FEB00000).
Apr 02 15:42:30 small-box kernel: [drm] VRAM is lost due to GPU reset!
Apr 02 15:42:30 small-box kernel: [drm] PSP is resuming...
Apr 02 15:42:30 small-box kernel: [drm] reserve 0x1300000 from 0x85fc000000 for PSP TMR
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resuming...
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x00000037, smu fw if version = 0x00000034, smu fw program = 0, smu fw version = 0x004e4b00 (78.75.0)
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully!
Apr 02 15:42:30 small-box kernel: [drm] DMUB hardware initialized: version=0x07000A01
Apr 02 15:42:30 small-box kernel: [drm] REG_WAIT timeout 1us * 1000 tries - dcn32_dsc_pg_control line:91
Apr 02 15:42:30 small-box kernel: [drm] REG_WAIT timeout 1us * 1000 tries - dcn32_dsc_pg_control line:99
Apr 02 15:42:30 small-box kernel: [drm] REG_WAIT timeout 1us * 1000 tries - dcn32_dsc_pg_control line:107
Apr 02 15:42:30 small-box kernel: [drm] REG_WAIT timeout 1us * 1000 tries - dcn32_dsc_pg_control line:115
Apr 02 15:42:30 small-box kernel: [drm] REG_WAIT timeout 1us * 1000 tries - dcn32_dsc_pg_control line:91
Apr 02 15:42:30 small-box kernel: [drm] REG_WAIT timeout 1us * 1000 tries - dcn32_dsc_pg_control line:99
Apr 02 15:42:30 small-box kernel: [drm] REG_WAIT timeout 1us * 1000 tries - dcn32_dsc_pg_control line:107
Apr 02 15:42:30 small-box kernel: [drm] REG_WAIT timeout 1us * 1000 tries - dcn32_dsc_pg_control line:115
Apr 02 15:42:30 small-box kernel: [drm] kiq ring mec 3 pipe 1 q 0
Apr 02 15:42:30 small-box kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 1
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_1 uses VM inv eng 1 on hub 1
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 4 on hub 1
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 14 on hub 0
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: recover vram bo from shadow start
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: recover vram bo from shadow done
Apr 02 15:42:30 small-box kernel: [drm] Skip scheduling IBs!
Apr 02 15:42:30 small-box kernel: [drm] Skip scheduling IBs!
Apr 02 15:42:30 small-box kernel: [drm] Skip scheduling IBs!
Apr 02 15:42:30 small-box kernel: [drm] Skip scheduling IBs!
Apr 02 15:42:30 small-box kernel: [drm] Skip scheduling IBs!
Apr 02 15:42:30 small-box kernel: [drm] Skip scheduling IBs!
Apr 02 15:42:30 small-box kernel: [drm] Skip scheduling IBs!
Apr 02 15:42:30 small-box kernel: [drm] Skip scheduling IBs!
Apr 02 15:42:30 small-box kernel: [drm] Skip scheduling IBs!
Apr 02 15:42:30 small-box kernel: [drm] Skip scheduling IBs!
Apr 02 15:42:30 small-box kernel: [drm] Skip scheduling IBs!
Apr 02 15:42:30 small-box kernel: [drm] Skip scheduling IBs!
Apr 02 15:42:30 small-box kernel: [drm] Skip scheduling IBs!
Apr 02 15:42:30 small-box kernel: [drm] Skip scheduling IBs!
Apr 02 15:42:30 small-box kernel: [drm] Skip scheduling IBs!
Apr 02 15:42:30 small-box kernel: [drm] Skip scheduling IBs!
Apr 02 15:42:30 small-box kernel: [drm] Skip scheduling IBs!
Apr 02 15:42:30 small-box kernel: [drm] Skip scheduling IBs!
Apr 02 15:42:30 small-box kernel: [drm] ring gfx_32782.1.1 was added
Apr 02 15:42:30 small-box kernel: [drm] ring compute_32782.2.2 was added
Apr 02 15:42:30 small-box kernel: [drm] ring compute_32782.2.3 was added
Apr 02 15:42:30 small-box kernel: [drm] ring compute_32782.2.4 was added
Apr 02 15:42:30 small-box kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Apr 02 15:42:30 small-box kernel: [drm] ring compute_32782.2.5 was added
Apr 02 15:42:30 small-box kernel: [drm] ring sdma_32782.3.6 was added
Apr 02 15:42:30 small-box kernel: [drm] ring sdma_32782.3.7 was added
Apr 02 15:42:30 small-box kernel: [drm] ring gfx_32782.1.1 test pass
Apr 02 15:42:30 small-box kernel: [drm] ring gfx_32782.1.1 ib test pass
Apr 02 15:42:30 small-box kernel: [drm] ring compute_32782.2.2 test pass
Apr 02 15:42:30 small-box kernel: [drm] ring compute_32782.2.2 ib test pass
Apr 02 15:42:30 small-box kernel: [drm] ring compute_32782.2.3 test pass
Apr 02 15:42:30 small-box kernel: [drm] ring compute_32782.2.3 ib test pass
Apr 02 15:42:30 small-box kernel: [drm] ring compute_32782.2.4 test pass
Apr 02 15:42:30 small-box kernel: [drm] ring compute_32782.2.4 ib test pass
Apr 02 15:42:30 small-box kernel: [drm] ring compute_32782.2.5 test pass
Apr 02 15:42:30 small-box kernel: [drm] ring compute_32782.2.5 ib test pass
Apr 02 15:42:30 small-box kernel: [drm] ring sdma_32782.3.6 test pass
Apr 02 15:42:30 small-box kernel: [drm] ring sdma_32782.3.6 ib test pass
Apr 02 15:42:30 small-box kernel: [drm] ring sdma_32782.3.7 test pass
Apr 02 15:42:30 small-box kernel: [drm] ring sdma_32782.3.7 ib test pass
Apr 02 15:42:30 small-box kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset(4) succeeded!
Apr 02 15:42:30 small-box xdg-desktop-portal-kde[10355]: The X11 connection broke (error 1). Did the X11 server die?

I'm not sure if any of that is helpful but It did seem to occur when the game crashed.

EDIT:

Reinstalling had no effect :(

Steam System information

1240440/config_info:

7.0-101
/home/thermatix/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/Proton - Experimental/files/share/fonts/
/home/thermatix/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/Proton - Experimental/files/lib/
/home/thermatix/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/Proton - Experimental/files/lib64/
/home/thermatix/.var/app/com.valvesoftware.Steam/.local/share/Steam
1679682280.0
1679682282.0
1516738214.0
/home/thermatix/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/Proton - Experimental/files/share/default_pfx/
1680292545.1690493
False
True
d3dcompiler_*.dll,d3dcsx*.dll,d3dx*.dll,x3daudio*.dll,xactengine*.dll,xapofx*.dll,xaudio*.dll,xinput*.dll,atl1*.dll,concrt1*.dll,msvcp1*.dll,msvcr1*.dll,vcamp1*.dll,vcomp1*.dll,vccorlib1*.dll,vcruntime1*.dll,ntdll.dll,vulkan-1.dll
False

Replying to [#5030 (comment)](https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1481932833)

I think you might be right! I havent really paid attention to it but it seems anything with capture points can cause crash. Maybe it's some specific shader used for the capture points?

I can confirm, it's happening when control point is visible. Using 3900x and 6950xt with reBAR on.

Although the game seems to work fine on my Steam Deck, on my desktop I have issues joining and ending matches. When joining a match, during the splash screen between "Match starting in... 5, 4, 3, 2, 1" and being dropped into the game, the game sits in the splash screen for an extended period of time. It often lasts long enough that I miss the first minute or so of the match. And sometimes it even lasts long enough that I get kicked for inactivity; I have to kill the game before this happens or else I can get suspended for "unsportsmanship".

When a match ends, it takes a minute or two of splash screen before I'm brought back to the menu, and then it tells me I've lost connection to the server.

This is on a system with a Ryzen 7950X and a Radeon RX 7900 XT.

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1504034182

I had completely the same issue yesterday. Ryzen 5950x, 6900XT. Opensuse TW, Kernel 6.2

NixOS, kernel 6.1.21, and mesa 22.3.7 for me, though mesa 23.0.2 didn't help.

My specs are:

OS: Arch Linux
KERNEL: 6.2.10-zen1-1-zen
CPU: AMD Ryzen 5 5600 6-Core
GPU: AMD Radeon RX 6600 (navi23, LLVM 15.0.7, DRM 3.49, 6.2.10-zen1-1-zen)
GPU DRIVER: 4.6 Mesa 23.0.2
RAM: 16 GB

I can play the game without issue, the only weird thing I've noticed is that the textures are missing/messed up:

any idea what could it be?

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1507824858

Enable rebar (or above 4g encoding), I think me and other people have said this over 10 times in the thread already :p

Some of us can't enable either of them 😂

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1507824858

I even switched to arch now (endevaour os) but i still have the issue with the long loading screen and server disconnect when exiting a match. So for me it is the same issue on opensuse tw and arch. tried zen and standard kernel

Replying to [#5030 (comment)](https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1507824858)

I even switched to arch now (endevaour os) but i still have the issue with the long loading screen and server disconnect when exiting a match. So for me it is the same issue on opensuse tw and arch. tried zen and standard kernel

Delete or rename your video folder

Delete or rename your video folder

@massatt212 What is this supposed to accomplish? Renaming the folder didn't have any positive effect on the match loading or server disconnecting.

With Proton 8.0 the game crashes at first loading screen due to vkd3d being too old. Using the vkd3d proton from experimental (proton 7) lets you get into the game but then the game constantly crashes when you try to enter a multiplayer match.

I have found some very weird behaviour with this game on my Steam Deck, I think?

I can launch the game and play just fine when I do not set an override for compatibility:

Of course, I have my Enable Steam Play for all other titles set to Proton 7.0-6:

However, when I try to manually set the override specifically for Halo Infinite to Proton 7.0-6, it does not work, it tries loading the splash screen and loading into the main menu then crashes out of the game.

I have noticed that it is "Playable" on the Steam store page - it's not "Verified", so doesn't that mean Steam isn't explicitly setting the Proton version for this specific game?

Am I missing something here? What Proton version is Halo Infinite using for me if it's not Proton 7.0-6?

@ipkpjersi It should be using Experimental by default according to steamdb. https://steamdb.info/app/1240440/

Currently noticing that things take a while to load. Sometimes there's texture pop-ins, but the Customize -> Armor Hall menu takes a long time to load, and loading into games takes significantly longer than on Windows.

Anyone have ideas for what would cause that?

i gave up on this game, just give it some time and check back in a month, on windows i can load all textures on a old motherboard without 4gb decoding, on linux i need 4g decoding, so give it another month so they can solve it or even 5 months.

same for me, play very rarely now, those loading times are just annoying. Hope the issues can get fixed eventually. Even leaving the map and going back to menu takes ages with server disconnects,

Don't have any of the 3 above issues, long loading times were fixed last week and just enable 4g encoding/rebar for textures

Server disconnecting after the match is something I get as well tho :(

I just played Halo a few days ago on my kde Manjaro system with kernel 6.3 and it worked fine What are you guys running?

Don't have any of the 3 above issues, long loading times were fixed last week and just enable 4g encoding/rebar for textures

Server disconnecting after the match is something I get as well tho :(

My motherboard doesn't have 4gb decoding, just said it old.

I just played Halo a few days ago on my kde Manjaro system with kernel 6.3 and it worked fine What are you guys running?

Nobara 37 with kernel 6.2.14-300.fsync.fc37.x86_64, running Gnome. Rebar is enabled but I still get weird texture issues. Load times are atrocious (videos directory is in fact deleted), and "server disconnected" when games finish.

I just played Halo a few days ago on my kde Manjaro system with kernel 6.3 and it worked fine What are you guys running?

Nobara 37 with kernel 6.2.14-300.fsync.fc37.x86_64, running Gnome. Rebar is enabled but I still get weird texture issues. Load times are atrocious (videos directory is in fact deleted), and "server disconnected" when games finish.

use a newer proton, proton experimental is new enough I think, but if you still have loading time issues, then just use proton experimental bleeding edge

I just played Halo a few days ago on my kde Manjaro system with kernel 6.3 and it worked fine What are you guys running?

Nobara 37 with kernel 6.2.14-300.fsync.fc37.x86_64, running Gnome. Rebar is enabled but I still get weird texture issues. Load times are atrocious (videos directory is in fact deleted), and "server disconnected" when games finish.

use a newer proton, proton experimental is new enough I think, but if you still have loading time issues, then just use proton experimental bleeding edge

Last I tried the latest Proton GE (as Experimental was behaving the same). Maybe Experimental has pushed ahead; the latest GE is getting a bit old.

I just played Halo a few days ago on my kde Manjaro system with kernel 6.3 and it worked fine What are you guys running?

Nobara 37 with kernel 6.2.14-300.fsync.fc37.x86_64, running Gnome. Rebar is enabled but I still get weird texture issues. Load times are atrocious (videos directory is in fact deleted), and "server disconnected" when games finish.

use a newer proton, proton experimental is new enough I think, but if you still have loading time issues, then just use proton experimental bleeding edge

Last I tried the latest Proton GE (as Experimental was behaving the same). Maybe Experimental has pushed ahead; the latest GE is getting a bit old.

yes, the last proton ge is too old

Try TKG proton

Just tried GE 8.0-4 (released today), tkg 8.0.45645.20230605, and Experimental (built into Steam) and they all behaved exactly the same in regard to loading/textures/server disconnect (at the end of the match).

Just tried GE 8.0-4 (released today), tkg 8.0.45645.20230605, and Experimental (built into Steam) and they all behaved exactly the same in regard to loading/textures/server disconnect (at the end of the match).

strange, I have no issues and im using an HDD

Yea, this is very unlikely to be hardware, my games are on an NVMe SSD...

I'm currently using proton experimental and suddenly stopped working. It tries to start the game, appears loading and closes unexpectedly.

I'm currently using proton experimental and suddenly stopped working. It tries to start the game, appears loading and closes unexpectedly.

There was an update to Proton Experimental today that seems to have broke things, try switching to Proton Hotfix.

I'm currently using proton experimental and suddenly stopped working. It tries to start the game, appears loading and closes unexpectedly.

yeah they broke the videos :/ (just remove the videos folder)

Switched to proton hotfix worked. Thank you both!!!

abotelho_halo_infinite.tar.gz

Attached a Steam Proton log of me launching the game, jumping into training mode, quitting, into a social skirmish, and quitting. Also included system information exported from Steam.

Hopefully this is helpful in some way. Today I actually moved Halo: Infinite from a secondary disk formatted with f2fs to my OS disk formatted with btrfs. Didn't seem to make a difference.

I haven't seen any note of this in the above thread (at first glance at least) but it appears that video settings such as the frame-limiter and minimum framerate settings do not appear to stick upon being set, but instead require the entire setting menu to be closed and brought up again.

A way to observe this behaviour would be to set the maximum framerate to 60, exit the menus and then set the maximum framerate to unlocked, the framerate limit does not change from 60 to an unlocked framerate unless you open the video settings tab multiple times.

I can try and catch logs when attempting to do this but I'm not sure how much additional noise will be in them.

Another observable issue on my hardware is sporadic frame times when running with variable frame rates.

Locking down the frame rate (see above comment in respects to issues with even doing that) with both minimum and maximum frame rates set to the same value appears to greatly fix frame-times to the point of the game running indistinguishably when compared to windows. Otherwise, you'll notice frame ghosting, and increased input latency.

Again, not really sure how to catch this in a log that would make it usable for debugging purposes.

Relevant system information: https://gist.github.com/ProjectSynchro/f0d4e4f102ca29c71a683ea49dd4df7e

water issues on map forest lmao
and the grappling hook has some serious artifacting on the latest proton experimental (bleeding edge)
also will the slow loading times ever get fixes and texture streaming issues?
this is on mesa 23.1.2 rx 6700 10GB

edit: trying mesa git which is mesa 23.2 at the moment texture streaming seems a lot better and loading times seem around the same or a bit faster idk lol and water is fixed on forest

I complained a lot already about the slow loading times, which partly makes connecting to game not possible. Nobody cares at all as it seems. I stopped playing halo cause it is so annoying, wait 1 or 2 mins for a 1 min game and then wait 1 min to go back to the lobgby with a high chance of a server disconnect message.

People with older motherboards can't even get proper graphics, but it works on Nvidia, so I know the game does not need 4gb video, AMD graphics driver needs to figure that out and vkd3d prob need some features to get the game running good.

I don't understand why your loading times are bad, I play on a HDD and they are more or less perfectly fine, no server disconnects either

People with older motherboards can't even get proper graphics, but it works on Nvidia, so I know the game does not need 4gb video, AMD graphics driver needs to figure that out and vkd3d prob need some features to get the game running good.

Have you tried VKD3D_CONFIG=no_upload_hvv

I'll try it in 30mijs I'll download over, and does it work with mesa 23.2.3

I'll try it in 30mijs I'll download over, and does it work with mesa 23.2.3

it works with any vulkan driver

Did not work, some textures are not working, video files are blurry and have no hands and the gun is blurry

People with older motherboards can't even get proper graphics, but it works on Nvidia, so I know the game does not need 4gb video, AMD graphics driver needs to figure that out and vkd3d prob need some features to get the game running good.

Have you tried VKD3D_CONFIG=no_upload_hvv

Didn't work, so weird Nvidia doesn't have the same problem with the same motherboard, but AMD radv does.

I have been playing Halo Infinite on an ASUS GA402RJ (Zephyrus G14 AMD+AMD) for the past week, and generally it works fine. There's still some "jank" with various UI elements (it feels like texture loading delays, but it's constant, even after I've been playing and navigating menus for a while).

However, I can say that I still have the "post-game-stall and disconnect" issue. It's not the end of the world, but it does add a 2-minute delay between every game that shouldn't be there.

I'm a fairly technical user, I can provide details about how our mesa (23.1.3), or libdrm (2.4.115), or kernel (6.3.10) are built, the exact version I'm testing with, etc. I'm just not sure what's important to look at. Alternatively, if there's some way to capture a more verbose log, I could do that just as the game is ending and supply that?

(Note: I've been using Proton Hotfix since someone mentioned that the newer GE proton builds wouldn't start (and I was seeing the same thing.))

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1619355319

Try proton experimental instead

I didn't try Experimental yet, but the latest GE-Proton-8 worked, and while it still feels a bit slower than on Windows, it was much faster and avoided the disconnect error for both games I tried. So it's in quite good shape for me (and I'm not using any AMD extra env vars or anything, and not on mesa 23.2 yet, so probably even better soon).

GE-Proton-8 did not solve the disconnect error for me.

Game has very slow loading times and IO in general. This includes menus, the game itself (e.g. initial loading screen), loading the gamemode/maps, loading into games (often missing the round start), the aforementioned after-game disconnect, etc.

Monitoring the game in MangoHUD the game almost never reaches more than 10MiB/s read speed and constantly goes back down to 0 MiB/s during loads. This is all on a pretty performant SATA SSD, by the way.

In-game, there isn't much of a performance hit. I can maintain 60fps with occasional stutter.. but the loading times make the game borderline unplayable.

Using Proton Experimental.

Specs:
Intel Core i5-6500
MSI Z270 Gaming PRO Carbon
Radeon RX 6600
16GB DDR4-3200

Debian 12 (bookworm) with kernel 6.4.3-1-liquorix-amd64
Mesa 22.3.6

If there's any info i need to provide aside from this, I can do so

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1632562765

could you update your mesa drivers? (to git would be most helpful)

I can't repro the loading time issues, they are decent even with my HDD. I can't repro the after game disconnect anymore.

could you update your mesa drivers? (to git would be most helpful)

I can't repro the loading time issues, they are decent even with my HDD. I can't repro the after game disconnect anymore.

will look into doing that
not exactly sure how to do that on debian, and google turns up barely any results

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1632562765

To solve stutters I'd suggest switching your mesa to a mesa version above mesa 23.1. I use kisak mesa repo on pop os and it works great for playing games with zero stutters on either dxvk games or vkd3d and you can turn off precaching on steam as well :)

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1632601481

is the kisak-mesa PPA safe to use on Debian? since i know that PPAs have been problematic in the past and the general rule is "don't use PPAs on debian"

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1632610062

Yeah it seems it's not ideal to use ppas on debian and I don't know any ways of switching out mesa on debian besides switching to debian testing

Could any of you who experience the very long loading times try to launch the game with VKD3D_CONFIG=no_upload_hvv %command% in the games Steam launch options?

Could any of you who experience the very long loading times try to launch the game with VKD3D_CONFIG=no_upload_hvv %command% in the games Steam launch options?

Applying VKD3D_CONFIG=no_upload_hvv to my launch options fixed the loading times and the stuttering I was having. Had the best game in months after that. Thanks :3

At first launch it gave me an "Assertion Failed!" error but that happens on occasion anyways and i just relaunched Halo and it worked fine.

Could any of you who experience the very long loading times try to launch the game with VKD3D_CONFIG=no_upload_hvv %command% in the games Steam launch options?

Applying VKD3D_CONFIG=no_upload_hvv to my launch options fixed the loading times and the stuttering I was having. Had the best game in months after that. Thanks :3

At first launch it gave me an "Assertion Failed!" error but that happens on occasion anyways and i just relaunched Halo and it worked fine.

I guess this deserves a PR then: https://github.com/HansKristian-Work/vkd3d-proton/pull/1633/files

I guess this deserves a PR then: https://github.com/HansKristian-Work/vkd3d-proton/pull/1633/files

Poor loading times and performance with ReBar on some devices.

Are we sure this is the case? My ReBAR is disabled (or rather, doesn't exist in my BIOS.) Unless having Above 4G Decoding enabled is essentially the same.

Unless having Above 4G Decoding enabled is essentially the same.

On Linux that usually does the same (at least in my case, but i think it depends on the specific setup) where as on Windows i need both options for ReBAR.
As to why this can be such a massive issue to begin with when it isn't on Windows is something I'll poke the vkd3d-proton devs about.

Can confirm that VKD3D_CONFIG=no_upload_hvv %command% fixed the loading problems for me.

Now I'm still left with one last issue I've had for a while: The game launches in windowed mode instead of full screen for some reason.

Can confirm that VKD3D_CONFIG=no_upload_hvv %command% fixed the loading problems for me.

Now I'm still left with one last issue I've had for a while: The game launches in windowed mode instead of full screen for some reason.

Yeah, If you didn't already know the game doesn't have an exclusive fullscreen mode for some reason.

Yeah, If you didn't already know the game doesn't have an exclusive fullscreen mode for some reason.

it certainly used to. It was only the past couple of months that it's run in windowed mode for me.

Awesome! VKD3D_CONFIG=no_upload_hvv solved it for me as well. It also fixed the issue I was complaining about with LOD staying low for a very long time.

Weather update: the Assertion Failed error happens much more frequently with no_upload_hvv. After a few launches it usually works but the long initial load persists.

I tried logging, the log was 1.3gb...

Also confirming VKD3D_CONFIG=no_upload_hvv works shockingly well here. It also seems to have solved this small problem I had when rotating models/characters in the Armor Hall would make them flicker like crazy. Totally smooth now.

Although this begs the question as to why disabling rebar would solve this. People were suggesting turning rebar on not that long ago.

Also confirming VKD3D_CONFIG=no_upload_hvv works shockingly well here. It also seems to have solved this small problem I had when rotating models/characters in the Armor Hall would make them flicker like crazy. Totally smooth now.

Although this begs the question as to why disabling rebar would solve this. People were suggesting turning rebar on not that long ago.

You still need rebar for correct LODs, but this just disables some vkd3d optimizations when rebar is on that are apparently causing lots of issues in this game

CPU: i5 12400f
RAM: 16GB
GPU: RX 5600XT
SSD: 512GB
OS: Linux Mint 21 XFCE
Tried all versions of proton and fail.
Log: https://pastebin.com/eH0BaFMc
I run Halo Infinity, in steam it shows that the game is running and after 3 seconds the game will close.
How to fix it?

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1645395375

What mesa is installed? Linux mint has a relatively old version of mesa I think so I would swap it out for kisak mesa fresh and then try again. If you wanna check what mesa version your running do glxinfo -B in your terminal. Idk if the kernel rlly matters as Linux mint also has a relatively old kernel because of its stability.

@pollux56 Mesa 23.1.0-devel

Halo Infinite

Issue transferred from https://github.com/ValveSoftware/Proton/issues/6943.
@ofili-1337 posted on 2023-07-21T08:45:47:

Compatibility Report

• Name of the game with compatibility issues: Halo Infinite
• Steam AppID of the game: 1240440

System Information

• CPU: i5 12400f
• RAM: 16GB
• GPU: RX 5600XT
• SSD: 512GB
• OS: Linux Mint 21 XFCE
• Driver/LLVM version: amdgpu 23.10.2
• Kernel version: 5.15.0-76
• Proton version: 8.0-2

Proton LOG:

https://pastebin.com/eH0BaFMc

I run Halo Infinity, in steam it shows that the game is running and after 3 seconds the game will close.

@kisak-valve https://gist.github.com/ofili-1337/03c59786679bf70b9bd4a06f92ca3e85

@kisak-valve what are those launch options?

I forgot to say. I still have Windows 10 next to Linux Mint on 1 single SSD. Does it somehow affect?

@kisak-valve what are those launch options?

I forgot to say. I still have Windows 10 next to Linux Mint on 1 single SSD. Does it somehow affect?

there's no launch options, all you have to do is uninstall amdvlk and install the mesa-vulkan-drivers from the linux mint repos

@Etaash-mathamsetty how to remove them?
I have Mesa 23.1.0 installed

there's no launch options, all you have to do is uninstall amdvlk and install the mesa-vulkan-drivers from the linux mint repos

how did you install them, amdgpu_install script or something else?

amdgpu_install script

amdgpu_install script

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1646007769

oh god, never use that thing, ever, install packages only through PPAs and packages maintained by your distro (unless you know what you are doing)
for AMD cards the drivers are included with the distro anyway,
anyway, just use script to remove it

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1646010880

I remember that I downloaded the AMD driver from the official site

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1646012415

yeah those drivers are literally crap, don't use them. Uninstall them and use mesa-vulkan-radeon via apt install

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1646012415

Here's a tip drivers are already preinstalled on Linux for amd and Intel gpus. so there is no need to grab those drivers :)

The only thing you may want to change is the mesa part of the radv drivers so that you have gpl which seems you already have 23.1 installed. And for rt things it seems that will be included in 23.2

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1646015121

I think it's better to reinstall Linux Mint. After reinstallation will it be necessary to install mesa or not?

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1646018520

Mesa is preinstalled on Linux mint but a rather old version of it so it's best you install kisak ppa of mesa fresh :)

You can grab it here
https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa

@pollux56 @Etaash-mathamsetty Ok. I try. There seems to be Linux Mint released 21.2.

@pollux56 @Etaash-mathamsetty
do I need to install these files? or how?
delete the old mesa before installation?

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1646031699

No no, what you do is add the ppa to your distro like Linux mint then just update like usual either through the terminal or on the Linux mint store and it will do all the work for you.

It says on the website how to add the ppa but here's what you do

sudo add-apt-repository ppa:kisak/kisak-mesa

Then do sudo apt update and sudo apt upgrade

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1646041790

thx

@kisak-valve Are your drivers compatible with new Linux Mint 21.2?

@kisak-valve Are your drivers compatible with new Linux Mint 21.2?

they should be

Does anyone experience poor performance in the campaign and big team battles ?
At least on nvidia there seems to be barely any gpu usage and framerate remains low, as if there is no proper utilization. It is good to note that this is the only game that does this, all the other dx12 games are fine.

Operating System: EndeavourOS
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
Kernel Version: 6.4.6-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor
Memory: 31,2 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3090/PCIe/SSE2

Replying to https://github.com/ValveSoftware/Proton/issues/5030#issuecomment-1656550965

Yes this is an issue with Nvidia specifically. It's been over a year and they still haven't fixed it fully

I was consistently getting "Could not find a data center suitable for all members of your fireteam. This is often due to network connectivity or latency issues." when attempting matchmaking using a self-built kernel. The stock Ubuntu kernel worked fine.

Eventually, I figured out that it's because I did not have IPv6 support compiled into the kernel (CONFIG_IPV6=y). Hope this helps someone save a few hours of troubleshooting.

For completeness:

Compatibility Report

• Name of the game with compatibility issues: Halo Infinite
• Steam AppID of the game: 1240440

System Information

• GPU: NVidia RTX 4080
• Video driver version: 535.86.05
• Kernel version: 6.4.7
• Link to full system information report as Gist:
• Proton version: 1690908628 experimental-8.0-20230801

I confirm:

• [ ] that I haven't found an existing compatibility report for this game.
• [X] that I have checked whether there are updates for my system available.

Symptoms

Matchmaking immediately returns "Could not find a data center suitable for all members of your fireteam. This is often due to network connectivity or latency issues.", shows status as Offline.

Reproduction

1. Run Halo Infinite on a kernel with IPv6 disabled.
2. Attempt matchmaking.

proton exp bleeding edge beta should have the patch that enables no_upload_hvv by default now. it trades a little bit of perf for the much better loading times, hopefully nobody gets mad about that lol

proton exp bleeding edge beta should have the patch that enables no_upload_hvv by default now. it trades a little bit of perf for the much better loading times, hopefully nobody gets mad about that lol

yeah ill take the little bit lower performance over loading times as loading into a game takes around 9 seconds now :D

also seems like how textures are loading on halo infinite are fixed! no longer do i see polygon textures being loaded into on the main menu or in game with other players in the intro or outro :)

proton exp bleeding edge beta should have the patch that enables no_upload_hvv by default now. it trades a little bit of perf for the much better loading times, hopefully nobody gets mad about that lol

out of curiosity, does the "patch" you refer to simply force no_upload_hvv by default when it sees the Halo Infinite AppID/Exe name? I'm wondering about such "quirks" lists work, how they "match", and how they're maintained vs "fixed" in game, vs "fixed" because of some deeper bug, etc.

proton exp bleeding edge beta should have the patch that enables no_upload_hvv by default now. it trades a little bit of perf for the much better loading times, hopefully nobody gets mad about that lol

out of curiosity, does the "patch" you refer to simply force no_upload_hvv by default when it sees the Halo Infinite AppID/Exe name? I'm wondering about such "quirks" lists work, how they "match", and how they're maintained vs "fixed" in game, vs "fixed" because of some deeper bug, etc.

Not sure what you are talking about in the second portion, but yes it's a quirk, a game specific patch

for some reason recently the game just crashes after a few seconds past the "press enter" screen. did anyone figure out what was causing that? I also cannot get a single thing to open with any proton 8 version, including GE or experimental. that is off topic but if its related let me know

for some reason recently the game just crashes after a few seconds past the "press enter" screen. did anyone figure out what was causing that? I also cannot get a single thing to open with any proton 8 version, including GE or experimental. that is off topic but if its related let me know