My first screenshot of the crash was taken on July 11th. I suspect the problem might have been caused by update 2.47.0.51, but I’m not sure. I was playing the new French tank MSC at the time not ARB. The 2.47.0.43 update is definitely clean, and one of the updates after that is the problem.
The version of the graphics card driver is 25.6.1 and I never thought of downgrading it to the previous version because if there was such a solution, someone would have said so by now and I think some NVIDIA users are having the problem too. If you want, I can try the unstable version 25.6.3, but I don’t think it will work.
I don’t think it’s related to a specific napalm or if it’s higher than a certain amount of explosive, but I can perform such a test if the developers want.
I have no contact with the DEV’s and very little insight into how the Tech mods handle things, best to ask the Technical Moderators if they want/need any more information to help narrow down the cause. I think @Piciu713 said to contact him if there were any further questions on this specific issue.
It doesn’t have to be directly related to the munition itself, it might be some particle effect that comes with it.
I have same problem after Leviathans major update to Update 2.47.0.72
crash game after enter battle and playing around 3-5 minute on Air battle and on ground battle crash happen after respawn.
try DX12 and DX11 , reinstall game, update driver, reinstall windows 10 same problem.
i see the common thing between users they have AMD GPU and I have one.
any updates on this bug?
AMD R7 5700X3D / 16GB RAM / RX 9700XT. Started like a month ago with an update from War Thunder. No blaming AMD drivers/Windows.
Many stating issues with napalm but I am not using it. Maybe fire/particles?
I had that happen in a battle - guy in TO-55 started flame thrower and I crashed* right away. 5800X3D, 9070XT Red Devil. Temps all fine. Restarted system and haven’t had it since, not sure what causes it.
Sending in more reports is in vain and steals only time. Do you really believe, that Gajin cannot reproduce this error on their own? Or do we have to start funding, so that Gajin can effort some PC Setups?
@Necronomica Not your fault, its bad communication from the devs or whoever can tell abouut the state of affairs.
Well, firstly; it’s almost never as straight forward as it seems when it comes to bugs.
I gave a short examples and explanations in this thread above:
Imagine if an issue only happens with a specific generation of graphics cards and only if they are used together with a specific generation of CPU that is on a specific bios and specific driver version for the graphics cards. And the issue only happens if the PC also has one specific program running in the background. It’s going to be quite literally impossible for anyone to reliably reproduce that issue if you don’t give them crash logs, system information files and things like that. The more files that are sent in the easier it will be for the dev’s to then see what all the systems have in common and at what point in time the issue happened (down to the millisecond due to how fast todays systems are) to then narrow down a source of the issue. And all that is just to find it, then you have to also fix it and that is an entire issue in of itself. Sometimes it’s even an issue that can’t be fixed on their end and they have to contact the manufacturer of that component to have the issue fixed in their drivers for example.
Additionally, once it’s fixed they have to test it extensively to make sure it works and hasn’t broken 7 other things that used the same function before actually sending the update to the live servers.
I gave an update a little while ago:
I don’t think they like giving statements while in the middle of things as that just risk leading to false hope and confusion. “Ah yes we think it’s this that is the cause” and then three days later “it wasn’t that and now we are back to square one” , “it might be this instead” , “nope, wasn’t that”.
It’s just going to create confusion as players will read the old messages and think “they found the cause three weeks ago why isn’t it fixed yet?” and things like that. Not the best idea.
I cannot play tank modes because it will freeze when I try to spawn in. It is not occasionally crashing, currently the game is literally unplayable since I crash 100% of the time.
Yesterday 04/08 I was playing air sim battles on dx12 without crash, just noticed a new driver appeared for AMD users. I think it could help, today I am gonna test if i get any crash.
to log on gaijin account on steam just play the game on steam, disconnect internet, when game log u off, connect it back. type your account ID and password, check autologin, and here you go
