Hmm… and as Napalm is usually never used in GRB or NRB, it would explain why the crash has largely been contained to ARB.
I guess that is as good a cause as we’ll get at the moment then. Interesting that regardless of BR from 8.3 to 14.0, players are getting to the bases at nearly the same time
Maybe that’s why I had so little crashes compared to everyone else. I only play GRB. I wonder if it’s actually only Napalm or if there could be something else.
Necro did point out that some aircraft have comprable effects when they crash. So its possible that its not napalm specifically but rather the associated effects
I have AMD GPU too and it happens to me too. I don’t want to play on DX 11, because FSR as anti-aliasing is better option than TSR.
Started happening around 13 days ago. Before that I was ok and no crashes on DX 12 since its introduction. I have RX 6700 XT and AMD 5 5600X cpu.
So small update for you guys:
I asked the Technical Moderators if they had anything to share regarding this issue.
It is actively being looked into. They are still investigating the issue so nothing concrete yet but it seems to be tied to some sort of issue with FSR and DX12, so until they find the exact issue you can try turning of FSR to see if that helps. If it doesn’t then changing to DX11 with FSR still off (I don’t personally have an AMD card so can’t test) might help. It’s not guaranteed to be a fix but it might be of help to some of you. :)
As with any issue there is sadly no telling when it’s going to be fixed, some issues are very complex and not only takes time to find the exact root cause of but might also take time to fix depending on what the cause is and how complex the bug is (in some cases it isn’t even the games fault and some other third party need to fix a bug in their drivers).
They are however looking into it. I hope they find the exact issue soon, I don’t think I’ll be able to be of much more help than this and if more users have the same issue then please link them both my previous lists of things to try (to possibly solve it themselves) as well as this answer.
Yeah, I asked Smin about it too and I got the usual PR response.
I have swapped back to DX11, but its a shame because the game looks a bit better on DX12 with things like SSAO enabled.
But thanks for the update. I guess we’ll just have to wait to see if we get a fix.
I’m not using FSR but i have the problem. I use SSAA 4X on 1440P with no anti-alasing. I dont want switch to DX11 because i get 50 more FPS with DX12 and %20 GPU usage. DX11 makes bottleneck.
Have you tried the things i have listed in this thread that might fix the issue?
Yes, its not about end-user i think its about DX12 api implementation.
Well there is certainly an issue, but it’s still worth trying those things if you have FSR off or aren’t using AMD cards to begin with and are still having problems.
got the same almost every day i playing…4070ti
Here are some fixes to try if you haven’t already:
( So is DX12 crashing never gonna be fixed? - #84 by Necronomica )
Hi, I have the same DX12 crashes. 9070XT latest drivers. No Ray Tracing. I was using FSR Native and got these random crashes. Tried Xess Native and worked for a couple of days but began having crashes again. DX11 looks and performs worse (but no crashes).
Then this answer is the latest i have for you: ( So is DX12 crashing never gonna be fixed? - #197 by Necronomica )
this is very annoying and the fact GAIJIN didnt even fixing it for weeks makes me mad…there was no issue before the big patch and now there is issue sine that for a month now every day
I feel like they didnt even trying. @Necronomica @Stona_WT If there’s anything you’d like us to test, please let us know.
I sadly won’t be of any more help than i already have been. The latest information i have is here: ( So is DX12 crashing never gonna be fixed? - #197 by Necronomica )
There weren’t a correct report made for quite a while and then it took a few days for the Tech Mods to get to it and review it so technically the DEV’s didn’t get the information about the issue until like 12 days ago. They then in turn likely have some internal prioritisation on what issues to fix in what order as well as some issues being SUPER complex and hard to narrow down and fix. It almost never as easy as “ah yes, this 1 should have been a 2 in the code all fixed now!” , it doesn’t work like that. Especially when there are also other things that gets periodically changed from the outside as well, like graphics cards drivers, DX version updates and so on. It might not even be an issue the DEV’s can fix, it might be something on AMD’s end and the DEV’s then send that info to them and have to wait for them to fix things. There are so many things it could be and some many reasons for things to take longer to fix than players often realize.
Let me at least give you the information I have.
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.
