When launching a fox-3 missile (RB 99) at long range when the missile is locked with its onboard radar, it starts spinning out as soon as the enemy visually de-renders and if not supported by TWS or STT.
It happens nearly every single time i look away and / or stop holding the TWS on the enemy and the missile doesn’t hit.
Here is a link to an in-game clip showcasing this, it can be seen on it that the missile spins out at the exact same time the enemy de-renders:
You can bug report it here: Gaijin.net // Issues (just search a bit first so that you don’t report something that is already reported and known about)
A guide on how to report bugs can be found here: ([Navigation] Technical Knowledge Base | War Thunder Wiki)
I’ve had this with R77, aim-120d and aim-120c-5
The c-5 seems to be slightly less effected for some reason? but it’s certainly still present. I think the 120d has it worst with the 77 shortly after.
very strange behaviour, definitely a major bug
hm, and i was starting to wonder whenever im going insane or my missiles are just acting up.
Can report probably similiar issue with R-77s and PL-12s.
people ask me why i refuse to go above sparrow BRs when this crap happens all the time
With all the QoL supposedly going around , maybe gaijin gets to overhauling this stupid outdated rendering system we currently have.
Can you please make a bug report on this?
It’s been made since September 18th, you can click that you have the same issue to make gaijin notice it more:
https://community.gaijin.net/issues/p/warthunder/i/No1R7pclraAG
I think this bug has been around for at least 4 years. It’s very obvious in sim, where you can see enemy dots only within around 10 km UNLESS you are painting them with radar (any AA search mode and no lock or TWS reguired). If they have smoky engines you can see their smoke from 20 to 30 km away but not the actual dot.