It is up to 50%. Even the numbers you provided at 800:
Is 43% higher.
And you said its inaccurate, but literally in the graph
Are roughly the same numbers you yourself provided.
At 1000IAS, this is
So for the whole 20s-30s duration where you are trying to run from the F-16A, he’s outaccelerating you. And you’re suggesting MLD is catching? Sure…
In this case its similar, but from my experience, I just don’t take statshark at face value
Afaik, statshark has been proven to be more accurate than WTRTI lol
Fyi, this is statshark’s time to speed from 800IAS at 100m:
You won’t be catching a MLD unless he dumbly commits, thats my point. Especially when you have to start with a positional disadvantage with low altitude, nor notching, or both.
You won’t gain distance in any meaningful time before he reaches very high speeds, which he can maintain at 102% afterburner or do a shallow climb. Without sparrows, you cannot punish him for ditching out like that
And is the average wt player known for being smart? Not really, right? So this is only applicable for like 1 out of every 10 or more MLD players.
And as proven before (and with your own acceleration), the acceleration difference is 40-60%. That’s a lot from 800 IAS you need 30s to outrun.
I thought we were talking about plane capabilities and not average player skill
Same XL thread points out how WTRTI have issues with other values such as STR. And even then your own data has shown to be similar to statshark.
So “plane must be played in very specific way” to not get run down by F-16 is the takeaway.
Yeah… Not exactly the “better than F-16” that you were claiming. Why don’t you make a thread saying MLD is actually better than F-16A and see the response? I’m sure many will point out the issues I did.
Then you didn’t read the thread. WTRTI is proven to have around 0.1-0.2deg/s error in worst-case scenarios, statshark can be 40x that.
Yet the thrust I showed you is within your own margins? curious. If you say it can be 40x, where’s the proof?
Flying straight requires so much skill
uh huh.
I’m going with your logic there, don’t uh huh me
F-16XL FM is ridiculous - Machinery of War Discussion / Aircraft - War Thunder — official forum
and
F-16XL FM is ridiculous - Machinery of War Discussion / Aircraft - War Thunder — official forum
Self citing is not proof. This is high school basic. And in those two links others also point out inaccuracies in your own data.
There is video proof of the flanker STR comparison. The values in statshark are not reproducible.
I proved WTRTI numbers are much closer to localhost. While statshark are not, simple conclusion really.
The up to 40x more inaccurate was for the F-106 FM at slow speeds that came up in the thread. Its simple math, I calculate the STR with an equation with the localhost values and check which one has more accuracy. Which is WTRTI, of course, often by a huge margin when talking about high AoA situations
Just because statshark doesn’t provide a specific value that another app does is not indicative of inaccuracy.
You were the one who brought it up in that same thread.
Yet those thrust numbers are nearly identical? Why is that? You’d expect something that’s “inaccurate” to be outside the margin of error, yes?
Try to give it a read at least. The reference values are from locahost, which are factually correct.
Again, you providing reference values from local host means nothing when there’s no corresponding statshark values to compare it to. Unless you have both, here, then this is just lip service.
And what’s to say just because WTRTI pulls from local host that statshark doesn’t? Even things like missile data on statshark is pulled right from game numbers.
