Instalează Steam
conectare
|
limbă
简体中文 (chineză simplificată)
繁體中文 (chineză tradițională)
日本語 (japoneză)
한국어 (coreeană)
ไทย (thailandeză)
български (bulgară)
Čeština (cehă)
Dansk (daneză)
Deutsch (germană)
English (engleză)
Español - España (spaniolă - Spania)
Español - Latinoamérica (spaniolă - America Latină)
Ελληνικά (greacă)
Français (franceză)
Italiano (italiană)
Bahasa Indonesia (indoneziană)
Magyar (maghiară)
Nederlands (neerlandeză)
Norsk (norvegiană)
Polski (poloneză)
Português (portugheză - Portugalia)
Português - Brasil (portugheză - Brazilia)
Русский (rusă)
Suomi (finlandeză)
Svenska (suedeză)
Türkçe (turcă)
Tiếng Việt (vietnameză)
Українська (ucraineană)
Raportează o problemă de traducere
But for Linux itself it seems particularly unstable. When I was using Bazzite the game *would* but only if I didn't use Proton at all, but then it would crash randomly during gameplay.
But as noted, the game itself is just an unstable mess. On my end, I was ablet o play without issue for hours, stopped playing and put my device to sleep, and upon trying to play again would crash at the start of every hunt. As far as I can tell, the game didn't randomly update without telling me but the game no longer works. So I think this is just how the game is.
Maybe some functioning neurons would help.
OP, have you tried switching to Bleeding Edge Experimental? That's the only way I got it to run on my machine. Linux Mint Cinnamon, btw.
I also had the suspicion that my save file might be corrupted since it only ever crashes after trying to load that but it crashed just the same after trying to start a new save file
anything in journalctl after it crashes ?
Last hope is this : if you remember WHEN the game worked, use Timeshift to roll back your OS to that day and stop/pause the updates for now. If the game worked fine before and now it doesn't, chances are the OS did some update that broke something, because the game works fine on Mint.
If nothing seems to work, move to Mint. Arch is many things, but stable is many times not one of it. Game works on Mint with Proton Experimental since release, to this day. Or some other stable distro, not a rolling one.
journalctl --since "00:00:00"
replace the zero with time hh:mm:ss otherwise you will get a massive output from multiple days. I say the last 5 mins from the time crash occurs should be plenty.
also run dmesg to see if anything crashed on the kernel side of things, you would expect a driver failure there if anything but possibly journalctl will give you the same plus more.
If you want to share it here use https://pastebin.com/ since it will be easier than putting the whole thing on steam discussion or you might be able to figure it out yourself if the error is straight forward enough if any.
https://pastebin.com/ygrPU0h2 (stuff before, probably unimportant)
https://pastebin.com/24WsAXQz during the crash
I can only understand what is happening to a certain extent but the crash message
"Mar 13 09:09:05 PIKAPOWER kernel: Out of memory: Killed process 10069 (MonsterHunterWi) total-vm:22989524kB, anon-rss:4565060kB, file-rss:844516kB, shmem-rss:10216kB, UID:1000 pgtables:22944kB oom_score_adj:200"
seems to imply that I have an issue with ram or vram? My GPU has 16GB VRAM but it might actually be my ram. One of my ramsticks LEDs didn't turn on anymore but after checking the available memory via "free -m" it showed me I still had the full 16GB. I checked again just now and it only is 8GBs so it might be fully broken now.
I'll see if I can fix that or whether I have to fully replace it. But please do lmk if there is anything else looking suspicious in the pastes
And Aldroen ty for recommending journalctl, it will be really useful for pretty much anything I do in the future