Naquaii

Not currently. And it would present a number of issues to implement as well. My two cents is that this is far down the rabbit hole that I'm fine with it being limited to human RIO only.

Not exactly, ACM does other things as well. If set to PH ACT in STT it will still go for the radar line of sight of the target but if done in TWS it will currently revert to a boresight shot as it is in DCS. IRL setting PH ACT would mean that it would go active immediately but then still receive commands if in PD STT or TWS as the real missile reverted to SARH updates until own active lock was achieved. This level of control is not currently available or possible in DCS.

Ah, I've ever only heard it referred to as ATC (Active Transfer Command) but as it is our information is quite explicit on it being pre-launch only so atm it is what it is. It might change with additional information ofc.

Not sure what that acronym stands for to be honest.

Yes, as discussed earlier in this thread there's currently a bug that we hope to fix as soon as possible with that.

RA - Range from own aircraft to hooked symbol. AL - Altitude of hooked symbol. GS - Ground speed of hooked symbol. BR - Bearing to hooked symbol. (Not magnetic) MC - Magnetic Course. MH - Magnetic Heading. HD - True heading of hooked symbol. LT/RT - Aspect hooked symbol is showing own aircaft. AS - True airspeed.

Depends on exactly what you're doing and what you're trying to do. If by TCS-STT you mean that you have the radar slaved to the TCS and have a TCS track then the missile will launch active and it will launch in the direction of the track and then not be guided further by own aircraft. The missing functionality here is that you should also be able to have a PD-SLAVED STT in which case you have a TCS lock but also a PD rate lock which will allow for a normal SARH launch of the AIM-54. This has never been working as we haven't implemented it yet. As for the AIM-7 you can launch it at the TCS track as long as you have the radar slaved to the TCS and transmitting, all that will be missing in this case is lofting as it has no range. When we eventually add the locked STT slaved modes this should be possible for the AIM-7MH. In the case you don't have the radar slaved to TCS the TCS will never matter for these missiles and all the normal launch types apply as normal.

They are described under http://heatblur.se/F-14Manual/general.html#computer-address-panel-cap. The key descriptions under numeric keypad corresponds to the readouts. I might later on add a prefix list as well to make it clearer.

Currently bugged unfortunately, we just now discussed it in the patch bug report thread. Hopefully it'll make a lot more sense once it's fixed!

Yeah, np, it should be exactly as the TA you describe very well in your articles!

Yeah, unfortunately it seems some gremlins have snuck in there, it does indeed not seem to work as it should currently. We'll be investigating that closely and hopefully we'll be able to sneak it into a hotfix. The only really new one is target aspect (RT/LT) which unfortunately seems bugged atm. The others are the same as the older readouts. HD would be heading.

It should indicated what aspect the track is presenting to you, LT being left side and RT being right side and then an aspect number indicating what angle from the nose on that side. So RT 30 would be right 30 meaning your on his 1 o'clock and LT 150 means left 150 meaning his 7 o'clock.

Thanks! The mission probably doesn't matter, that should not be possible. We'll have to look at that and see if that particular fix somehow was left out or if it's a bug.

Yeah but you shouldn't be able to lock them up.

I'm not sure exactly what you mean by this. If you have no track for the target on the TID (no trackfile) the missile will never go active in any situations as the WCS has in effect stopped supporting the missile as it has no track associated with the missile anymore. A lost track (marked with an X) should still allow the WCS to send the active command if the track position is within the antenna scan zone (i.e. the radar will sweep past the missile and be able to send the commands). Wether the missile will actually track will then depend on if the target is close enough to the extrapolated, lost track that the missile seeker can see it.

A track is marked as lost when it hasn't received an update for 8 seconds, so 5 scan patterns. Then it's extrapolated for an additional 14 seconds or 2 minutes if Track Hold is active.

Afaik, yes. I'll ask Grover to elaborate.

No, that's incorrect. The INS is used as a correlation reference in the RWR, otherwise the aircraft wouldn't know to associate the same threat with the same emitter when the aircraft turns, it'd spew out new multiples of the same thread indicator as the aircraft banked as it wouldn't know to associate them to the same threat. This is however not a perfect process so there might still be sporadic doubles, esp as the rear quadrant sensors are located on the stabilators that themselves move (which the RWR can't compensate for) but without INS it would be much worse.

It should be the same regardless, maybe it's harder to see if it's a lost track but I'd have to check. The missile does not confirm anything, it doesn't send anything back to the AWG-9. Active indication is simply that the active command has been sent.

It doesn't really have anything to do with time, depending on what is set using the target size switch the AIM-54 will be commanded active at a given calculated range to target. At that time the missile will have to be within AWG-9 radar scan zone so that the WCS can command the missile active. If it isn't the missile will never get the command as it's transmitted via the radar. After that it's also a matter of if the target is close enough to the missile for it to see it the track is lost. If the track has moved far enough away from the calculated lost position the missile won't find it. So unlike newer missiles you need to look at the target and the missile with the radar until it goes active at which time the TTI numbers will flash.

In all cases should the target of an AIM-54 get a warning as long as it has an RWR. Either the missile is in SARH or ARH but both gives a lock and engagement warning. A "TCS Phoenix LOS shot" is when you have the radar slaved to the TCS which makes the AIM-54 launch hot along the TCS line of sight, giving an active missile warning. The AIM-7 can do the same but the WCS needs to be in on to allow for the CW illuminator to go active at launch, this is not flood but the CW illuminator following the TCS line of sight if the radar is slaved to TCS. Apart from this there are also TCS-STT modes where you have the radar slaved to the TCS but also lock on in rate or range (PD or P). These behave like normal STT but the angles are tracked using the TCS and not the radar but the range and rate come from the radar. This is useful if the target is hard to track with radar for whatever reason (jamming, clutter). This is not currently implemented but would be activated by going half-action in radar mode on the TCS and highlighting the correct return on the DDD and the going full action resulting in that kind of STT. The silent AIM-54 shots are bugs but we're hopeful that fixes we're implementing in the next patch will solve this.

Obviously I'm referring to that we've drawn this conclusion from the information available to us and like I said if you stumble across any evidence to the contrary I'd be happy to have a look at it. I do get you point but I don't agree with it.

That's part of the seeker logic and not anything we can set and like GGTharos said, there's no such thing as a "notch angle". Notching is about relative speed being blind to a radar, not angles.

And we have documentation explicitly saying it only works pre-launch.

No, that's not currently possible in DCS. When it's active it's active and on it's own as it is. If that change we'll implement it of course but not currently possible.