The title is enough in itself. This is a bug.
Anyway, for more details. Im playing with the buccaneer currently, lots of fun. Im good at precise bombing so i enjoy it.
I unlocked the missiles. Went to try them in a match. I also put some bombs to atack ground too.
I couldnt hit anything with the bombs. Weird. I realized the red circle camera from third person doesnt align with the bombing camera. This never happened before. I went to test it and as i thought. If you have missiles equiped, the bombing camera will aim to random places, so its usless.
If I equip bombs while having missiles, I can only use the third person circle in the floor aim. Because the bombing camera will just aim to random places.
If i switch back to pure bombs and no missiles, the bombing camera will go back to normal.
(BEFORE ANYONE ASKS. THIS HAS NOTHING TO DO WITH BOMBING WITH MISSILES. THIS IS ABOUT THE BOMB CAMERA NOT WORKING IF YOU ALSO EQUIPED AIR TO AIR MISSILES)
You can bug report it here (just search a bit first so that you don’t report something that is already reported and known about): (Gaijin.net // Issues)
A guide on how to report bugs can be found here: ([Navigation] Technical Knowledge Base | War Thunder Wiki)
Done! the bug has been submited and a workaround exists. Activating bomb selector resests the camera. Just turning bomb selector on and off on every match fixes the camera.
1 Like
Good to hear that there is a workaround for now and i looked for it and can see that it got accepted. :)
Some tips for the future when bug reporting:
The Screenshot isn’t for the image itself, it puts a tag in the code so that the developers can look for the issue in the code around the time it occurred in the match. So if you encounter any bug in the game then take a screenshot as soon as possible. The logs that games in general produce are usually around 10-20 lines of code per second from the moment the game is launched to the moment you turn the game off… I don’t know exactly how large War Thunders logs are but it would be unreasonable for the dev’s to sit and read through tens of thousands of lines of code to try to find the issue when they can use the tag that the screenshot creates to get within at least plus/minus a few hundred lines of code to look at.
You did write a good description of the issue, the more descriptive it is the better (sometimes players think something is obvious but then it turns out that there are 20+ different reasons for the bug to have happened so with no description the devs can’t really be expected to sit and test 20 different scenarios for something that might not even be an actual bug to begin with).
A step by step guide on how to reproduce the bug is also VERY helpful as the devs can then very easily test it and verify that there is indeed a bug before the search for the underlying issue and a fix can even begin.