prestonflying

This is a current ability of SimApp Pro using the provided `C:\Program Files (x86)\SimAppPro\resources\app.asar.unpacked\dcs_event_bind_config.js` file, you can define your own aircraft profiles (In a json dictonary, but there is an example of the F18 and other planes that work), Attached are images of a JF-17 using custom lights and the F18 profile. You can extend this to work with any plane and any light value You will need to look in the game files of the module to determine the value for `dcs_id` as this is the argument number for the module. Example, dcs_id 376 controls the APU light in the hornet. You can find these values in "<DCS_INSTALL>/Mods/aircraft/FA-18C/Cockpit/Scripts/MainPanel/lamps.lua" Other modules will have similar files to get the light values needed for the `dcs_event_bind_config.js`nullnull

Update: Version 17 has been uploaded to the Git Hub with the SuperBug suggestion from Triagati, I tested this with my UFC and Super bug and confirmed it was working. Thanks all for the interest and support. Download Link to Version 17

@Trigati Very nice work! I think your solution is correct, I do not have the mod, but I will implement your wwtExport.lua tweak with the renaming of the SuperBug to the regular hornet and perhaps others can test. This lines up with what others saw prior to our addition of the generic profile (The super bug was working). Thanks, the update should be on github in a few minutes

Some limitations of the screen, it an LCD Matrix display that is around 64x200 ish. So we can not put display exports such as RWR, or HUD on it. But we can write strings on it. So Speed, AOA, gear state, flap state, missile selected, etc. It supports A-Z, 0-9, * unlike the hornet UFC which has limitations on characters on each window.

So after writing up this response yesterday, I felt the need to try it mysnullelf! Here is the result, Ill be continuing with a stand-alone application that allows any data to be drawn on this LCD screen. This means when flying the Tomcat, you could put airspeed, selected weapon, arm status, etc on this screen. It is early on in development as I just finished up Step 2 in my list above.

And the next phase begins, working on something new! Going to be spinning up a new mod made for the F16 that is stand-alone (unlike the F18 Universal UFC mod which requires SimApp Pro) Here is a screenshot of me getting data on the ICP (took a little while to figure out, but now onto the fun part of making software that talks to it using data from dcs) This is exciting because ALOT more data can be shown on this ICP DED compared to the F18 UFC. My ask from you all is to start thinking of the ideal way to use this! Think big. My current plan, a small stand-alone program that is open source and allows text to be written to the screen. Perhaps stand up a UDP protocol so DCS Export lua, SimConnect, etc can send data to be drawn to the device. If this goes well, I can port this over for the F18 Mod then SimApp Pro will not be needed for custom use of these screens. This would allow developers/community to use this device for any game. Let me know your thoughts! Thanks null

@Flav I have explored making something like the F18 UFC mod for the F16, but it would be much more in-depth and time consuming. This is what I found: - The F16 ICP is a matrix display, thus you can not display a screen or window on it, instead if works Dot Matrix display - WinWIng Export lua exports the string characters currently shown on the ICP, it does not export the actual DED export window - SimApp Pro reads these string messages of the DED and draws them on the Dot Matrix display using custom code within SimApp Pro Possible paths to get data on the DED screen without using SimApp Pro and showing custom data: - Determine what SimApp Pro is sending the USB DED to get data to appear on the screen, you could use a program like Reverse USB Protocol or USB Trace - Once you determine what data is being sent to the USB F16 DED, you can then written a program which writes to this device using HIDAPI or some other api to send read/write messages to the USB Device. Lets call this program DEDWriter (since it writes data to the DED) - Once we can send custom data to the device, you then determine what data you want to appear (Example: Flying the A10 and you want to see the number of bullets remaining, you can use Export.lua to send out a udp message to DEDWriter with the value of the A10 bullets remaining, this can be extended to other types of info from DCS). We are not limited to DCS either, you could use SimConnect to export data from MSFS - The end result here would be 1. DED Writter (Program that listens for data to draw on the DED and sends USB write commands via HIDAPI) and 2. Some program (either DCS export lua or SimConnect for MSFS) to export data via UDP to DED Writer

@nick_thain Welcome to the party! Glad you are enjoying the add-on and thank you for the kind words! If your offer still stands, the F-4 would be awesome to try as it nearing release and will be the most detailed module to date. And let us know if you have any missing features you'd like added in return for a module you fly! Happy to adjust/fix any features

As you found out, the `dcs_event_bind_config.js` works for lights, not the LCD/matrix display on the f16 ded/f18 ufc made by WinWIng. "What controls the DeD displays" 1. SimApp Pro starts up and runs in the background, it detects your F16 ICP/DED 2. You start DCS, it has an export.lua script (wwtExport.lua) that runs when a mission starts 3. wwtExport.lua sends your aircraft type to SimApp Pro and says "Hey, SimApp Pro, im ready to start sending you game data. Here is the light value for gear handle, weapon count remaining, and the DeD/UFC values, etc" and sends that every few milliseconds 4. SimApp Pro reads these messages from wwtExport.lua (DCS Game state) and updates the appropriate device. You have a few options to get a working DeD with the F16 mod or any aircraft are the following: Out of the options listed, I am a fan of Option 3 the most. It would be open-source, eliminate the need for SimApp Pro to power displays, and be totally customizable. Not saying I have the time to make this, but if someone does that would be amazing and I bet the community would enjoy a proper stand-alone, open source, tool to power their displays. 1. Have WinWIng update SimApp Pro to support natively. This is hard because then WinWing is responsible for supporting 3rd party mods, deciding what to show on the DED when flying the A10 or AH64. They have hinted at this being possible in 2024, but unsure what level of support will look like Pros: Super easy to use, all users would benifit Cons: WinWIng now must decide what is shown on the DED for all aircraft, and people may want variations. WinWIng could allow customization, but take a look at the F16/F15EX vibration customization, it leaves alot to be desired. 2. Have WinWing extend SimApp Pro API (the one wwtExport.lua sends data to) to be more generic and accept data which will populate LCD segmenet screens. I am a fan of this option since WinWing could add this as they have developed in-house how to write data to the LCD segments. Example: Send a UDP packet to port 16500 with {device: "DED", line1: "Master Arm: On", line2: "Nav mode selected", line3: "Your custom data populate from any game, xplane, msfs2020, dcs, etc for ANY aircraft"} Pros: Simple to use, allows 3rd party developers to create mods/addons for different sims and aircraft Cons: Limitations with LCD segements on what can be displays. IE: No letters in a number only lcd segement, etc. WinWing must define an API/documentation for 3rd party devs to use. 3. 3rd party dev develops Option 2. This can be done as showcased here where you can get data to appear on WinWing devices by using USB write calls (HIDAPI). I wrote a small example of how this could work, but this is only a proof-of-concept, it would take a lot more refining to get a polished product: https://forum.dcs.world/topic/318859-custom-data-shown-on-ufc/ Pros: Open Source, makes development for other games easier Cons: Time consuming 4: Hacky solution of what Universal UFC did for the F18 UFC, in the wwtExport.lua, mimic an F16, and send the expected DED payload to SimApp Pro. Now when we fly the A10, we can send custom DED data to SimApp Pro and we get the expected result on the DED. Link to WinWIng UFC Mod: https://forum.dcs.world/topic/319024-universal-ufc-works-with-all-modules-simple-install/ Pros: Quick, easier than the above options Cons: hacky, prone to breaking with updates to SimApp Pro

No errors present, this tells me data is being sent to the UFC. Can you try and manually turn on the brightness in SimApp Pro? There may be an issue where the backlight was set to 0%, thus nothing is showing. I attempted to add a fix for this so it was set to 100% by default, but it is worth checking SimApp Pro -> UFC -> brightness controls to make sure

@hinapilot I see you got the latest version (1.0.16), can you include a your Saved Games/DCS.openbeta/Logs/dcs.log file next time you load into the harrier and get now data? Are you doing a cold start, or a hot start. Thanks

@Wostg @cweiss1 I found the issue, a bad commit removed a very important line of code. I just updated it, V 1.0.16 should be working (not at PC to test) Let me know if that works, I can verify when I get home as well

@Wostg recently added an update, are you using the latest version (V1.0.15) from the github?

@Wostg I added your updated F15-E profile as the default in GitHub, thanks for the work! Version 1.0.15 Download Link Here is the release the includes the F15-E Profile + the above F16 ICP fix. To get the latest, be sure to check the https://github.com/llamaXc/winwing-ufc-addon/releases page to see current and old versions.

Happy new years everyone, I made a new version that excludes the F16. Reason, if you own the F16 ICP and fly the F16 it will not work if you have this mod installed. The updated version of UFC Patch Mod will be disabled when flying the F16 to prevent any problems so you can enjoy the F16 ICP without issue. This is not ideal, but until I have more time to dedicate to this project this will do for now. If anyone has ideas or wants to chat about this feel free to send a DM or comment below.