War Thunder Vulkan
Clide Birkner
A few seconds after the game opens and begins loading assets I get this error with some references from a call stack, which seems mostly useless other than providing that it's some issue it's having with Vulkan. I haven't seen any other references to this problem, past or present. Not entirely sure where to go from here, other than looking through journalctl, so if requested I will provide that.
My best guess would be either something weird with a Mesa package, or something in the game itself. There haven't been any reports on the War Thunder Reddit yet from what I've seen, so I would assume that it's an issue with my own configuration rather than with the game.
Now it crashes my entire X11 session when I attempt to open the game. Some added context is that it was already causing problems by freezing plasmashell most of the time, but this was an easily remedied problem so I ignored it. I believe this is the important part of the journalctl:
This is the journalctl logs from a crash where the game crashed all of my graphics processes, and I'm pretty sure OS as well.
Not entirely where to go from here. This has happened multiple times, with about a 50/50 chance of it just crashing/freezing KDE, or crashing/freezing my entire computer.
Running theory now is that it's attempting to call an nvidia driver, which should not happen as I'm on a full AMD system. I think I have some nvidia stuff installed for build tools, but I will see if uninstalling them fixes this issue.
Also, I did some more testing and found that the error does not occur when using the RadV vulkan driver over the Pro and AMDVLK drivers. More info here if anyone else shares the same, or a similar issue in the future.
I recently downloaded War Thunder for Ubuntu and tried to get Vulkan to work because I have low FPS with OpenGL. I used this guide _run_war_thunder_with_vulkan/. The only thing I didn't know how to get to work was the "-forcestart -driver:vulkan" for the shortcut.
Everything works fine until after the game tries to connect to the servers. I then get this error. I tried removing the cache file and reinstalling the game so far. Please note that I am a beginner when it comes to Ubuntu.
I don't believe vulkan is at all supported, and according to some people here one of the recent updates completely broke the workaround people used to get it working (I experienced extreme client instability with it, so just stuck with OpenGL, even though it sucks, comparatively speaking).
Anyway. I heard the AMD Rx 5700's are out performing the nvidia chips. ONny thing. You need PCI 4.0. I haven't tested any of this, but new NVIDIA graphics cards should push the price down with in the next 2 years.
Notice I reset gamma a few times, that's because without gamma adjustments (to 0.72 ish), my screen gets too bright and the LCD OSD is not easy to adjust so I do it via nvidia drivers (that you can't use when kwin is down btw).
I would go back to the 450 long run driver. There is nothing in the 455 that benefits War Thunder. It doesn't say anything about War Thunder in patch notes. I tried them both and get no difference and now I am back on 450. All the same bugs. Flickering shadows in hanger. Vehicle is kind of like a flash-light lighting up world as I go around and to much contrast outside of that. If i let it sit for long time I can get a few battles that are all right. I 've had to reinstall everything a lot in the last few weeks. Having so many issues, but this game seems to work still. I get errors like that... Restart... update, try again later. Over and over again until it works.
I saw that. It has normal non x gddr6 and they sync it especially with ryzen5 to get more bandwidth out of memory, so to get promised performance as advertised I think you would need ryzen5? idk don't trust it.
The updates that broke my systems on last trying arcolinux D and B had hundreds of MB , because were the first ones after install the rolling realease systems. Again not sure what part of them mess it. I have read that deepin 20 is the culprit...
Very recently (as of today, I played yesterday) the game dies after "updating vulkan shaders". As in, steam tries to launch it, and then it just immediately dies with no indication of why.
I'm not even sure how to begin to troubleshoot this, but since this game is getting me through covid, I'd really like to get it fixed.
I am playing via steam on ubuntu 18.04
I just tried my Steam WT install and it's now doing the same as yours. I will investigate this issue, In the mean time as a workaround, You should be able to launch the game directly by going into your main "WarThunder" directory (Located here for Steam installs: .local/share/Steam/steamapps/common/War Thunder) and execute the "launcher" executable. Double clicking it should work or running "./launcher" in a terminal in the same directory.
Thank you ! Ok, so that's got me halfway there, but has revealed another problem.
I have dual 4k monitors. I reinstalled the game while trying to get this to work. It blew away my video config.
Previously, I had done what you recommended here:
Then the game launches, but when I'm done playing, exiting the game also doesn't work. I'm forced to go back to the command line and use CTL-C to terminate the application. Any ideas? Any more info you need from me?
EDIT: I added a "steam_appid.txt" file with the game's appid to both the base game directory and "linux64" directories, but neither changed the outcome: the game still won't launch unless I do so from the command line.
WT is installed and played through Steam
Almost a year no problem, but suddenly now the launcher simply does not launch the game.
After reinstalling the game starts from desktop shortcut (and I can play) just ONLY ONCE !!
Second attempt to start - nothing.
No new .clog or .dmp or other logfiles appear. Only thing what I can found, is few rows from syslog and kernel logfile:
A work around if you can't get the launcher to work is to use the outdated launcher in `./update/bak`. Not sure if it helps but it worked for me. Also doesn't have the crash that occurred under the most recent launcher.
In the Meantime I played around with Proton 5. 13 -2 or the Steam Linux runtime. With Steam Linux runtime nothing happens when I try to start War Thunder. If I try the same with Proton 5. 13-2 it says the launcher.exe is missing. Maybe this is a helpful thing.
I can kill the process with a CTL-C from the CLI. Only the "aces" executable in the "linux64" directory will launch the game. This may be an issue for me if an update is pushed and my game is no longer compatible. Just an FYI.
5. Game Launcher displays, but the entire screen goes "Blank" so I have to [ALT][TAB] to another open window or hit the [Win] key to show the desktop. The screen isn't really blank, its just 'hogged up' by the game launcher, so every time I make a selection on the game launcher the screen goes 'Blank' I usually don't hit anything other than 'Play' anyway.
Yes, I have a GTX 970, and I was equally confused by the output. I only saw it because you said the "launcher" executable should work, and I hadn't yet tried it. Hence, why I included it. Here's the important specs from screenfetch:
Right, Not sure whats going on there then, When you start the launcher directly and the screen goes black the launcher is still working in the background, If you Alt+Tab to a different window the launcher should display, It only turns the screen black when in focus. So if you start the launcher, Alt+Tab away and let it finish, Then click the "Play" button it should start the game fine.
Launching the "launcher" executable in your main "War Thunder" directory should work, Although as your DE is Cinnamon you might get the black screen issue, If you do what I have said above in this post you apply to you as well.
Right now, after update game is covered in black screen same way as launcher rendering it unplayable. Looks like is rendered under black screen covering screen. Content is visible in app preview in task bar and is clickable (sounds etc work).
c80f0f1006