Also if i understand well :
The R-77 missile uses those Grid fins to interact with the airflow which makes the missile to steer.
So there is 2 situations with this grid fins drag problem :
→ high Drag in should appear in turns (over 5g)
→ low drag valie should be used under that.
Still the missile reaches 80km, when going in straight line, from what i’ve seen
But again: this is another topic, while the missile remains of similar range than any other comparable missiles in game.
How’d you get them? Restarted and no change
I play with the native launcher, not on steam. Still showing 2.43.0.17… I’ll try and figure something out
edit: analyzed files in the launcher settings and all of a sudden it changed to 2.43.0.23.
It didn’t even give me the full 52 flares
It gave me what I asked for, but I can change the slider mid match.
EDIT: nvm, the countermeasures are bugged again, it says I have them but they dont actually pop, number just bugs out and goes down and up.
EDIT: Caused by WIP client.
Do you have a video of the issue?
Yea Im working on getting all of it, it wouldnt flare with the button but it did with MAW, its all kind of jank.
Might be server related, but I also had an issue firing MICAs, after the first shot they wouldn’t fire anymore and would just turn the seeker off.
Guess I’m doing another bug report tonight, the display count of flares and chaff is all over the place, pressing chaff sometimes drops flares and uses chaff, sometimes actually drops chaff, kinda funny. This is with seperate key binds mind you.
EDIT: Was on my end, using WIP client.
I cannot reproduce the issue on my side, everything works regularly for me. If you get a chance to make a report pass it here so we can take a look.
The vast majority of missiles use their fins to interact with airflow and steer. Including thrust vectoring missiles. Lattice fins should not induce more drag in maneuvers compared to most fins (plausibly they should induce less for a few reasons, but I don’t know if that’s canceled out by other aspects), and should not induce excessive drag above or below transonic speed compared to competition.
In game, the lattice fins have what should be the transonic flow rate drag values for the entire envelope of the missile’s flight.
After restarting my game everything seems to be functioning normally now
Players: ask to recalculate drag, increase range (battery life time), add prop nav
Gaijin: here you 8 missile, and now bye GE
Linux client mind you, so this might be a bug exclusive to it atm. I’m not sure Morningstar’s OS.
Let me know if I forgot something, Im very tired and sick right now.
Also including the video in this thread because I think the “chaff” is funny.
EDIT: Caused by WIP client.
My issues were because my game didn’t properly update, I didn’t see the 2.43.0.17 in the corner until after I had played a game. after updating it everything works for me your issues might be linux exclusive if you’re on 2.43.0.23
Are you using Work-In-Progress Client? If so, that is likely the issue. If you test-drive the vehicle you should not have such issues, while in live games you do because matches at the moment are created on a previous version of the game.
Drag is induced by any surfaces, because of this boundary of airflow seperation:
Yet this is true at subsonics,… but at supersonic speeds, the missile is steered away by deflecting airflow, which creates the same kind of seperation (even bigger) at the moment the Grid Fin is turned to steer.
Yet, we agree that when fins are completely straight, the Drag number should be lowered.
But once you start steering, this is completely the opposite, as the amount of Control surfaces creates way more areas in which the airflow is disrupted, which tend to increase drag significantly.
To date, what i’m understanding of this problem is that Gaijin may have been using Subsonic number as a whole for the entierity of Flight Model, which is wrong (but done similarly to all missile) but considering that and all the above:
Subsonic drag number is fine
Supersonic drag number in straight trajectory should be around 0.25
Supersonic drag number in turn trajectory should be around 2.2 (due to excessive amount of surfaces and edges on those grid fins)
I’m using the steam “release_candidate” version, which I was under the assumption was just the equivalent of the regular launcher in terms of patches. Given that it works fine in test drive it seems you’re right, I even have access to the sliders.
My bad, I had assumed the other branch was the same pipeline as the regular launcher and that steams regular branch was a sort of “stable” because it seems to get updated much later.
Edited and removed my posts so not as to muddy up the thread.
