Bailey

Post your lua here so someone can take a look. Development of the app is focused on dcs-bios integration. If you can make those exceptions for the handful of aircraft it would be greatly appreciated.

I do not know. I’d you do find something out that works, it would help quite a lot.

I am glad to be able to allow people to spend less time in code and more time in the Mirage F1! 1. I was thinking about the icons for what felt like quite a while as the NWS switch is so hard to know at a glimpse in the aircraft. Eventually simplicity won. No only clearly visible, but understandable at a glance too. I really like that one even if it is so simple. Maybe that's what make it work so well. 2. The jet may not be "smart" but I'm counting this one as a computer Thank you for your feedback. It is much appreciated. Enjoy!

Yahoo! Would you like to share how?

Mmmmm. Nope, I have not given that deep thought. If you like, you can work towards that. All of the code is available on github. It would be pretty cool to see though.

Mirage F1 Update - Added Total Fuel Needle Tile (8005) Needle version on the left Thumbwheel version on the right

I cannot. There are more than 15 tiles. There is a Depression Table Calculator (export 8043) in the wiki. The tables are reduced to 1 tile.

Added: MF1 First Jet Strike Fighter | Caucasus | 2022JUL27 MF1 Flight Suit Attitude | Caucasus | 2022JUL27 MF1 Hunter Becomes the Hunted | Caucasus | 2022JUL27 MF1 MiG Sweep | Caucasus | 2022JUL27 MF1 Street Sweeper| Caucasus | 2022JUL27 MF1 Sabre Strike| Caucasus | 2022JUL27

More missions you can enjoy with the Mirage F1. I have modified missions already in the game and replaced the player aircraft with the Mirage F1. All have been tested and are good to fly. Feel free to submit more missions via GitHub or this thread. Enjoy! https://github.com/asherao/MirageF1Library/ (You can download all missions at once here: https://github.com/asherao/MirageF1Library/archive/refs/heads/main.zip) Current missions available (click to download via direct GitHub link): Mission | Date Added Caucasus: MF1 Mission - AWACS | 2022JUL27 MF1 Mission - Airbase | 2022JUL27 MF1 Mission - Hercules | 2022JUL27 MF1 QuickStart - Ground Attack | 2022JUL27 MF1 QuickStart - Intercept | 2022JUL27 MF1 First Jet Strike Fighter | 2022JUL27 MF1 Flight Suit Attitude | 2022JUL27 MF1 Hunter Becomes the Hunted | 2022JUL27 MF1 MiG Sweep | 2022JUL27 MF1 Street Sweeper| 2022JUL27 MF1 Sabre Strike| 2022JUL27 MF1 Caucasus - MiG-21 Ground Attack | 2022AUG02 MF1 Caucasus - MiG-21 Intercept | 2022AUG02 Nevada: MF1 QuickStart NEVADA - Ground Attack | 2022JUL27 MF1 Nevada - MiG-21 Ground Attack | 2022AUG04 (Beta) MF1 Nevada - MiG-21 Intercept | 2022AUG04 (Beta) Normandy: MF1 QuickStart Normandy - Camp Attack | 2022JUL27 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 Missions Total: 21

Try exporting one of the values that follow `local` to its own export number. Try many.

Nice demo. I did this back in the day with the A4. It's relatively time consuming, but pays off down the road. I wonder if tables can be crowd sourced into a master table that could be nice. Thanks for the video. For others out there, remember to note altitude, angle, and airspeed and watch that vsi and G on level drops (my fav).

Before the convo gets too derailed, I do not support anti-hide of the stick to, what the initial request says, be “even prouder”. With that said, if there were a more agreeable reason for this “feature”, I believe it would be for the individual module devs to implement. To address the original post rebuttal, I also do not think it is a worthwhile endeavor to enable such a feature so that you can feel like the other person didn’t have an advantage over you because you didn’t hide the stick because you wanted to be more immersed in VR. It seems you are requesting a feature to satisfy/increase your level of fun at the cost of others on a matter that does not seem deserving or significant to me.

Yes

This is sooooo much better! It helps not having to be heads down for bombing runs and low alt ops. Thank you!

Nice work! Thank you!

Haha, I just tried them out. Turns out there are two solutions that work equally as well. Go figure! Thanks!

Although a great bank, I don't think that has the specific solution.

Mirage F1 Update - Pressure Converter (8079)

You can try this:

Here is a temporary workaround

Mirage F1 Update - IFF Tiles and Readouts added (8076-8078)

Mirage F1 Update - Added Fuel Calculator (Set the Mrad depression value to the amount of fuel burned in 10 seconds to get fuel time remaining) https://github.com/asherao/DCS-ExportScripts/blob/master/Scripts/DCS-ExportScript/ExportsModules/Mirage-F1CE.lua Pic demonstrates the two states of the calculator.

Here you go:

Updated M2K - PCA (2010-2019) - Radios (2020-2023) https://github.com/asherao/DCS-ExportScripts/blob/5014f815bc27010b2220b0d7cfde9d7d3738b23e/Scripts/DCS-ExportScript/ExportsModules/M-2000C.lua There you go. Enjoy! function ExportScript.Radios(mainPanelDevice) -- top radio local top_RADIO = GetDevice(20) local topFreq = ExportScript.Tools.RoundFreqeuncy((top_RADIO:get_frequency()/1000000)) ExportScript.Tools.SendData(2020, string.format("%7.3f",topFreq)) -- U/VHF Com Preset (top radio) --[436] = "%.4f", -- Preset display (1-20) local lUVHF_RADIO_PRESET = {[0.00]="1",[0.10]="2",[0.15]="3",[0.20]="4",[0.25]="5",[0.30]="6",[0.35]="7",[0.40]="8",[0.45]="9",[0.50]="10",[0.55]="11",[0.60]="12",[0.65]="13",[0.70]="14",[0.75]="15",[0.80]="16",[0.85]="17",[0.90]="18",[0.95]="19",[1.00]="20"} ExportScript.Tools.SendData(2021, ExportScript.Tools.DisplayFormat(lUVHF_RADIO_PRESET[tonumber(string.format("%1.2f",mainPanelDevice:get_argument_value(436)))], 2)) -- bottom radio local bot_RADIO = GetDevice(19) local botFreq = ExportScript.Tools.RoundFreqeuncy((bot_RADIO:get_frequency()/1000000)) ExportScript.Tools.SendData(2022, string.format("%7.3f",botFreq)) -- Best way to get digital radio preset channel is unknown. Use export 2023 end function ExportScript.PCApanel(mainPanelDevice) -- Weapon Panel top line local lPCAUR = ExportScript.Tools.getListIndicatorValue(4) local pca1 = '' local pca2 = '' local pca3 = '' local pca4 = '' local pca5 = '' if lPCAUR ~= nil then if lPCAUR.PCA_LCD_1_0 ~= nil then pca1 = lPCAUR.PCA_LCD_1_0 end if lPCAUR.PCA_LCD_1_1 ~= nil then pca2 = lPCAUR.PCA_LCD_1_1 end if lPCAUR.PCA_LCD_1_2 ~= nil then pca3 = lPCAUR.PCA_LCD_1_2 end if lPCAUR.PCA_LCD_1_3 ~= nil then pca4 = lPCAUR.PCA_LCD_1_3 end if lPCAUR.PCA_LCD_1_4 ~= nil then pca5 = lPCAUR.PCA_LCD_1_4 end end ExportScript.Tools.SendData(2010, pca1) ExportScript.Tools.SendData(2011, pca2) ExportScript.Tools.SendData(2012, pca3) ExportScript.Tools.SendData(2013, pca4) ExportScript.Tools.SendData(2014, pca5) -- Weapon Panel bottom line local lPCABR = ExportScript.Tools.getListIndicatorValue(5) local stores1 = '' local stores2 = '' local stores3 = '' local stores4 = '' local stores5 = '' if lPCABR ~= nil then if lPCABR.PCA_LCD_2_0 ~= nil then stores1 = lPCABR.PCA_LCD_2_0 end if lPCABR.PCA_LCD_2_1 ~= nil then stores2 = lPCABR.PCA_LCD_2_1 end if lPCABR.PCA_LCD_2_2 ~= nil then stores3 = lPCABR.PCA_LCD_2_2 end if lPCABR.PCA_LCD_2_3 ~= nil then stores4 = lPCABR.PCA_LCD_2_3 end if lPCABR.PCA_LCD_2_4 ~= nil then stores5 = lPCABR.PCA_LCD_2_4 end end ExportScript.Tools.SendData(2015, stores1) ExportScript.Tools.SendData(2016, stores2) ExportScript.Tools.SendData(2017, stores3) ExportScript.Tools.SendData(2018, stores4) ExportScript.Tools.SendData(2019, stores5) end

What have you tried?