xoomigo

Ah, yes. I had missed that. Okay, I will accumulate it with other changes in the next release. BTW, are you on the TP v4.2 beta-3 or beta-4 release? I am asking because the earlier issue of slow loading of the "Edit Control Screen" was only fixed in the beta release concerned, not the stable version.

Okay, it's done - DCS-COINS.exe patched with changes to Common Data and L-39 (as discussed with virgo47). https://www.digitalcombatsimulator.com/en/files/3319022/

Yes, they are - okay. What I wanted to say was that any change to L-39 for me means blanket overwrite of the section meant for L-39, without having to identify, compare one-by-one how/what was changed and then making the change itself. So it means all accumulated changes that you have made since day one. This was a message from the 3rd party node.js API for TP. I had added some code to enable the 2-way slider update (adjustment in the knobs in DCS will also automatically update the TP slider) and also the TP hold functions - which inadvertently added some "noise" to plugin communication between DCS-BIOS and TP. The attempt did not pay off and I had left the code active - hoping that it was a TP4 issue and that future TP revisions may fix and make them work. I will disable them as they are now causing them. Will release a new plugin version soon.

Thanks. For subsequent changes, perhaps you can just send me the entire batch of your modified section - both new and old. I can then just overwrite my copy with yours without having to do anything else. Will be cleaning up my codes before uploading to Github. Will let you know when done. It will be publicly available.

Please include only those lines which are modified. Will include as an exception to overwrite the generated results. Future revisions of DCS-BIOS could have added, removed or changed others. So other than the exceptions, these needs to be retained as-is from future DCS-BIOS lua file. Frankly, I have no idea. I wasn't aware that they exists until now. They were not there originally when I got started with DCS-COINS. Any newly-added parameters from DCS-BIOS would be active by default. I will add them to the default deactivate list if they are not useful. Sure, will do for the next bundle.

The PP record structure: Aircraft Parameter ID TP State ID TP State Description (DCS-BIOS description) Action Type 0: No action 1: "set_state" 2: "fixed_step" DEC INC by 1 3: "variable_step" -<num> +<num>|"suggested_step":<num> 4: "action": arg:"TOGGLE" 5: "hold"/"set_state" 6: "connector/slider control/variable_step" (superset of "3") Action Step - increment/decrement value (if applicable) Enumerated list of options/Range of values TP Default (Starting) value "UpTo2" specifies range from 0 to 2. Based on the option sequence in DCS-BIOS description, it should be 0 for "TAXI", 1 for "OFF" and "2" for "LANDING" - but I have found that it's not always the case. I have set the PP value to default of 0 for almost all the parameters (on consideration that most users would just cold start the aircraft in DCS and that the switch of 0 value in most cases). Note that when you changes between different variants of the aircraft (eg. between "C" and "ZA"), you are essentially still using the same base DCS-BIOS lua program. It does not "reset" to default when you subsequent switch into a different variant or reload the same variant. To restore to the defaults per PP file, you can do a generic "RESET" option from the Common Data module. If you want to change to a different PP default, you can directly edit the PP file with a text editor. Eg. change your example above to 1: FRONT_LAND_LIGHTS|front_land_lights|Front Taxi and Landing Lights Control Switch, TAXI/OFF/LANDING|1|0|UpTo2|1 And if you do, I can preset it every time in future DCS-COINS releases so that they would stay the same - save you the hassle of re-adjusting them again. Cheers.

Glad that it's useful and serves your purpose.

Okay, done. Common data issue is fixed with the latest patch (usual link). Just make sure that the setup program version is 2404.03. null

Ah, missed this - a result of the inconsistency of file naming convention used on the Sabre in DCS-BIOS. It had a space whereas others were standardized with a underscore. This came about due to recent changes in the BIOS.lua. Anyway, this has been fixed with the latest update to the plugin. Kindly extract from the usual link and replace DCS-COINS_Setup.exe and it should work. Thanks for the highlight! Oh, okay. Will look into it.

Okay, the latest release of DCS-COINS is now available. And yes, it requires Touch Portal v4 and also the latest version of DCS-BIOS (which is bundled together in the package). https://www.digitalcombatsimulator.com/cn/files/3319022/

Hi all, An update to DCS-COINS is now available: https://www.digitalcombatsimulator.com/en/files/3319022/ Changelog: Repacked with the latest FlightPanel's DCS-BIOS 0.8.0 (DCS Unified 2.9.3), Setup support for new DCS-BIOS changes, Addition of state "aircraft_model" (variant ID) - as requested by virgo47, and Fix for identification of SA-342. Important: You need to upgrade to DCS-BIOS version 0.8.0 and Touch Portal v4 for this version of DCS-COINS to work. Cheers! xoomigo

Okay, that confirms it. I can see a few variants for SA342, consisting of SA342, SA342L, SA342M, SA342Minigun and SA342Mistral - supported by FP's DCS-BIOS. Coincidentally, I am currently working on a few enhancements - including adding a state called "aircraft model" to identify variant of the loaded aircraft. This will allow users to configure auto-switch to different pages or changing of buttons according to the variant concerned. Expect the next DCS-COINS release within the next few days.

You had asked and before and had done it before. See my post on April 29, 2023 in the link below: https://forum.dcs.world/topic/207264-touch-portal-app/page/13/

Hi SuperTonique, I happened to chance upon your post here. You had asked me before about the issue and I had pointed to DCS-BIOS being the issue - requires know-how which is beyond my pay grade. After going though plugin setup again and reviewing the latest bundle of DCS-BIOS, I now suspect it may be due to changes in the aircraft alias in the latter which may be the cause of the disconnect. Please post the output of "dcs-coins -v" when you have the SA342 up and running. I need to know the "aircraft" value returned by DCS-BIOS for the confirmation. Cheers!

It should be doable. Just need to create a state similar to "Aircraft" parameter. Need to add to my to-do list.

Looks great! Like the way you did the makeover of the buttons. There's evidently a lot of time spent and love for the L-39. I will add the link to the DCS-COINS plugin in the next opportunity. Your video is also impressive! All aptly covered and explained - with key points and limitations highlighted. Great job! Appreciate the promo of the plugin.

KleineWimpie, Please share the content of your Export.lua file. Thanks & regards, Mun Tutt

TP 4.2 Build 1 (Beta) is out and supposedly fixed the bug I mentioned earlier. But it did not fix the lag in button/slider dialog window loading time. The issue appears to correlate to the number of plugin actions/events or connectors registered. The more you have, the longer it takes to load. Therefore for the time being, I would advise to limit install the aircraft module one at a time - to the one that you are going to work with in your TP pages. I will need to contact TP to report this issue. TP4 "Edit Control Screen" does not appear to be optimized to initialize large number of actions, events and connectors. I will take a look later. I hear you. It's on my to-do list.

Hi Virgo47 & all who had been waiting patiently... It's finally done. You can get the TP4-compatible DCS-COINS Version 4 from the same place: https://www.digitalcombatsimulator.com/en/files/3319022/ Note that this version of DCS-COINS is not be compatible with TP v3 and older. Therefore, please do the necessary backup of your existing TP pages and DCS-COINS version on-hand before you do the upgrade and page editing. The TP4 basic plugin support is not exactly clean. I had to do a workaround to enable its new parser to accept the generated TPP format. It may be a problem later when the known bug is fixed in future. The bad news is that all actions added using the pre-TP4 format cannot be edited. The only recourse is to delete and then add them again - and you will need to bear with the 5-second loading time of the "Edit Control Screen" with each button click. Cheers. xoomigo

Just a little note that I will start review of the latest TP requirement changes soon... hope to be able to give an update here in a few days time.

Hi virgo47 & DCS-COINS users, Besides work, I have been very preoccupied with many other things and have been out of touch with DCS and TP for quite a while... The latest TP 4 release came with revised TP format structures - which unexpectedly broke certain DCS-COINS functionalities. I will need to go through the API documentations to identify the changes needed before I can determine what needs to be done for the plugin. However, I can only try to do so sometime in the first quarter of next year. Sorry.

Will look forward to it!

Thanks for the update - you are welcome! Will the next DCS-BIOS release by FlightPanel will include your mod? Also, will you be sharing your work on TP pages when it's complete?

Can you share the BATT_SW line in the PP file? Potentially, it is caused by unexpected inverted values. If the second last column value is "OnOff", change it to "OffOn", or vice-versa.

Sorry, the earlier format that I gave you was incomplete - it was missing the first column which indicates the PP file concerned. Please try replacing the line in CustomACParams.dat file: MH-60R.pp|LGHT_SW|lght_sw|Lighting_Switches|0|0|=int(65535)|0 Or if you want the value to be in percentage, then use the following MH-60R.pp|LGHT_SW|lght_sw|Lighting_Switches|0|0|=pct(65535)|0