Universal UFC| Works with all modules | Simple Install

[Heli Shed]

14 hours ago, 3ra_Luke said:

Working correctly here. After the two DCS updates, and the two SimappPro updates, I copied again the wwt folder in both places, following the instructions, and everything seems to work. 

Thanks - all sorted now

Edited April 14, 2024 by Heli Shed

[Lekaa]

I really wish that someone could do the A10IIC here, i tried but it's Chinese for me =( 

[Wostg]

Occassionally I've loaded up the A10 and tried to get into it but its the mod iterself which is beyond me. Like I kind of wish I'd bought it and literally nothing else and become an A10 master but have to accept its not going to happen. What is the exact layout you'd like in each box and I can try and throw something together

[Lekaa]

22 minutes ago, Wostg said:

Occassionally I've loaded up the A10 and tried to get into it but its the mod iterself which is beyond me. Like I kind of wish I'd bought it and literally nothing else and become an A10 master but have to accept its not going to happen. What is the exact layout you'd like in each box and I can try and throw something together

Appreciate it, ithe preset channels on com1 and com2 for the 2 radios, not the FM one. 

Scratchpad, and on the options maybe current selected mode. Nav, ccip,,ccrp, gun. 

Steerpoint.

Gun count(bullets)

Total fuel

Chaf/flare count

 

Edited April 18, 2024 by Lekaa

[Wostg]

cool will have a look later - If the scratchpad does letters etc I'll try and copy the apache

[Wostg]

@Lekaa@Lekaa quick question - are the selected modes represented by buttons or dials, or just something shown in the HUD or in an MFD?

Basically the UFC can show things you can already technically see - I. E. Any lights or buttons in the cockpit, even if your trackir is pointing somewhere else. But if 'CCIP MODE' is only otherwise seen on a particular MFD screen, it won't show if that screen isn't live. So if a dial shows 1,2,3,4, we can just say 'when dial is 3 show CCIP on the UFC' if that makes sense. 

 

[Lekaa]

4 minutes ago, Wostg said:

@Lekaa@Lekaa quick question - are the selected modes represented by buttons or dials, or just something shown in the HUD or in an MFD?

Basically the UFC can show things you can already technically see - I. E. Any lights or buttons in the cockpit, even if your trackir is pointing somewhere else. But if 'CCIP MODE' is only otherwise seen on a particular MFD screen, it won't show if that screen isn't live. So if a dial shows 1,2,3,4, we can just say 'when dial is 3 show CCIP on the UFC' if that makes sense. 

 

Oh I see. 

It's shown on the middle of the left mfd om the weapons page, it will also be shown on the hud when toggling between them. 

 

Do what you see fit in that case

[Wostg]

 

Hey, here's the first step - it reflects some of what's on the hud but its fairly fluid so not as persistent as you'd want.

I'll have a look at the A10 scratchpad soonish, and do the radios as well. Maybe have them rotate between them and ammo (like chaff/flares) in the UFC scratchpad if they're xxx.xxx format

hope that works!ufcPatchA10C2.lua

Edited April 19, 2024 by Wostg

[Lekaa]

6 hours ago, Wostg said:

 

Hey, here's the first step - it reflects some of what's on the hud but its fairly fluid so not as persistent as you'd want.

I'll have a look at the A10 scratchpad soonish, and do the radios as well. Maybe have them rotate between them and ammo (like chaff/flares) in the UFC scratchpad if they're xxx.xxx format

hope that works!ufcPatchA10C2.lua

 

You did a wonderful job, I'm verry happy that someone is doing the A10!
Now it'll be more enjoyable thanks to you  

a little feedback, If able, Let the current mode be there all the time, ie, not "mode" on the option but the current selected mode, ie CCIP , CCRIP, GUNS or NAV. Just like you have it now, it will show you the modes that you are currently selecting while toggling but let it stay with the current selected mode. Bad explanation but I hope you understand it.

Secondly Let the Mode be on the TOP UFC option 1. 

Third, when you can, The Scratchpad is just like the Apache, I think. It can take letters and numbers. shown in the HUD usually and on the CDU, computer to the right knee. 

and the radios, You have to select the "Preset" to have the preset shown as the picture. Main radio is in the HUD, Second radio on the orange box

Also, The Gun count is perfect, if you run out of places where you can place the gun count, you could skip the altitude.

Again, Thank you!!

Edited April 19, 2024 by Lekaa

[Wostg]

ufcPatchA10C2.lua

Try this - hit mode once to go into guns, ccip etc. They should be persistent but the ammo will only update when guns mode is visible, still its a good reference I guess.

Scratchpad seems to work, maybe!

[Lekaa]

11 hours ago, Wostg said:

ufcPatchA10C2.lua 5.99 kB · 3 downloads

Try this - hit mode once to go into guns, ccip etc. They should be persistent but the ammo will only update when guns mode is visible, still its a good reference I guess.

Scratchpad seems to work, maybe!

Thanks man!

I have put the radio channels on the Com1 and Com2, took only the hole night .. haha Feels amazing

I do have a question though, Where do I find those numbers?
Like in this example. getDCSListIndication(12)

Here is the my modified version with the radio channels working when selected "Preset" on both radios . 

Thank you!

 

ufcPatchA10C2.lua

[Wostg]

Nice work! Feels good eh, I told @prestonflying the same when I started to figure things out.

Finding the indication numbers was basically always a nightmare - sometimes you can work it out from the scripts within the mod's own files, and sometimes the key ones have been already figured out by the smart guys doing all the work for dcs-export and dcs-bios, alongside all their clear references to cockpit gauges, tumblers etc.

Preston gave me a script to log individual indicators but eventually I shouted at chatgpt until it made me the attached one which prints everything active on the readout devices into a file in the main dcs folder. From the A10 notes you can see everything as it appears in the mod and puzzle it out from there - eg. Indicator 8 is going to be one of the chaff/flare readouts, others will be the scratchpad, main and HMD huds etc. 

LOGGING SCRIPT ufcPatchF15e.lua 2404 a10 notes.txt

Edited April 20, 2024 by Wostg

[Lekaa]

On 4/20/2024 at 1:29 PM, Wostg said:

Nice work! Feels good eh, I told @prestonflying the same when I started to figure things out.

Finding the indication numbers was basically always a nightmare - sometimes you can work it out from the scripts within the mod's own files, and sometimes the key ones have been already figured out by the smart guys doing all the work for dcs-export and dcs-bios, alongside all their clear references to cockpit gauges, tumblers etc.

Preston gave me a script to log individual indicators but eventually I shouted at chatgpt until it made me the attached one which prints everything active on the readout devices into a file in the main dcs folder. From the A10 notes you can see everything as it appears in the mod and puzzle it out from there - eg. Indicator 8 is going to be one of the chaff/flare readouts, others will be the scratchpad, main and HMD huds etc. 

LOGGING SCRIPT ufcPatchF15e.lua 2.13 kB · 5 downloads 2404 a10 notes.txt 6.07 kB · 5 downloads

 

Thanks!

Another question, this is related to the F15E, I'm trying to put the total fuel instead %.

This is the actual line for the %.
local Fuelpercentage = "F" .. string.format("%03d", math.floor(LoGetEngineInfo().fuel_internal * 100))

can I just change this line or do I need to add another ufcUtils.getDCSListIndication ?

[Wostg]

F-15E Strike Eagle > Air Force > Fact Sheet Display (af.mil) says that max Fuel capacity: 35,550 pounds (three external tanks plus conformal fuel tanks) (mission editor will confirm)

You could try adding this:

local totalFuel = LoGetEngineInfo().fuel_internal * 35550
local fueltotal = string.format("%2dK%1d", math.floor(totalFuel / 1000), (totalFuel % 1000) // 100)

and change option5 to = fueltotal. That might work, and show hte maximum on the 4 digit display as 35K5, which is what I liked to do with baro height over 1k to show cleanly.

You could put scratchPadNumbers=totalfuel and it might show the full 5 digit figure tidy in that space.

"LoGet" commands are legacy code left over from the lockon games (as far as I understand,  thanks again Preston and Android) that lets you get the detail for some features without having to reflect the cockpit or displays. Hopefully that would work because otherwise you'll need to draw from the Fuel Quantity Indicators e.g.

DCS Export for the F15e shows that the TOTAL LBS tumblers are controlled by:

[370]    = "%.2f",    -- PILOT Fuel Totalizer Counter 100
[368]    = "%.2f",    -- PILOT Fuel Totalizer Counter 10K
[369]    = "%.2f",    -- PILOT Fuel Totalizer Counter 1K

and you can't forget the wiso if you ever use that cockpit:

[1376]    = "%.2f",    -- WSO Fuel Totalizer Counter 100
[1374]    = "%.2f",    -- WSO Fuel Totalizer Counter 10K
[1375]    = "%.2f",    -- WSO Fuel Totalizer Counter 1K

The last tumblers I rememeber looking at were the Viggen QFE pressure:

    local QFE_1_hPa = MainPanel:get_argument_value(115) * 10 -- ones
    local QFE_10_hPa = MainPanel:get_argument_value(116) * 100 -- tens
    local QFE_100_hPa = MainPanel:get_argument_value(117) * 1000 -- hundreds
    local QFE_1000_hPa = MainPanel:get_argument_value(118) * 10000 -- thousands
    local QFE_value = QFE_1_hPa + QFE_10_hPa + QFE_100_hPa + QFE_1000_hPa
    return math.floor(QFE_value + 0.5)

So you could modify that for the 3 pilot tumblers (local P_FUEL1K = MainPanel:get_argument_value(369) * 10000 -- thousands) and have something like 

local PILOT_FUEL_TOTALISER = P_FUEL10K+P_FUEL1K+P_FUEL100

and do the same with WISO_FUEL... etc   (the math.floor bit is to round it upwards, may not be needed)

Then you would have scratchPadNumbers=  PILOT_FUEL_TOTALISER or WISO_FUEL_TOTALISER or "", which should show the 'live' one depending on the seat you're in.

Hope that makes sense - module not installed at the moment to test  

[Lekaa]

22 minutes ago, Wostg said:

F-15E Strike Eagle > Air Force > Fact Sheet Display (af.mil) says that max Fuel capacity: 35,550 pounds (three external tanks plus conformal fuel tanks) (mission editor will confirm)

You could try adding this:

local totalFuel = LoGetEngineInfo().fuel_internal * 35550
local fueltotal = string.format("%2dK%1d", math.floor(totalFuel / 1000), (totalFuel % 1000) // 100)

and change option5 to = fueltotal. That might work, and show hte maximum on the 4 digit display as 35K5, which is what I liked to do with baro height over 1k to show cleanly.

You could put scratchPadNumbers=totalfuel and it might show the full 5 digit figure tidy in that space.

"LoGet" commands are legacy code left over from the lockon games (as far as I understand,  thanks again Preston and Android) that lets you get the detail for some features without having to reflect the cockpit or displays. Hopefully that would work because otherwise you'll need to draw from the Fuel Quantity Indicators e.g.

DCS Export for the F15e shows that the TOTAL LBS tumblers are controlled by:

[370]    = "%.2f",    -- PILOT Fuel Totalizer Counter 100
[368]    = "%.2f",    -- PILOT Fuel Totalizer Counter 10K
[369]    = "%.2f",    -- PILOT Fuel Totalizer Counter 1K

and you can't forget the wiso if you ever use that cockpit:

[1376]    = "%.2f",    -- WSO Fuel Totalizer Counter 100
[1374]    = "%.2f",    -- WSO Fuel Totalizer Counter 10K
[1375]    = "%.2f",    -- WSO Fuel Totalizer Counter 1K

The last tumblers I rememeber looking at were the Viggen QFE pressure:

    local QFE_1_hPa = MainPanel:get_argument_value(115) * 10 -- ones
    local QFE_10_hPa = MainPanel:get_argument_value(116) * 100 -- tens
    local QFE_100_hPa = MainPanel:get_argument_value(117) * 1000 -- hundreds
    local QFE_1000_hPa = MainPanel:get_argument_value(118) * 10000 -- thousands
    local QFE_value = QFE_1_hPa + QFE_10_hPa + QFE_100_hPa + QFE_1000_hPa
    return math.floor(QFE_value + 0.5)

So you could modify that for the 3 pilot tumblers (local P_FUEL1K = MainPanel:get_argument_value(369) * 10000 -- thousands) and have something like 

local PILOT_FUEL_TOTALISER = P_FUEL10K+P_FUEL1K+P_FUEL100

and do the same with WISO_FUEL... etc   (the math.floor bit is to round it upwards, may not be needed)

Then you would have scratchPadNumbers=  PILOT_FUEL_TOTALISER or WISO_FUEL_TOTALISER or "", which should show the 'live' one depending on the seat you're in.

Hope that makes sense - module not installed at the moment to test  

I've been working on the F15E the whole day and been fighting with ChatGPT a lot. I also learned a lot. 

I have made few improvements, it's already midnight, feel free to add the fuel if you have time. My idea was like yours, looking down and see 35.2 or something. or X9.2. 

I have made so the radio channels in the correct place like the hornet and much more. 



 

 

ufcPatchF15e.lua

Edited April 21, 2024 by Lekaa

[Lekaa]

By the way, i tried 

 

local totalFuel = LoGetEngineInfo().fuel_internal * 35550

local fueltotal = string.format("%2dK%1d", math.floor(totalFuel / 1000), (totalFuel % 1000) // 100)

With the option5 corrected, it didn't work. Didn't display anything on the whole thing. 

[Lekaa]

I also tried this :

local FuelTotalizer_10k = MainPanel:get_argument_value(368)
local FuelTotalizer_1k = MainPanel:get_argument_value(369)
local FuelTotalizer_100 = MainPanel:get_argument_value(370)
local FuelTotalizer_left_100 = MainPanel:get_argument_value(374)
local FuelTotalizer_left_1k = MainPanel:get_argument_value(373)
local FuelTotalizer_right_100 = MainPanel:get_argument_value(378)
local FuelTotalizer_right_1k = MainPanel:get_argument_value(377)
-- Calculate total fuel in pounds
local totalFuel = FuelTotalizer_10k * 10000 + FuelTotalizer_1k * 1000 + FuelTotalizer_100 * 100 +
                  FuelTotalizer_left_100 * 100 + FuelTotalizer_right_100 * 100 +
                  FuelTotalizer_left_1k * 1000 + FuelTotalizer_right_1k * 1000
-- Convert total fuel to a string and extract the first four characters
local totalFuelString = tostring(totalFuel)
-- Determine the number of digits in the total fuel
local numDigits = totalFuelString:len()
-- Extract the first four characters if the total fuel has more than four digits
local firstFourDigits = totalFuelString:sub(1, math.min(numDigits, 4))
-- Include first four digits of total fuel in payload
local fuelPercentage = firstFourDigits

It worked but i didn't see the the same fuel count that was in the jet, tried for hours but no avail. 

[Wostg]

That's fantastic  

I would uh, love to try this out and check the fuel but when I tried to install the f15 just now I got "The following (F15) DLCS are not authorised and will be disabled" 

After doing a full repair and frantically checking my account profile still confirms the purchase receipt I have no idea. Will have to try again tomorrow at this point and try not to assume its anything to do with current 'drama'

Well done again with your work

[Wostg]

Having a play while I figure out what matters, or a good pilot tells me - Main comm channel, Pitch angle, AOA, TACAN, IAS, BALT/RALT, Bearing, Fuel, Flares/Chaff

ufcPatchPHANTOM.lua ufcPatch.lua

Edited May 24, 2024 by Wostg

[prestonflying]

@Wostg Just added your F4 files to the latest https://github.com/llamaXc/winwing-ufc-addon/releases. V1.0.18. Thanks for the support!

[Chicki]

Dang.  I loaded this up in the x86 Program Files and my Viacom and my Jetseat stopped working.  Gosh knows what else.  What the heck.  Luckily, the Winwing software was calling for an update so afterward, all was restored.  Love to try this out.  Any ideas?  Thanks.

[Wostg]

try reordering where everything sits in C:\Users\Chicki\Saved Games\DCS\Scripts\Export.lua, commenting out anything you don't need
mine is currently something like

-- 1 Winwing 
efdfs
-- 2 DCS -exportscripts
fdsfd 
--3 dcs bios
-- ewrwerw (currently out of use)
--4 helios
defewrwe

[prestonflying]

@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')

 

[TrigaNZ]

Hi everyone.

I have to put the WWT folder into scripts every time I to use the AV8B (I put it in OB and DCS)

Also, my SimAppPro is not in Program Files (86) so I can't use the more permanent solution. Can't find it elsewhere.

Any ideas?

Cheers

[Wostg]

Right click on the start menu / shortcut and open file location (or if it brings up the shortcut, right click on that file)

First time I got annoyed with it I dragged the folder into my quick access links, then when I got sick of it looking messy I uninstalled SAP and reinstalled it into my main games folder to find more easily