Wostg

I can't think of anything clever, but maybe whatever would be good to have 2/3 in one icon - all the bottom right HUD nav items in one grouping, RALT/BALT, stuff like that? When you were first looking into the script, did you find where all the gauges were hiding - usually they're in mainpanel_init.lua but that's empty and I want to find the fuel and engine monitor displays.

The push will be a separate button command. For dials you can only use the 'allow cyle to beginning' so it resets to the first value. If you want it to go backwards you need to make a separate dial with negative increments.

Yeah, there's typos in that section @Trigati, needs replacing with: -- RIGHT SIDE DESCENDING FROM THE TOP if UFC_Data.UFC_SC_12 ~= nil then ExportScript.Tools.SendData(82021,UFC_Data.UFC_SC_12) else ExportScript.Tools.SendData(82021," ") end if UFC_Data.UFC_SC_11 ~= nil then ExportScript.Tools.SendData(82022,UFC_Data.UFC_SC_11) else ExportScript.Tools.SendData(82022," ") end if UFC_Data.UFC_SC_10 ~= nil then ExportScript.Tools.SendData(82023,UFC_Data.UFC_SC_10) else ExportScript.Tools.SendData(82023," ") end if UFC_Data.UFC_SC_09 ~= nil then ExportScript.Tools.SendData(82024,UFC_Data.UFC_SC_09) else ExportScript.Tools.SendData(82024," ") end if UFC_Data.UFC_SC_08 ~= nil then ExportScript.Tools.SendData(82025,UFC_Data.UFC_SC_08) else ExportScript.Tools.SendData(82025," ") end -- THIS IS THE RADIO LINE 1 if UFC_Data.UFC_SC_07 ~= nil then ExportScript.Tools.SendData(82026,UFC_Data.UFC_SC_07) else ExportScript.Tools.SendData(82026," ") end

If I tell you can I ask you to squeeze the lot into a 5x3 profile? Its from line 868 of the 0.3 file, 82021 is the top line righthand e.g. 'STR 1A': if UFC_Data.UFC_SC_12 ~= nil then ExportScript.Tools.SendData(82021,UFC_Data.UFC_SC_12) else ExportScript.Tools.SendData(82021," ") end

Nice! Tested the UFC, all good except the right side in the script needs correcting for UFC_Data.UFC_SC_12-07

That's odd, just launched and working here as pasted here, will say if I can think of anything

My apologies, I forgot entirely that the new gazelle scripts and updated SD profile were kindly supplied here: SA342 Gazelle - Stream Deck Profile v1.2.1 (Updated 26-12-2022) (digitalcombatsimulator.com) Editing the above to match.

They're different formats. Ctyler started to incorporate dcs bios in a beta of his SD plugin but it's very limited. Dcs Flightpanels will let you do a complete sd menu using dcs bios but it's an entirely different system than what's been used in this thread.

Dcs bios just dropped a complete file, is there anything useful in https://github.com/DCSFlightpanels/dcs-bios/blob/master/Scripts/DCS-BIOS/lib/F-15E.lua? (I spent a minute trying to convince chatgpt to do a straight up conversion lol)

New Export Scripts and Gazelle SD profile at: SA342 Gazelle - Stream Deck Profile v1.2.1 (Updated 26-12-2022) (digitalcombatsimulator.com) Thanks to those looking into the strike eagle

DCS: F-15E by RAZBAM - Known Issues MFD exports not yet implemented

Awesome, sorry for the hassle!

Heya, I couldn't say if this is the reason, but I remembered I left a 15 second delay in the startup which was my first clumsy address to fix my cold start problem. Maybe that affected the steamdeck?? Here's an updated file with the delay removed and the other cold start fixes I tried in the above files. (goes in C:\Users\xxxxx\Saved Games\DCS.openbeta\Scripts\wwt\ufcPatch\aircraft) ufcPatchF16.lua

Fair enough, thank you for checking - I applied the same fix to the ka50 and also found something weird. At point of cold start the ufc is working, but just after autostart completion it switches off and the log returns this error: 'INFO COCKPITBASE (Main): couroutine killed'. No further detail given. Will do a full manual start and see if that changes anything. I worry my pc has some peculiarity but who knows what that might be - steam install? Gpu? Bloatware in the background?

Yep, errors logged, e.g.: [string "C:\Users\ \Saved Games\DCS\Scripts\wwt\ufcPatch\aircraft\ufcPatchJF17.lua"]:41: attempt to perform arithmetic on global 'Radio1Freq' (a nil value) [string "C:\Users\ \Saved Games\DCS\Scripts\wwt\ufcPatch\aircraft\ufcPatchAV88.lua"]:20: attempt to index local 'av88HarrierUFC' (a nil value) [string "C:\Users\ \Saved Games\DCS\Scripts\wwt\ufcPatch\aircraft\ufcPatchF16.lua"]:17: attempt to index local 'HUD' (a nil value) Chatgpt says: 'In summary, the common point among these errors is that there are variables or objects being accessed or manipulated without being properly defined or assigned a value. To resolve these issues, you should review the respective scripts (ufcPatchJF17.lua, ufcPatchAV88.lua, and ufcPatchF16.lua) and ensure that all required variables are defined and initialized correctly before they are used in any arithmetic operations or indexing.' Ran the Harrier, F16 and JF17 through it, and it appears to have solved the issue. I tried them with a hot and cold start - the UFCs now populate when they're supposed to, and no crashes in the log. I'll modify other mods as I get to them, but looks like the changes suggested might be Good Practice for our future tinkering? ufcPatchAV88.lua ufcPatchJF17.lua ufcPatchJF17.lua

That's a good idea, I've been copying and pasting from everything (good job with flares) when I start messign with a new one so good to have ready to go So I'm having trouble with cold and dark starts. If I start up with Preston's AV8b script it won't populate the UFC at the right time, same with my F16. If I replace those scripts to show "TEXT" or the universal ones like LOGETGROUNDALTITIDE() they will work from start. I've reinstalled simapppro, removed everything from export.lua that isn't simapppro, removed the hooks folder - not helping. Are you guys able to do a cold and dark start with custom UFCs? Do they populate at the right time? Any ideas what I can look at?

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

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

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

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

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

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)

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

Numbers yes, letters no. Cheers