It is september and stll no fix ? Having the same problem with different LINUX Distros and diffent hardware.
Shortly after joining a gound battle the game hangs with 1 FPS for about 5 seconds returns to normal for about 5 seconds hangs for about 1 second and with disabled V-sync runs with 500+ fps till the next game starts.
Ryzen 9 7950X3D
64GiB Ram
RTX 5090.
1 Like
8 month with this issue and still Gaijin doesn’t care…
1 Like
same issue
I have this same issue as well. I normally only play Realistic Ground Battles and accidently played some Arcade battles and noticed, this issue didn’t appear at all - Strange how it’s only in the realistic battles.
Hello everyone,
This issue should be fixed with the latest update (2.49.0.25) so could you all please let me know if any of you are still experiencing this issue?
I’ve done a couple of GRB matches and haven’t gotten the 5 second freeze so it seems to be working for me at least.
1 Like
Hello, I can confirm that the main freezing where my OS usually ask me to kill the game is no longer present. However there is still a smaller freezing at the start of the game of around half a second, much better experience overall, thank for finally fixing it!
Right, Thank you for confirming it’s been fixed for you. Could you please submit a bug report regarding the smaller freeze you are still getting?
https://community.gaijin.net/issues/p/warthunder
Making sure to follow the reporting guidelines and include all the required files and information. Including a .clog file with the performance profiler data included and the .dap files that are created.
1 Like
Nope, the issue still present for me. Ground rb start of match and 5-10 sec freeze if lucky only 2-3. Im using steam to access the game, since recently warthunder launcher also fails to boot on linux for me.
Could you plese post your system information from the inxi -F command? The freeze that was fixed was a very consistent freeze around 5 seconds long so you might have a different issues.
looks like they finely fixed it (there is still a single freeze but its extremely short so i could live with that)
Hey guys , this seems to be the cause of the issue for me
here is some general info
War Thunder (Linux client) - using legacy launcher from compatibility settings
System Context
Linux system with hybrid graphics (Intel iGPU + NVIDIA dGPU)
NVIDIA proprietary driver
Steam Linux Runtime (Legacy)
Use of gamescope, PRIME render offload, and Vulkan
Root Cause Summary (Exact Issue)
The issue is caused by a GPU context deadlock during Vulkan device initialization, resulting from improper interaction between NVIDIA PRIME render offload, gamescope, and Steam launch options.
Specifically:
Incorrect process wrapping
The game was launched with an invalid command order, causing Steam to invoke the game binary more than once.
This led to undefined behavior in the graphics initialization stage.
Hybrid GPU ambiguity
The system exposes both Intel and NVIDIA GPUs.
Vulkan attempts to enumerate multiple physical devices.
The application intermittently binds to conflicting GPU contexts.
Vulkan synchronization stall
During match loading, War Thunder submits Vulkan command buffers to the GPU.
Due to GPU ambiguity, the NVIDIA driver waits for a response from a context that never resolves.
The application enters a blocking wait state (deadlock) instead of crashing.
Absence of fatal error
No segmentation fault or assertion failure occurs.
The process remains alive but unresponsive, producing a freeze rather than a crash.
Why the Freeze Occurs at Match Start
The hangar/menu uses light GPU workloads
Match start triggers:
Full Vulkan pipeline compilation
Shader cache usage
High GPU synchronization
This is where the hybrid GPU conflict becomes critical.
Contributing Factors
PRIME render offload without strict GPU isolation
gamescope introducing an additional Vulkan layer
NVIDIA Vulkan driver sensitivity to multi-GPU enumeration
Steam Runtime and host library boundary differences
Corrective Direction (High-Level)
The issue is not hardware-related and not a performance limitation.
It is a graphics stack coordination failure.
But the way i fixed it was using these launch options from steam
__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia __VK_LAYER_NV_optimus=NVIDIA_only gamescope -w 1920 -h 1080 -r 60 -f – %command% -USEALLAVAILABLECORES -threads 8
keep in mind i am on a arch + hyprland , this also fixed the fullscreen issues
hope it helps !