Devs specifically requesting Debug Files and Replays for bombs not working

[Blankwindow]

http://forum.warthunder.com/index.ph...nks-need-help/

Hey, guys

There possibly some rare issue in the game, when you cannot kill a tank by a direct hit of your bomb.

If someone experiencing this type of problem, could you please provide us with log and replay of the fight?

Logs are .clog files, located in War Thunder directory in the folder Debuginfo

Replays are located in the folder Repalys

If this problem occur, please quit the game after the fight, select the latest log and replay and report the bug HERE

[Blankwindow]

Oh and he says "rare" it aint rare. I'm getting it 75% of bombs I drop that are direct hits.

[Imaginative]

I think he means rare player wise, I don't have the problem.

[Aviation21]

I used a bomber for the first time late last night the German Wellie and managed to kill 3 medium tanks that I thought I missed because they were desperate drops due to being attacked. I used 500 lbs'ers and remember saying check out the splash damage... I actually killed those tanks and in the past I would have missed them with those poorly aimed drops.

I will test again tonight!

Thanks Blankwindow.

[AOD_Danneskjold]

Oh and he says "rare" it aint rare. I'm getting it 75% of bombs I drop that are direct hits.

If they are asking for replays and clogs, that means that they are having trouble reproducing it, and need to see it happen to figure out what the problem is.

[Blankwindow]

If they are asking for replays and clogs, that means that they are having trouble reproducing it, and need to see it happen to figure out what the problem is.

I know what it means I moonlight for a company that closed alpha and betas tests a shit ton of games.

But considering how many people I see complaining about it in game. And my own experience, it is not a rare bug

[DaddyWabbit]

I had the problem several times day 2 of new patch, i.e couldn't even kill a tank with 1000kg bomb direct hit lol,,dafuq?

but not at all yesterday hopefully they corrected this already.