Bailey

I'm not gonna lie, that's some pretty varsity stuff that I don't know how to do. If it is possible, that stuff may be behind some code that took me months to understand. I can take a look at it as see what I can do from my side. In the meantime, watch Charles Tytler's youtube videos, which will eventually teach you how do do it.

In general, here is the flow for getting what you need. - Think of what you want - Draw what you want the Tile to look like on a piece of paper - Look at the module Lua and determine which instrument, argument, or animation give you want you want - Make a function that reads the argument and then converts it into the data you desire - Export the converted argument to the StreamDeck. This process is much more simple in ww2 aircraft like the mossie. As you get more and more digital like the F18, the process gets much more difficult. I'm curious, what would you like to export for the F18? That would be the first 2 steps. Thinking, and then laying it out on paper. Disclaimer: It's likely to be quite difficult, assuming it's possible. I suggest learning to make custom exports like this with a ww2 bird. Opening the Lua file and seeing how things work helps get exposure to what you should/could do things.

This Mossie update brings what will be the last of the majority of the mossie exports. If this were a release, it would be the "1.0". All of the tiles that need need to be "dynamic" are in fact "dynamic". Radio freqs, radio presets, engine settings, navigation, oxygen, and even the Best Power settings are dynamically adjusted on the fly depending on the aircrafts altitude, engine settings, and a few other values. It's basically like having the navigator crunch numbers at your fingertips, letting you know how to best fly the aircraft. Feel free to cherry pick what exports you want to use and which ones you don't. There is a table of all the exports on the wiki that have previews of what each export will look like. Enjoy! (https://github.com/asherao/DCS-ExportScripts/wiki/MosquitoFBMkVI) - Updated Mossie Wiki Streamdeck IDs and Mossie Media - Added the following Mossie Tiles - Pilot Oxygen Tile - Copilot Oxygen Tile - Oxygen Tile - Takeoff Power Tile - Intermediate Power Tile - Max Continuous Power Tile - Emergency Power Tile - Max Rage Climb Tile - Max Range Climb Tile - Best Cruise Tile - Approach Speed (w/ Glide at Idle) Tile - Max Speeds Tile 1 - Max Speeds Tile 2 - Stall Speeds Tile - Added the following Mossie supporting exports - Pilot Oxygen Flow Rate - (is) Pilot Oxygen Flow Emergency - Pilot Oxygen Supply - (is) Pilot Oxygen Supply Red Zone - Copilot Oxygen Flow Rate - (is) Copilot Oxygen Flow Emergency - Copilot Oxygen Supply - (is) Copilot Oxygen Supply Red Zone - (is) Pilot Oxygen Emergency - (is) Copilot Oxygen Emergency - (is) Either Oxygen Emergency - (is) Aircraft Stall Pics of current Mossie 40xx series exports.

I took a look at chucks guide and it seems that the arrow is a power indicator. I couldn't see what represented it in the list_indication, so I would have linked it to the mode switch position of the radio itself. Just FYI. Also, good luck parsing the list_indication with the blinking cursor. It's tricky.

- Mossie - Added special characters for temp and No10/12 tanks - JF-17 - added example for arrow output and comm1/comm2 freq output - Wiki updated for Mossie and JF-17 - The special characters in this update post were added via this method. TODO - Document in Library Git

There are two ways to get the character you want: 1)Go to this site (https://unicode-table.com/), then scroll down to the arrows (https://unicode-table.com/en/blocks/arrows/). Click the one you want and then click "copy". Then paste it directly into the lua file. 2) Open Windows Character map by pressing the start/windows key and type "character map". Scroll down to find the character you want. Click the character and then click select. You should see it populate in the lower box. Then click copy and paste it into your lua. After completing option 1 or 2 you will still have to parse the list_indication output in order to put the arrow in the correct location. I made the following code as an example. Tested and working for the JF17. It gets the status of the flight stick (argument 970) and determines which string should be used. This code is only an example and may not be applicable to every situation. Click the bottom of the stick ingame to toggle it and therefore the resulting exported string. function ExportScript.arrowTest(mainPanelDevice) local stickShowHide = mainPanelDevice:get_argument_value(970) local stickStatus if stickShowHide >= 0.5 then stickStatus = "↑Up" else stickStatus = "↓Down" end ExportScript.Tools.SendData(2001, stickStatus) end Remember to put ExportScript.arrowTest(mainPanelDevice) into the function ExportScript.ProcessIkarusDCSConfigLowImportance(mainPanelDevice) function. Having this knowledge I'll be going back to the Mossie lua to put in the special characters for the air temp degrees and No10 and No12 tanks. Thanks! Update (sry for small pic): Another Update (what hath i unleashed?!?! xD):

Library updated. See Git for details. Thank you to other DCS-ExportScript forks where these updates came from. - A10A - Added speedbrake detection - A10C2 - Created A-10C_2.lua - Bf-109K - Added a digit to the bomb fusing selector output - F15C - Enabled canopy open/close detection - F16C - Adjusted .lua spacing - F5E - Added Guns, Missile and Camera Switch Cover Export - F18C - Adjusted some export accuracy - Added export 2090 ScratchPadString2Display all characters - M2000C - Added VHF radio export - Added Fuel exports

- Updated the Git to mirror sda's format so that its a 1-stop-shop - Spitfire - Fixed typos - Fixed a condition where the trim display would not show unless trim was adjusted - Mosquito - Updated Wiki (https://github.com/asherao/DCS-ExportScripts/wiki/MosquitoFBMkVI) - Cleaned up the export descriptions a bit - Relocated some functions to "low importance" - Added the following tiles (see wiki for more info) - Air Temperature - Navigation 1 - Altimeter Dial - Instruments - Trim - Added the following sub-tiles (see wiki for more info) - Air Temperature - Compass Dial Readout - Compass Dial Needle 1 Readout - Compass Dial Needle 2 Readout - Altimeter Readout - Pressure Readout - Airspeed Readout - Vertical Speed Readout - Elevator Trim Readout - Rudder Trim Readout - Aileron Trim Readout - (is) Gear Up - (is) Gear Down - Flap Indicator

Click "Export Backup".

No problem. Sweet. I hope it turned out well.

I'm glad you found the git. No, I don't have anything more for the F18 than what is already available in the forums or the ED User Files.

So, umm, I may have run into a slight problem. I am using a great number of "Tiles" that have a greater number of conversions and equations that happen in the .lua. The problem that I am having is when I have the, all enabled, after a few sim restarts the amount of memory that streamDeck.exe uses shoots up to like 4GB of ram, which is crazy because it starts at around 400MB. This number grows until it freezes the SD GUI or the SD itself. Honestly, I think it is a problem with the SD or the SD GUI, which is made worse by the number of calculations that are performed and then rendered to the SD. The problem does not seem to happen when I am using a low number of Tiles that don't require many calculations. This post is just to say that I have noticed something odd and if anyone in the future (or past) runs across this, the more info the better. Here is a pic of the mossie Tiles. The 8 on the left are always running calculations. Well, I guess they all are if they are being called every time. But, the eight on the left change quite a lot. It may be worth the cycles to put the 9 tiles on the right into low importance events, which I have never done before.

- Updated Mossie exportScrips lua - Added Engine Instruments Left Tile 1 - Added Engine Instruments Left Tile 2 - Added Engine Instruments Right Tile 1 - Added Engine Instruments Right Tile 2 - Added Gun Sight Solution Tile - Added Fuel Inner Tanks Tile - Added Fuel Center Tanks Tile - Added Fuel Outer Tanks Tile - Added Fuel Total Tanks Tile - Added Pilot Radio Tile - Added T1154 Radio Blue Tile 1 - Added T1154 Radio Blue Tile 2 - Added T1154 Radio Red Tile 1 - Added T1154 Radio Red Tile 2 - Added T1154 Radio Yellow Tile 1 - Added T1154 Radio Yellow Tile 2 - Added R115 and T1154 Radio Tile - Added exports 3000-3026 to support the above Tiles - Updated Mossie wiki (https://github.com/asherao/DCS-ExportScripts/wiki/MosquitoFBMkVI) - Added Mossie pics - Update wiki table formats - Added Mossie media pic - Added psd files - Added calculator files - Updated spitfire pics - Updated Spitfire lua - Added Trim Tile (3011) - Added elevator and rudder trim readouts (2018 and 2019) (Mossie Tiles Added)

Hmm, via ExportSripts, I have no idea.

Its live! JF-17 Standalone DTC by Bailey https://www.digitalcombatsimulator.com/en/files/3318506/

It's not dead yet! I planned to post this here a few days ago but I totally forgot, oops! I too am looking forward to the DCS-BIOS integration. I really hope that making custom functions is just as or easier than in DCS-Export.

Dcs Bios is an underlying framework that allows a mode of communication from outside the Sim to inside the cockpit. It is typically used to allow communication from homemade buttonboxes to the aircraft cockpit. I have adapted voiceAttack to be able to send the same types of commands. The great thing about it is that once you install it, it's sits silently in the background. No additional steps, no menus, no maintenance (except for updates for new planes and such). I'll explain how to install DCS-BIOS, which is documented on the DCS-BIOS FlightPanels wiki: https://github.com/DCSFlightpanels/DCSFlightpanels/wiki/Installation Installation of DCS-BIOS Download Download DCS-BIOS Select a release. Click on Assets to expand a list of downloadable files. Download the zip file DCS-BIOS_x.x.xx.zip. Unzip DCS-BIOS into a temporary location. Open DCS Script folder [drive:\Users\<username>\Saved Games\DCS\Scripts] or [drive:\Users\<username>\Saved Games\DCS.openbeta\Scripts]. Create it if it doesn't exist. Copy the folder DCS-BIOS and the file Export.lua to the DCS scripts folder. After that it will have been installed. Feel free to read more about DCS-BIOS via the link above, but it is not necessary to do so to use the VA profile. If you need any more assistance, feel free to post here again.

When playing the mission in Easy, Medium, or Hard the flak takes out the raid before you can catch up to them and engage, resulting in mission completion.

Yes

The great part about a library is that not only are there already books there, but ppl go there to study, learn, and discuss too! It’s a very flexible place. Yes, the ExportScripts Library is the perfect place to post these ideas of yours. I, too, am quite curious… Don't worry about the GitHub part. I’ll take care of that.

The results are in. The exponential equation is about 6 times "faster" compared to the process of a linearly interpolated table. Each operation was done 10 million times. Maybe exponential may be the way to go if you have like 20 of these on the SD at once or if an animation has a particularly nasty equation.

- Added Hind Wiki (https://github.com/asherao/DCS-ExportScripts/wiki/Mi-24P-Hind) - Organized Hind lua (no major changes) - Added Mosquito Wiki (https://github.com/asherao/DCS-ExportScripts/wiki/MosquitoFBMkVI) - Added pics for SRS - Added Viggen Pics

- Added nosaMtrevoC's P-47D export lua (https://www.digitalcombatsimulator.com/en/files/3310456/) - Created Wiki (https://github.com/asherao/DCS-ExportScripts/wiki/) - Added Spitfire to wiki - Added P-47D to wiki - Added Mossie pics - Added hind pics - Added Spitfire pics - Added Spitfire media - Demo of the Gun Sight Solution Tile - Current Spitfire exports and "Tiles"

@scoobie @Simm0 @nosaMtrevoC @ctytler, just a heads up. Also thank you for your contributions to the luas that are already in the library.

I took the dive and decided to open my Git as a public library. Feel free to add to it.