pet333r

The files in the "lib" folder are overwritten with the new ones. Config.lua file is not updated (just so as not to broke the IP addresses stored in it) If you don't want to update the Tools.lua file, you can delete the wips about it in update.ps1 (find: 'Tools.lua' and remove this line)

1. exactly (just to update the "Modules" folder with the F-14A) 2. to update the entire folder, along with the files to be automatically updated because there was an error which made the files not downloaded and updated (when trying to run update_pw-dev_script.bat it crashed an error so you had to update manually by replacing the files), you can replace all files (except Config.lua), and when you need to update the script in the future, simply run update_pw-dev_script.bat (all files except Config.lua will be downloaded from github and updated automatically, no need then to download zip files and manually replace)

Download zip: https://github.com/pet333r/pw-dev_script/releases/download/script/Scripts.zip and replace the "Modules" folder with that in the zip file with what you have on drive C You can also copy the contents of the zip file (without the Config.lua file so as not to overwrite the IP addresses in this file), and then, when you need to update the script again, just run the file: update_pw-dev_script.bat located in the folder with the script (the file is fixed so the automatic update should now work fine)

New version 1.0.2020.1119 avaible - Fixed a crash when launching the application - fixed some other small bugs The update fixes a few bugs, including the error causing the application to crash during its launch, at this point it works as it should:thumbup: Additionally, for F-14A support, update the "Modules" folder in the script

F-14A support added, just update the "Modules" folder in the script:thumbup: https://github.com/pet333r/pw-dev_script/releases/download/script/Scripts.zip

You have the A-10C_2.lua file in the Modules folder ?? https://github.com/pet333r/pw-dev_sc...es/A-10C_2.lua

add "--" in front of a script to disable it and check if the rest works the current version of DCS-BIOS is 0.10.0 and a lot has changed there

Check if there is a conflict with SimShaker. Additionally, what version of DCS-BIOS are you using? in newer versions, DCS-BIOS automatically added an entry to the Export.lua file along with the appropriate paths. This is what it looks like for me: BIOS = {}; BIOS.LuaScriptDir = [[C:\Program Files\DCS-BIOS\dcs-lua\]]; BIOS.PluginDir = [[C:\Users\pet333r\AppData\Roaming/DCS-BIOS/Plugins\]]; if lfs.attributes(BIOS.LuaScriptDir..[[bIOS.lua]]) ~= nil then dofile(BIOS.LuaScriptDir..[[bIOS.lua]]) end --[[DCS-BIOS Automatic Setup]]

the most sensible solution:thumbup:

vibrations, I think I can add, as for the sound, these buttons sounds are already in DCS and twice the same could be a little distracting

Ah, ok I understand what's going on, actually quite a good idea:thumbup:

1. It is not finished yet, therefore it is not active, it will be in the next one 2. what dividing lines? give more information so that we understand each other well, in this update I increased the size of the buttons a little to make it easier to "hit" the button 3. I will improve the display on the LCD a little:thumbup:

send me the whole "Scripts" folder from C drive and screenshots from ipconfig and wifi on Android

it can happen to anyone:smilewink: good that you found the cause of the problem:thumbup:

No, it is in the script (e.g. -11 instead of the 2nd line -> it is displayed on the 3rd line, I need to look at the files in A-10C and compare with the script)

1. I will consider how it could be sensibly added, it seems to me that an additional option in the settings with the selection of the switching mode (buttons / gestures) only needs to be reasonably planned on each panel so that it does not overlap with other switches 2. I am planning to add a horizontal version of the CDU 3. Radio also in plans, not only for the A-10C:thumbup: As for the display error on the CDU, the lines must be mistaken in the script

Moving to the MFD is possible from the UFC panel to the left (example: for the F/A-18 UFC panel you swipe to the left, same for Viper, A-10 or Harrier) Nice idea to add an indicator of which MFD is supported, it may be useful, I will add

Works with multiplayer. The "Allow player export: true" option must be enabled on the server. From what I've seen, about 95% of servers have this option turned on

How you have DCS-ExportScript set up that you can use StreamDeck together with the application? You changed something in this script's configuration files, etc.

Do you use DCS-ExportScript only for StreamDeck? If so, the script should be able to turn off individual sending options and leave only sending data to StreamDeck.Maybe it will help

Amazon tablets do not have a Play store as standard, but as far as I know, it can be additionally installed. You can also look for something used, maybe you will find something good for little money

Will be in the next update, waiting for approval of the update in the Play store

This is very good and important news that it also works with StreamDeck. I will add information about it in the script installation instructions and an example of the Export.lua file. I couldn't check it myself because I don't have StreamDeck. Thanks for the great info[emoji2]

Also, I noticed that this can happen after updating, I think I know why it is. I will correct it

Try disabling some scripts and check if there may be a conflict here. Then turn on one at a time to see where the problem may be. There is definitely no problem with DCS-BIOS, Tacview, SRS There can be a conflict with StreamDeck when data is sent from DCS to StreamDeck