Bailey

This is possible with VoiceAttack macros.

I will be looking in a way to include the AH64D into DiCE. It may not be possible due to how ED coded the countermeasure system. Just a heads up.

I am working on a lua and profile for the AH64D. Both will be publicly available. If you have any requests, input, or would like to help, please feel free to do so.

It’s been quite a while since that profile was released. First, make sure the original commands work from a fresh profile install. If those don’t work, your modifications are not likely to work either.

Due to how the commands are coded, if you change the command they will break. Behind the scenes it takes what you said and parses it into numbers to calculate the movement of the cockpit controls.

Ah, ok! Thats a nice solution! I thought you were trying to use CTLD on different servers which may have required different menu stuff. My bad. I'm glad that Pfeil was able to help you out.

Other than coding each option by hand for each case, no, not that I know of.

It will work, you will just had to make the correct logic and be conscious about when to use the commands. This is some of the reasons why I add the server name to the end. If you fly multiple aircraft you can add the aircraft name too. Be creative with the patterns if you like.

You can download the PDF via the Guide link in the first post.

Use the second page of the brief for the correct binds. They will be the copilot Mode and Reset Chronometer binds.

Use what is necessary. Most DCS aircraft don't need rudder for less than a standard rate coordinated turn, including the F14.

Download the campaign on ED User Files: https://www.digitalcombatsimulator.com/en/files/3320893/ You have been assigned to a peacekeeping operation in the Caucasus region. On the way there you heard that the guy you will fly with ditched the Huey for a newer ride. You are excited as you realize UN's UH-60L has rockets and hellfires... (UH-60L Mod version 1.2 is required) This is a UH-60L conversion of the default DCS UH-1H UN Pilot Campaign. All campaign credits go to the original authors and actors. As one of the best default DCS campaigns, it is highly recommended in its original form. I have not changed any of the story elements. You can use this forum thread to talk about the campaign. Please do not write any content that could be spoilers for those who have not yet experienced the campaign. If unsure, you can write your entire post using the spoiler tag. Enjoy!

See below:

It is working for me like this. Select all of them. Allow Cycling to beginning. The solution for this is the same as the MDI

You can use this for the hotkeys. The vanilla one does not let you pick left and right modifiers. https://github.com/BarRaider/streamdeck-supermacro/blob/master/README.md

Where did the lua come from? You can try the one from here: https://github.com/asherao/DCS-ExportScripts

Welcome to the future https://www.flyingmag.com/a-uh-60a-black-hawk-just-flew-with-no-pilot-on-board/

I may not have a solution, but I have heard that some people have been able to play with the order of the plugins in export.lua to get both to work.

Done. PM for paypal

I dont think I have made a F-14 profile. But, to clear duplicates you look at the list of the [xx] = "xyz" numbers. Delete the numbers that repeat.

The devs would have to write the code to be able to use the weapons. If you did a model/name/reference swap the module does not know what you want to do with it.

Have you cleared all duplicate args from the lua? Also, if you can put things in Low Importance it may help the processing of High Importance functions. It looks like you are adding “00” to the end of the arg. If you delete the .. “00” part, does this give you what you want?

Looking at the lua you posted: [104] = "%.1f", -- ALTI_NeedleBaro [262] = "%.1f", -- ALTI_ThousandsR [300] = "%.1f", -- ALTI_HundredsWhite [301] = "%.1f", -- ALTI_HundredsSmall1 [302] = "%.1f", -- ALTI_HundredsSmall2 [303] = "%.1f", -- ALTI_HundredsSmall3 [304] = "%.1f", -- ALTI_HundredsSmall4 [305] = "%.1f", -- ALTI_STDBYcard [306] = "%.1f", -- ALTI_LeftKnob [307] = "%.1f", -- ALTI_RightKnob Take your time and be patient. I did exactly what I suggested earlier, searched for "alt".

clickabledata.lua line 725 says the altimeter knob is arg 119. I used modelViewer to confirm. Reading the note, something looked odd. I checked args around 2009. Arg 2008 is the altimeter flag. Arg 2005 is similar to arg 119. Jumped in ME to confirm. Arg 119 is correct. Couldn't Find the STD flag. You can either look for it in model viewer or assume that the position of arg 119 is linked to the position of the STD flag, which it seems to be. I hope that gets you closer to a solution.

Agreed! Yahoo!