I’ve tested this with War Thunder Real Time Information and found out that the Critical G % stayed at 0% with the Su-30SM2, it works fine with every other aircraft I tested it with.
thanks for when You implement it Gaijin devs.
I’ve tested this with War Thunder Real Time Information and found out that the Critical G % stayed at 0% with the Su-30SM2, it works fine with every other aircraft I tested it with.
thanks for when You implement it Gaijin devs.
That’s because the Su-30 is made of adamantium, which is obtained by melting down Wolverine’s claws, so it can’t break.
that explains it gahh dayum
Makes sense, it’s Russian tech. It’s just that good.
stalinium wing spars
Su-30SM2 is most definetly able to rip its wings due to overload
also with a full loadout
you should not complain to gaijin but to whoever made WTRI
It’s not WTRTI’s fault for not showing it. Some local host values are just inconsistent, like a lot of planes have no fuel according to it lol.
but even then you shouldnt come to random conclusions like saying that the Su-30SM2 cant rip its wings due to G overload

It kinda is.
I hope it has a big ass disclaimer saying something like: “This app is cheeks and thus shouldn’t be used by anyone. If you still want to proceed, you should expect bugged data, even for the most basic of information.”
Its literally pulling it from the game’s local host? Why would it be WTRTI’s fsult that the game is inconsistent and doesnt always show all values? Local host is part of the game, ie on gaijin’s end, not WTRTI’s
It’s their fault for not reading it properly and highlighting values that are seemingly impossible.
Their fault for reading values that just arent even there?
You should expect certain values to be there and if they aren’t, you know something’s up and should properly notify the user. I just hope whoever made that thing is an intern-level dev, for their own good.
good to know that it can.
I just realized that I never tested it out with more than 34m of fuel as that’s My most common fuel amount on Su-27s and on
Localhost returns a value of zero when its not there. So its not as simple as just saying, oh yeah if this returns null, its obviously broken.
Yes there are still way to detect it, like by running continuous checks in comparison to other values. But then you realize you gotta come up with these for basically every value and its no longer that quick to add.
That’s fine as long as you stop bogus values being read by the user.
People trust these things way too much without a second thought, which is why we have this thread in the first place.