Universal UFC| Works with all modules | Simple Install

[prestonflying]

On 11/13/2023 at 2:58 PM, Lekaa said:

Are any of you guys planing on getting the F16 ICP ? More screen area to extract to

We could do some damage with a large dot matrix screen! If I get it, I will look into updating the repo and figuring out how the F16 ICP works

[Sundevil]

Loving this! Thank you all. 

Question. Is anyone else not seeing displayed information in the T-45?
All the others seem to work for me but not the T-45.

 

Cheers.

 

[prestonflying]

On 11/26/2023 at 1:14 AM, Sundevil said:

Loving this! Thank you all. 

Question. Is anyone else not seeing displayed information in the T-45?
All the others seem to work for me but not the T-45.

 

Cheers.

 

Glad to hear!

I have not tried that module, can you load into a mission with the T45 and then attach a copy of your /Saved Games/DCS.openbeta/Logs/dcs.log file? It might help explain what is happening. 

[ANDR0ID]

I haven't run the T-45 in some time, but happy to take another look on my end... will update with my findings.  

[ANDR0ID]

I tested the T-45, and my profile is working... 

Admittedly I haven't updated SimApp Pro or from prestonflying's repository in some time, but I can reupload my T-45 profile if issues are still being had for others. 

[Wostg]

Sale time so have been messing around in the Viggen and its pretty neat; test file ufcPatchViggen.luaattached and ufcPatch.lua snippet here if anyone wants it.

local ufcPatchViggen = require("ufcPatch\\aircraft\\ufcPatchViggen")

    -- Viggen sends throttled data every 0.2 seconds
    elseif moduleName == "AJS37" then
        if ufcExportClock.canTransmitLatestPayload then
            return ufcPatchViggen.generateUFCData()
        end

Annoyingly, I'm getting similar issues to the Aviojet in that there's a conflict with the FA18's UFC brightness knob and flying around makes the UFC brightness dance all about the place. This time I've tied it to the Viggen's ILS (109) eg:

Viggen mainpanel_init.lua:

-- VerticalILS							= CreateGauge("parameter") -- FLI37 ILS
-- VerticalILS.arg_number				= 109
-- VerticalILS.input						= {-1 , 1}  --Degrees?
-- VerticalILS.output					= {1.0, -1.0} 
--Rollindex.controller				= controllers.base_gauge_Roll
-- VerticalILS.parameter_name			= "FDUADIILSV"

FA-18 clickabledata.lua:

elements["pnt_109"]		= default_axis_limited(_("UFC Brightness Control Knob"),				devices.UFC, UFC_commands.BrtDim,		109,	0.0, 0.1, false, false, {0,1})

I'm sure its that connection as eventually the ILS figure, when displayed on the scratchpad, settles itself down to 0.5000 and the UFC at a pleasing 50% brightness.

So @prestonflying to dump this all in your lap, how can we separate these two in the patch files? I can only imagine commenting out the Viggen ILS entirely or doing a global rename of the number which would probably cause all sorts of issues. Assuming the Aviojet's pitch itself is 109 (what file would even show that??) its probably not a universal solution. Merry Xmas 

 

[Wostg]

And to contribute something, I tried the T45 and it wasn't working, but saw that my current version of ufcPatch.lua was missing the following:

local ufcPatchT45 = require("ufcPatch\\aircraft\\ufcPatchT45")

Checked and its not in the 1.0.12 download either so guess it got lost somewhere along the way!

Stick that in and it will work.

[prestonflying]

7 hours ago, Wostg said:

Sale time so have been messing around in the Viggen and its pretty neat; test file ufcPatchViggen.luaattached and ufcPatch.lua snippet here if anyone wants it.

local ufcPatchViggen = require("ufcPatch\\aircraft\\ufcPatchViggen")

    -- Viggen sends throttled data every 0.2 seconds
    elseif moduleName == "AJS37" then
        if ufcExportClock.canTransmitLatestPayload then
            return ufcPatchViggen.generateUFCData()
        end

Annoyingly, I'm getting similar issues to the Aviojet in that there's a conflict with the FA18's UFC brightness knob and flying around makes the UFC brightness dance all about the place. This time I've tied it to the Viggen's ILS (109) eg:

Viggen mainpanel_init.lua:

-- VerticalILS							= CreateGauge("parameter") -- FLI37 ILS
-- VerticalILS.arg_number				= 109
-- VerticalILS.input						= {-1 , 1}  --Degrees?
-- VerticalILS.output					= {1.0, -1.0} 
--Rollindex.controller				= controllers.base_gauge_Roll
-- VerticalILS.parameter_name			= "FDUADIILSV"

FA-18 clickabledata.lua:

elements["pnt_109"]		= default_axis_limited(_("UFC Brightness Control Knob"),				devices.UFC, UFC_commands.BrtDim,		109,	0.0, 0.1, false, false, {0,1})

I'm sure its that connection as eventually the ILS figure, when displayed on the scratchpad, settles itself down to 0.5000 and the UFC at a pleasing 50% brightness.

So @prestonflying to dump this all in your lap, how can we separate these two in the patch files? I can only imagine commenting out the Viggen ILS entirely or doing a global rename of the number which would probably cause all sorts of issues. Assuming the Aviojet's pitch itself is 109 (what file would even show that??) its probably not a universal solution. Merry Xmas 

 

Ill take a poke at that and get the above issues added! Thanks for the work 

[prestonflying]

@Wostg @ANDR0ID Fix for T45 import and an attempt at UFC brightness (was not able to test without owning viggen).

Latest build: https://github.com/llamaXc/winwing-ufc-addon/releases/tag/V1.0.13
 

[prestonflying]

Found a tutorial on the Universal UFC!!!

 

[Wostg]

You're famous!

Also, pretty sure you fixed it - no sign of the UFC wavering with the Viggen. Couldn't find the C101 draft I was using, but the General config didn't have issues with pitch, so assume its fine as well.  Well done and thanks very much!

Will try and improve the Viggen a bit and forward another script. If anyone actually knows what they're doing in that module (or any others for that matter) and could say what would actually be useful on the UIFC, please let me know and I'll adapt accordingly.

 

[ANDR0ID]

Excited to try the new updates! 

[Wostg]

Ok here's my final Viggen before I get more convoluted

        option1=Atimeter (xxxM below 1000, xxKx over)
        option2=Airspeed KPH
        option3=Rotates distance to waypoint (6 seconds) Fuel percentage (2 seconds)
        option4=Selected waypoint, or weapon selected if in ANF master mode
        option5=Master Mode
        scratchPadNumbers=6 digit data panel readout
        scratchPadString1/2=Angle of Attack
        com1=Shows whether AFK or Thrust reverser is active
        com2=Shows if afterburner on at stages 1/2/3

 

ufcpatch:

local ufcPatchViggen = require("ufcPatch\\aircraft\\ufcPatchViggen")

    -- Viggen sends throttled data every 0.2 seconds
    elseif moduleName == "AJS37" then
        if ufcExportClock.canTransmitLatestPayload then
            return ufcPatchViggen.generateUFCData()
        end

ufcPatchViggen.lua

Edited December 10, 2023 by Wostg
Amended radio controller missiles to Sea/Ground/Air labels

[Lekaa]

The f15E, the scratchpad is not showing on the scratchpad screen anymore, is it intended?

[Wostg]

Apparently an update made some changes that affected things  - the UFC and WSO UFC used to be devices '8' and '16' but suddenly they're '9' and '18'. Have any major new systems been introduced they may have needed to rearrange stuff for? 

I updated very quickly and hte scratchpad is back at least - let me know what else is broken and if anything else would help

ufcPatchF15e.lua

[Lekaa]

35 minutes ago, Wostg said:

Apparently an update made some changes that affected things  - the UFC and WSO UFC used to be devices '8' and '16' but suddenly they're '9' and '18'. Have any major new systems been introduced they may have needed to rearrange stuff for? 

I updated very quickly and hte scratchpad is back at least - let me know what else is broken and if anything else would help

ufcPatchF15e.lua 9.07 kB · 0 downloads

Many thanks to you!
Yeah, this module is going to be updated alot. next update will have some stuff done to the IFF, so maybe they will change stuff with the UFC again.

[AstroEma]

Hello @prestonflying I have been using your wonderful program since it came out and loving it!  There is the possibility of the side effect of completely removing the backlight and annunciator light syncing capability through SimAppPro.  Is that a good assumption? If yes, is there anything that can be done to avoid this? 

[prestonflying]

12 hours ago, AstroEma said:

Hello @prestonflying I have been using your wonderful program since it came out and loving it!  There is the possibility of the side effect of completely removing the backlight and annunciator light syncing capability through SimAppPro.  Is that a good assumption? If yes, is there anything that can be done to avoid this? 

Hey AstroEma, we spoked on discord yesterday. Ill report back if I find anything, shocked I never noticed this, but I fly VR so I don't look at lighting. 

[RogueSqdn]

@Wostg

Just got the F-15E working.  Thanks for your work!

 

However, I'd much rather have the comm digits in the windows next to the comm knobs, and maybe the chaff/flare count in the first option window.  Looking at your LUA file, I'm not sure how to accomplish that.  Could you guide me in the right direction, please?

Thanks!

[Wostg]

Hey just on my phone so not exactly sure if this is right but if you change the following at the bottom:

Com1=UFCL06NoSpace,

Com2=UFCR07NoSpace, 

That will hopefully reflect the comms in those boxes. 

If you change one of the Options1-5 to SNARES, it will show either the chaff or flares, depending which is the lower and above 0, or 00 if both are out. Alternatively you could put

optionx=Flaredigits .. Chaffdigits, 

Which should show something like xxyy on the display with both current values. 

bombDisplay in option1 is me trying to be clever and have it switch from comms to bomb timers when relevant. You might want to try changing the four references to Comms around 'bombDisplay = COMMS' to SNARES instead and that may keep that working without changing the Options. 

bombDisplayre

bombDisplay

Flaredigits

Edited January 1, 2024 by Wostg
typo

[RogueSqdn]

@Wostg

I've managed to get chaff on line 1 and flare on line 2 by putting this in the body and changing all the 99 references to 999 (since chaff default is 120):

	local ChaffCount = "C" .. Chaffdigits
	local FlareCount = "F" .. Flaredigits

and this at the bottom:

 		option1= ChaffCount,
		option2= FlareCount,

 

 

I've tried what you listed for Com1 and Com2 but get no results.

 

EDIT:  Your suggestion works, idiot me didn't have commas after them.

ufcPatchF15e.lua

Edited January 1, 2024 by RogueSqdn

[Wostg]

Lol phew - I was going to fix my typo and say make sure they are L06 and R07 respectively.

If the snares give you any issues you could also do:

local ChaffCount = "C" .. LoGetSnares().chaff

local FlareCount = "F" .. LoGetSnares().flare

LoGets are the basic DCS references used by all modules so should always work (thanks Preston for teaching me all this stuff)

[RogueSqdn]

2 minutes ago, Wostg said:

Lol phew - I was going to fix my typo and say make sure they are L06 and R07 respectively.

If the snares give you any issues you could also do:

local ChaffCount = "C" .. LoGetSnares().chaff

local FlareCount = "F" .. LoGetSnares().flare

LoGets are the basic DCS references used by all modules so should always work (thanks Preston for teaching me all this stuff)

I had copied them from elsewhere in the file. 

 

    return ufcUtils.buildSimAppProUFCPayload({
 		option1= ChaffCount,
		option2= FlareCount,
        option3= Altitudes,
        option4= "B" .. HeadingString,
        option5= Fuelpercentage,
        scratchPadNumbers=scratchPadNumbers,
        scratchPadString1=scratchPadString1,
        scratchPadString2=scratchPadString2,
        com1=UFCL06NoSpace,
        com2=UFCR07NoSpace,
        selectedWindows={}
    })
end

 

No chaff/flare issues yet with what I posted.  Will keep in mind what you posted.

[prestonflying]

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.
 

[prestonflying]

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