AstonMartinDBS

Well, you're absolutely right. But static templates have at least one great disatvantage, too: they're map-bound. Maybe ED will find a way to combine the advantages of the group and static templates. Thank you - I'll check them out! It wasn't easy to find your templates via filtering by user name due to your modified name in the user files section (Rudel-chw). BTW: I'm already using your carrier templates since month, they're fantastic!

Thanks for your clarification @Rudel_chw. It's very strange, that ED removed some of the templates, including the one for easy pupulating FARPs. That's what I already thought. Thank you! I guess, you have a large collection of custom templates. Let me know if you wanna share it, please.

Great! Thank you BN!

I have the same problem as the OP: I accidentally removed some of my templates by clicking on the "-" right next to the dropdown, but the hint from @Rudel_chw didn't work for me as expected. Deleting/renaming the file templates.lua from {DCS installation path}\MissionEditor\data\scripts and running a repair restored the file, but the deleted templates are still missing: I've tried this solution (deleting/ranaming the file template.lua from the directory %USERPROFILE%\Saved Games\DCS\MissionEditor\) also, but it didn't restore the deleted templates as well. I am still missing the templates for the FARP units for instance. BTW: I'm running the current OB.

I want to share my personal, printable, two-sided cold start checklist for the AH-64D, which is based on @Wags Cold Start Tutorial and @Casmos Startup Walkthrough. The first page contains the steps for the PLT (Pilot) and the second one those for the CPG (Co-Pilot/Gunner). To avoid unnecessary fuel consumption, the steps for the [CPG] should be processed pior to the engine startup procedure. Legend: Column 2: Cockpit Area/Input Device LC: Left Console FWD: Forward CCP: CMWS Control Panel RC: Right Console KB: Keyboard Column 3: Panel Column 4: SW: Switch BTN: Button Column 5: L: Left Mousebutton R: Right Mousebutton W: Mousewheel Download: v0.7.3: DCS-AH-64D-ColdStartChecklist-en-v073.pdf Changelog: v0.3.6 (09.04.2022): Initial release v0.3.9 (12.04.2022): [PLT] POINT management and SHOW settings moved further back (after alignment completion and prior to engine start); [CPG] radio SQL switches optional (the radios have been squelched already by the PLT at this point, the current switch behaviour is wrong implemented, the switches should be spring loaded); minor optical improvements v0.4.0 (22.04.2022): [PLT]+[CPG] certain procedures re-arranged (IHADSS boresight procedure prioritized over weapons setup), [PLT]+[CPG] several pushbutton sequences optimized, [PLT]+[CPG] added some optional steps (MAP setup for instance), [CPG] added a few missing steps (WCA reset); v0.5.0 (29.04.2022): adjustments to the latest DCS Open Beta update (2.7.12.23362): DOPPLER and RDR ALT are activated by default; minor pushbutton sequence optimizations; v0.5.2 (28.12.2022): adjustments to the latest DCS Open Beta update (2.8.1.34667.2): LASER is activated by default (fixed in v0.5.3); v0.5.3 (29.12.2022): LASER has to be activated manually (as usual); v0.6.1 (22.11.2023): tiny adjustments for the latest DCS Open Beta version; checklist order optimized; v0.7.0 (20.12.2023): adjustments for the implementation of FCR in the latest DCS Open Beta update (2.9.2.49629): [CPG] added the steps to powering up FCR; v0.7.2 (02.02.2024): [PLT] COMM setup adjustments after implementation of COMM presets (DCS Open Beta 2.9.0.46801); [PLT] step 67 changed from [PageUp] to [Num+] to avoid the 'Low Rotor RPM' warning; v0.7.3 (12.11.2024): [PLT] step 44 added to activate the FCR (MMA); Notes: The checklist is still WIP. It's designed for my personal purposes. Other Downloads: F-16C: ALIC Tables for the AGM-88C HARM (.pdf and Kneeboard) F/A-18C: Threat Codes for the AGM-88C HARM (.pdf and Kneeboard)

Red marked text should be deleted.

As Wags mentioned in his Controls Setup Tutorial there should be no real need to bind the first detent of the RHG LRFD Trigger.

Thanks! This explains why the CPG radios are already squelched while the SQL switches are in down positon when I squelched the PLT radios before on a cold start procedure.

Good to know! I didn't recognice this until I'd read your comment. Alignment incomplete: Alignment complete:

Thanks, this solved the problem for me after my first mission with cold start.

Maybe you can upload your mission here so others can check it for proper setup.

Already tested with current OB (2.7.11.21408.1) and Huey: the embarking and disembarking of 14 soldiers worked without issues.

Draw tool generated text doesn't scale with zoom level: Is this behaviour intended? If yes: an option to make it scaleable would be great.

I'm glad, that the long wait was worth it. I loved Jane's AH-64D Longbow, but the extraordinary level of detail of the DCS version is just impressive. Thanks for this great product! It took me several hours in total to configure and finetune my HOTAS controls, but I think I have it. Wags tutorial was a great help to find the important bindings. Now I can set my focus to the systems.

Waypoints are not shown by default, when TSD is set to ATK phase. You can change this setting using the SHOW sub page (T3 on TSD) followed by L2. You can show/hide specific points independent for ATK or NAV phase. See also Wags tutorials "TSD Basics" and "TSD Points" for detailed information around those settings.

Size isn't limited AFAIK, but the aspect ratio should be 1:1,5 = 2:3 for best results (1.000 x 1.500 px for instance).

All works fine here and I didn't notice any change since last update. I don't have any deadzones in my TDC axis either.

This worked for me: TMS right (area track) slew TGP to the desired target TMS fwd (point track)

Great, you found the solution yourself.

Well... typical user error, I skipped step 4 and didn't get the "cleared hot" message, of course I retried JTAC Test Reaper.miz and I was able to deliver 4 GBUs successfully.

Your mission contains a few unnecessary (advanced waypoint) tasks and requires some tweaking (AFAC callsigns and COMM frequencies for instance), but the communication worked for me and I managed to force the JTAC to mark the targets. I've created a similar simple test mission with a Reaper as AFAC which marks the targets with laser only. You (F/A-18C) are supposed to deliver GBU12s. Contact the JTAC via 251.000 MHz AM, frequency is stored as Ch 1 in COMM 2. Edit: All of my few test runs resulted in successful laser designation by the AFAC, but for any reason I always got the "ABORT ABORT ABORT" message immediately after each bomb release (which causes an abandonment of the laser designation and - of course - a dumb GBU trajectory). JTAC Test Reaper.miz

I hope so. At least...

Related to both Pods are identical at the moment, besides the optical difference.

That's really strange but explains, why I wasn't able to reproduce the bug immideately after flyin' the mission. I've started DCS and watched your replay four times within one DCS session. The results: bug was present no issues bug was present no issues BTW: installed GPU = RTX 2080 SUPER, Driver version = nVidia 511.23