Naquaii

The F-14 with F110s were at first called the F-14+ but was then renamed to F-14B. So F-14A+ equals F-14B more or less.

That being so, however much we do not want for this to happen it's simply not possible for us to test against each and every unsupported community mod. We don't know either why it is happening, but if what's behind this is discovered and it's an easy fix on our side we will ofc fix it. We haven't done anything out of the ordinary as far as we know and have no idea wherein the issue lies. It could be becuase of the old F-14A existing and it could be something completely unrelated in core DCS, even if triggered by us somehow.

It's unfortunately due to the addition of the -A and to have both use the same keybinds. The alternative would be to have two keybind setups, one for each aircraft. Your keybinds are not deleted though and can be imported for each controller if you rightclick the controller name itself and find and import your old controller keybind file.

The manual at http://heatblur.se/F-14Manual/ is now updated as follows: Added F-14A specs and DCS version differences to intro chapter. Added F-14A-135-GR (Late) panels and warning lights to cockpit description. Added TF-30 description to general chapter. Added section about HB F-14 AIM-54 implementation to weapons chapter. Additionally multiple errors were fixed in the whole manual. Special thanks to you guys who helped out finding those! The pdf version of the manual will be updated later on as the current build takes a lot of adjustment for it to turn out right. Note: You might need to manually refresh the webpage to see new additions. Default keybind for Windows F5 or ctrl+F5.

The simple answer is that we're focusing on having the -A Tomcat out over the MAK-79s. Rest assured though that we're also tired of not having it done and it will be at or near the top of our modelling todo list after the -A is out.

Link 4C isn't based purely on frequencies, it also uses the set IDs. As has been mentioned in this thread the group ID is set by the ground crew and currently this is done via the ME by having the F-14 that are going to be talking to each other in the same flight. We have discussed adding the capability to change this to the kneeboard but haven't decided on anything as of yet.

At first the bullet fairing and then further on we’re looking at making a version with only the ALQ-100 and light but no promises. Both versions did exist afaik.

The IRIAF F-14A will be an F-14A limited to the weapons available to the IRIAF. It will also come without the TCS and Datalink as those were not used by them. It will also have IRIAF liveries. As for all the other more "exotic" weapons claimed to have been used them, those are very much speculative and not something we're going to implement as it is now. That stance could of course change if we get evidence of their integration and how it was done.

The ECM page is still a thing. HSD is the name for that display itself. There is a setting allowing the ECM to automatically appear if the system get a missile alert or missile launch state though. Yes, this is still in and working. It depends greatly on where the contacts are though.

Afaik the upgrade that added the PTID added that bus allowing the integration of the AN/ALR-67. The information shown on the HSD and ECMD are the same, I was referring to the display being different using the ALR-45 and -67. The different types of lines on the display indicate different types of threat.

That was an early misunderstanding on our part. That is the later integration of the AN/ALR-67 which was possible from the PTID and onwards as that upgrade added the 1553-bus. The AN/ALR-45 we're doing and that both use the HSD and ECMD as displays though. But the information shown on the displays is different.

Unfortunately not. The patch was short notice and we didn't manage. Expect it at latest next major patch.

It wasn't in our list of datalink capable units, we're adding that now so should be fixed next patch.

It sounds to me like you're talking about fire direction radars maybe? The AWG-9 has no capability at all for CW except as an illuminator for the sparrows, but it does not process and receive the cw itself. It uses the pulse and pdd stt modes to point the antenna and then the CW illuminator emits seperately. For a fire direction radar / target illumination radar what you're describing sounds about right. The operator in that case would be looking at some sort of A-scope which makes it easier to see this as well.

Hi! Please see this link: https://www.radartutorial.eu/10.processing/sp16.en.html . A modern radar with a dedicated helicopter detection channel uses techniques not available in an older analogue radar like the AWG-9. If detected in the AWG-9, which would be unlikely as the RCS of the rotor blades is very small, the AWG-9 wouldn't know what to make of it. The returns would be random snapshots of a very tiny target exhibiting seemingly random doppler returns and would make it highly unlikely that you'd receive two identical consecutive returns making the formation of a track very unlikely. If detected you might be able to see faint traces on the DDD from the helictoper but being very very faint and random it would be really difficult to differentiate from clutter. Unfortunately this means that helicopter hunting in the F-14 should be restricted to Pulse mode only. (Unless you're hunting a very fast helicopter ofc!)

Sry about that! The HQ-7 entries are added now but will still show 7 for the search radar and U for the tracker until an upcoming patch when that'll be fixed. The Rapier has also been added to the manual.

The MRL mode is quite illogical because of the way it uses the HCU, i.e. that the HCU controls azimuth and elevation instead of azimuth and range. Like what has been mentioned above you shouldn't place the cursor over the return, you should just press full action immediately when you see it as the cursor show antenna position, not the position you need to move to to lock-on. The MRL was difficult to use IRL also and our SMEs have said that it was seldom used because of this.

Ah yes, but that's likely the bug we've been talking about in action. The DDD MLC is working but the TID one isn't. IRL they would be the same but this bug affects only the TID afaik. We have identified this bug and are working to have a fix for next months patch (or sooner if possible).

Yeah, absolutely. Currently it seems like you guys are the only ones having this issue with a radar that seems completely dead.

That sounds very strange. Could you please make sure to do a repair, check your keybinds and disable any eventual external programs affecting control (like VIACOM)? And also check that your WCS really is in ON and not STBY and that you don't have any keybinds that might affect it. Just wanting to make sure, this is an error we can't reproduce at all.

Not sure which part you're talking about?

"Mostly" level flight might also cause it, keep in mind that we're talking about 3 degrees here. If you have mountainous terrain ahead you might actually have to manually enable the MLC filter. As for going from pd stt to p stt it's not a guaranteed transition by a long shot. Firstly pulse does have a much lesser range and secondly it's also susceptible to a lot of more clutter situations than pd is. With MLC turned off there should be clutter in the DDD as well. And no, it wouldn't be in a straight line, on the DDD it will be a curved arced like described in the manual with the curve being greater the faster your own speed. The contacts on the TID on the other hand will be random within that area and with the MLC logic not currently being stabilised to the horizon even more so.

We have found a bug in which the MLC is incorrectly controlled by how the radar antenna is looking vs the aircraft nose instead of horizon which makes the MLC filter turn off incorrectly while the aircraft is in a nose down or roll maneuvre. The screenshots posted here seems to have the aircraft in a non straight and level attitude and the resulting contacts on the TID looks like ground clutter so this might be it. This issue has been found and should be fixed next patch.

A human could in some cases discern that a return is multiple targets where the computer algoritms wouldn't.

The AWG-9 in our F-14B module is modelled after data we have on the real thing. Unfortunately this is one of the areas in which the age of this radar shows. This has also been extensively tested by SMEs with experience of the real thing. It's just one of those disadvantages that you have to work around.