Not a direct hit.
So the spalling may have destroyed the ammo, but spalling itself may not have dealt enough damage to detonate the ammo.
Not RNG in that case.
Edit:
This is probably the best direct hit example. It could be desync, it could be an old client with the bug, I could be mistaken about it being a direct hit.
is this not a direct hit too?
now you are making stuff up
Have you seen the video of a T-80 gunner eating literally dozens of HSTVL darts to the face and not dying? I fail to see how this is possible without some sort of crew damage reduction code gone awry
I see too many convenient ‘bugs’ in the game that benefit Russia especially to believe that they are in fact just bugs. 100% there is some sort of altered code behind the scenes.
you are completely missing the point, why do we even have RNG ammo explosions at ALL?
btw the russian bias topic exists, go vent your conspiracy theories elsewhere
I’m not missing any point, I’m talking about War Thunder on a War Thunder forum.
Ammo explosions should not be RNG. End of discussion.
Conspiracy theory? Do you really want to go there? I can pull up all the evidence and it won’t end well for you.
That could’ve been when the bug was still going on.
The BMP-2 has modules now.
IS-4M: Round went through the radio and hit crew member.
Fragments destroyed one round of two piece ammo.
AML-90 and favorite armored car that doesn’t have turning wheels.
Could be desync, old client. Either or.
Desync is the leading cause of ammo issues on newer clients.
@Bowman_1
There are zero bugs that benefit Russian vehicles over others.
I’ve never had issue facing T-series tanks with my HSTVL.
You have no evidence of Russian bias, and even if you did here’s the topic to post it:
what would be your cope about that za35 shot? man can you just admit that this RNG is absolutely NOT good for the game?
pull that evidence you have and put it in the topic alvis linked you
this thread is about RNG BS gaijin pulls with random chance ammoracks
Yes there is, and yes I do. Don’t try and dispatch me out of the thread after making a completely false claim. PM me if you want the evidence you say doesn’t exist. Out of respect for the OP I’m not clogging this further.
That was already posted:
IDK about you, but most of my game connectivity issues are from me connecting to my own country of USA for whatever reason despite having rather excellent gigabit fiber.
We’re all capable of desyncing with the games’ servers.
this doesnt look like desync to me, the hit cam is serverside afaik
The hitcam on our client is very much client side.
We won’t ever see the desync ourselves, but only ever get suspicions.
I’m also not saying that the ammo bug didn’t return, however after testing a few fragmentation shots in test drive, the ammo bug would’ve happened at least once there leading to desync being what I suspect you experienced.
For those saying “not a direct hit” just watch the litteral first comment of the topic, there is no doubt on the fact that it was a direct hit and with a 90mm shell at that.
Well, the game has many mysterious.
Like how sometimes a shell breaks a wing and another time it just turns black.
Same with engines. A black engine can still run but it can also be dead.
So maybe modules with like less than 5% health, or something like that, turn black, meaning ammo can turn black without blowing up.
I don’t think we need 10 000 examples, Alvis is just a troll so don’t bother. It definitely is RNG related and thta’s one of the many things Gaijin needs to fix or explain
Client side or server side? Because that could also be explained with desync.
Pretty sure server side
