Naquaii

Correct, going half-action reverts back to the basic mode, pulse or pulse-doppler search only but it's quicker than reaching for a button! :-)

A human RIO would just go half-action and release. With Jester it's easiest to just quickly depress and release PLM, when it doesn't find a target it should release and revert back to pulse allowing Jester to take over again.

The intention is to eventually simulate having external cooling available when you have the external air connected. In regards to the -C being described the same as the -A in the manual, the answer is simple, we didn't know! The documentation we have describes only the -A but I'll keep it in mind for revisions.

A CCRP drop is generally not precise enough for precision strike which the LANTIRN was integrated for. For precision delivery of dumb bombs CCIP (Computer Pilot) would generally be preferred, CCRP (Computer Target) is intended for saturation/area bombing or toss bombing which is also quite inaccurate.

15 or 16 total is what I'm hearing from the guys. A human RIO can also hold the limit switch which changes it to max 6, Jester can't currently do that as we haven't decided on how to handle the switch as you need to hold it in place. In regards to display mode you can actually already tell Jester to change that via the wheel. It's under CMS/RWR and then RWR Display Type. I must confess I never used that as I usually fly RIO for the more advanced missions! :-) My bad on that one.

As the HUD can't draw more than one of each the gun sight takes precedence. Thus the VSL/PAL modes won't show visually.

I'll forward that, sounds easy enough.

It doesn't really work like a filter, it prioritizes the selected category instead. Meaning that if you have only two threats, as an example two AI, those will still show after setting the switch to AAA if you have no AAA threats. If you however have a lot of threats the selected category will show first and then other threats according to threat level until max number of threats are displayed.

Problem is we're also missing data on the PTID, especially regarding all the different menus available. It's less of a black hole than the -D but still missing critical stuff.

It's still on the todo-list, missing functionality atm.

We're always happy to recieve new information if you have any. The problem with the F-14D is that the manuals previously available on the net are the unclassified -1 NATOPS which details systems pertaining to everything but weapons and sensor systems. This in itself is far from enough information to do a combat simulation of an aircraft, it would however be enough to model an aircraft just for flying it, enough for MSFS not for DCS. We simply haven't found information detailing the new radar and weapons employment systems in the F-14D as these are, to my knowledge, still classified.

Code-wise it's not too difficult, thing is we have no info on the missile every being used by the F-14, was it after the F-14s service life? Did it require features not present in the F-14A/B? There's just not enough information for us to act on unfortunately.

Actually, both Link 4 and Link 16 are very much line of sight only, the Link 16 even more so as it has a higher frequency. If you don't have a direct line of sight to the AWACS you'd have a real hard time getting a link. With the AWACS usually being at high altitudes it can sometimes work as you'd be looking up from a valley towards it but still hard.

Just and FYI, the reason for the COMP panel being important for all navmodes is that the WCS compares the INS and compass to calculate the magvar. At least that's my understanding.

The designator moving like that is likely due to the sensor moving about on the target because of changing IR/RCS with aspect. It also means that it's most noticable close in. This is something that's hard to model in a simulator that doesn't simulate that and if we did it would have to be a more or less random algoritm.

Ok, cool! The manual mode would work the same except for no hud indications at all, this is normally the mode I use when dropping from a LANTIRN on own aircraft and would work well in your case as well. Only difference from computer/plt is the lack of ballistic calculations ofc and thus no HUD indications.

Are you trying to do manual bombing runs using the manual mode or using any of the computer modes? None of them use a waypoint as the basis for the drop calculations. The inaccuracy of the INS is the reason for this and also why even the Computer/IP mode needs a visual fix before delivery.

Our -B is based on the -B NATOPS from 95 for a F-14B Tomcat without DFCS and PTID upgrades. See attached image for the exact date information.

The AWACS works as in MP. You tell Jester to tune the desired AWACS. If you use a human RIO he'll have to check the frequency on the kneeboard or if you want a F2F link with AI wingmen set the link to 300 MHz manually.

The NATOPS we use for our F-14B actually specifically mentions that the pitch and roll SAS switches reverts to OFF. It does mention that they're disabled while the paddle is held but also says that.

The frequency for the AI wingmen are by default set to 300 MHz. If you ask Jester to switch to F2F under the datalink menu and then choose 300 MHz from the presets in the same menu (it's marked as AI F2F) you should link up to your wingmen. This should work both in mp and sp.

Can't really detail further but rest assured that it's on the list.

Not at this time unfortunately.

Short answer? In DCS, they don't currently do anything unfortunately. Long answer: The MSL options switch allows the RIO to set the AIM-7 to PD mode or the Phoenix to active mode. PD mode for the AIM-7 allows the newer versions to be guided with pulse doppler giving greater range. Active for the AIM-54 tells the missile to go active immediately after launch, in effect reducing it's range greatly (this is normally not needed as the pulse modes does this automatically and the pd modes do this when at short range). The missile speed gate configures the missiles acquisition gate, allowing the RIO to fine-tune the missile to find the correct target easier. The MSL options switch is something we can feasably model and intend to eventually do, the missile speed gate is a bit undecided as we're talking % of P-kill and it might be a lot of work or not even possible currently in DCS.

Thanks for the info! Not something that's really covered in the manuals! :-)