xoomigo

@virgo47, it could due be my mapping of the aircraft alias names for the L-39. I will take a look when I get back after work.

Folks, DCS-COINS Version 3 is now available. * 2022-10-06: VERSION 3 RELEASE 2210.03 - Support for Slider controls with TP API version 4 - Analog aircraft controls accessible via TP slider and/or action button (both operates independently - action does not update slider position) - Support for Mirage F1 (requires DCS-BIOS 0.7.46 or newer) - User friendly values for AH-64D, and minor PP file fixes - Packaged with DCS-BIOS 0.7.46, which includes support for Mirage F1 - "Common Data" Action "Reset Aircraft States" option to reinitialize aircraft to intial default values - Execution in verbose mode ignores action requests to DCS-BIOS - avoid duplicate commands - NOTE: Certain parameters/values created with previous DCS-COINS versions may no longer be compatible with this version. You will need to delete and recreate them. https://www.digitalcombatsimulator.com/en/files/3319022/ The following illustrates using button and slider to control the Hornet's Formation Light Dimmer.

Errm..., this doesn't seem the same from my end. The drop-down list should show options from "[0] 1", "[1] 2", "[2] 3",...."[19] 20" - where the number within the square brackets is action value. There if channel selector is "2", then the action command "[UHF_PRESET_SET 3]" would be sent to DCS-BIOS. The A-10C.pp file, line 670 should show: UHF_PRESET_SEL|uhf_preset_sel|UHF Preset Channel Selector|1|0|UHFVHFAmFmPreset|1 Is yours the same?

Sorry, my earlier statement about future DCS-COINS releases not supporting certain aircraft modules was made prematurely. I was thrown off by the unexpected errors encountered with the listed modules in my quick-and-lazy tests, and had concluded hastily. Now that I have dived deeper into the issue, I discovered that Flightpanels' developers occasionally change aircraft lua filenames in between DCS-BIOS releases. This means that the library of PP files bundled with the plugin need to be tied to a specific FP's DCS-BIOS release. The dependency is such that the selected aircraft must have a DCS-COINS PP file mapped to a set of DCS-BIOS lua and json files - all must have a matching filename (minus the file extension). Otherwise, the DCS-COINS setup or the TP plugin installation will fail. Bottomline is to avoid DCS-COINS installation issue, use the DCS-BIOS version (including BIOS.lua) which is the same as the one bundled with the DCS-COINS package concerned. Future DCS-COINS releases will support aircraft modules supported by the latest version of DCS-BIOS of the day. Yes, you should upgrade to DCS-COINS version 3 and the latest DCS-BIOS when the former is released. If L-39C and L-39ZA are supported by the same file set (pp, lua and json) per the DCS-BIOS concerned, you should not lose any functionalities you currently have. Instead, you will gain access to analog controls (currently disabled or restricted to a small number of controls) in both button and slider modes, updated DCS-BIOS, and other back-end fixes (incl. TP API). The cons are that you will need to test and may need to re-do (remove and add back) some of the controls (if they fail to not work with the new version). Anyway, do a backup your BIOS.lua and DCS-BIOS in your DCS script folder, custom TP pages and TP Munt.G_DCS-COINS plugin folder, before you try out the new version - just in case you want to revert back later.

Your logs shows the same "1" parameter for the action "UHF_PRESET_SEL" being triggered. Note that running DCS-COINS version 2 in verbose mode in the Command Prompt will trigger duplicate action commands to DCS-BIOS. Can you share the value you used for each of the actions?

Hi CARTOK & Kyle, I have found a way to handle this within the plugin. DCS-COINS v3 will include an action "Reset Aircraft States" for use with a button press, under category "Common Data" to reinitialize the values to default.

No idea how to invoke this from DCS-BIOS. Need someone familiar with Lua to probe the codes and advise. Anyway, the latest DCS-BIOS seems to generate more states/events on aircraft start-up. You can check it out with the version 3 release of DCS-COINS soon. Yup, these parameter names are exactly as extracted from DCS-BIOS - albeit without the aircraft prefix. There are inconsistencies in the naming conventions by different DCS-BIOS coders.

Errr... I did not do anything yet. If there' was any performance improvement, it's due to the DCS-BIOS update. I have found the cause of the issue that you had encountered earlier when installing the plugin into TP. I did not realized that there were format changes to a few entries in the BIOS.lua file from the last DCS-BIOS update in my last release. Selecting the impacted aircraft module will resulted in a corrupted entry.tp file, which will hang the TP plugin installation. Anyway, the upcoming DCS-COINS release within a day or so will address it.

This is strange but could be due to an unexpected error which did not kill the program execution.

Ah, I see that the module that broke your installation was actually the Supercarrier. Will investigate it on the sidelines of my development work later.

L-39 is good. Only the variant L-39ZA is not. As long as DCS-BIOS keeps it up-todate/working with DCS World updates, it should continue to work in future DCS-COINS releases. Work on DCS-COINS Version 3 is progressing well. The package will include user-friendly AH-64D values and pre-defined aircraft control as connectors for TP sliders (operates similarly to starship controls we see in Star Trek ). Assuming no unforeseen hiccups, expect it to be released either this weekend or early next week.

Hi Kyle & all, I have tested and discovered that the installation will fail if one or more of the following modules are selected. C-101CC F-14B Hercules L-39ZA SA342M Therefore, please do not include any of them in your list of aircraft in DCS-COINS_Setup. They will be excluded from future DCS-COINS releases. Cheers.

Please attach the entry.tp file for me to check. In the meantime, run DCS-COINS_Setup (no need Admin access as it was not an issue) and select only one or two aircraft that you had used earlier eg. F/A-18C and import the plugin into TP. If it works, then I suspect it could be something to do with the untested SA342 module. I will test this on my side later.

Kyle, I had the same issue in my new PC setup. Suspect it may be due to more restrictive program permission in Windows 11. Are you on Windows 11? Please check the folder contents in C:\Users\kyle_\AppData\Roaming\TouchPortal\plugins\Munt.G_DCS-COINS\DCS-BIOS If the folder is empty, that means the setup program did not manage to copy the required files there from the DCS-BIOS script folder. In this case, try running the DCS-COINS_Setup.exe as an Administrator and do the install again. And if it still fails, please share the last section of TP logs (set it to show all errors including from plugins first before doing the plugin install).

Hi CARTOK, Yes, your observation is correct. There are 2 instances of DCS-COINS running when doing "DCS-COINS -v" with the Touch Portal plugin loaded. Both will send an DCS-BIOS action each on the same TP command. In the upcoming version 3, I will disable DCS-COINS from issuing action commands to DCS-BIOS when it's running in verbose mode. Hi Kyle, I need to check this and also whether I am interpreting the PRESS/DEPRESS controls correctly in general. This may have something to do with the missing json files in the Munt.G_DCS-COINS\DCS-BIOS folder. Try the unpacking of the DCS-COINS.zip to a new folder and then run DCS-COINS_Setup.exe there. And if it still fails, rename your existing DCS-BIOS to something else in the DCS script folder (for backup) and reinstall DCS-BIOS from DCS-COINS_Setup.exe.

Hi Virgo47 & all, I have just finished testing a proof-of-concept to include DCS-COINS support for TP sliders. The results are encouraging. Currently by default, all aircraft "Control Knob" parameters are disabled. I will be enabling all these as slider controls for AH-64D, AV8BNA, F-14, F-16C, F-5E, F-86F and F/A-18C, and Mig-19P in the next DCS-COINS release (version 3). Others with the "Intensity" settings will be identified (will need your help) and included as well. Stay tuned here.

Instead of using "When the plug-in state" event, try "Update Button text each cycle (500ms) to".

Hi CARTOK, Many of the generic option set for a aircraft parameter eg. "OffOn" were programmatically derived based on my experience with some of those aircraft that I was spending time with (setting up for TP pages). And unfortunately, it's not correct for all - as you have pointed out, regarding the Flap setting. There are a few coders for the DCS-BIOS lua files and not all are following the same standard in defining the names, descriptions, values, sequence, and etc in their work - and that broke my logic for a correct interpretation to a meaningful name for some modules. I don't have the A-10C and many other aircraft modules - and also the time to test out/map the values of those that I have, to user-friendly names. I have done so for the F-18C and partially for a handful. I will take your input here to fix the Flaps Setting in the next DCS-COINS release. If you have identified more, please let me know so that I can include them as well. Regarding your issue of no messages triggered for certain actions, I can only speculate that it may be due to a bug in the Lua code for the A-10C in DCS-BIOS. I am planning the next DCS-COINS release with the latest DCS-BIOS pack, and along with updated TP API library. Expect it to be available within a week. Hopefully, this will solve some if not all of the issues you and the others are facing. I will announce it here when it's done. Cheers!

I thought I came across an on-change trigger setting in TP - I will need to check. The feature to set an action with a precise value appears to be supported in TP v3.x. However, DCS-COINS does not support the needed structure yet. This will also depend on the 3rd party API that DCS-COINS used to communicate with TP. I will need to spend some time to research and test this.

I have not explored doing that with DCS-BIOS logging. But I did a quick search and found this: Perhaps, you can try this. If I am not mistaken, it's from the same developer who maintains FlightPanel DCS-BIOS library.

Input and output here should be from the DCS perspective. Input = action commands from DCS-COINS Output = event/state updates from DCS (to DCS-COINS)

Try this - from DCS-COINS_Setup.exe, check the P-51D option and then regenerate the tpp file and reinstall the DCS-COINS plugin for TP. Yes, if one or more # characters appear on the line, it would be ignored. You can remove the # character to enable it to be processed by DCS-COINS - but you will need to regenerate the TPP file and reinstall the plugin.

Assuming that your PC setup is decent - runs DCS without any lag, I would say that it is a DCS-BIOS issue. I found a few of the Mozzie parameters having the similar issues while doing a panel for it. You may need to reach out to the FlightPanels DCS-BIOS author(s) about the issue.

Hi Virgo47, I think the P-51D option is supports the free TF-51D module - according to the DCS-BIOS aircraft alias definitions. Though there may be likely some features listed which may not be available to the free version. You are the first user I know of who flies the L-39. When my rig is fully restored with DCS and the IDE for DCS-COINS, I will check out the TP slider feature yet. Will update in this channel if there's any progress.

Hi Bertuz, Firstly, I want to state that I like and appreciate that you have presented a very thorough situation of your issue on hand. From your logs, we can strike off response time as the cause. They showed the "inherent" issue that I had noticed and was aware of right from the start. Text values are sometime returned in partial state - some are more frequent than others. At this point in time, I do not have the expertise to troubleshoot Flightpanel's DCS-BIOS and/or Daniel Tian's DCS-BIOS API. I can however, try to find and develop a holistic way to address the issue within DCS-COINS - but it will take time. This year has not been good for me. DCS is off limits to me for the past few weeks due to my motherboard being faulty. Its replacement along with a new CPU are only expected to arrive early next month. It will run Windows 11 and will require a bit of effort to set it up before I am back in business. I have a hanging work-in-progress Apache keyboard unit (CDU) along with update and relabeling of AH-64D parameter values. Also in queue, is the repackaging to include the latest FP's DCS-BIOS with support for the Mirage F1. I will send you a PM when I have a solution later though I cannot say when. I want to use your neat-looking UFC as well - if you are okay. Cheers!