Bailey

Here you go. Merry Christmas. https://github.com/asherao/DCS-ExportScripts/blob/master/Scripts/DCS-ExportScript/ExportsModules/P-47D-30.lua

There are some times where I feel like I had to restart DCS. Hard to say what fixes the problem. Good luck!

Lots of good solutions here. I tend to gravitate to the “least clicks” option, which is why I made DCS Shortcut Generator to have an exe on my desktop or toolbar for each unique flavor of DCS I want to use at the time. Otherwise, the good ole force_disable_vr is the simplest and most effective solution that solves the issue.

For arguments and their values and descriptions, most are listed here for every aircraft https://github.com/asherao/DCS-ExportScripts open the lua files and start reading. Have fun!

Good catch. Thanks. Edited.

Ah, you must install DCS Interface plugin before the profile. That may be your issue.

The Stream Deck Profile contains everything it needs, self-contained. So, if you installed the Profile correctly, you should get all the icons.

Have yall who have the problem checked the target save location by right clicking the Saved Games folder, clicking Properties, then clicking the Location tab and verifying that the location is 'C:\Users\YourProfileName\Saved Games'? You can click the Restore Default Button to reset it.

Nope. The icon file is for people making their own buttons.

You can try this or this https://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/amp/

Words like “high quality” mean different things for different people. I have intentionally tested the title subject in the past. My conclusion is that more expensive hardware makes AAR easier due to accuracy of the sensors and the mechanics of the stick sweet spot for AAR. Of course, there is a financial limit. Just know that if you are buying a cheaper stick that it’s likely harder to make precision adjustments compared to the more expensive stick. I wouldn’t buy/avoid a stick solely due to AAR reasons. You can AAR on a Logi3D or on a controller. It just may take more time, patience, and practice.

Possibly. I can’t repeat the possible error at will. I typically kill the SD process and replug the SD to fix it.

DCS Shortcut Generator is an app you can use to create unique shortcuts for DCS. This uniqueness comes in the forms of VR/No VR, options luas, resolutions, icon images, or any combination thereof. Click to Download DCS Shortcut Generator HERE via ED Userfiles How to use DCS Shortcut Generator 1. Double click DCS-Shortcut-Generator.exe to launch the program. 2. DSG will try to automatically determine your DCS.exe and options.lua file locations. If they are incorrect: a. Select your DCS.exe. Example: ‘C:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe’. b. Select your options.lua file. Example: ‘C:\Users\UserName\Saved Games\DCS\ Config\options.lua’. 3. Select either Disable VR or Enable VR. 4. Name your shortcut. 5. Click the Export button to export the shortcut. It will be exported in the same location as the app. You can move it to another folder or your desktop if you like. There is much more information included in the Readme. Thank you to JCofDI and Hornet for testing the app before release. Thanks to you for downloading the app and reading this Readme. Thank you to all of those who play and create mods for DCS. - Please join us in the Discord server: https://discord.gg/PbYgC5e - Please feel free to donate. All donations go back to the DCS community to create even more free mods, just like this one: https://www.paypal.com/paypalme/asherao - Check out my other Mods, Utilities, and VoiceAttack profiles here: https://www.digitalcombatsimulator.com/en/files/filter/user-isbaileywa/apply/?PER_PAGE=100 - If you would like to contribute to the development, check out the code, or if you like spaghetti, the Github is located here: https://github.com/asherao/DCS-Shortcut-Generator -Feel free to contact me on the ED forums (Bailey) or better yet on Discord (Bailey#6230). Remember that comments, questions, critiques, and requests are always welcome! Enjoy! ~Bailey 2021DEC Version Notes: v1.2 - DSG will try to auto-detect the dcs.exe location on launch (Thanks Lazyboot) - DSG will try to auto-detect the options.lua location on launch v1.1 - Added a tiny auto-reassuming QoL for the swap lua and icon pick dialog popup - Changed the height of buttons and text boxes fr om 19 to 20 v1 - Release

It may have been made with a dev version of the game, being a newer version.

You are likely on Stable release. The missions were likely made or edited on open beta release. The open beta mission editor may have different features and may have used these features that the stable version does not have, thus the warning.

With some time we learned how to do so here:

You found it, nice. Feel free to ask a specific question. I think of Viewports as “windows”, just like the ones in your house. You make a section titled “Viewports” and in that section you will create your “windows” to the world. You can name them whatever you want, but it makes sense to name them some recognizable, such as “center” or “right”. Those will be your “center” and “right” viewports. You will also define each viewport, just as you would define the shape and properties of you a hand made “window”. Near the bottom of the lua you will see that is where we finish the definitions and “call” the viewports. You are telling the game that you want a viewport in a certain place or on a certain screen. I hope that general description makes sense. The things outside of Viewports such as Left_Mfd and Right_Mfd are not “windows”. They are templates that have been defined elsewhere. You can still shape them and assign some properties though. So instead they are more like “pictures”. You get what you asked for, but you can still place it wherever you want in your home.

The only reason why a lua hasn’t shown up for me is due to a syntax error. No, there isn’t a separate file that names the monitor lua. The first few lines of the monitor lua name it. Post yours here and someone may be able to take a look and see if it works for them.

My VA profiles that I have made should be in my signature if you’d like to take a look. My naming scheme is typically [object] [action]. For example: Battery on. Wings fold. Etc. For more complex things I use a simple command but call multiple commands within. An easy example is how to tune radios. Instead of saying “Twist knob 1 left, twist knob two right, twist knob two right, twist knob three left…” I say “tune frequency 246” and in the code it does all of the correct actions. That may be an obvious example, but expanding that to other kinds of command is crucial for remembering the least number of commands. For most of the aircraft I have VA’ed I can simply say “Give me [weapon]”. If I said “Give me guns” VA will configure the entire aircraft such that when I pull the trigger bullets come out. Same for rockets, bombs, etc. In essence, a whole mission could be the following commands, in order: “Autostart”, “clean up”, “give me bombs”, “prepare for landing”, and done. The only button I pressed ingame for the mission was the bomb release (but I still have a “bombs away!” command just for fun too.)

I like this idea. All of them (Not actually all, but most that make sense.) It also makes things like controller and VA profiles easier to share with others when all of the keyboard binds are uniform by default.

So close! It looks like you were off by about a factor of 10. The A-10C.lua already has a totalizer calculation, but the author didn't copy it to the correct place in the file for the app. Instead of telling you some possibly confusing stuff, I'll just add the lua and post a snip of the code. It is working ingame. Edit: If you are wanting to use the 'round' nd 'format_int' functions, you will have to add the functions from the F16 lua to the a10 lua when you modify it. A-10C.lua

For a first time lua edit, that isn't half bad! I can see that you are developing your way of thinking of a solution. That is good, as it only gets better with time and practice. I took a shot at it and here is what I got. There are may ways to "think" in lua, and many more ways to write it. Below you will see my code for the function in a Spoiler block so that it does not take up so much space. I tried to comment as much as made sense. You could really write a novel on this stuff if you really wanted to. As a general note, make sure to use Notepad++ or a similar editor. It helps a lot. (I really need an IDE or something because I spent like 30 minutes tracking down a rouge "L" typo that should have been an "i". Sigh...the life of lua . Almost took me monger to find it than it took to write the code.) Remember to add ExportScript.TripleFireFeature(mainPanelDevice) at line 559, in the 'ProcessIkarusDCSConfigLowImportance' block. Let me know how it goes! FA-18C_hornet.lua

When there is an APU fire, Left engine fire, or Right engine fire, you want a single StreamDeck button to say which thing is on fire and then when you press it, it fires the Discharge switches in-game? If that’s the case there are two major things you will have to do or figure out. First is the changing text. Second is the way to press the discharge switch. For the first issue, that is going to be a “simple” IF statement. At the end of the if statement you will export the text to a unique ID. For example, IF argument(apuLight) equals 1(on), then textToDisplay = APU FIRE. ELSEIF argument(leftEngineFireLight) = 1, then textToDisplay = L ENG FIRE. And so on. At the end you’ll export textToDisplay to a unique ID for your button. The tricky part is part two. If I remember correctly, the switch has a cover. I don’t know if the switch is press-able ingame while the cover is on. Maybe, maybe not. If it is not, you’ll have to counter that in two ways. Either making 2 buttons or making a multi action button using the multi action function in the streamdeck app. Good luck! If you get stuck I’ll be glad to assist. Oh, and unless it’s already defined, you’ll have to use the model explorer to find the correct argument of the lights. Which means changing them one by one. Or if you are lucky you can find a profile that already has those lights built into it.

I am glad you got the views figured out. I'll likely be making a profile for the AH-64D, in which I will VoiceAttack the radios and comms. Overall, it uses the same principle that you used for the views. You say something and VA presses the right keys with respect to what you said. I'll admit, the processes involved in "Tune radio one to frequency 246.8" is a little bit more involved.

You can define your own variables. You can also look in other default monitor luas to see some code they left laying around and examples too. Some modules also have example monitor Lua code like the Jf17.