prestonflying

I do not have the Super Hornet to test with, but can you attach a dcs.log when loading in with the Super Hornet and I can see if there is a fixable issue

Awesome job! Glad you are enjoying and nice skills

@TrigaNZ The issue you were facing is now solved. I was able to reproduce and get a fix for it. You can download the latest version here: https://github.com/llamaXc/winwing-ufc-addon/releases/tag/V1.0.21

@TrigaNZ Thanks for the DM and the log, I see the cause in those logs and will work to get a fix out shortly. I will reply here with the updated version when it is complete.

@thetford569 Awesome, once SI SimAPI supports UHF I will update the modules to begin emitting those.

@Hallsy Thank you! I set up the lua DCS export so new additions only require creating a new <AIRCRAFT_NAME.lua> file and filling out the required methods to extract data from the cockpit of a given module (since each module has unique ways to access this data). Re hornet weight: This can be hardcoded to a resonable number like 40000lbs, I just got carried way and tried to account for Fuel and stuff. SayIntentionsAI just needs a handful of fields to know where you are and what freq you are on. For UHF only aircraft, it is possible we could do something like subtract 200hz from a UHF to get a proper VHF channel inside the export script for a given module (hacky, but would work). SayIntentionsAI requires a VHF (110-150hz) radio channel to communicate with the airports. And these radio channels are set inside the cockpit. Another solution would be having the SayIntentions desktop application set the radio frequencies, the DCS-SI lua adapter would capture those radio frequencies and store the current COM1 value and use that instead of the value in the cockpit. This solution would mean the pilot would not be able to set the radios from the cockpits, and instead the export script would handle all radio communications. As for adding more modules, the biggest limitation is I do not own all modules (I have hornet, huey, tomact, viper, ch47). So adding more modules will require someone with those to implement them. But anyone with super basic DCS lua knowledge will be able to add these modules. I added an example template file if someone wants to try to add their own

Got a repo up with a DCS adapter, it is an export script you add to your Scripts/Export.lua. Let me know if you have any issues or feature ideas. https://github.com/papiplanes/sayintentions-dcs-adapter/tree/main

@Darcaem I am also looking into this and writing an adapter using the newly released SimAPI for SI as a DCS Export LUA Script. I agree with the "WHEEL RPM:0" question, seems like SimAPI just needs to know if we are moving on the ground or not, thus a simple function of speed + wheel radius should do. re- how do I read/change radio freqs? You can use the "Device" for the VHF radio in the lua export script to interact with the VHF Radio Device. Example for UH-1H local VHFRadio = GetDevice(20) local freq = VHFRadio:get_frequency() -- Setting frequency to 121.5 for VHF radio in DCS VHFRadio:set_frequency(121500000)

The cause is most likely inside the UFC code for this plugin, can you attach your /Saved Games/DCS/Logs/dcs.log file, it will include the reason for the failure and better help fix it

@Nightdare Looking at the default dcs_event_bind_config.js, there appears to be an entry for the F-14B, does the default profile landing gear light work? If so, I would use the existing one and tweak/add to it. Otherwise there might an issue within SimApp Pro { // f-14b默认没有完全对应的灯，但是可以自己自定 // f-14b does not have a completely corresponding light by default, but you can customize it yourself aircraft_name: ["F-14B","F-14A-135-GR"], isResetLight: true, recv: [ //F-14B { // 控制台灯光亮度 dcs_id:1801//目前只能按键调节，9个档位 // 另外还有仪表灯光亮度 dcs_id:1800 // 副驾驶的仪表灯光亮度 dcs_id:1802 // 副驾驶的控制台灯光亮度 dcs_id:1803 dcs_id: "0.1801", process: (dcs_id, dcsmag) => {// 临时作为反向处理 // Temporary as reverse processing dcsmag = 1 - dcsmag; return dcsmag; }, device_name: 0, led: ["Backlight","INST_PNL_Backlight"] }, { // 起落架指示灯 // Landing Gear Indicator // 目前暂时将起落架指示灯映射为起落架手柄灯 // Currently, the landing gear indicator is temporarily mapped to the landing gear handle light dcs_id: "0.15001", device_name: ["F18_TAKEOFF_PANEL", "TAKEOFF_PLANEL_2"], led: ["Landing_gear_lights"] } ] },

Cockpit/draw_args.lua looks to be the right spot. I see `Landing_Gear_Light=15001`, `WEAP_Master_Caution=9200`, etc. You would input this into the the winwing js file as dcs_id: "0.9200"

@Nightdare Do you have a light or switch in mind to activate the Winwing Panel Light? I can take a look in the F14 dir and explain how I got there

@pierre0000 The steps would look something like this Open the file, use NotePad++, VSCode, or other code editor: C:\Program Files (x86)\SimAppPro\resources\app.asar.unpacked\dcs_event_bind_config.js Add this into the list of exported objects, you will need to look for the DCS Module argument to power the light, I put a random one of `120`, which will not work. I do not own F4E so I can not look at the list of arguments, but they will be in this folder in some lua files: DCS_INSTALL_PATH/Mods/aircraft/F-4E-45MC module.exports = [ {*F18 Code block, etc}, {*Other module code blocks, etc}, { aircraft_name: ["F-4E-45MC"], isResetLight: true, recv: [ { dcs_id: "0.120", // You must find the DCS argument for the given data you want to drive this light. Look inside DCS_INSTALL_PATH/Mods/aircraft/F-4E-45MC/ and look through the lua files for the arguments you wish. Others on the forms might be able to help if you post device_name: ["F18_TAKEOFF_PANEL"], led: ["Landing_gear_lights"] } ] } ];

@colsona Here is the latest version of the UFC Mod that includes the Torque for the UH-1H in slot 4! (Note: We are limited to 4 characters, and the gauge for torque is in PSI from 0-100, so I put the readout in the following format: `55%` for 55 PSI, `22%` for 22 PSI, etc). This version also includes light control for the UH-1H Starter Gen Switch On => APU Light Super Taurus Throttle Skids On Ground => Landing Gear Light On PTO Master Arm Switch On => AG Light PCR On @Wostg@ANDR0ID For my fellow developers on this project, I added a light framework (just like the UFC payload methods to generate data, there is one for lights now). The UH-1H is setup with an example of controlling lights, ya'll will get the hang quickly. Feel free to add to other modules and make a pull request on Github

I did explore a test branch on Github adding a light payload as you described, here is the commit showing code to get lights working. I never added to the project but can re-visit if it would be helpful to others. The example shows setting the PTO landing gear light on and can be conditionally controlled via Huey argument values. It is exactly what you described, a mapping of module commands into SimApp Pro F18 Commands

Sounds like a fun things to add, I will get an update out today with it

Agreed, this mod works by sending data to SimApp pro as if you are flying the F18. When flying other modules, that data is being sent over and SimApp Pro does not know you are actually flying the apache. So this would break lights on other aircraft such as master arm light, apu light, station jettision light. Ill try to think of a way to avoid this. One fix would be if WinWing allowed the F18 UFC payload to be set even if you are not flying that module, but SimApp Pro requires the aircraft type to be F18 in order to render data on the UFC for now.

Nice PR, merged and updated links to newest version (1.0.19)

Hello, a user in the Papi Planes discord hooked up the ICP with X-Plane to extract data and draw on the ICP while flying. Here is a screenshot of it. (Discord invite https://discord.gg/MaerngqfKS -> tmp-f16-ded channel is where we discuss this).

Hey, if you can load into a mission and attach your `dcs.log` file (Located under Saved Games/<DCS_FOLDER>/Logs/dcs.log) I can take a look to see if there is a possible error occuring. Also, SimAppPro can overwrite the modded lua files which will remove the functionality so this may be happening, you can manually check the filed under Saved Games/<DCS_FOLDER>/Scripts/wwt/wwtExport.lua, try following the steps again from the GitHub page

I am not working on any features for it, just showing a proof of concept. I posted onto Github with a start template of writing data to the DED if others want to take a go at it. The hard part was figuring out how to draw/write text on the screen which in the Github project I use the DLLs from SimApp pro to call the methods WinWIng wrote to interface with the F16 DED.

Just verified it is still working, if you are not seeing what you expect on your UFC, re-copy the downloaded files from the installation (https://github.com/llamaXc/winwing-ufc-addon/releases/download/V1.0.18/wwt.zip) and paste the contents into your Saved Games/DCS/Scripts/wwt folder. Then replace/overwrite the existing files. Once SimApp Pro updates, it will overwrite these files. So you just need to re-copy them in. Let me know if you have any issues!

Oh no, can you attach your `Saved Games/DCS/Logs/dcs.log` after you notice it not working? Ill take a look sometime this week and try to replicate it as well

Interesting edge case, I’ll take a look at it and test it out. I have an idea in mind what is causing this. I’ll report back here with an update

@Chicki The cause of this: The Lua Scripting environment in DCS shares variables if they are not declared/setup. When you add multiple lua files, it is possible there are conflicts. The known work around is to re-order the script entries in /C/User/Saved Games/DCS/Scripts/Export.lua and try until everything works. This is how mine is setup local wwtlfs=require('lfs') dofile(wwtlfs.writedir()..'Scripts/wwt/wwtExport.lua') pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\scripts\DCS-SimpleRadioStandalone.lua]]); end,nil) local telemffblfs=require('lfs');dofile(telemffblfs.writedir()..'Scripts/TelemFFB.lua') local ButtKickerLfs=require('lfs');dofile(ButtKickerLfs.writedir()..'Scripts/ButtKicker_Export.lua')