xoomigo

A few was working on it. But no idea on the progress.

It's just a matter of replacing the overwriting the files concerned in the acdb folder and re-running the setup. However, Kyle's files here were meant for troubleshooting only. They have been superceded by the latest DCS-COINS repack.

@ebabil, I have added a ICP page to my existing F-16C dashboard. However, there is a caveat. The DED text display takes a few seconds to update after a keypad button is pressed. There's nothing I can do to make it refresh faster as it is fully dependent on DCS-BIOS timing to provide the events/values. And also, some symbols on the DED are unavailable as keyboard characters. Hence, DCS-BIOS substituted them with alternate characters which may make the text appear corrupted (see screenshot above). In addition, the font used is not perfect but is the best in the current TP library to match those of the DED - there's text alignment issue in some instances. Lastly, inverse character indicators will not be shown. If you are still interested, you can get it from https://www.digitalcombatsimulator.com/en/files/3319505/

I had the issue of the Viper rolling to the left every time. It took me a while to figure it out. I forgot that I had binded ROLL HDG SEL and A/P controls to my my throttle switches and they were left on.

Ditto.

Okay, it's done. I have uploaded the updates... Can sleep better tonight... Now, that's an odd TP behavior... Ah, okay. I remember reading about this trick. Yes, I will do the same. Thanks!

You can set up a plugin event change (under Event Settings) to trigger (go to the KBU page) when the KU display parameter text value changes to the display input prompt concerned. I am not aware of any means within DCS-BIOS to provide any indicator of which seat is in focus (PLT or CPG). Therefore, it is a challenge to determine which page with the KBU to switch to - especially if the seat change is triggered from Voice Attack with a key press. If you trigger the seat toggle via the TP pages, you can add a TP value to track the seat in use (perhaps "1" for PLT and "2" for CPG) - and on the event trigger, use the value with a "IF-ELSE" condition (no idea whether this is available with the current TP version) to switch to the desired page accordingly. But taking this approach would mean you cannot use Voice Attack to switch between seats. I would like to use Voice Attack with the Apache too. Please share the path you will take. Cheers!

@PHMAC, thanks for the compliment/feedback. Now that I am aware, the OCD in me cannot ignore the fault - even a slight cosmetic one. I will have it fixed in the next opportunity.

My Apache dashboard pages are now available. https://www.digitalcombatsimulator.com/en/files/3326762/ Below is the TEDAC page.

I have hit a snag doing the Apache TEDAC panel. The Sight Select for TADS and horizontal control knob are not working with DCS-BIOS. Anyone else encountering the same or other issues with the Apache?

For those interested in TP pages for AH-64D, here's my sample of the keyboard unit (lumped together with other controls for filler). Pilot pages done. Starting on CP/G pages.

I am still in the midst of doing the AH-64D dashboards. I may work on the F-16C ICP panel later - but I can offer no promises nor any timeline. Hopefully, someone who have done it may share it here soon.

Yes, it's a plugin for Touch Portal. Check out pages # 3 and 5 for UFC for F-18C page screenshot, video and ready-to-use TP page by Marcos Paes. Similarly, the F-16 ICP can be supported.

Are you referring to the below download which was created before DCS-COINS came into existence? https://www.digitalcombatsimulator.com/en/files/3308519/ If you are thinking of using another table in addition to your existing tablet with the F-16 ICP page, it is not currently possible. A Touch Portal desktop app does not support more than one device at a time, but according to its FAQ, that may change in the future. Hence, you can try to modify your copy of the F-16 ICP page to add the display of DED lines (buttons) - will require resizing the existing buttons to make space for new buttons. IMHO, it may be easier to create it from scratch, albeit it may not look that realistic unless you are good with graphics editing.

I have also updated my Viper dashboard. https://www.digitalcombatsimulator.com/en/files/3319505/

No, that's not how it's meant to work. The reset action is merely to put the all the current aircraft states back to the defaults as defined in the aircraft PP file concerned. As far as I understand, it's not possible to force (actively poll) DCS-BIOS to send all event updates to the plugin. The plugin can only passively 'listen' for events - it cannot 'ask' for update to any state. Hence, it is only useful in situation where you restart the same mission from a cold start.

In case anyone is interested, I have updated my Hornet dashboard. https://www.digitalcombatsimulator.com/en/files/3319504/

DCS-COINS release 2022-10-23 is now available: Fixed issue with"Reset Aircraft States" not working as expected Streamlined plugin execution in verbose and non-verbose mode PP movement values enhanced to percentage format PP adjustments F-16C, F/A-18C, Mosquito and UH-1H - mostly on cold start defaults https://www.digitalcombatsimulator.com/en/files/3319022/

Yes, I am well aware that I will not be around forever. When I first offered this plugin to the community almost exactly a year back, I have no idea how it was going to be received. Firstly, other than local PC backups, I have a private server to host my codes but I will be moving it to GitHub soon - as a private repository for now as I have yet to decide on the long term direction of DCS-COINS. Will look to implement a mechanism to convert the source code in GitHub for public release if there is no update for 12 consecutive months to ensure possible continuity by other developers. The next release within a day or two will have the fix along with some execution enhancements. Currently, still testing some adjustments to the PP files.

The "UHF_PRESET_SEL" and "VHFAM_PRESET" (I assume this was the you were comparing against the former) do not appear to be set up to work in similar manner - based on my "noob" interpretation from the A-10C.lua file. defineTumb("UHF_PRESET_SEL", 54, 3001, 161, 0.05, {0, 1}, {" 1", " 2", " 3", " 4", " 5", " 6", " 7", " 8", " 9", "10", "11", "12", "13", "14", "15", "16", "17", "18", "19", "20"}, false, "UHF Radio", "UHF Preset Channel Selector") defineRadioWheel("VHFAM_PRESET", 55, 3001, 3001, {-0.01, 0.01}, 137, 0.01, {0, 0.20}, {" 1", " 2", " 3", " 4", " 5", " 6", " 7", " 8", " 9", "10", "11", "12", "13", "14", "15", "16", "17", "18", "19", "20"}, "VHF AM Radio", "Preset Channel Selector") From Util.lua, it seems like "defineRadioWheel" is a superset of "defineTumb". The latter has this: inputs = { { interface = "fixed_step", description = "switch to previous or next state" }, { interface = "set_state", max_value = max_value, description = "set position" }, } The former has the additional: if state == "INC" then GetDevice(device_id):performClickableAction(command2, command_args[2]) end if state == "DEC" then GetDevice(device_id):performClickableAction(command1, command_args[1]) end DCS-COINS "mined" DCS-BIOS json files accordingly to determine the "tpActionType" field value (4th field in the PP file). And this corresponds "1" for "set_state" and "2" for "fixed_step". "3" is for "variable_step". Excerpts from the A-10C.json: "UHF_PRESET_SEL": { "category": "UHF Radio", "control_type": "selector", "description": "UHF Preset Channel Selector", "identifier": "UHF_PRESET_SEL", "inputs": [ { "description": "switch to previous or next state", "interface": "fixed_step" }, { "description": "set position", "interface": "set_state", "max_value": 20 } ], "VHFAM_PRESET": { "category": "VHF AM Radio", "control_type": "discrete_dial", "description": "Preset Channel Selector", "identifier": "VHFAM_PRESET", "inputs": [ { "description": "switch to previous or next state", "interface": "fixed_step" } ], Therefore per the above, I can conclude that "UHF_PRESET_SEL" will not work properly with tpActionType "3". But on the other hand, I have no explanation why it worked for "VHFAM_PRESET" as you said. Other than directly debugging/fixing DCS-BIOS code for A-10C here (which is outside my expertise currently), I can only suggest you try changing the PP file for "UHF_PRESET_SEL" to tpActionType "2". UHF_PRESET_SEL|uhf_preset_sel|UHF Preset Channel Selector|2|0|UHFVHFAmFmPreset|1 Yes, I see what you mean. When I tested it, I saw all the associated arrays and variables reinitialized when the action was called - and I thought it gave the same impact as restarting the plugin. Apparently, not so. Will need to test further.

I have already completed and uploaded a patch. Will take a break now. And need to focus on my other priorities. Will get back to you guys later.

Your suspicion is correct. I will have to limit what can be defined as connector/sliders. Will make the adjustments and release the patch as soon as I can.

I don't think you can simply change any control type "0" to "3" and it will work to switch values in increment or decrement manner. It depends on how DCS-BIOS is programmed to respond to the commands for the controls concerned. If it's not getting you anywhere, I can only advise you to switch to DCS-COINS 3 which works off the latest version of DCS-BIOS - which hopefully, fixes the controls concerned (assuming if they were buggy).

Unfortunately, yes. The current DCS-COINS design is based on DCS-BIOS-defined Lua file names - and the names are also used to derive TP prefixes. It's the prerogative of DCS-BIOS developers to decide on how on to name the files and also to rename existing files (as discovered a few days ago). With this recent revelation, I will need to find a way to mitigate the issue to prevent future DCS-COINS/DCS-BIOS releases from potentially rendering previous DCS-COINS-enabled pages inoperable - as you have encountered.

I have just uploaded a patch for the aircraft alias file. Can you download and try again?