Wostg

I remember export for the f-15e had to be 'switched on' by the devs, it happened in the first or second patch about a week after release

Well done you guys For anyone super keen who's going to publish their ultimate streamdeck profiles, please have mind to a 6x3 version - even if it's just dumping everything in folders for others to sort out while you complete your XL masterpiece. Thanks! (looking fwd to trying the profile above)

I used the code I got in my confirmation email from Heatblur Simulations <noreply@sendowl.com> late last year

Wow, I want one!

MAXsenna above is entirely correct, but Helios does make it all easy, once you've figured it out. Set up all your Helios MFDs to manage your exported screens + IFEI etc - this is the video which helped me understand it: On Simappro's Game Peripheral Display / Set MFD display page, deselect the 3 FA18 MFDs monitors with the blank space. Ensure DCS is set to: null (or whatever resolution as appropriate) The exported viewports should be then working. Switch on any widgets created with the Control Center and you should be good to go, in-game

Hope I understand you correctly, but basically you need to stop using Simapppro for everything but the UFC and lighting: you can't use both simapppro and helios for screen exports at the same time, so dcs needs to be set to run the helios monitor config, screen size set to 3440x2464 (or whatever based on your setup) and not winwing simapppro is only running to control the led readuts on the ufc and lighting helios does the mip screen exports to their 3 monitors, and also your IFEI/RWR on your 4th, 5th etc on mine, the mip monitors are set to portrait 768x1024, each display is set to 768x768 and placed at the bottom of the helios view (the top section being covered by the buttons)

why do I need two dongles for my kb and m, one of them even calls itself unified

Got mine in the uk post, no evidence to suggest I'll get a "we paid your taxes" bill from FedEx in 3 months time

THIS IS A STUPID PERSON'S GUESS Each command in DCS is attached to a number, the one for button 1 on the ECM in the F-16C is is "460": (from DCS' own scripting) elements["PTR-ECM-BTN-1-460"] = default_2_position_tumb(_("ECM 1 Button"), devices.ECM_INTERFACE, ecm_commands.OneBtn, 460) Number "460" in the FA-18C is (according to popular external script DCS-BIOS): defineFloat("CONSOLE_INT_LT", 460, {0, 1}, "Internal Lights", "Console Lightning (light green)") So my untested guess is that there's leftover code from the FA-18 MIP panels and simapppro is receiving and acting on some kind of lights off command. If its not just you then definitely worth raising a ticket with WW, they can be fast about these things sometimes.

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

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

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

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!

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

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

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

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

You say you're running both DCS and beta - is that necessary now? If so do you have the paths set correctly in the Simapppro options - maybe its only updating the monitor set up for one install. Try removing the path for the version you don't want to use. [Ultimately I'd recommend forgoing SAP for monitors and moving to Helios. It will take a day to set up but once comfortable you can control the monitors better, and also stick the DED as on overlay on your main monitor for your sick button box, RWR etc]

Is winwing selected in the monitor settings

Has anyone tried Tobii's webcam solution (there was a beta for some? laptops on steam I think) as I guess that will be Beam's commercial rival

Try the demo for sure but afaik it uses opentrack - compare beam against the 'neuralnet' model available for free within opentrack first I reckon. Get all the curves right and it's pretty good!

Fair enough - OP try contacting Virpil, if its not a trade secret they're usually very responsive and friendly. (maybe they'd even sell those parts too, probably at a markup from their own suppliers tho)

Virpil will sell them to you individually for £2.50? each. If you have access to a 3d printer I think the design is online somewhere. There's at least one guy out there selling custom caps.

Edited above with updated Viggen to make better use of space: option1=altimeter option2=airspeed option3=Data Selector option4=Master Mode option5=shows Weapon Mode or Interval, if interval is adjusted scratchPadNumbers = shows Data Panel numbers, or QFE if adjusted scratchPadString1= e.g. L1 scratchPadString2= e.g. L1 com1= shows Fuel or F above 99% com2= always shows KMs to next target or D above 99km selectedWindows-- first 3 show afterburner stages

Here's the Viggen complete for now (could probably do radios in the same way as QFEs?) and the KA50 I updated a while back e: updated Viggen to show distance to target in Com2, still show the interval when it is adjusted ufcPatchKA50.lua ufcPatchViggen.lua