Asenna Steam
kirjaudu sisään
|
kieli
简体中文 (yksinkertaistettu kiina)
繁體中文 (perinteinen kiina)
日本語 (japani)
한국어 (korea)
ไทย (thai)
български (bulgaria)
Čeština (tšekki)
Dansk (tanska)
Deutsch (saksa)
English (englanti)
Español – España (espanja – Espanja)
Español – Latinoamérica (espanja – Lat. Am.)
Ελληνικά (kreikka)
Français (ranska)
Italiano (italia)
Bahasa Indonesia (indonesia)
Magyar (unkari)
Nederlands (hollanti)
Norsk (norja)
Polski (puola)
Português (portugali – Portugali)
Português – Brasil (portugali – Brasilia)
Română (romania)
Русский (venäjä)
Svenska (ruotsi)
Türkçe (turkki)
Tiếng Việt (vietnam)
Українська (ukraina)
Ilmoita käännösongelmasta
Hosting custom games may invoke different NAT rules, causing the issue as well. There may be a base-windows service that just doesn't exist on your linux machine, so it crashes. but we don't have any documentation for it - so its just a guess. If Proton has a clean-boot option similar to windows, you can see if something is conflicting with MCC when it happens - or if you are aware of your network setup well enough, you can compare it to a normal windows environment.
You can also check the steam deck patch notes for anything useful
https://support.halowaypoint.com/hc/en-us/articles/14589112499348-Halo-The-Master-Chief-Collection-MCC-Steam-Update-April-2023
Primarily, joining groups with people on other OS's causing crashing. No guarantees there, but something to think about.
Lastly, you could submit a bug report to see if there anything official support can offer - though I know its unlikely.