Chacal_IX

I was wondering what the requirements are to succeed in this mission. I've done it several times and managed to land at the base and each time I've only got a 50 percent success rate.

@ctytler Effectively it doesn't work with the web interface. Thanks for your answer.

I finally managed to get my Stream Deck to work with the DCS BIOS and the F-16 or M-2000 (I suppose the other DCS aircraft work too) but I still have a problem with the A4E-C. The communication works in the direction DCS ==> Streamdeck but not in the direction Streamdeck ==>DCS. Any ideas?

Same Issue here

You have to increase the Device ID number by +1 on the buttons that no longer work. At least, this is what corrected the same problem for me.

Don't use a switch Button. You need a momentary Button for this function

You need to set them like this...

You can try to follow the link of this post

Hello, this happens when there are duplicates in the script that do not have the same decimal value or decimal point. In your case, for the master arm cover and master arm switch, delete lines 635 and 636 or modify them as below. [1046] = "%1d", -- WEAP_Master_Arm_Cover [1047] = "%1d", -- WEAP_Master_Arm Sorry, my script is far to be perfect but I didn't have the time or the desire to correct all the defects.

I don't have a solution for that. Unfortunately I don't have the skills to create this because I don't know anything about the scripting language.

I followed the links of this post.

Sorry to deceive but nosaMtrevoC hasn't posted for 7 months. Unfortunately, I'm afraid the project has been abandoned.

I can't be sure that nothing is missing but these scripts should be very complete. The F-14 script is a bit special as I have added some lines that nosaMtrevoC created.

?

I used the tools provided by ctytler and created the script for the missing aircraft (F-14, F-16 and JF-17). But it was a big job.

To start, try with my F-14 script and tell me if it works better. F-14B.rar

Oh, right. Sorry, I only have the 32 button version of the Streamdeck

Yes, and this is how I set it up on my profile. I only quickly tested the 59 output, but the configuration is similar with the difference that you have to put at least 4 digits after the decimal point.

The 6102 output works well on my side for what you want to do. On the other hand, it is possible that output 59 will be more complicated to program because there are more than 4 digits after the decimal point.

with this perhaps [6102] = "% .1f", - DDD_radar_mode [59] = "% .4f", - WEAP_Type_Wheel

What do you call 15 button unit ?

@bones1014 For the current position, try with the line modified like this. [200] = "%.1f", -- Datapanel Selector

You can download the F-16 script here

Thanks

I finally re-tested and managed to keep the C-130s alive but the mission was only 50% validated. I will be attaching my Tacview files from the first test and the second. You can see that it is every time the third C-130 lands that it is considered destroyed. This is my first ACMI file. Tacview-20210302-210907-DCS.zip.acmi And the second...Tacview-20210306-160732-DCS.zip.acmi