xoomigo

@virgo47 This is really strange. I tried the steps a few times that you mentioned but failed to get the error concerned. When you get the error, do not proceed with "Next" and share the generated files in: folder Munt.G_DCS-COINS DCS-COINS.cfg, ACJSON.cfg folder Munt.G_DCS-COINS\acdb aircraftModules.cfg Did anyone else get the same problem?

@virgo47, I have also added the function '=ictr'<max value> (inversion of '=ctr'<max value>) that you have asked for. Try it out and let me know how it goes.

DCS-COINS Version 5 is now available. Revamped to adapt to latest Skunkworks DCS-BIOS (Note: Compatible only with version 0.8.2 going forward) Optimized for smaller TP payload Repacked with DCS-BIOS 0.8.2 (incl. support for F-4E, Mirage-F1BE, OH-58D and UH-60L) Enums for L-39 (by @virgo47) and FA-18C_hornet (add-on by @Kyle_Katarn https://www.digitalcombatsimulator.com/en/files/3319022/

Hmm.., DCS-BIOS does not appear to be generating the events. Can you please test the NS430 events with the tool? https://github.com/DCS-Skunkworks/BIOSBuddy

@virgo47 or @OSchmidt, can you please help do a test of NS430 functions using the attached DCS-COINS.exe? 1. Rename your current copy of the DCS-COINS.exe to a temporary name (eg. DCS-COINS_orig.exe). 2. And then extract DCS-COINS.exe from DCS-COINS_5Beta.zip here. 3. Load up Touch Portal as usual. 4. Run "Command Prompt" and navigate to your DCS-COINS folder where you have DCS-COINS.exe installed. 5. Run "dcs-coins -v". 6. Run DCS and start up any aircraft with NS430 support. 7. Invoke a few NS430 commands/functions in DCS. 8. Observe the command prompt window and see whether there's any NS430 events recorded. Capture a screenshot of the events - if available. When done, quit DCS, close the command prompts, and delete the DCS-COINS.exe and rename your previous copy back to DCS-COINS.exe Let me know if it works - please share the screenshot if so. Thanks. DCS-COINS_5Beta.zip

@virgo47, I need to look into enabling NS430 support from DCS-COINS. I see DCS-BIOS configuration to pair specific aircraft with NS430. On another note, I have discovered that the latest DCS-BIOS had signicant code change in its Lua script, which will require adjustments to the DCS-COINS setup program. So, this will involve more than a repack...

@Kyle_Katarn, I have gone through your files and I get what you are doing. They look okay and should not impact other users. All, I have regenereated the PP files from the latest DCS-BIOS release and applied the customizations. However, I have yet to perform any basic sample tests - will do so within the next few days. @OSchmidt, sorry, I do not have the NS430 module. @virgo47, the NS430.pp was generated as its JSON file was located together with the aircraft modules in a DCS-BIOS folder. Similarly, did anyone try Supercarrier? Can you check whether "dcs-coins.exe -v" show any output on NS430 in the beginning when you first load an aircraft that it supports?

@Kyle_Katarn I wasn't expecting you to do your version of aircraftEnums for Hornet as I had already done so - and it's already in use by other users. If you had started afresh without the packaged aircraftEnums, then it's definitely going to conflict. And it's not a good idea to duplicate impacted parameters as they would appear multiple times in the plugin options, confusing to users who's trying to create their own TP pages for the aircraft concerned. I will need to review and let you know. The setup program approach was simple and "quick-and-dirty" tool to do a one-time job. Hence, it does not save the path for the Export.lua file. I can add that feature later. But for now, if you are using a non-standard default folder location, you will need to select it each time the setup is run. All, Sorry for the delay as I have other urgent stuff on my plate. Will target the coming weekend to review (test) the latest stable DCS-BIOS release before repackaging it with the plugin. Stay tune.

Virgo47, thanks for correcting my typo above. Great to know of your contributions there. Nope, no change to PP structure. Will review/integrate your attachment - hopeful over the coming weekend. Cheers!

Welcome back to TP! Adding to virgo47's response, Skunkworks (formerly Flight Panel) did a major revamp of DCS-BIOS which involves standardization of the naming convention of parameters. Check out https://github.com/DCS-Skunkworks/dcs-bios/wiki/Release-notes - latest DCS-COINS is packaged with DCS-BIOS v0.8.0. Hence, unavoidable to remap the non-working controls. DCS-COINS v0.8.1 has been released 2 days ago - virgo47, you are listed in the credits!. Will need to find time the next few days to test out and issue a repack. virgo47 and Kyle_Katarn, you can send me your aircraft eNums file if it's ready for inclusion. Could be a DCS-BIOS bug. Need to feedback to the Skunkworks team.

Perhaps. I will review it again after I am done with my current project. Ah, okay. Missed that. I had assumed that it was an issue for others as well. Yes, good idea. It will probably be useful for others as well.

Rough cut answer is yes and yes. Need to build mechanism to "remember" the parameters which requiring inversion. All incoming DCS-BIOS events and outbound actions to DCS-BIOS need to be checked each time against a list to determine whether they require inversion and then perform the inversion if matched. Of course, there can be an initial check on the aircraft parameters being loaded to determine whether any requires inversion and then set a global variable accordingly. If there's none, then the variable will not trigger the logic block to check and perform the inversion. I thought you no longer need the inverter function in the plugin since you will be working with the DCS-BIOS folks to correct them. No?

Hi virgo47, Yes, I had taken a look at doing the inverter function to reverse the min/max value for certain parameters. It was not a straight-forward change as anticipated earlier. And it will create additional CPU cycles in the processing of each DCS-BIOS event and action - which I fear may impact its performance in lower spec PCs. Excellent! I was also going to suggest the same - addressing the issue at the source. I was using https://github.com/DCSFlightpanels/dcs-bios but looks like that's the old name/link - DCS-FlightPanel is now known as DCS-Skunkworks and the link will redirect to the same link that you referenced. So yes, it should be the same repo. Let me know when the next version is released so that I do can a rebundling of the update. FYI, I am caught in the midst of another project - my home automation is in a midst of a hardware and software upgrade... other half indirectly nagging to get it done ASAP. Facing a technical issue and will require some time to sort out in my limited spare time... I will follow up with the promised release of my code in Github after that.

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.