Classic RazerVon moment, absolutely wrong and so uninformed they don’t know it.
HE shells don’t fragment properly after Kings of Battle update. // Gaijin.net // Issues
Educate yourself.
1 Like
That’s a separate alleged bug.
The bug report you linked is specifically claiming that HE shells don’t fragment correctly, not that their damage is incorrect.
The only “not a bug” is that “don’t fragment correctly” as Trick is stating they do fragment correctly, so that’s not the bug the video showcases.
Congrats on proving yourself wrong by citing the bug report that proves me correct.
Read the bug reports before linking them next time.
“If you see problems with damage, please report specific guns and shells.” - Trick.
2 Likes
Sounds like cope to me.
You’re wrong as usual RazerVon. Unless you’re arguing that Gaijin is wrong of course.
Weird since my statement of fact has evidence to back it up, the evidence you found yourself so I didn’t have to link it myself.
There’s more to guns than fragmentation.
After all the previous bug was fragmenting inside bullets, which wasn’t incorrect fragmentation, nor was it incorrect damage, but it was a fragmentation spawn bug.
You have absolutely no evidence.
You made the laughable claim that Gaijin said it was a bug (with no evidence), so I linked the bug report from this very thread reporting this issue wherein Gaijin themselves say it is not a bug.
And you still have not provided any evidence to assert your claims.
All you have done is lie about what Gaijin have said.
Classic RazerVon moment, never right, always wrong.
1 Like
I do, here’s the evidence: Community Bug Reporting System
You even linked it…
This thread is about a bug occurring with ammo.
The bug report is one aspect, and it turns out that specific aspect is not bugged, so that narrows it down to damage, spawning of fragments, or other issues.
Oh my RazerVon, you really can’t read can you?
You still have provided no evidence that Gaijin have acknowledged this as a bug.
And you still can’t read that this was the bug report from this very thread on the issue and deemed NOT A BUG by Gaijin.
That’s alright though, we know you’re objectively wrong but you can tear up about it all you want.
1 Like
No, the bug report is on fragmentation, not damage nor ammo as a whole.
Why is it so hard for you to read?
We get it, you think ammo is perfect.
Sorry, but ammo is bugged.
You can continue claiming everyone is wrong all you want, won’t change anything.
1 Like
RazerVon I know you’re illiterate but you still have not provided any evidence of a bug report where they acknowledge this issue.
And I have provided the one from this very thread where they deem it NOT A BUG.
Maybe you should check yourself before you make bold faced lies that you cannot substantiate.
Now I know you’re not going to let this drop because you cannot handle being wrong, but you’re just going to have to argue with yourself because I’m not going to sit here and repeat objective facts ad nauseum at you.
So I’ll leave you with this, your abject loss.
1 Like
I’m glad you agree with me 100% that Trick said that fragmentation is not bugged currently.
It would be nice if you 2 would consider to continue your fight outside of this thread. The majority of participants are just not happy with current damage output / RNG whilst using cannons…so at the end of the day the results count and the question why we get there and if gaijin does acknowledge it or not doesn’t matter.
If you might agree that this mess started a while ago and nobody was happy with the damage output - just check post #2 in this thread:
Thx!
The issue is there are countless factors, and we have to make educated guesses on which one to report.
If I think hard:
Fuse timing.
Desync fuse timing.
Fragmentation spawn position.
Damage of [insert asset here].
Aircraft resilience to X.
Fragmentation simulation [RealShatter], which seems to be working fine according to devs.
And so forth.
Like it’s tough.
1 Like
That was always the case with realShatter. You hit near any module and it’s complete RNG whether fragments will hit the module or not.
That’s why realShatter inherently sucks, since it just creates some random damage instead of something predictable.
I agree with you, right now I personally believe that the damage is too low so when we add the RNG factor to it, it makes guns way too inconsistent.
1 Like
Yep, they also stated that same thing months ago when ppl were complaining about HE. However they eventually found out the bug n fixed it.
About the report I made… perhaps they checked the damage / HE values in the files and reached the conclusion that nothing has changed compared to before. This time I will report guns damage instead of “HE”.
What I find unfortunate on the bugreport plataform is that they close your report before you can debate with them / show where they could be wrong.
You best be careful, people have been banned for questioning technical moderators before.
Really? am not even trying to be hostile here… just trying to address this issue.
HAHAHAHAHA
So bugs do not exist in your world
let me enlighten you
Gaijin has not changed a single parameter in regards to real shatter in over 2 months. Datamines confirm that
Yet damage has changed.
So it is an unintended change.
The last time damage was low was also due to a bug and not by design.
1 Like
Never said this
Never said the change was intended. Them making a change and it having knock on effects, does not equal intended change.
Datamines do not record every change that is made to the game. There are plenty that do not get recorded.
Strange, when i asked for 100% complete patchnotes with every minute change done listed I was told to go look at datamines as they list every change already and there is no need for gaijin to actually list every chnage they make because of that.
Strange. It is almost like this community is living off of excuses