Banzaiib

10/10 LSO material right there.

don't know what to say man, but you're just wrong... but I've hosted a bunch of AA training sessions where we dodge 120's and practice re-engaging and the AIM-120 when launched from the hornet in STT does not give a launch warning until it goes active... period, the end of story. Go test it with a friend... that's just how it is. And that's how it was with the AIM-54 until a patch or two ago. The main difference in communication between aircraft and missile with the 54 and the 120 is the 54 uses radar antenna in the rear of the missile to receive information from the AWG-9, where the 120 uses a radio data link system. They both do essentially the same thing, though, which is receive radar information processed in the aircraft firing the missile. STT firing fox3 does not have to mean you get a launch warning when you're on the receiving end. It's about how the radar beam changes when the missile is fired, which is what triggers a launch warning in the target's RWR.

I've locked and launched on cruise missiles and harpoons... so probably. You should test it :)

This is simply incorrect. Not trying to be rude, but your comment is not correct. The AWG-9 can both guide the AIM-54 via an STT lock AND send target data via antenna on the back of the AIM-54 and signal it to go active. That's just how it works. Feel free to prove me wrong with actual SME quotations on the matter. Also, you can see from TLTeo's comment above that IronMike clearly states that STT locks help guide the AIM-54, which means it is also actively guiding itself as well. TLTeo, i believe IronMike is referring to shots inside 15 miles, which would be active off the rail since 54's go active at 15 miles in DCS right now. I believe that should actually be closer to 10 miles... but why fix something like that when there's a bunch more to fix regarding missile guidance.

Truly outstanding work. I can't get over how real that aged paint looks. Insane...just mind boggling.

FM over textures... i like HB's priorities in this regard. I can wait for this one to be fixed... would rather have a Forrestal and the 14A, quite frankly.

I appreciate the response, but that's not entirely how it works IRL or in DCS. IRL, the AIM-54 receives guidance through antenna in the rear of the missile as well as the seeker head itself, and does receive a command to go active at the appropriate time, even when launched in STT, which cannot be modeled properly in DCS right now... i get that. Also, in DCS, the AIM-54 is not active off the rail. It goes active at about 15 miles. Also, in previous patches, the AIM-54 did not give a launch warning right off the rail when STT locked, that's why I'm asking.

Was training with buddy in F-18 the other night, and noticed that he gets a launch warning from the AIM-54 as soon as it's launched if I have him STT locked (at any range - we tried 50nm, 30nm, and 20nm). In TWS, he doesn't get a launch warning until the missile goes active. That does not happen with the 120. When the 18 has me STT locked, and he fires a 120, I do not get a launch warning until the missile goes active. Is this working as intended?

it's not his fault... it's entirely possible they are flanking you, and thus the notch filter makes them disappear. They may also be turning cold, and if they're not + or - 100 kts compared to you, they'll disappear. Try switching to ground stabilized mode to see their true direction (will show if they're flanking on data link). In aircraft stabilized mode, you see only their relative velocity, not their actual heading. Also, get below them. The AWG-9 does not like ground clutter. It's very hard to break a pulse lock if you're below them, even if they flank or go cold.

14 works fine on warthog hotas, just have to bind the axes properly. I'd just delete the current axis bindings and re-map them manually. Should only take a few minutes to get them right. If that doesn't work, do you have some special setup in the TARGET software?

100% agree, shame our relations with Iran are so crappy. C'est la vie... Did the AN/APG-71 have medium PRF? Is that classified i wonder? also, 10/10 would buy

KC-10 is a beast! +1

for the sake of realism, why don't the wings break off?

This would be my guess too... or how to turn off your ground safety and fire mavericks... either one. :)

That was discussed in this thread (and was the original topic actually, so not off topic at all because PAL = CW pulse locks), and determined that CW can guide the AIM-7M, based on HB's responses and their documentation (see earlier posts in the thread).

That's exactly what I'm saying. My radar is not breaking lock, the AIM-7 just stops guiding... which is kind of silly and very unrealistic when it's a CW pulse lock from below the bandit (no ground clutter). (I'll post some tracks and tacviews to show what i mean) What I think is really going on is that ED's missile guidance code is so bad or unrealistic that the AIM-7 is basically just an AMRAAM with horrible notch resistance that stops guiding if you break lock... so basically none or very little of the real physics behind the AWG-9 are implemented currently both for the AIM-54 guidance and the AIM-7. This would explain why they had issues with AIM-7's guiding themselves when STT locks were broken in the past... and oh by the way, R-27's and R-33s have had that issue as well. I sincerely hope that ED does a serious pass on their missile guidance and multiplayer sync code after the push to release the 16 dies down a bit... because if you really get into air-to-air fighting in DCS, you'll find BVR extremely lacking. It's probably the best there is, don't get me wrong... but that doesn't mean it's good. And any debate we have or discussion about real physics and real tactics is made mute by the fact that guidance logic and code is not following similar rules... or coded to at least appear to follow them.

This problem has been mentioned before, and you are not alone. Almost every single flight I see a bandit on the TID, tell him to lock him, he says "OK", followed immediately by "lost lock". Maybe the bandit is maneuvering, maybe it's flying perpendicular to the radar so you can't lock him, despite him being on the data link... there are, actually, quite a few legitimate reason why this would happen. To sort out legitimate reasons from Jester just being stupid, I'd need to see a track file

100% I'm not sure what changed about the pilot default.lua, but I had to add the commands for it to work. Probably because they added some commands to jester regarding elevation... or something...

Thanks Quigon, and that makes complete sense.... but... Then why can bandits notch / beam an AIM-7M fired from a Tomcat so easily? Shouldn't it be the most notch resistant thing in the game when you've locked them via PAL? Maybe I'm wrong, but I thought the notch filter was a component of pulse doplar signal processing. I get that ground clutter should be a problem, but damn, all a bandit has to do is bank hard and the missile drops lock as soon as it near 90 degrees, no matter the range, or even if you're underneath them... The AIM-7 is so bad it's not even worth carrying on the tomcat.... and that's super disappointing, since it really was a pretty effective missile IRL (looking at you ED... fix your missile guidance and MP desync).

FM feels great, and her performance is so close to all the graph data available, it's insane. There is so much depth to how she flies, and each of the last 3 patches have been awesome improvements. Really looking forward to the "A".

My apologies if this has been brought up before, but I recently RIO'd in the Folds of Honor gun tournament, and spent 1/2 the flight blacked out. Pilot was fine, but when the turning got real heavy, i just stared at a black screen and hoped the next thing i didn't see was a fireball. Anyway, I don't RIO often, I was really just there because he needed a 2nd set of eyeballs to keep track after the merge, but I thought I'd bring it up. The g-tollerance of the RIO is a joke.

*cries in F-14*

The AIM-7M requires a PD lock to guide, but PAL mode locks in pulse mode. Or does it change when you have an AIM-7 selected? Just curious about the behavior of PAL mode when AIM-7 is selected before PAL is.

That's correct. It was AI firing at a player in a dedicated MP server. The MP AI behavior is much improved after the last patch, but fighting magical fox 3's isn't fun... especially when it took you a bunch of time to set up the interaction (startup, patrolling, and all the other logistics of organizing 40 people into a big ole mission)...

this has been reported before, and marked as a bug in the 18 forums, but it's such an easy fix... low hanging fruit for ED on this one. The F-14 has a much lower dispersion, yet it's the same gun as the 18, 15, and soon to be 16... it's so easy to fix this it's insane.