Bailey

Yes, all Lua files are up to date with the wiki Tile documentation.

No, I have not posted a newer profile. The profile remains mostly the same. The differences can be found in the wiki. If you need help making or finding specific tiles, let me know.

Ah. I misunderstood. When you said not working I thought you meant the switch is not moving. My bad. Very well. It’s a common issue with some community mods. Thanks for the heads up and correction.

If you would like assistance on how you can get it yo work for your system, please describe your processes and expectations as detailed as you can. It has worked for myself and many others.

> I still cannot get the ID lookup button to populate even though I have a copy of the Su-30 mod in the Eagle dynamics /mod/aircraft folder with the entry.lua file removed. Does yours populate?? Nope. It is a DCS-Interface programing limitation. > I also am trying to get bindable buttons to work in the controls tab. Try {down = device_commands.Button_127, value_down = 1 , name = _('Battary 1 ON'),category = _('Systems')},

Bailey's VoiceAttack and Stuff Discord https://discord.gg/d4VFhde49b When you get in, let me know which link didn't work. Thanks and looking forward to seeing ya!

DCS-Interface can be thought of as 2 different halves. The first half is DCS-Interface listening to dcs. This is how it gets information from the sim and displays it on your streamdeck. The second half is the communication from DCS-Interface to DCS. This is how buttons are manipulated. Because they are two halves, one can be working perfectly while the other isn't working at all, depending on your network settings, lua files, etc. The Su33 does not have a clickables file, so it cannot interact with the second half of DCS-Interface, the buttons manipulation half. As you have noticed, there is a Su33.lua file, which is the other half, which works. For the Su30, this is working for me. Your assumptions were correct. It manipulates the battery switch. If you are having trouble, make sure your network settings are set correctly. You can try other known working aircraft (not mods) to make sure. For the keybinds: Change Batt1OnOff to Button_127 and you will get some progress.

1. Yes. Make sure you have enough slots 2. Copy/paste. You will have to make new shortcut links if you had any.

SU30 mod luas added https://github.com/asherao/DCS-ExportScripts/tree/master/Scripts/DCS-ExportScript/ExportsModules The Mirage F1 is not recognized because DCS-Interface does not have the capability to read the files for modules with multiple versions like the F1 and C101. There are instructions on how to use DCS-Interface with the Mirage here: https://github.com/asherao/DCS-ExportScripts/wiki/Mirage-F1

Hi there. The Su33 is not clickable. This is why you wont see entries in DCS Module Clickable Data in DCS-Interface. Looking at the Su30 code, it is not made in a way that DCS-Interface will recognize. Someone will have to find out the stuff by hand, similar to how people have done for the Mirage F1. I have made the Su30 Luas for you and others. https://github.com/asherao/DCS-ExportScripts/tree/master/Scripts/DCS-ExportScript/ExportsModules You can find the raw clickable data here: C:\Users\...\Saved Games\DCS\mods\aircraft\Su-30MK_SFM v2.01B\Cockpit\Scripts\clickabledata.lua The method to assign them as buttons is similar to the Mirage F1. There is a guide for that here: https://github.com/asherao/DCS-ExportScripts/wiki/Mirage-F1

DCS Mirage F1 Voice Attack is live! This is no optical illusion. You can use you voice to fly and operate the Mirage F1 in DCS with this Voice Attack profile! You want your weapons, you got it. You want the gear, you got it. You want Crew Chief to rearm your baguettes, you got it! Enjoy! https://www.digitalcombatsimulator.com/en/files/3325382/

Remove the files you installed.

No issues.

The default campaign. Top 3 best default campaigns in dcs imo.

Since you are not using VAICOM, you can follow standard Voice Attack voice recognition instructions in the VA Help pdf. I personally use it in open mic mode. Others use PTT. It is up to you. (Thanks @MAXsenna)

The standalone is not as developed as the integrated. The terrain option only populates the name of the terrain. You can change it after a DTC is generated.

Added: Nevada: MF1 Nevada - MiG-21 Ground Attack | 2022AUG04 (Beta) MF1 Nevada - MiG-21 Intercept | 2022AUG04 (Beta) Syria: MF1 Syria - MiG-21 Dogfight | 2022AUG04 MF1 Syria - MiG-21 Ground Attack | 2022AUG04 MF1 Syria - MiG-21 Intercept | 2022AUG04 MF1 Syria - MiG-21 Take Off | 2022AUG04 Updated: - First post format. Removed Map from names. Put missions in Map groups.

Added: MF1 Caucasus - MiG-21 Ground Attack | Caucasus | 2022AUG02 MF1 Caucasus - MiG-21 Intercept | Caucasus | 2022AUG02

QFE is useful for crop dusters and country bouncers.

As of right now, it is not listed in the typical place, list_cockpit_params(). You could get it via something like: local UHF_RADIO = GetDevice(7) local uhfFreq = (UHF_RADIO:get_frequency()/1000000) for example. That is similar to what I do for the Stream Deck.

Haha, ty. You can remove them. No reason to keep the duplicates in the file.

There's likely duplicate export IDs. Remove the duplicates.

The control is, but the reaction isn’t.

Yep that's pretty much it. Don't forget both the install and saved games folders.

Awesome. Thanks for sharing. Sounds like an issue similar to the battery switch of the UH-60. The control activation works only for clicks and keybinds because the logic is in tge FM (flight model) part of the mod.