Wostg

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

It would be cool to use the 7 digit scratchpad, and the long numbers can scroll right to left like a calculator, but it can't display letters so it would get awkward trying to enter grid coords. You could use the 2 extra letters to the left (fixed to AH here) as abbreviations for LL, ID for IDENT, MR for MANUAL RANGE? etc, but you couldn't type in A for auto, PBQ as above unless you made them show up somewhere else which is getting too weird

Ok you can pretty much put anything you want there now, either one letter or 2 numbers.

?

Ok here is my Apache script - I would have sent to @prestonflying but I will leave for him to decide if he wants to publish this at this stage. Please note the attached file is just his most recent release (that had the skyhawk), but the changes are a modified ufcPatch.lua and added ufcPatchAH64.lua if you prefer not to trust the whole package. The top level is extremely basic, just generic heading, TAS, RALT, BALT and VSI. When the KU is activated it should take over options1-5 and allow for text entry to be displayed as you go. When entering long coordinate info past 20 characters it should scroll back to let you see what you're typing. You can use the in-game keyboard, the numpad on the UFC, streamdeck or whatever else. You can display /, -, and * but not + or much else so good luck with equations. After 7 seconds of inactivity (i.e. after a lone cursor has disappeared) it should revert back to top level. Please note that it works for both pilot and CPG but if both have data up at the same time it will flick back and forth between the two which is annoying so tell your gunner to stop playing with the buttons. @android please feel free to use if helpful at all! wwtapache1.zip

I know @ANDR0ID@ANDR0ID is hard at work on it but I've been playing with the KU for the apache and just about got that presentable at least

No I'll figure it out from Chucks etc, but thank you for asking. That was just the next gripe that came to mind of things that either aren't covered, or appear to have changed since early release. (not harrier related) With Chucks, youtubes etc there's plenty to work with. What I'd really like is for advanced beginners guides that DON'T spend 30% of their time telling you how to decide between VR and TRACKIR, but instead talk about actually playing the game e.g. what's SEAD all about? (yes SEAD is in the core DCS manual)

Cheers, it's a little thing but confusing (see also: we haven't covered radios yet but set it for kobuleti and request takeoff. Also simple comms is disabled lol)