Naquaii

Problem is that both missiles have these systems, they're just implemented differently, and compared to our data on the -A a lot of the -C stuff is conjecture. In any case we're not at a stage where this makes any difference in DCS apart from numbers for countermeasure rejection and seeker performance.

The current wording in the manual is a bit ambiguous, I'll add it to the list for things needing improvement. Like you guys have discussed, the Vc bug only controls the scale of the Vc bug in the STT modes. X-4 being 800 knots opening to 4000 knots closing, NORM 200 knots openening to 1000 knots closing and VID 50 knots opening to 250 knots closing. It's the aspect switch that controls the whole DDD scale in the pulse doppler modes. NOSE has the screen show -600 to +1800 knots, BEAM -1200 to +1200 knots and TAIL -1800 to +600 knots. All this with higher positiv rate being towards the top of the screen.

As we have no hard data on the -C we'll model it as the -A until we find data to the contrary. Correct, this is in the works.

The scales on the sides of the DDD has no set scaling, they're just visual references for the RIO. He still has to know what scale he has currently set. On the very early tomcats the scales were printed on the DDD itself but this was quite quickly removed. The 0 on the bottom is just a leftover. And as the scales change depending on settings it doesn't really matter what side you use for reference. The danger of manually disabling the MLC is that a lot of false targets in the MLC can get processed as tracks by the WCS, both placing unneccesary load on the computer and also using up the limited number of tracks it can hold. Not sure if this is currently modelled, if not, it will be.

The AWG-9 would have to be sweeping over or looking at the calculated track position to be able to send the active command to the missile. The AWG-9 antenna is used to transmit commands to the missile. We're always on the lookout for additional information, we'd need some kind of source to be able to realistically use the information though.

The track hold function was actually enabled automatically for targets under missile attack for this reason, when we get control over the seeker we'll look at adding this if possible. If so that would make the missiles go towards calculated track position and then go active as long as the AWG-9 is looking at that position in space. In regards to the C, we don't have that much info as our manuals are older than the -C. If you have any info feel free to share! :-)

Basically the current AIM-54 works exactly like the AIM-120 in DCS. It will go active on it's own within a certain distance to the target regardless of mode and will do so even in PD-STT. It will receive updates just like the AIM-120 as long as the launching aircraft track the target. The first improvement we plan to add is control of the missile seeker, meaning that we can then control when it goes active in TWS and have it not do so at all if you loose track in addition to enabling the pure SARH mode that's used in PD-STT. 5: Yes, it will currently go active in PD-STT as we have no control over the seeker yet. 2: Currently the missile decides to go active on it's own as per how the AIM-120 works. When the above is implemented we will change this. 3: Sensor LoS is related to radar in P-STT and TCS in which case the AIM-54 will launch active along that sensors line of sight. 6: Correct, due to the short seeker range (within 20nm) all active modes do not loft and while we currently do not set this specifically it shouldn't do anyway due to the short range. We will set to a hard no lofting as soon as we can though, probably at the same time as the seeker update is implemented.

Eventually switching out of PD will loose the missile yes as this i how it was irl afaik. Just keep in mind that currently the AIM-54 works exactly like a AIM-120 in DCS. It will always go active within a certain distance to target. The first improvement we plan to add is to stop the seeker from going active until we tell it to which will mean that we can implement the PD-STT mode were it never goes active as well as fine tune when it goes active in TWS.

This will not be possible afaik when we have TWS AUTO modelled as the WCS forces this mode to support the missiles.

1. This is just the way the AWG-9/AIM-54 was designed as far as we know. 2. It does, if you switch out of pulse-doppler before the active command is sent the missile is effectively lost. 3. Setting the MSL OPTIONS to PH ACT tells the AIM-54 to go active along sensor LoS just as in a pure pulse mode with reduction in range as per those modes. 4. IRL the missile would track actively but fall back to pulse doppler if it loses track. PD STT is advantageous over TWS in that it has longer range and that you have more control over the specific target track, i.e. less risk of attack the wrong target. It's also much easier to loose a target in TWS. That said, a lot of this is still not modelled in DCS as this is kinda the first more detailed active missile in the sim. At launch the AIM-54 behaves much like the AIM-120 in the sim and the first step will be adding more control over the seekerhead and the lofting. This will more or less correctly model the AIM-54 not going active in PD-STT.

The TWS Auto isn’t yet fully implemented and works like TWS Man until it is.

Depends on when and if we can model this, but IRL it seems the missile would be lost as it uses what is set at launch and switching to P-STT removes guidance. Not that this is not modelled currently.

It's not a question about removing it. The DCS engine does not allow seat switching in multiplayer for multicrew enabled aircraft. If this changes we can have a look at implementing it.

The vertical search volume is centered around commanded elevation. 5,75° above and 5,75° below.

Not currently, this will be added during EA depending on DCS functionality that is being added.

Ok, gotcha. The target designator diamond in a/a is mostly a function of how well the HUD is calibrated in relation to the radar, and as those are known facts the display should be very accurate.

It's a function of how radar works more than a man machine interface consideration. Using the DDD correctly in PD modes is quite challenging and takes practice.

They would show the same observed closure rate vs the ground, yes. The rate scale is correct relative the observed closure rate, but yes, you have to judge the relative speed to the ground from where the MLC trace would be. Just keep in mind that you're only seeing the part of the targets speed vector that points towards the radar, i.e. if you were looking at a target that's moving 45 degrees left of your line of sight you'd only see half his real speed. As far as determining when the target approaches the notch you'd have to guestimate when it's near to entering the MLC filter that follows the MLC. The only way really to see it visually is to turn off the MLC filter and try to see it visually. To do this accurately takes training.

Yes and no, the scale corresponds to observed closure rate, in effect being the part of the targets rate vector that points towards the radar. That target would not be in the clutter and/or filter as the ground is not at 0 at that aspect.

Thx! Added to our internal tracker.

I might have to clarify that passage in the manual but while it do indeed show a closure rate that compensates for own aircraft speed it doesn't compensate for the angle of the antenna. So as the antenna sweeps towards the sides the observed speed of the ground will decrease due to looking at it at an angle. That's why it archs downwards.

The ACM modes are pulse by default as it's preferable close in.

The target designation depends on the accuracy of the INS, the radar is used for slant range only. While not accurate enough to allow engagement of preinput waypoints it should be accurate enough once designated, at least long enough that you won't notice it during A/G operation.

There's currently no indication of pitbull on the TID screen, if the whole target blinks that's an indication of the target approaching optimum range. The numbers blinking for active will be introduced later on during EA depending on a couple of other factors.

The groundcrew has no PTT so the pilot do indeed have to set his switch to Hot Mic to be able to hear the ground crew. This does however not stop them from following your commands, you just can't hear them if you have it set to anything else.