Universal UFC| Works with all modules | Simple Install

[Wostg]

4 minutes ago, Lekaa said:

strange that this is the case, because in the hornet, the  cords (Numbers) can be shown there.

But you have done wonderful job

Numbers yes, letters no. Cheers

[prestonflying]

Love seeing the new work for the AH64, I do not have it personally, so if others test it out and like it I will include in the main project so others can easily use! Thanks for everyones work and contributions, glad to see this being used and expanded!

Re triangle/ww update: @Lekaa SimApp Pro would be responsible for drawing the triangle on the UFC USB device, so AFAIK no change to the wwt export is needed. That said, I will do a check to see if anything new has been added recently that should be in the wwtExport.lua file that is included in this project

 

Edited May 30, 2023 by prestonflying

[Jarmak]

I keep having an issue where this works the first time I copy the wwt folder and boot dcs, but then never again afterwards.

 

Looking at the log it shows the script start up (in my case the harrier) and then shortly thereafter says "export stopped" for no discernable reason.

Any ideas what could cause that?

[Wostg]

Try the 'more permanent install' instructions and copy to Program Files/appdata as per llamaXc/winwing-ufc-addon: Allows custom data to be exported to the Winwing F18 UFC. (github.com) if you haven't already

[prestonflying]

2 hours ago, Jarmak said:

I keep having an issue where this works the first time I copy the wwt folder and boot dcs, but then never again afterwards.

 

Looking at the log it shows the script start up (in my case the harrier) and then shortly thereafter says "export stopped" for no discernable reason.

Any ideas what could cause that?

Wostg suggestion is a good start, SimApp Pro will override the lua files causing the add-on to not work which is most likely what is happening.

Can you DM or upload the associated dcs.log file next time this happens?

[Jarmak]

I'll try the more permanent install option. I thought setting the wwt folder to read-only would prevent it from getting overwritten by simapppro

[Lekaa]

Im having issues with the sync of lights with this, anyone having this issue? lights don't sync, they do sync if using default winwing WWT folder

[prestonflying]

1 hour ago, Lekaa said:

Im having issues with the sync of lights with this, anyone having this issue? lights don't sync, they do sync if using default winwing WWT folder

Which module are you using? 

[Lekaa]

28 minutes ago, prestonflying said:

Which module are you using? 

I just noticed that the hornet light sync works, but all other modules, like the A-10, Harrier, they don't work when using this custom WWT folder.

[Wostg]

You mean the brightness? Yeah that's locked in place

(there's a weird thing where the C101 Aviojet's flight pitch controls that brightness, like it literally goes lighter or darker if you fly up or down - maybe that'll solve the problem, sadly there aren't many resources for this jet to crib from) 

[Lekaa]

1 minute ago, Wostg said:

You mean the brightness? Yeah that's locked in place

(there's a weird thing where the C101 Aviojet's flight pitch controls that brightness, like it literally goes lighter or darker if you fly up or down - maybe that'll solve the problem, sadly there aren't many resources for this jet to crib from) 

i'm talking about the light sync for the MFD buttons and the UFC/Combat panel light which i have them syncing with dcs, they don't work with anything but the F18

[prestonflying]

15 minutes ago, Lekaa said:

I just noticed that the hornet light sync works, but all other modules, like the A-10, Harrier, they don't work when using this custom WWT folder.

Ah, that is because for this mod/add-on to work, the export script tells SimApp Pro the user is flying an F18 (so the UFC can display data). Without this add-on, SimApp Pro can handle the lighting states for other aircraft, but for the UFC add on to work, we are limited to spoofing the current aircraft as an F18. See code here

Otherwise, the ufc data would not appear. The proper fix would be for each module in this ufc add-on, to also extract the backlight values and send to SimApp Pro (I would have to test this to get it working).

In addition, you could also in SimApp Pro change the backlight settings to be bound to an axis so it would work regardless of your aircraft.

Edited May 31, 2023 by prestonflying

[Lekaa]

12 minutes ago, prestonflying said:

Ah, that is because for this mod/add-on to work, the export script tells SimApp Pro the user is flying an F18 (so the UFC can display data). Without this add-on, SimApp Pro can handle the lighting states for other aircraft, but for the UFC add on to work, we are limited to spoofing the current aircraft as an F18. See code here

Otherwise, the ufc data would not appear. The proper fix would be for each module in this ufc add-on, to also extract the backlight values and send to SimApp Pro (I would have to test this to get it working).

In addition, you could also in SimApp Pro change the backlight settings to be bound to an axis so it would work regardless of your aircraft.

 

makes sense, thank you for explaining that

[Wostg]

@ANDR0ID Dld you get anywhere with FC3, static or otherwise? I've been playing with the A10A (and hoping my attention shifts before I start looking at the C2 in the next sale) and it would be great on the ufc.

[ANDR0ID]

11 hours ago, Wostg said:

@ANDR0ID Dld you get anywhere with FC3, static or otherwise? I've been playing with the A10A (and hoping my attention shifts before I start looking at the C2 in the next sale) and it would be great on the ufc.

I have basic profiles built for all FC3 aircraft, but the last time I worked on it they would not load on the UFC, even just static data.... jump into a full fidelity aircraft and everything works. That issue is why I haven't release them yet and I haven't had time to revisit the issue. 

[Wostg]

Cheers, same. I imagine it would need significant updates to P's main patch files beyond my ability to yell at chatgpt until things work lol

[ANDR0ID]

On 4/7/2023 at 7:04 AM, ggerman2862 said:

Would it be possible to do a profile for the CJS Super Hornet? Hopefully it wouldn't be too difficult, since it's exactly the same as the stock F/A-18C!

Thanks in advance!!
Greg

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. 

[Wostg]

I tidied up the F16 script I was playing with a month back. Like the Apache its fine to use but doesn't do any of the big and clever things I was thinking about yet - it draws a few things from the HUD and hopefully doesn't crash/reverts to gauges if the HUD can't display. It doesn't use the DED or have data entry like the Apache KU yet - from doing that and the skyhawk I've got a little better idea of how to do them without breaking it.

@prestonflying Merge if you like - like the apache there's nothing actually wrong with it (hopefully). Also I snuck in the fix for showing R before the radar alt in the ka50...

@ANDR0ID tried that seahawk your name was on briefly, seems neat  

 

Edited June 4, 2023 by Wostg
e: updated below

[ANDR0ID]

@Wostg Great work on the Apache profile, especially the KU page... much better than my original plan. 

I did take the liberty of editing your profile with some of the items I was working on, interested in what you and the community think. 

Changes: 

Updated altitude to be a constant 4 digit value, ie on the ground is "0000" (currently radar alt, but easy change to barometric) 

Updated heading to a constant 3 digit value + M for magnetic 

Added (total) Fuel in pounds 

Edited the speed conversion... the values originally used didn't seem to be on for meters/sec to knots? 

Added a status window for Master Arm/Safe which will also display Master Warning and Caution alerts 

Edited the Vertical Speed readout to display Feet per Minute to align with the AH-64 HUD

Added Chaff and Flare Counts to the main and KU pages. 

_____

Edit: I found a heading bug Shows negative values for 353-359 Magnetic, will correct in the next version. 

wwtapachev2.zip

Edited June 4, 2023 by ANDR0ID

[Wostg]

Awesome! Yeah my top level was very low-effort just to get the KU out there. Looking forward to giving this a spin

[Wostg]

Ok I removed the earlier F16 file because the fuel totaliser would work from an air start, but not from a hot runway start (???). I've used a clunkier method (it goes a but screwy sometimes but corrects itself, known issue that's highlighted in DCS BIOS etc) but it works.

The entire script doesn't appear to work from a cold and dark start. Tried to fix this but might be a higher level thing. Some modules do work from cold start, some do not and the difference is beyond me.

The attached has the updated Apache, and updated F16 together. 

wwtapachev2.zip

[MustangSally]

4 hours ago, Wostg said:

Ok I removed the earlier F16 file because the fuel totaliser would work from an air start, but not from a hot runway start (???). I've used a clunkier method (it goes a but screwy sometimes but corrects itself, known issue that's highlighted in DCS BIOS etc) but it works.

The entire script doesn't appear to work from a cold and dark start. Tried to fix this but might be a higher level thing. Some modules do work from cold start, some do not and the difference is beyond me.

The attached has the updated Apache, and updated F16 together. 

wwtapachev2.zip 30.8 kB · 2 downloads

Works well mate, both in cold and hot start as well as the training missions.

[prestonflying]

@Wostg I added your AH64 + F16 to the main repo! Great work

[Wostg]

Cheers  Here's some basic info for the A29b Super Tucano. Ok that's me done for a while lol

wwta29b.zip

[ANDR0ID]

I've built/submitted a "general" profile which should work for any full fidelity module or mod that doesn't have a separate profile. Currently built to display vertical speed (FPM), Altitude (Feet), Magnetic Heading, Fuel (%), and Airspeed (knots), as well as Flare/Chaff count. Fuel may be off depending on the module, but most I've tested seem to be able to show it as a %. 

I still plan to build more detailed profiles for modules/mods as time and access to them allows, but this should provide the basics for almost everything now. 

Note: FC3 planes are NOT supported... and there may be some other outliers I'm not aware of as I haven't tested this with every full fidelity module or mod.