Amarok_73

I've found replay track from the moment we tried to recreate it. It was about 25 degree... aim54.trk

This is the position of our plane at the moment of shooting... null

@WarthogOsl On the first screenshot You can approximate how high was our nose. Definitely nothing that could qualify as "manual lofting". At this screenshot You can see missile's heading as 352. 17 seconds later (last screenshot) You can see it's heading is opposite (172). But still it's all out of the point, and I have enough of such a pointless discussion. It always have to get to the point where instead of a factual answer from a competent person, you get a lot of useless comments from fanboys. And it's bloody tiring to fend off nonsensical attacks that implicitly suggest that you are only a complaining jerk, without understanding for your benefactors being carried under the clouds. My devotion to the module is proved by the history of my purchases, which shows that the F-14 together with Supercarriers three times, once for myself, two for friends with whom we had a lot of fun playing war in this module. And now it is ... as it is.

Thanks @DSplayer. What I read is that Mike as couple other respondents in this thread confirming, that reaction on "lofting" is actually bug, what is in line with my and my colleagues feelings. So my question about quick fix for this issue (between others) is not as out of sense as some here implies.

If You're so kind, please post the link(s) to such information, clearly stating what's the reason of that, please. Honestly, never meet with such information from any of HB personnel. And it's nothing like intentional manual lofting, as we're usually flying fast and high, it's just one of the scenarios that can happen in the heat of action.

We're flying it for more than two years, and with each and every patch that comes out, we notice constant degradation of efeiciency in Phoenixes employment, while our techniques improve due to the practice and knowlege we gather with each hour we spent in this beauty. And like I said, since the recent changes in AIM-54 flight model, the joy was replaced with frustration and awaiting for the patch that will get us back to the times when using the Phoenix was not alike to playing roulette. How can we think seriously about any engagement, when shooting to the plane that is at altitude requiring to pull the nose around 15 degree over the horizon can cause us to shot ourself in the back, or other colleagues flying behind us? C'mon, You're not the only one who can call yourself the lover of F-14 by HB, but recent decisions about changes in the game engine and module itself really narrowed down the options, and for devoted ones render the hard time to keep with this attitude.

...as long as You're using the F-14 for sightseeing, but I am concern rather about AIM-54 that became useless.

Any chance for a hotfix? Waiting all summer for finding the meaning of flying the F-14 is "a bit" depressing.

Here are the movies. This one is from CP/G position, no response on levels rotary after he's back in control of TADS: This one is from my (pilot) position, for some reason no microphone was recorded: Track is bigger than 5 MB, so I put it on GDrive: https://drive.google.com/file/d/19usTK4pwmzPiMtmDyrwAp4sJrOGBKPv4/view?usp=sharing

It's faster just to press the button to cause the turn of TADS to my LOS instead of calling the "check my LOS", then waiting until the CP/G will manage it. In the heat of battle, this possibility is priceless.

We're not changing seats. It's on multiplayer sessions. and yes - CP/G sets the levels to suit his needs, but when me as pilot takes control, levels are changed (as I assume) according to my settings. Then he gets it back, and goes angry as he have to set levels back for him. To me it seems like after such action, the TADS switches to the auto gain control when I look on VIS set to TADS on my screen. I will try to get the tracks and perhaps record the short movies from his station.

My CP/G reports an issue with TADS levels (gain, brightness), after I'll take control over it then return it to him. If this is not in the bugs backlog, we'd appreciate if it would be considered.

I put the Bx7 on the periphery of the Bx8 point circle and if Bx8 is centered on the target(s), at least one of the missiles achieve the target.

This specific maneuver is done always the same way and there's no possibility to control this behavior. Obvious solution in this situation is to switch weapon release mode from "SERIE" to "IMP", then put the second Bx7 slightly in offset to the first one, so the "fifteens" goes to the target from two different directions.

This "swerve" is actually the maneuver that increases the probability of achieving the target by decreasing the flight track predictability in the final flight stage.

Hello, I've just noticed, that in non-A/A mode, on the radar display, started to appear the radar centering indicator (?), but I can't find what specific mode and settings cause to appear it. This indicator is not the same as the one that appear in A/A mode, as it has only one horizontal line instead of three. Can anyone tell me please, what conditions cause to appear this indicator?

+1

How unfortunate! That's the only servers we fly on with my CP/G

Can anyone please confirm if this issue is still valid?

Hancer, as I saw, You're using the BotSay on Your servers that uses some kind of webhook. Try to disable it and restart server(s), then check if it changed the situation anyhow.

Nope, It was shoot flying straight level to the target on the same altitude. Unfortunately, the track wasn't saved. EDIT: Tried to recreate it now, and indeed, shooting when climbing around +15 to +25 causes it.aim54_2.trk

That was in MP. I have waited for my CP/G to get into the cockpit and completely load the cockpit to minimize probability of desync, but still this happened. Whole time when my CP/G was engaging the enemies, I was in cockpit.

WPN page shows two Hellfires, while there's none of them available.