Naquaii

It does but due to DCS engine limitations we can't point the missile itself, we can only control the seeker state. What happens is that the code checks whether the intended target is within the seeker area of where the missile would be if going for the held track and if it is it activates the missile. A truer implementation would be to tell the missile exactly where to go and then activate the seeker if within the scan zone there but that is not currently possible. Against a maneuvering target this is unlikely to result in a hit ofc but that is also true of the real functionality.

Thanks! Seems to be a new bug introduced at a late stage that we didn't catch, we've confirmed it and are working to fix it.

Found a bug with the LTE being too short, we'll have a look at that, thanks. The LTE should be 1.8 secs for everything but ACM and Flood which should be 0.7 secs.

Yes, as long as the target is inside the flood area but you need to make sure the missile is positioned so that it's seeker sees it before it's too late, otherwise it'll go dumb. This is not that easy and also the reason it was regarded as a bad idea IRL.

The only ACM mode that works outside of 5NM is PAL which works out to 15NM. PLM and VSL is only inside 5NM. The LTE for the Sparrow should be 1.8 secs. That's what I get when testing.

Can't reproduce. 1. How are you trying to lock him? 2. Flood work fine for me using BRSIT but you need to be very precis with aircraft pointing. It was regarded as a really bad idea IRL and very finicky. 3. Noticed nothing strange. 4. Same as above. 5. Works for me. ACM not needed and BRSIT should not be pressed. The slave switch must be set to RDR to allow the radar to slave to the TCS to guide the AIM-7.

It's strange though, I have the same pedals and have no issues at all. Maybe you could try to remove the standard configuration in the main dcs folder as well? It should be called the same thing and be located in the same position as in the saved games folder.

Yes, this has been discussed at length before and the non PTID LANTIRN usage was indeed an oddity that was only used in the beginning, but it did exist afaik.

It is fully utilizing what we set out to when we were talking "missile api". Anything else is out of our hands and not something we have been part of.

It has been since the november patch. This entails the ability for us to control seeker activation an lofting, everything else is on EDs side.

Please try rightclicking the column header saying saitek pro flight and clear the binds completely and rebind. That might fix this. You could also try to manually delete the bindings for your pedals in the saved games/dcs/Config/Input/F-14/joystick/ folder and then rebinding them.

It will be set to norm unless you tell Jester otherwise. The tgts switch can be set via the Jester-wheel now as per the patch notes.

The missile will have to switch modes to again look for the semi active returns from the AWG-9 as the seeker can't do both at the same time, just as any other radar. And this is just in case it doesn't find the target ofc.

Jester does not set this automatically, he will default to norm if you don't tell him otherwise. This is more of a preference than anything but you can tell him which setting to use via the Jester-wheel as per the patch notes.

The TGTS switch affects a lot of stuff, some of it hard to model in DCS. In fact it's more of a general setting for expected target RCS and affects amongst other things missile launch zones, tws minimum track initiation range, thresholding settings in tws as well other radar related stuff. So it very much affects both weapon launch settings as well as radar stuff. The range at which the missile ATC and the activation of the AIM-54 seeker occurs seems to be mostly related to the range at which the missile seeker is expected to actually detect and track the target. I do concur that the battery life is probably not too much of a worry here as the large setting was obviously expected to work. The two reasons I can think of for not wanting to switch to active too early would be that you'd want to deny the enemy seeing the active seeker and that having activated the seeker with it not finding a target would have it switching back and forth between active and looking at SARH returns as it can't do both at the same time meaning less time in either. The original intended use of the different settings, afaik, would be large for bombers, norm for fighters and small for missiles. That you have to support the missile until ATC was probably not as much as a thing IRL as you were expected to support it until a hit anyway but in DCS it will ofc be a worry for many. In any case, the new information we have is quite clear, the implementation we now have is the most realistic one within the limits we have in DCS. And yes, that information do indeed confirm it being range based and not time based.

The simple fact is that there were still bog standard F-14As around until the end. Saying that an F-14A is a late F-14A doesn't equal PTID. Heck, there were even F-14D with fishbowl TIDs. Like I've stated before, the missing parts in regards to information is all the different menus for the PTID as well as the Sparrowhawk HUD weapons implementation afaik. Afaik the PMDIG upgrade included stuff other than the PTID, as it also affected other things in the aircraft apart from the display itself. The introduction of the 1553 bus amongst others. That said, even if we did get that information it does still entail a lot of additional work and is not something we're commited to as of this time. We do hear you and I wouldn't mind having a PTID F-14 or even a F-14D myself but it's not currently in the cards.

Changed DDD description under cockpit and general chapters as well as the AIM-54 description under the weapons chapter to reflect new missile ATC behavior. @kotor633The manual is located as a pdf under the docs folder in dcs/mods/aircraft/f14. It is not as current as the html version as the pdf build is quite a lot of work currently.

Yes, pretty much. According to our sources the delay could be long enough that it affected handling.

The position lights can only flash when the anti-collision lights are off and with gear up.

If you set both throttles at the same location and they after delay end up in the same zone (setting) it is correct.

So you're saying you bounced 100 feet up into the air and still trapped? :music_whistling: In all seriousness though, afaik what we're talking about here is looking at adding hook skipping etc and having the position of the hook actually influence the trap. If we can manage this you'd need to be more careful with AoA et al when landing.

Just to clarify, if set to the same position both throttles should eventually catch up, even in afterburner. If you're throttles are physically at the same position and you see a larger difference between engine rpm than like 1-2% or the throttles visably in different positions in the pit there's likely something wrong with your input hardware as if both throttle tell dcs that they're at, as an example, 80%, that's where they'll be in the aircraft as well. The afterburner delay we're talking about is just the time it takes for the zones to light, they should still end up the same after that delay.

We can more or less only set values for chaff resistance in regards to seeker performance. That's what we've been trying to set but how that is set has changed a couple of times which has had us chasing that around. Other than that the API changes we asked for allows us to control whether the missiles loft and what seeker mode the missile is in. Then it's simply about if our radar tells the missile if it sees the target or not which is how it has always been. That's it.

https://www.forsvarsmakten.se/sv/akt...jus-i-morkret/ I know not all of you read Swedish but that is the offical webpage for the Swedish Armed Forces describing night vision goggles. In there it says that it was first with the JAS-39C that the cockpit lighting was adapted for night vision goggle use but that they've been used for nearly 20 years. It then goes on to list them being used in the SK-60, helicopters and the Viggen. That does ofc not mean that it was standard equipment but it was used. And having to content with too bright cockpit lights seems to have been a part of that.

This is actually not a bug but rather a fix to make sure the missile goes active. As the TTI is inaccurate in some cases we made sure it went active as to give the target fair warning. (Still dependent on the AWG-9 actually seeing the target and painting it ofc.) We will be looking at more correctly calculating the TTI and make this stopgap unneccesary but as it's rather complicated it might take a while.