quote=“Nagisei, post:514, topic:29021”]
Question, if a missile goes pitbull but then loses lock and goes back to IOG, does it also still receive datalink information or is it shut off once pitbull?
[/quote]
I’m pretty sure only the R-27 (Ahistorically) has the capability to reconnect Datalink once a target has been lost.
It should not, since the missile would still have its notch gate to contend with, and now would have an additional notch gate too. At best you may confuse the enemy with 2 different radar locks.
IRL the Phoenix could be SARH guided, but again, that’s 2 Doppler gates instead of one, which is worse.
Hard locking may provide a more ‘stable’ target track though, so you are less likely to lose the target while your missile moves to Pitbull range.
1 Like
Looks like the R-Darter/derby got a loft profile “fix” where they were given a cookie cutter loft profile from another one of the fox-3’s.
There are now only 6 different loft profiles across 14 fox 3’s in-game, and I have my doubts about the efficacy of some of these considering my previous testing on loft profiles for the AIM-54.
I have not tested the effects of loft profiles on the new fox 3’s in-game, which all have some rather different thrust and drag profiles compared to the AIM-54, so take what I say with a grain of salt, but at first glance, I’d hazard a guess at saying none of the loft profiles used by fox 3’s in-game are particularly good. I’m starting to think the reason we have these seemingly standardized loft profiles is that there is little to no effort being made at loft profile optimization on gaijins end, and they’re just copy pasting values they find functional. That also likely explains why stuff like the R-Darter/Derby had such horrifically bad loft profiles at first. They were given a “different” one to try to differentiate them, but nobody bothered to check if the “different” loft profile was functional…
3 Likes
The AIM-120 has it’s pitbull fixed. It’s now 22 km’s
2 Likes
Was so glad to see this when I read the data mines this morning, wonder why it wasn’t mentioned in any change logs. Bless the data miners for finding this.
The reason Derby/R-Darter got bigger loft, is because they are smaller missiles compared to the rest of them, and they have to compensate range by lofting, and they do loft more than other missiles irl. When it comes to in game developers decided to give it the more, but i think someone forgot to check how much more.
Do you have any actual proof the R-Darter/Derby loft more irl? Its pretty clear nobody bothered testing the loft, my question is more “does the person deciding the loft value even know what they’re doing, or did they have their 7 y/o kid pick a number at random?” cuz omegaMax of 2.5 is not only the highest omegaMax value in-game, but it is clearly and egregiously too large when coupled with the loftTargetElevation and loftElevation the missile was given.
It was one of Rafael press releases, if i find it i will link it. When it comes to values, no one knows them, Snail made them up.
I know nobody knows the values, theyre an overly simplified way to code trajectory shaping, and are overly rigid and rather poor at it, which leads to subpar modelling of trajectory shaping. What I do know though is that the values used in-game are pretty generally terrible across many missiles that do loft (both air to air and air to ground) and could be improved substantially to better fit their roles, but aren’t.
Bad loft values are also the reason why the AGM-114 Hellfires dont actually top attack most of the time in-game btw
1 Like
Yea, i feel so too.
Oh i know that very well, and the worst thing is, that when it comes to Hellfire we have a decent amount of information about how it flies in different scenarios, but nothing was done with it.
Yea, I’m not holding my breath on loft profiles ever being properly implemented/fixed…
I stopped bug reporting entirely a while back because quite frankly, gaijin are a joke at actually fixing anything.
No amount of primary sources or information can ever get a bug fixed, at the end of the day, its up to whatever gaijin dev is in charge of the specific thing being bug reported if it gets fixed, which is why despite the fact some bugs could be fixed by literally changing a SINGLE value , or a few lines of code, which would take a dev no more than 30 seconds, they sit “acknowledged” for months or years, if not indefinitely.
4 Likes
Yea, i also recently lost most of my will to do things, as it seems 3 sources stating thing is a prototype, and 3 sources stating it fiered its weapons are not convincing it was real…
2 Likes
Those of us that do report stuff live off copium that maybe they’ll consider it a positive change and fix it. Ultimately it’s not even about whether or not they believe it to be true but rather that it benefits their “vision”.
The whole bug report website is a massive, horrifically bad joke and is so poorly implemented that I wouldnt be suprised if the devs just ignore it entirely tbh. It looks like it was setup as part of a 12 y/o’s “my first webpage” project in middleschool…
There are going to be changes to the bug report site in the future, how will it go, i have no idea, but i know they are coming.
Late reply but, basically, as soon as the missile goes pitbull, no point having either TWS or hard lock as the missile will always ignore your data?
keeping a plane hard locked can assist with missile tracking IIRC as the missile still tries to follow the largest radar return and your onboard radar can assist with providing that, so if you’re firing at one enemy and have no reason to unlock your radar it might be a little better to keep them locked
2 Likes
Interesting, is that confirmed or just assumed based on IRL performance?
If you lock a target and never unlock him, missile fired at the said target will still keep getting datalink updates. If missile goes pitbull and you don’t unlock the target, if missile loses the target, it can still get datalink update and then go and lock the target with its own onboard radar second or third time until impact.
2 Likes
