Hello.
Does this not happen with wined3d?
If it doesn't then does this also happen with regular proton experimental which uses official dxvk and not the async version (tho i can see from your log async isn't specifically enabled). Also might be worth testing proton 7.0-5 which uses a dxvk version based on 1.10.3 and not 2.0

okay, lemme try with proton exp, i'll keep you in touch.

It also happens with proton experimental and proton 7.0-5, too. Maybe it's not DXVK, then...

They will still use dxvk by default.
To test without dxvk launch the game in steam with PROTON_USE_WINED3D=1 %command%

Nope, still happens, even with PROTON_USE_WIND3D=1 %command%... I'll make an issue on the proton github page. thanks for the help !

No problem. Hope you figure out your issue

Edit: i see there is a typo in the env var you posted. I made that typo at first before correcting If you copy pasted

Holly molly, yeah, it was a typo, thanks ! Indeed, after correcting it, ram usage stopped skyrocketing. So maybe it is dxvk...

@SpidFightFR are you able to make a apitrace? You can find a guide here https://github.com/doitsujin/dxvk/wiki/Using-Apitrace

If done together with dxvk in proton all you have to do is to dump the DLLs next to the exe and launch. Tho dunno if it's better to do it without dxvk in a case like this.

Hello, sorry i'm late, i tried to move the DLLs into my game files, but there's no apitrace files in the desktop folder of the game pfx... I think i'm making it wrongly...

If you are trying to make it with wined3d and not dxvk then you need to add wine dll overrides in your steam launch options WINEDLLOVERRIDES="d3d11,dxgi=n,b"

But it works with wined3d, the ram stays at 8Gb of usage, while with dxvk, it jumps to 24Gb and eventually crashes the pc.

Yes the devs will try to replay the trace locally with dxvk on top to see if anything sticks out.

But if you can get a trace recorded with dxvk also that would be great. There you should just be able to dump the 3 dll's (remember correct bit version) next to the exe and launch. Remember to remove PROTON_USE_WIND3D=1. (yes i know i already said this, so just repeating and adding extra notes to make sure)

Okay, i'll check on PCGamingwiki to make sure i have the correct bit version and all. I'll keep you in touch. thanks again for the help.

Okay so i tried to put the dlls, both in the MCC.exe folder and Halo1 folders, but nothing worked, in the prefix folder, i don't have a file created.

Btw i looked at the wiki and it asked for winecfg or something, i don't have access to this command, is it normal or i need a package to log the apitrace ? (Sorry i'm a noob)

winecfg comes with regular wine installed through your package manager. But the env var WINEDLLOVERRIDES="d3d11,dxgi=n,b" should work fine in steam without when using wined3d and shouldn't be needed when using dxvk (tho doesn't hurt either).

I don't have wine installed using my package manager, i only use the tools given in proton or proton-GE so i guess it's normal.

Yet, despite many attempts, and trying to run the game with the env var and all, with or without dxvk, the .trace file doesn't appear in comptdata/{gameid}/pfx/c_drive/users/steamuser/desktop, like said in the wiki you sent earlier... It drives me nuts...

Hello again.
So i've been able to reproduce this and did a bit of searching. It seems to be a game bug introduced in the latest game update and also happens on Windows with the devs being aware and looking into it. See https://www.reddit.com/r/halo/comments/zfyd6u/the_new_mcc_update_has_an_issue_with_memory/

Besides dxvk on Linux i could also reproduce with wined3d, but it happened alot slower (maybe because my performance was horrible) so took alot longer for memory to slowly climb up.

Hello, interesting…
Okay, i’ll close the issue then. Thank you so much!