Speak of the devil… just played 8.3 USSR - TO-55 flamethrower =
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.
Try these things to see if it fixes it for you: (So is DX12 crashing never gonna be fixed? - #84 by Necronomica) at first glance it sounds like you are having a different issue than most here are having.
They label it fixed.
The fix well be applied to the next update.
https://community.gaijin.net/issues/p/warthunder/i/MpKt50MRU72E
Ah nice. I was getting fed up of all the email notifications so had turned off the notifications so hadnt seen that yet.
The million GE question will be if it actually resolves the issue or not
Thank god. Hopefully I will be able to play FSR native AA without constant crashes.
I wasted few games in Rafale because of that 2,5 weeks ago.
Its fixed after almost 1 month but its better then nothing i guess.
Hey guys,
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.
I have put war thunder back onto DX12 but I made sure FSR3.1is not selected and so far no crashes!
note (I did this yesterday)
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
With new 25.8.1 drivers from AMD no crash in last 4 rounds.
Todays WT update also fixed it
Though as minor asside. Anyone noticed FPS drops when napalm is used though?
Doesnt crash, but I just get a momentary stutter (and this is with like 150-200 FPS at all other times)
I have got FPS drops on ground battles when standing near a burning tank. So i believe the problem is with fire effect
Thank you. Definetly might be worth a bug report then
I can report I am still getting crashes in Air RB games, but now it IS crashing the AMD drivers. I also can still get napalm in test flights to crash the game and driver as well. I also am getting the frame stuttering while looking at fire. Maybe Ill try to turn effects down. Things seem much more stable, but I believe some improvements are still necessary. Hopefully I can find some stability and stick with DX12.
Ah here we go again ): .
After update it to 2.47.0.91 has same issue even on DX11 Game Crash on all Game mode.
Turning down effects didn’t have an affect for me.
However, I found that downgrading my AMD GPU drivers from 25.8.1 to 24.12.1 has had outstanding results. 0 crashes, even less stuttering with napalm drops(they haven’t crashed the game for me). Have played 7 Games of 12.7 Air RB with 0 crashes. Will report back if anything changes.
I’m assuming there are other drivers other than 24.12.1 that will work but I’m just happy to be able to play w/DX12 without crashes.
12900ks Z790 32GB DDR5 7900XT