Home Fries

Found and fixed. It will be in the next update.

I was hoping the LANTIRN could be mounted on the F-14A-135-GR (Late) model, as the LANTIRN was fitted on many A models late in the Tomcat's lifecycle. VF-41 famously brought the SCAR mission to the Tomcat as depicted in the book Black Aces High, and were flying the A model at the time. However, in the online manual the F-14B description says Are we to interpret that the LANTIRN is a B exclusive, or will we get the pod on the A as well?

Fellas, I won't be able to test the Cougar until at least Thursday. Please be patient.

I'll take a look at the Cougar to make sure I didn't break anything.

What hardware are you using?

That sounds right. Thanks! :thumbup:

I figured it was contract maintenance! :megalol:

Try CENTER_MFCD

You can also use "Autopilot On" and "Autopilot Off" discrete commands. They're right next to the entry in the second post's screenshot, but without the "else" commands. Use the ones without "else" commands unless you're using a switch on your Thrustmaster throttle base.

The original LANTIRN pods used on the Tomcat couldn't fire the laser over 25k MSL (I think it was a heat issue). These were replaced, and 40k capable LANTIRN pods were standard in the USN by 2001.

I'll have to fix the Huey code; that was put in before I supported VAICOM/SRS. Thanks for the report. The Mic Switch was primarily fixed for the Mi-8, but the Mi-8 and Huey use the same routine so that may help with VAICOM/SRS.

@IronMike, I'd be happy with the stock checklist without alternate flows, provided you could use the wheel to skip a step or cancel the checklist. Another option could be to use the wheel to initiate a checklist so it doesn't just automatically pop up, though this should probably be selectable in the Options menu to allow for people who want to be prompted by Jester.

I'd be happy if it passed IC! :music_whistling:​​​​​​​

These are excellent points, but this appears to be a classic case where perfect is the enemy of good enough. Dynamic modexes that meet most organizational standards make up the 90% solution, and modexes that don't conform could be static (which is exactly what we have now and therefore no worse off). What you describe regarding the italics makes sense, and since enough tomcat squadrons italicized their modexes, HB could add a second set of dynamic modex numbers with the top corners skewed. This would take care of the kerning and people would still use a non-italicized font for the modex font.

+1

I'm absolutely loving the new kneeboard, but I was thinking that it would be great to transcribe text that is passed by way of mission trigger. This could be done on the Tasking Order page or the Notes page. I'm not sure how difficult this would be to implement because it's probably not directly tied to the communications API, but this would be very useful when pre-set information (like coordinates) is passed (often without a way to repeat).

Right now, we can mark a point on the F10 menu, and anywhere the cursor goes we can see a lat/long. This is great, but I would also like to see the converse of this feature. What I mean is that I would love to manually enter a lat/long and see that point on the map or make it a map marker. This feature would be useful when a mission provides a lat/long for a target or target area, and people who are flying don't have time to cursor-surf the F10 menu. This feature would be especially useful in the F-14, where you can see at a glance where the lat/long of your special waypoints correspond, and you can also have Jester input a map marker as a waypoint (a critical feature in multiplayer without a human RIO).

With each patch, it is prudent to open missions and re-save them in the latest version to ensure maximum compatibility. For people who run servers with a lot of missions, this becomes cumbersome. What I would love to see is either a separate EXE or a DCS command line argument that will open a miz file, read the ME lua files, parse the miz for any necessary changes (like the regular ME does right now), and then save the file that conforms to the latest version (optionally backing up the original file). Something like this would reduce the time to update missions at the very least, and could ideally be batched for people who manage large servers.

The faster you go the more down-trim you need to stay level. I imagine you're getting the upward push after diving to low level, where your acceleration is at peak. The other thing you can do is set the autopilot + altitude hold, then press the NWS button when you're at the altitude and speed you want. This will trim you in level flight for that speed, and even if you disengage the autopilot you'll still be properly trimmed.

FWIW, here are the emergency sweep discrete presets I use, which are based off the Wing Sweep vs. Mach Schedule in NATOPS. H/T @Wintermute74 for the original code. {down = device_commands.WINGSWEEP_EmergencySweepLever, cockpit_device_id = devices.WINGSWEEP, value_down = 1.0, name = _('Emergency Wing Sweep Handle (20)'), category = { _('-MODIFICATIONS'),_('Throttle')}}, {down = device_commands.WINGSWEEP_EmergencySweepLever, cockpit_device_id = devices.WINGSWEEP, value_down = 0.9272, name = _('Emergency Wing Sweep Handle (25)'), category = { _('-MODIFICATIONS'),_('Throttle')}}, {down = device_commands.WINGSWEEP_EmergencySweepLever, cockpit_device_id = devices.WINGSWEEP, value_down = 0.5633, name = _('Emergency Wing Sweep Handle (50)'), category = { _('-MODIFICATIONS'),_('Throttle')}}, {down = device_commands.WINGSWEEP_EmergencySweepLever, cockpit_device_id = devices.WINGSWEEP, value_down = 0.4905, name = _('Emergency Wing Sweep Handle (55)'), category = { _('-MODIFICATIONS'),_('Throttle')}}, {down = device_commands.WINGSWEEP_EmergencySweepLever, cockpit_device_id = devices.WINGSWEEP, value_down = 0.4178, name = _('Emergency Wing Sweep Handle (60)'), category = { _('-MODIFICATIONS'),_('Throttle')}}, {down = device_commands.WINGSWEEP_EmergencySweepLever, cockpit_device_id = devices.WINGSWEEP, value_down = 0.3013, name = _('Emergency Wing Sweep Handle (68)'), category = { _('-MODIFICATIONS'),_('Throttle')}}, {down = device_commands.WINGSWEEP_EmergencySweepLever, cockpit_device_id = devices.WINGSWEEP, value_down = 0.0, name = _('Emergency Wing Sweep Handle (OVR)'), category = { _('-MODIFICATIONS'),_('Throttle')}}, 20 degrees - Mach 0.4 25 degrees - Mach 0.7 50 degrees - Mach 0.8 60 degrees - Mach 0.9 68 degrees - Mach 1.0+ And the code for the handle: {down = device_commands.WINGSWEEP_EmergencyLeverExtended, cockpit_device_id = devices.WINGSWEEP, value_down = -1, name=_('Emergency Wing Sweep Handle PUSH IN'), category= { _('-MODIFICATIONS'),_('Throttle')}}, {down = device_commands.WINGSWEEP_EmergencyLeverExtended, cockpit_device_id = devices.WINGSWEEP, value_down = 1, name=_('Emergency Wing Sweep Handle PULL OUT'), category= { _('-MODIFICATIONS'),_('Throttle')}}, {down = device_commands.WINGSWEEP_EmergencyLeverExtended, up = device_commands.WINGSWEEP_EmergencyLeverExtended, cockpit_device_id = devices.WINGSWEEP, value_down = -1, value_up = 1, name=_('Emergency Wing Sweep Handle PUSH IN/PULL OUT (Toggle)'), category= { _('-MODIFICATIONS'),_('Throttle')}},

2.51 is up. Change Log: Removed numerous Script_Debug checkpoints to free stack space. Mi-8/UH-1: Fixed comms routine and improved VAICOM/SRS integration Mi-8: Updated comm switch functionality JF-17: Added AAR Lights to Warthog and Master Caution to Warthog/RMFD AV-8B: Minor button fixes P-47D: Multiple minor improvements for D-40 File Updates: Diff Luas: Spitfire, Mi-8, JF-17, AV-8B, P-47D, A-10C Snapviews (both classic and boresight) Custom Luas: AV-8B

The difference is (at least based on my limited stick time in the T-2) that IRL you can actually "trim out the resistance," or thumb the trim hat until your arm is relaxed. We would need force feedback to replicate the same feedback that makes trimming that much more natural IRL.

Version 2.5.65 is released for DCS 2.5.6.57264.

Re: Caucasus, with as many new campaign implementation features as we see with this campaign (i.e. the dynamic triggers), it makes sense to do the first campaign on a map that is a known and proven quantity. This isn't just about market share (although the management responsibility may turn off casual fliers and already make this a niche campaign), but about about being able to test the myriad of trigger combinations and be confident that any bugs or performance issues found are not due to the theater. Now that the campaign system has been fleshed out, I would love to see something like this involving the F-14 in PG or Syria! Disclosure: I am a minor voice actor in this campaign.

The RIO kneeboard is the same as the pilot kneeboard, and I don't have trouble with either station. Do you use custom bindings to bring up your kneeboard? If so, make sure you map them for both pilot and RIO.