Impossibly open, uncovered, blatant premium bias

Machinery of War Discussion Ground Vehicle
1

ussr_t_80ue1_120mm_jm33_111.45.blk (1.5 KB)
ussr_t_80ue1_120mm_jm33_118.38.blk (1.5 KB)

Playing WarThunder for 1500 hours my gaming chair went from catching fire because of my own skill issue to catching fire because of unbalanced vehicles of various nations to catching fire because of the premium bias (the unfair advantage player gains just from playing a premium vehicle), often misinterpreted as “(insert nation) bias”. They say, everything goes, but this does not. I have encountered the instances of premium bias previously (and I have mostly been writing this off as my own fault, which sometimes hurts a lot), but never ever this has been more obvious and more blatant than this time. Files listed above contain three hit replays saved through the power of in-game hit replay system. Two files – two hits for T-80U-E1. For the purpose of easier visual understanding screenshots have been made:
– First T-80 hit:

изображение
изображение1259×917 100 KB

изображение
изображение1280×697 93.4 KB

– Second T-80 hit:
изображение
изображение1274×801 99.3 KB

изображение
изображение1162×807 100 KB

изображение

The replays and the screenshots, to me, are self-explanatory.

I hope to be able to leave some day.

2

Probably a bug - I would submit a ticket

3

I could have included more – for Christian II, but the Forum does not allow me to link more media files in one post, so I paste them here:
sw_strv121b_christian2_120mm_jm33_413.61 Возмутительная херь с РПУ.blk (1.5 KB)

изображение
изображение1280×805 109 KB

изображение
изображение1202×924 87.5 KB

изображение

4

Useless. I cannot even link the necessary files there, and reports without proofs are not considered

5

If you try the same shots on a T80U and a 2A4, exact same parameters, what results do you get?

I agree that the bug report system can be arduous at times, but if you post both the regular T80U taking damage to the same hit that the U-E1 does not take damage from, you probably could get traction.

6

You need to hit the tank in weakspot, if you hit it in most armored part you will nod do DMG.

in short - skill issue, git good, topic can be closed

7

I can and will now try, of course, but i will probably be not able to recreate the exact parameters of those shots

8

Not exclusive to Premium vehicles, I’ve played a match yesterday, point blank distance from the target, only could knockout his commander, zero spalling after, direct hit with the ammunition,

Some times also, on the KPz-70 (and variations) I shoot the left side where the commander and gunner sits, it only takes out one of them, but it’s a few moments.

9

Oh yes, wise man, did you even look at the contents of my post? The issue is not that I am not able to pen/damage the T-80 and that is the issue, no. The issue is that it is very much obvious that I should have done at least some damage, according to the hit replay.

I suggest not being so quick in judgement.

10

The KPz-70 at least has some explanation to this (the spaced armor) but yes, (although less with me) it also happens on tech tree vehicles sometimes.

11

You can open the hit replay files (.blk) and notice they’re .txt. files in reality.

You can copy and paste them into pastebin to share them freely.

For bug reports, just upload to the “Other files” section as you would replays.

12

Thank you, I did not know that

13

SteamLibrary\steamapps\common\War Thunder\ReplayHits

Where to find them. Do note, you need to manually save them with the appropriate button.

Following is an example of one’s contents:

Spoiler 
version:i=7
time:r=244.25
damageRole:t="offender"
offender:t="RunaDacino"
victim:t="UnrealAndor"
object:t="germ_mkpz_m48a2ga2"
offenderObject:t="uk_conqueror_mk_2"
spawnerObject:t="uk_conqueror_mk_2"
projectileUid:i=25166397
weapon:t="gameData/Weapons/groundModels_weapons/120mm_QQF_Tk_L1A1_user_cannon.blk"
ammo:t="120mm_l1g"
ammoType:t="apds_early_tank"
bulletSetNo:i=0
ammoNo:i=0
isBelt:b=no
supportGun:b=no
lPos:p3=9.83212, 2.23374, -5.1077
lDir:p3=-0.850745, -0.00241037, 0.525573
pos:p3=3708.51, 683.066, 2457.5
dir:p3=3708.51, 683.066, 2457.5
speed:r=1465.22
travelDistance:r=246.36
piercingShift:r=98.46
justExplosion:b=no
testProperties:b=no
seed:i=418471395
shotDistance:r=249.55
distance:r=249.55
isSabot:b=no
isSecond:b=no
startPenetration:r=501.7
startDamage:r=359.78

penetrationTable{
  p:p2=10, 501.701
  p:p2=100, 496.796
  p:p2=500, 475.573
  p:p2=1000, 450.319
  p:p2=1500, 426.411
  p:p2=2000, 403.779
  p:p2=2500, 382.355
  p:p2=3000, 362.075
  p:p2=3500, 342.879
  p:p2=4000, 324.709
  p:p2=4500, 307.512
  p:p2=5000, 291.236
  p:p2=6000, 261.259
  p:p2=7000, 234.423
  p:p2=8000, 210.411
  p:p2=9000, 188.941
  p:p2=10000, 169.764
  p:p2=15000, 101.375
  p:p2=20000, 69.5604
  p:p2=25000, 69.5604
  p:p2=30000, 0
}

turretPos{
  pos:p2=31.4717, 0.0611367
  pos:p2=-0.0429425, -0.191887
  pos:p2=0, 0
  pos:p2=31.4717, 0.0611367
  pos:p2=0, 0
}

parts{
  size:i=141
}
14

Yes, I checked it already – should be able to file the proper bug report now

1 Like
15

So a singular pixel shot on tech tree vehicles means there’s a bias on premium vehicles?
Aim at a different spot…

Also yeah bug report that pixel shot.

16

These are not tree vehicles and those were two different shots. Three times in a single match with different angle shots are too much to be a coincidence – and I have accustomed to having to face things you call coincidences.

Yes, I already reported this case thanks to RunaDacino.

17

The T-80 series of tanks are in tech trees.

18

The T-80U-E1 I was shooting is not. I am aware of existence of other T-80’s, but that was not a tech tree variant. Your point?