I should be able to reverse engineer the maths, but I’ll take a look tomorrow.
The biggest problem I see is warthunder does not utilise body lift in missiles.
Part of why the devs think the Stinger can only do 12g when it is capable of double that at least.
Or maybe a better way to measure the difference in angle is when the brimstone reaches the nose of tornado and the angle it produces relative to the plane of the fuselage
Which I think Is what Devil did
Could do so in replay
Another difference to note is that the irl missile is flying in its direction of travel, the WT missile is falling in that direction…
Attempt 2
Brimstone should achieve higher AoA
https://community.gaijin.net/issues/p/warthunder/i/Yjnp0lyaM3LR
Honestly not sure if this bug report will stick, mostly just cuz “pulling 40° of AOA” may not be the correct way to explain it, but idk if theres a better way to put it either.
Maybe something more along the lines of “the source provided indicates that the brimstones pre-launch gimbal limits are set to 40° to allow the missile to service late show targets. At the moment, the missile in-game is incapable of hitting targets at the limits of its pre-launch gimbal as would be required to match the specified capability in the report, implying the Brimstone to be lacking in max load-factor and control surface authority” might work better?
Thats just my 2 cents tho, either way, I appreciate the work you’ve put into the report :)
That’s not the thing. The seeker is capable of tracking. The missile itself does not pull.
Adding the whole pre launch gimbal is not a thing as its gimbal is greater. The 40 degree is a zone where when fired it should go for the target.
And I added the source used to buff the pre launch, so it’s already there.
I just read the whole thing again. My brain short circuited during the first read.
You are right, I just might go and explain it to like I was talking to a kid.
Still the pre launch gimbal is not a correct term there.
Im not saying the pre-launch gimbal is the problem, I’m saying that the missile is currently unable to pull enough G’s and enough G’s fast enough to hit a target at the limits of the pre-launch gimbal as would be required for the source to make sense.
ie: its not that the missiles max AOA is too low, its that its max load factor (g-load), and the control authority of the control surfaces (how quickly/efficiently the fins can induce the required G-load) are too low.
Maybe my language was too flowery or something, I guess I shouldnt backseat bug report…
Changed it a little, hope it highlights the issue better.
I’ll review the whole brimstone pull stuff through the day.
The AOA of the missile is our best chance and getting this fixed right now, it’s the only absolutely measurable item of data we have from current sources that can be used as a source.
You can see that the missile is effectively utilising body lift and large angles of attack to generate signficant load factors at the point of launch, far beyond what the fins can produce on their own.
We can then use this information, a bit of pythagoras and calc to determine how much G the missile is pulling in that moment, but not what the maximum the the missile is capable of.
This is because we don’t have any source or information on what the maximum G is for the misisle, we only have information regarding the maximum AOA, angle deviation and displacement at the time of launch.
Has anyone else noticed an Issue too with the Targeting Pod? Because normally its Gen 3 TVD, but sometimes the quality goes down to Gen.1 TVD
Oh, thats normal.
It’s simply PIRATE being jelous you are not using it. (even if you do not have it on the plane)
German EF has no PIRATE )))))
And still has the issue:(
