Naquaii

No, it doesn't work like that. Both IRL and in DCS. Firstly, IRL the missile might still be launched outside of a range where it can find a target, in that case it will go straight until it finds a target and then track. The seeker might find the target further out and it might not find it until further in. It all depends on target RCS, 18NM is a long way a way for a missile seeker, even IRL. In DCS it also does not work like that. We use the missile seeker modes available to us and in TWS or PD-STT we guide the missile from the F-14 directly as those are modes supported by the AWG-9. When launching the missile active of the rail we literally tell the missile what direction to go and that it should be an active shot. We cannot control at what range the seeker will find a target on it's own. That part of the code is not available to us, we can not make our own missile guidance code, we only input missile parameters into EDs functions and missile seeker range is not one of those.

Yeah, the RWR not needing to see reflections bouncing back from a target but instead the signal directly from the emitter means that a maddog shot should really be like having a screaming maniac coming at you. Everyone should see it clearly quite far out on their RWRs. But the current DCS implementation just doesn't allow for that afaik.

Yeah, I understand what you mean. Was asking cause it behaves as if you have BRSIT enabled. I have yet to see this myself but I'll try to have a look at it in the weekend. Not really, you'd have to ask ED about this. I'm not entirely certain it's exactly 10NM but it's somewhere around that number. IRL that number would depend greatly on seeker performance and target RCS. It's not an unreasonable number, just very generalised. The biggest issue as it is is the RWR behavior as the RWR should be able to see the missile seeker from much farther out even if the missile does not see the aircraft carrying the RWR.

Prepositioning the missile seekerhead means that as soon as the missile is free to meanuvre the missile will turn towards where the seeker is looking. So in effect it will make an immediate turn and then fly off towards the direction of where the track was at launch. That is not an additional command to the seekerhead positioning, it's the same thing. What you're describing sounds like a boresight launch where the missile flies along ADL and then engages when it finds the target, that should only happen when you have no track or have set BRSIT. What you described earlier sounded like ACM with BRSIT set, if you set BRSIT you override and force a boresight launch along ADL.

Nope, only a command to go active at launch and what direction to head out at. That's not a launch at an area though, it's a launch att the exact track direction but within those parameteres it behaves like a maddog launch. Leading the target will at most only cancel out any after launch turn the missile will have to do to go in the correct direction. If you lead the target the missile will launch but then immediately turn directly at the target cancelling out the lead. The missile will only begin to lead the target once it acquires a track itself, prior to that it has no idea of target aspect or velocity, only the direction of it. Just keep in mind that this is specific to when you have manually set the missile to PH Active in PD-STT or TWS, no other active launches.

The part about the missiles in the AWG-9 section is more about what the different radar modes can support but I might add a link from there to the AIM-54 section and add some more tips and tricks about the missile in the DCS section.

In the active launch case the missile does not use english bias, it simply flies straight down the indicated sensor line of sight while going active. As long as there is either a radar or TCS track this should work. I've yet to see this not work under the right conditions and it has been working recently for me but I can try to have a look at it when I have the time. I guess it is this sentence you are referring to: "When using boresight or ACM without a track the missile will launch along the ADL locking onto the first target seen while launching at a non pulse doppler radar track the seeker head will be prepositioned onto that track." The first part refers to BRSIT or ACM without a track and that it launches along the ADL in that case while the second part describes that the seekerhead will be prepositioned to make the missile fly out along the line of sight of the sensor tracking that target. (At launch that is as the missile can't be controlled afterwards.) With ACM and BRSIT the missile will always launch along ADL as BRSIT selection forces the missile into boresight mode and disregards all tracks. As for fallback to SARH, that does not work in DCS as it's not currently possible for us to model that. It's on my todo list to clarify in the manual that this describes how it should work but that it's not implemented like that in DCS due to limitations atm. That said the fallback to SARH would only work specifically for PH Active which is when you have the radar in TWS or PD-STT but manually select active launch. Like I said before the pulse modes are technically incapable of controlling the missile in any way, so no SARH. PH Active is a different thing than ACM Active which is what you get in ACM. As for the desync issues we have been looking at those but as far as we've seen this is related to poor latency and general connection between server and client and unfortunately and issue out of our hands as it's not in our code. That said my personal opinion is that there seems to exist a strange bias against the F-14 and the AIM-54 due to the range of the Phoenix in the competetive PVP environment while the AIM-54 is absolutely not an undefeatable missile, in many cases it's much easier to defeat than the other allowed missiles. And additionally the desync issue is not unique to the F-14 even though it occurs more often. That said we do ofc still very much want this issue fixed.

The AWG-9 can’t send commands to the missiles in pulse, only in pulse doppler. So when launched in P-STT it gets a pre-launch active command and an azimuth and elevation to fly out along, but in effect it’s a maddog shot along the sensor line of sight (tcs or radar). The 10NM limit is how missiles in DCS works so the missile won’t be seen on rwr or guide until within that limit.

This is working as intended. P-STT always launches active and is not supported as pulse can’t command/support the missile. The missile itself won’t track until at about 10NM even if it is active as in DCS the missile seekers have a hardcoded range of 10NM. That is also why the rwr warning appear at that time and that’s not something we as a 3rd party dev can control.

We're kinda trying to avoid adding things we don't have documentation for. We don't know what other upgrades or modifications that display depended on so unless we find more information regarding this whole configuration I'd say that's a no for now.

We do know about the double line TID readouts but as far as we've found that was related to the later software tapes that we don't have any information about. Likely the same software tapes that added TID menu functionality. Our current implementation with the alternating standard readout was slightly earlier than that and shows more or less the same information but a bit slower. The latest -B we model might've had the two line readout IRL but we just don't know and even if we knew for sure we're lacking the needed information for that, that's why we chose to stick with the current implementation.

That is correct. Area track uses the whole of the image to try and track an area unlike point track where it uses a single point in the center of the image to track. For a INS guided positional track you need to have a designated target or track a waypoint, rates track in the LANTIRN is a bit unreliable. The area track and scene track in the LITENING and AT-FLIR work the same.

Not that I think this was intended by us it's also not an issue as it seems to be realistic to me! Locking onto a human dangling in a parachute with a radar would be quite hard as he's unlikely to give off enough of a radar return. The TCS however would be able to lock onto the contrast of the human and the parachute given the right conditions.

IIRC the visual representation of gates were implemented but it seems they are not working currently. We'll have a look at that and the fact that the TID shows targets that it shouldn't. The gating functionality used to track targets in STT is though, it's the visuals and those tracks that aren't working correctly it seems.

The TALD is not a weapon we model ourselves. If ED add them we might also add them.

As far as we know the only valid TALD loadout on the F-14 is one on each fuselage station using a TER for distance.

We have had a little bit of a discussion about the breakaway and concluded that we probably set it to 0.4NM due to video footage as we couldn't find a better number. After rummaging through my documents we concluded that 1000ft is probably a better number and co-incides with the inner cue. We'll have a look at the gunsight accuracy, it's not something we've noticed before.

Most likely. We have documents listing the loadouts possible in DCS as validated and approved and this is not one of them. This one in particular does not make sense for anything other than display as the aircraft sees a TER as a single payload that it can pulse multiple times to release all mounted weapons. So if this was actually done the results would be... interesting! Physically mounting something to a hardpoint is one thing and actually using it another. The IRIAF seems to be particularly good at showing off stuff hung on their F-14s that we have no proof of actually working.

Yeah, the issue here if so is the missile itself. Unfortunately that needs a bug report to ED in the DCS 2.5 bug forums, as we can't control the missile after launch in this case in our module. Afaik there's also a range limit for when active missiles show up on RWR in DCS, so even if launched active they'll not show up until somewhere around 10NM. The antenna seeker limits on the AIM-54 is somewhere around 60 degrees afaik so 40 degrees isn't impossible at all but that still doesn't change the fact that if the missiles sees you it should warn you.

As I said in my earlier post, P-STT does not support the missile and thus will launch active directly at the sensor line of sight.

When loading up the module the rwr code marks all aircraft radars only existing as friendlies as such as that's how a threat library for an RWR would be constructed IRL. So if you have a mission with hornets only on one side, an F-14 on that side would see them as friendlies. If you then open the mission editor and add hornets to the other side as well the rwr in the F-14 will then not mark them as friendlies as it would then see that they exist on both sides.

Yet that isn't what you wrote. Maybe people don't care as much about something that's obviously a bug and will be fixed? Yet again you talk as if we're ignoring something because we want to cheat and you talk about bias yourself? Maybe you should check your own bias against an aircraft you clearly don't like? At some point you might want to take a step back and realise that if everyone is "misunderstanding" you, you might want to refrase?

Because having our missiles completely immune to chaff would be a cheat. What we're after is tuning them to be affected the right amount. The chaff is not stationary when launched from the aircraft but it becomes so later on so will affect doppler radars, at least at first. If you want to make your point please try to not lie to reinforce them. This is the 5-6th time you claim we ignore issues that are clearly bugs and that we have acknowledged.

We have been chasing changes made by ED to these values and are continueing to tweak them. As GGTharos says above those values is a sort of percantage chance for the missile to go for the chaff, the issue that exists currently is that a player can just continue to dump chaff and each bundle will make a new "dice roll" if you will. So even if we set it very low to compensate it will still depend greatly upon the amount of chaff dumped which is unrealistic as IRL the effect is not that cumulative and also dependent on speed/wind etc. Setting it to zero is not something we will do as that would in effect make our missiles cheat.

I think you've got some things wrong here unfortunately. In P-STT you never support the missile, it will always launch active along the target line of sight. You say you tell Jester to break lock and then P-STT again, but on what? From the image it looks like the missile is launching straight ahead which would suggest a boresight launch. If that is the case it won't matter if you support it or not which you can't do in P-STT anyway. The only difference with a P-STT track would be that it would launch at the direction of the track and go active. It still wouldn't be supported. After launch the missile dynamics are entirely out of our hands as it's then EDs missile dynamics that take over. But what are you basing the 40 degree limit on?