Yeahhh this a common problem I find incredibly frustrating. Pains of being an early adopter. Good to know the Proton version works, I was debating on trying that to see if the problem exists there but the aforementioned AC issue is what primarily stopped me. I still have my doubt the original error was strictly a Mesa issue and was Warthunder interfacing with it in strange ways that happened to strike a mine.
Admittedly I don’t really have much to back this up other than as I mentioned before I currently see and at the time saw no other game inducing this problem despite other games being more demanding. Sample size of one and all.
Right, Thank you. When do you normally get these crashes? A few minutes into playing, After an hour or more, etc.
It should be located here regardless of if you have it installed via steam or run it directly from the launcher:
~/.config/WarThunder/.game_logs
Unless you have either WT or Steam installed via Flatpak, In which case it will be located in that directory in the Flatpak’s directory. Which should be something like:
Here’s where it gets weird, as I tried an experiment as well. Timing itself doesn’t seem to have much of an impact as how many matches are played. I noticed that it usually triggers somewhere between 4-6 matches, usually when entering the match but on occasion at the end. One thing I also noticed is I decided to try periodically restarting the game and noticed this did not seem to break the pattern whatsoever. This is when immediately restarting, waiting a few hours between shutting the game down and starting it back up, and one time I even waited a full 24 hours. It almost feels like the sudden unload/loading of assets in the loading screen is somehow triggering this.
One other thing I noticed, when the crash happens it tends to black out the screens specifically on my dGPU which the game is running on. In the time period of these crashes I recently swapped one of my monitors over to my iGPU and noticed it does not follow this behavior, the last image on that monitor stays on screen, though all screens connected to the dGPU do black out as well.
Somehow I missed checking the config directory, rookie mistake. I’ve zipped up all the files in this directory including the dmp files as well. Going to be 100% honest I don’t remember which dates were full crashes and which ones were times where I got off normally however. The file size is hovering around ~550MB which is over the file upload limit here. Do you have a preferred place for me to upload this file to?
Had the same I believe, can’t recall the exact error code but what you describing basically. After few games crash out of nowhere. Sometimes stable for hours.
Switch to steam version solved the issues for me.
Steam Linux Runtime, no proton nor GEProton.
Launch option with gamemoderun on.
That’s incredibly odd that running it through their run time fixes it. I’ll have to give that a go, thank you.
Thinking on it more, the run time uses Debian as a base, meanwhile everyone in here so far has reported this on Arch… That would make a lot more sense if there’s something different with how Arch handles GPU interactions that Dagor /really/ doesn’t like in some situations
At this point I’m willing to take any option. Catastrophic crashes are massively disruptive to other things I do on my system lol
I’m kind of wondering if this is the same error I saw on Endeavour, and somehow some of the changes Cachy makes are what’s pushing it over to a catastrophic crash as opposed to an app crash
Yes thank you for forwarding them, the bug manager #1 does their job its just as if the devs refuse to acknowledge linux specific problems.
I am always on the cutting edge with the drivers, update them every day and currently on driver “Nvidia 610.43.03”
The real question is what does “Forwarded” mean? Do the devs have any incentive to take a look at these at all? One bug was accepted 2 years ago(bug reporting manager #2 didnt chime in at all), another nearly 3 months now with 49 people clicking “I have the same issue” yet its radio static. How about this, none of these issues exist on Proton compatibility layer, could you maybe try to talk to the devs to enable use of BattlEye anti-cheat through proton? I would be using BattlEye if it wasnt for the anti-cheat not initilizing properly and locking me out of 95% of the game.
Why does gaijin insist on having a native client if they refuse to maintain it? They can just make sure proton works and leave it like that…
This is a very common issue with Linux gaming as well unfortunately. IIRC Steam doesn’t allow you to advertise your game as Linux compatible if your game needs Proton to run on Linux.
On the other hand however, the Linux client for Warthunder did release far before Proton entered the scene.
I’m pretty sure it’s a client fault, not distro specific - I spent lot of time trying to fix this. Saw bug reports existing for a long time and unresolved. So many ideas and tries to find/overcome the pain point that I lost the count.
No worries, just curious. Debian tends to handle update cycles very differently from Arch and Fedora based systems, often holding back feature updates in favor of stability.
I wouldnt know since i’ve been using linux only for about 6 months so I am a newbie by all means.
When I realized the bunch of bugs I was ready to report all of them uuuuuuntil i realized the developers barely even checked them and any further time I would spend filing bug reports would be wasted time as they would go down the pit of unresolved issues. Its really annoying, this half commitment of gaijin everywhere. Simulator game mode gets the same treatment as the linux client lol.
Also here you guys go, another game breaking bug.
Each time you alt tab there is a 1% chance the game stops just rendering. The sounds keep coming but the screen is just empty. Only fix is restarting the game. Also doesnt happen with proton btw!
Dont worry the recording isnt broken you are seeing exactly what I see when this happens.
I feel like if i report this this will also just go ignored so I never really bothered.
Welcome to the penguin! We all start from somewhere. This kind of treatment like I said is unfortunately common from larger studios/publishers however. The more profit driven the more likely Linux versions are neglected per the previous marketshare issue.
Proton has really alleviated this issue a lot but has unfortunately also incentivized “lazy” support for Linux simultaneously lol. Anticheats are really the only thing that majorly screws with Proton support these days
Interesting, By the sounds of it then your GPU driver is perhaps also crashing. By the sounds of your other posts you are running the WT client directly and not through Steam, etc right? Please let me know if running it through Steam Runtime stops any of the crashes or changes anything.
I don’t particularly need any of the files right now, I was just wondering if the .dmp files lined up with any of and if so which crashes you are getting.
Right, Have you tried the latest Production Branch version (595.91.07) of the Nvidia drivers just to see if the crashes happen with them as well?
Forwarded means a report has been forwarded to Gaijin’s internal bug tracker. Gaijin are not refusing to maintain the Linux client, There has been a lot of Linux specific bugs fixed and a lot of work on the Linux client to get it where it is today.
I will just say to all three of you, If you are experiencing any crashes that produce a error message, Then please always send the crash reports through the crash reporter that pops up after the crash as this helps the Devs know what crashes are still happening and how many players are affected which is very useful information to have.
Also please submit a report for any of those types of crashes that produce a error message as well on the Community bug reporting platform:
That’s what I was thinking as well. Something going whack in the game that cascades out to the driver which then just causes a panic. I’ve redownloaded the game through steam and using that run time, currently it’s 1.0 Scout as it’s not letting me select any other. I have noticed performance improved dramatically, like 40FPS on average (~140 to ~185)
Funny enough I did try this, dies every time. I keep forgetting the other one exists, will do.
Yep, I know brick mentioned earlier that Proton performance seems to be noticeably higher than the native version, was weird to see that kind of spike from the runtime version however.