Universal UFC| Works with all modules | Simple Install

[cweiss1]

Hey! I am not getting any visuals when using the the f15e is there any bugs or anything?

[prestonflying]

1 hour ago, cweiss1 said:

Hey! I am not getting any visuals when using the the f15e is there any bugs or anything?

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

[cweiss1]

8 hours ago, prestonflying said:

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

Yes I am, I have re-installed twice. I had it working for one flight and it stopped after that 

[Wostg]

Hi, I think something is up. I tried the latest files wit the f15e and apache and I couldn;t get either to work.

I ended up rebooting, and replacing the files with wwt1013, and the recent F-15e lua and now both seem to be working ok.

I didn't see anything obvious in the log - did simapppro update since you did the f16 thing?

[prestonflying]

@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]

All good now

[RogueSqdn]

@Wostg any way to get channel numbers in the comm windows without the asterisk?  That causes them not to work. 

[Wostg]

Oh right I think that was why I put them in option1 in the first place so you could show the asterisks. I know one of the scripts has a bit to remove any instance of a special character so I'll have a play with that over hte next couple days 

[Wostg]

try:

-- To go with all the other local ='s to remove asterisks from strings
local com1Raw = UFCL06NoSpace
local com2Raw = UFCR07NoSpace

local function removeAsterisks(str)
    return string.gsub(str, "%*", "")
end

-- Replace com1 and com2 with:
com1 = removeAsterisks(com1Raw)
com2 = removeAsterisks(com2Raw)

Edited January 8, 2024 by Wostg

[Wostg]

Here's my updated KA50 that tidies it up a lot and uses more accurate numbers from whatever source seemed best. I took out the PVI display but put the range to target on the scratchpad next to the VVI, which felt like the PVI's best use there.

 

Edited January 13, 2024 by Wostg
new version below with cold start protections

[rrutko]

Since I have no clue on how to enable/code for this request maybe others could help. I would like one of the options for display for as many helicopters that can extract the VVI date to be able to display it. I know UH-1 does as do a few others. Looking for KA-50, MI-24, MI-8 (been awile since I checked that one.) Again stellar work to all that have contributed/created this.\

 

[Wostg]

Ka50 above has it under 'variometer' , displayed on the scratch pad. Most of that is to get rid of an annoying jiggle between 0 and - 1 when on the ground

[rrutko]

perfect now for the MI-24

 

[Kubi]

On 6/3/2023 at 7:14 PM, ANDR0ID said:

I started to work on this, but it appears the CJS Super Hornets work just fine off the default F-18 profile... no new profile required. 

What do I do wrong. Mine don't work yet. All Buttons do but not the Displays.

[hinapilot]

Same for me on the Harrier, all buttons work but no data displayed on the physical UFC.

Downloaded and pasted the latest Github version, I haven't touched anything in SimAppPro though (no Key Binding or Virtual Device Mapping or anything of that sort)

 

Data is displaying just fine on regular modules like the F18 or the F16

Edited January 10, 2024 by hinapilot

[prestonflying]

@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

[hinapilot]

Sure let me get that for the Harrier! In the meantime I tested with the F15E and I got the attached log. It looked very similar with the export start line and a few frames later the export stop with the Harrier.

 

That was an Instant Action hot start for both cases.

2024-01-10 17:21:45.185 INFO    WWT (Main): Winwing export installed!
2024-01-10 17:21:45.185 INFO    TACVIEW.EXPORT.LUA (Main): Starting [C:\Users\benja\Saved Games\DCS.openbeta\Scripts/TacviewGameExport.lua]
2024-01-10 17:21:45.185 INFO    TACVIEW.EXPORT.LUA (Main): Loading C++ flight data recorder from [C:\Users\benja\Saved Games\DCS.openbeta\Mods\tech\Tacview\bin\]
2024-01-10 17:21:45.185 INFO    TACVIEW.EXPORT.LUA (Main): Tacview 1.9.2.200 C++ flight data recorder successfully loaded.
2024-01-10 17:21:45.185 INFO    WWT (Main): Export start!
2024-01-10 17:21:45.217 INFO    VISUALIZER (Main): Preload() radius: 150000.000000
2024-01-10 17:21:45.463 INFO    EDTERRAINGRAPHICS41 (Main): ITerrainGraphicsImpl4::forceLoading(): pos=(-182164, 4570.89, 650863), radius=150000
2024-01-10 17:21:45.582 INFO    EDTERRAINGRAPHICS41 (18948): surface5 clean up LOD 0: left 0  released 0
2024-01-10 17:21:45.582 INFO    EDTERRAINGRAPHICS41 (18948): surface5 clean up LOD 1: left 0  released 0
2024-01-10 17:21:45.582 INFO    EDTERRAINGRAPHICS41 (18948): surface5 clean up 0.042700 ms
2024-01-10 17:21:46.285 INFO    GRAPHICSVISTA (18948): Creating Resource "Unicode" of type 1
2024-01-10 17:21:46.296 INFO    EDTERRAINGRAPHICS41 (18948): instancer factors has been changed. Update lod buffers.
2024-01-10 17:21:46.296 INFO    EDTERRAINGRAPHICS41 (18948):      distanceFactor = 1.500000
2024-01-10 17:21:46.296 INFO    EDTERRAINGRAPHICS41 (18948):      instancerDetailsFactor = 0.666667
2024-01-10 17:21:46.296 INFO    EDTERRAINGRAPHICS41 (18948):      forestDistanceFactor = 1.000000
2024-01-10 17:21:46.296 INFO    EDTERRAINGRAPHICS41 (18948):      forestDetailsFactor = 0.666667
2024-01-10 17:21:51.624 INFO    VISUALIZER (Main): Preload() finished
2024-01-10 17:21:51.637 INFO    TACVIEW.DLL (Main): Tacview Flight Data Recorder 1.9.2.200 Loaded.
2024-01-10 17:21:51.637 INFO    TACVIEW.DLL (Main): Config={tacviewModuleEnabled=1, tacviewFlightDataRecordingEnabled=1, tacviewSinglePlayerFlights=2, tacviewMultiplayerFlightsAsClient=2, tacviewMultiplayerFlightsAsHost=2, tacviewBookmarkShortcut=0, tacviewAutoDiscardFlights=10, tacviewDebugMode=0, tacviewTerrainExport=0, tacviewPlaybackDelay=600, tacviewRealTimeTelemetryEnabled=1, tacviewRealTimeTelemetryPort=42674, tacviewRealTimeTelemetryPassword="", tacviewRemoteControlEnabled=0, tacviewRemoteControlPort=42675, tacviewRemoteControlPassword="", tacviewExportPath=""}
2024-01-10 17:21:51.637 INFO    TACVIEW.DLL (Main): Running in single player mode.
2024-01-10 17:21:51.637 INFO    TACVIEW.DLL (Main): Tacview is set to [Record All Available Data]
2024-01-10 17:21:51.637 INFO    TACVIEW.DLL (Main): Export path: [C:\Users\benja\Documents\Tacview\]
2024-01-10 17:21:52.121 INFO    Dispatcher (Main): precache units resources in slots
2024-01-10 17:21:52.121 INFO    LuaNET (Main): [MovingMap] broadcast started
2024-01-10 17:21:52.177 INFO    LUA (Main): Lua: States: 714, CPU load: 4.1%, Mem: 470.2 MB
2024-01-10 17:21:52.457 INFO    EDCORE (Main): Created game pool: h:2 n:5 l:2
2024-01-10 17:21:52.457 INFO    Dispatcher (Main): loadMission Done: Сontrol passed to the player
2024-01-10 17:21:55.360 INFO    WWT (Main): F-15ESE
2024-01-10 17:21:55.379 INFO    TACVIEW.DLL (Main): Recording flight data in [C:\Users\benja\Documents\Tacview\Tacview-20240110-172156-DCS-F-15E - Caucasus - Free Flight (DAY).zip.acmi]
2024-01-10 17:21:55.386 INFO    TACVIEW.DLL (Main): Export rights granted by the host: PlayerPlane=[1] PlayerSensors=[1] OtherObjects=[1]
2024-01-10 17:22:12.403 INFO    LUA (Main): Lua: States: 714, CPU load: 6.8%, Mem: 473.9 MB
2024-01-10 17:22:42.587 INFO    Dispatcher (Main): Stop
2024-01-10 17:22:42.696 INFO    LuaNET (Main): [MovingMap] broadcast stopped
2024-01-10 17:22:42.709 INFO    TACVIEW.DLL (Main): Closing current flight data recording...
2024-01-10 17:22:42.720 INFO    TACVIEW.DLL (Main): Successfully saved [C:\Users\benja\Documents\Tacview\Tacview-20240110-172156-DCS-F-15E - Caucasus - Free Flight (DAY).zip.acmi]
2024-01-10 17:22:42.720 INFO    TACVIEW.DLL (Main): End of flight data recorder.
2024-01-10 17:22:42.759 INFO    WWT (Main): Export stop!

dcs.log

Edited January 10, 2024 by hinapilot

[prestonflying]

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

[Wostg]

ufcPatchKA50.luaUpdated KA50 again, made sure it works from cold start in multiplayer.

[Wostg]

Been playing with helios instead of the WW monitor exporting so I could stick some gauges on unused mfds, works very well with the UFC.

[ANDR0ID]

On 1/17/2024 at 9:04 AM, Wostg said:

Been playing with helios instead of the WW monitor exporting so I could stick some gauges on unused mfds, works very well with the UFC.

I've been exclusively using Helios with the MFDs... takes a bit of work to set up, but the ability to use it across all airframes is too valuable not to use it in my opinion. 

[ak22]

On 2/7/2023 at 2:28 PM, prestonflying said:

Add custom data to your Winwing F18 UFC using this addon. Installation instructions below.

TLDR: Replace the Scripts/wwt folder with the downloaded Latest Release wwt folder.

• Base Profile: For any aircraft no listed here, includes altitude, airspeed, vs, flares, chaff, fuel (Readouts may vary on aircraft so keep an eye out)
• AH-64: KU Keyboard, chaff/flare, radar altitude, [Credit @Wostg @ANDR0ID]
• A29: Heading, fuel, aircraft mode, altitude [Credit @ANDR0ID @Wostg]
• C130 Herc Mod: Heading, fuel, altitude, chaff/flare [Credit @ANDR0ID]
• T45: Heading, fuel, altitude, radio freq, master arm, airspeed [Credit @ANDR0ID
• AV88 Harrier:  UFC + ODU
• A4 [Credit @Wostg]
  F-15E [Credit @Wostg]
• F-16 [General data fields shown on UFC] [Credit @Wostg]
• KA-50 2+3: Altitude, waypoints, chaff, flare, gun count,. [Credit @Wostg]
• MI-24/MI-8/UH-60/UH-1H: Radio coms, radar altimeter, chaff/flare, arm state, etc [Credit @ANDR0ID]
• JF17: Mimic JF17 UFC displays [Credit @ANDR0ID]
• TF51D: Radio selection, altitude, true heading [Credit @ANDR0ID]
• A10C2: Static text on the option displays. FUNC, HACK, LTR, MK, ALT, displays master caution light status
• Other modules: Any module can be supported, just needs to be added. Comment any modules you want to see supported or leave a "issue" on the Github Project.

Github Project + Source Code
This add-on does not effect other parts of SimApp Pro and preserves all functionality as you would expect.
It just enables other modules to show UFC data and is customizable.

Install Instructions

Install Tutorial Video: 

 

Install  Text Instruction

1. Download the Latest Release
2. Unzip the .zip file using 7-zip or some other compression program.
3. You will have a folder titled wwt.
4. Ensure SimApp Pro is running
   Note: SimApp Pro may overwrite Scripts/wwt/wwtExport.lua. If this happens, this add-on will need to be re-copied over. This may happen during a SimApp Pro update or clicking "Repair Lua" in SimApp Pro Settings. See Note on step 6 for a more permanent way to install.
5. Make a copy of your <USER>/Saved Games/<DCS>/Scripts/wwt folder incase you ever want to undo these changes, I keep mine on my desktop just in case.
6. Copy the wwt folder into <USER>/Saved Games/<DCS>/Scripts/ and replace the existing wwt folder
   Note: More permanent install (until SimApp Pro has a version update): Do step 5, then replace C:\Program Files (x86)\SimAppPro\resources\app.asar.unpacked\Events\wwt with the wwt folder from step 3 (the one you also copied in step 6 This makes it so every time SimApp Pro starts up, it will not overwrite your add-on). **Requires installation after SimApp Pro does an update.**
7. Launch DCS
8. Select a compatible module.
   AV88 Harrier: Supports ODU and UFC replica of DCS
   UH1 Huey: Supports Radar Altimeter on scratch pad
   A-10C2: Supports static text on the option displays. FUNC, HACK, LTR, MK, ALT
   MyCustomModuleExample: Shows an example of adding a new module
9. Fly DCS and verify UFC is working.
10. If something does not look right, take a look at <USER>/Saved Games/<DCS>/Logs/dcs.log and look for any errors from the WWT log output. You can also file an issue if you are having problems.

Have issues?
Leave a comment, i'll do my best to help you.

Want to remove this add-on?
In SimApp Pro go to Settings->Repair Lua. This will install a fresh version of the "wwtExport.lua" and this add-on will no longer be active.
To re-install, re-follow the steps in the Instructions section above.

Other modules:
Please leave feedback on what module and features you want to see added. Any data about the module can be shown on the UFC.
Gun count, airspeed, fuel remaining, VSI, engine percent, etc. These are all module specific and will have to be added, but the add-on is easily update-able to include new modules.

If something does not look right:
- SimApp Pro most likely overwrote the `Scripts/wwt` folder you added. Just re-copy over the addon `wwt` folder after launching SimApp Pro and you should be good to go. 
- Look at <USER>/Saved Games/<DCS>/Logs/dcs.log and look for any errors from the WWT log output. You can also file an issue if you are having problems.

Know a little bit of coding/lua?
You can edit the wwt/ufcPatch/ufcPatch.lua file and export your own data to a module of your choice! Refer to the "CustomModuleExample" for adding a new aircraft and adding new UFC fields. Explore other modules and get that data flowing! Want to pair on this, reach out and I help get you started.

How does this addon work?
SimApp Pro generates some export lua files to extract game state into SimApp Pro. SimApp Pro then interacts with the UFC.
This updated export lua adds code that extracts Harrier ODU/UFC data (and adds the possibility for future module support) and sends what SimApp Pro thinks is an F18 UFC Payload message. But this message bound for SimApp Pro contains custom data from a specific module. 

 

 

 

Any chance you own the F-16 ICP and can do something similar ? 

[nick_thain]

@prestonflying, @ANDR0ID, @Wostg,

Stumbled upon this tonight, outstanding effort gents, love your work!

Serious question; what’s the number 1 DCS module each of you would like that you’re missing, either to work on for this project or just to fly?

Let me know and I’ll gift each of you, this is amazing work and I want to say thanks in the best way I can.

Cheers!

Nick

[Lekaa]

I wish the A10 could get more useful data then the static data, like channel freq, guns bullets count, mode of weaponry, etc. 

[Wostg]

@nick_thain That's very nice of you! I'm mega impressed that through the others' work we're able to get so much more use out of this kit, certainly made me a lot happier with my ridiculous purchase and actually taught me a couple of things too. For my part I wouldn't ask for anything (I get real stupid at sales time) but if you really want to, throwing a few bucks at your local cancer charity is always a good idea

(not to guilt out the others, I'm sure they'd love an f4 and a kiowa lol) 

Edited February 22, 2024 by Wostg