yeah I think the whole code needs a revamp though its all WIP and this issue being on a bunch of missiles and not just one should hopefully mean it’ll get fixed up
It doesnt help because by the time you meet your parameteres to fire, the enemy is already close. We need way bigger maps to make use of the phoenix
A more aggressive loft would help cause we could definitely launch sooner. Most times I don’t even try to launch when I know it would loft, because it’s so minimal.
The only time I have faith in a shot is when it’s 40km at about 20k feet Mach 1.1-1.2. And at that point I’m already close enough the missile won’t loft. Even if I reach these parameters I would still not launch at 60 km because the missile doesn’t gain any extra speed from climbing because the loft is so poor.
With the new fox 3’s they currently have a much more meaningful loft, and absolutely have positive gains when lofting. Currently the phoenix when it lofts does not seem to make much or any gain when it does so.
2 Likes
Also I don’t know how to do it but I’m curious how the pheonix would perform with the new loft profiles copied over.
ARH in test event currently has the bug where if missile comes down too steep, it won’t acquire a lock. On top of that, data link isn’t working correctly, I think Gaijin haven’t added data link support to radar code. So data link is supported by the missile, but radar isn’t sending anything to the missile.
great stuff… imagine not braking something for once
Devserver phoenix is incapable of achieving a historical kill (and maximum range confirmed kill) in-game now. This is likely due to the increased fin AOA (and already excessive drag)
Previously, I have performed this kill using my user mission, however now it is unable to do so.
Do you mean that the increased fin AOA slows down missile more?
I need to analyze a bit more, I just did it with the A-Phoenix but the C stalled itsself out before hitting the target, and seemed to prematurely dive on the target
Probably doesnt help that the AIM-54’s never got a time to target guidance section in-game like all other SARH/ARH missiles added after the AIM-7F…
AIM-54C:
It likely wasn’t much of a concern before because it didn’t have enough actual control authority for it to matter, but now that it has more, it accentuates a whole slew of issues that already existed for the AIM-54.
At this point the 54C basically needs a rework.
1 Like
My sensor view just windows vista’s when I try to use it, but it seems like it just… doesn’t loft sometimes?
The A-Phoenix when I fired it performed exactly as expected, I just re-did it with the C and it went up, and just stopped climbing and spent the entire flight at a constant slightly upward angle until it hit the target. Very wierd.
Should it get it given that it’s a very old missile?
The AIM-54 is known to have adapting lofting capabilities. If a target is close enough it will not loft while if it is far away it will loft a ton. Its very likely this was based off of time-to-target data or more likely an assortment of data from the datalink and onboard inertial guidance unit. It was an absurdly sophisticated missile, and certainly had the room on-board for advanced guidance computing.
2 Likes
Its a newer missile than most missiles that got it… atleast the C variant is…
The A entered service only 2 years before the 7F, and the missile has an active off the rail mode for dogfighting soooooo yeah… it should definitly have time to gain code in WT.
No, we have been over this. It has the ability to go active off the rail, doesn’t make it a specialized dogfight ‘mode’.
It’s unlikely the AIM-54A had time to gain tables that update based on target data post-launch based on remaining estimated time to target from the seeker. It might have trajectory shaping profiles formed prior to launch that go unmodified… but not post-launch.
We know that the AIM-54 at least has two distinct modes; Normal, and Active (correlated track with auxiliary sensors / datalink), which I believe would be Lock-on Before launch.
There is also the additional mentions of Boresight missile mode(s), distinct from (Active) mode, likely indicate Lock-on After Launch (we know that the Sidewinder can’t do, so refers to both the Sparrow, and Phoenix) capability of which we know;
The Sparrow is capable of (WIDE, or NARROW Speedgate Launches with the appropriate BST & Aspect knobs to approximate range & range rate information)
But the Sidewinder isn’t, it has its own set of SEAM capabilities, which extend to a expanding the field of regard(effective pre launch Fov, via sequential sweep of the seeker though space), but the listed values would clash the larger of the listed antenna program(s) due to the 22.5 degree ASE launch limit for the AIM-9G (also as the AIM-9D doesn’t have access to SEAM capabilities.) so Sidewinders probably aren’t being referenced.
Thus Dogfight mode, for the AIM-54 is probably, Active off the rail, without a Lock-on.
4 Likes
Again, doesn’t imply some special method of improving maneuverability with this alleged ‘mode’. It is literally just hail marrying it in active mode hoping to hit something at close range without supporting the missile with additional information.
This also doesn’t show that it should have any time to hit gain tables that update based on time to target. The design was practically finalized in 1963.
Without a range it also shouldn’t loft either, improving short range velocity due not gaining altitude, also the same way the Dogfight mode for the Sparrow eliminates some of the inbuilt delays in fuse arming, a similar process probably occurs, reducing the minimum range of the missile due to the fuse arming in a shorter period after lock-on is established
We also know that Sparrows earlier than the -7F employs an autopilot magnification factor ( band A [1:1], -B[1:2] & -C[Bang Bang(Full deflection)] autopilot), that is set pre-launch based on own ship Altitude & Look Up / Down angle, of which the -7F optimizes.
The AIM-54 having a more complex set of altitude bands or a special set for each launch mode wouldn’t be unexpected considering that even the AIM-7C & -7D’s autopilot functions as described above.
7 Likes
Seeker function aside, I was more pointing to the fact that the current AIM-54’s have immediate access to 100% of their maneuverability in-game once 3.5s from launch has elapsed, which can pretty clearly lead to suboptimal energy use when targetting a target at long ranges, which is why the 7F and all other S/ARH missiles added after it with lets call it “adaptive” autopilots use the time to gain functions for.
The idea that the AIM-54, particularly the AIM-54C, couldn’t/wouldn’t optimize available control surface authority and trajectory to optimize kinetic energy at intercept and time to target is laughable. Particularly when we consider that for shots at longer ranges than 16km, command inertial guidance would be used, which is specifically used to optimize trajectory.
If the AIM-54, or its command inertial guidance couldn’t optimize its trajectory, then we’d see the missile go to space during every single shot, which would make it completely unusable at close range, something we know not to be true due to the existence of the “active of the rails” mode (or dogfight mode), along with congressional accounts of its use and effectiveness in dogfighting.
Without the time to gain tables, the missile is just not optimized for long range shots, which is likely why a large increase in control surface authority like were currently seeing is having a negative impact on its energy at range as @pyroraptor841 indicated
As a sidenote to all this actually, I’d be curious to test if the AIM-54 is seeker gimbal limited when in its command inertial guidance mode. In theory it shouldnt be, as the seeker isn’t whats guiding the missile during that period, but it wouldnt suprise me if gaijin made it work that way…
3 Likes
What is the aim54 changes?