Wostg

do you mean like https://store.steampowered.com/app/1844610/Reality_Mixer__Mixed_Reality_for_VR_headsets/E

All good now

Hi, I think something is up. I tried the latest files wit the f15e and apache and I couldn;t get either to work. I ended up rebooting, and replacing the files with wwt1013, and the recent F-15e lua and now both seem to be working ok. I didn't see anything obvious in the log - did simapppro update since you did the f16 thing?

DF should cover some of this - you can have an 'all monitors on, including MPDs' profile and a 'just the big monitor(s) with other switched off' profile and switch between them. I haven't figured out how to get it to autoload the preferred one on boot, but its easy enough to select. You can have it show taskbars on just the primary monitor, or all monitors. I can't see how to exclude from the MIPS. I haven't found out how to get it to do clever things like show the taskbar on a non-primary monitor only, or display vertically. You can get the mouse cursor to wrap around at the sides, and prevent it from snagging on awkward corners between different sized monitors, but I can't see how to block travel entirely.

This is not an endorsement as it causes its own issues from letting 3rd party software control UI things that in a sane world Windows would do natively but: DisplayFusion is currently on sale on Steam. It can: Save monitor layouts in custom profiles so when you reboot your pc and windows has thrown all your monitors to the winds it will put them straight back into exactly where simapppro expects them to be. Disable monitors so they give the appearance of being 'off' and out of your monitor layout create virtual monitors that might be good for sticking DCS Maps or the 4th F-15e panel or whatever in a discrete space As above, not an unqualified endorsement as it takes over Explorer and may do all sorts of unexpected or unwanted things that give you grief but the above are useful.

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)

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

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

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

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.

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.

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

Hope the above worked for you, but if you're talking about exported monitors, with the outer symbology being perfectly clear but the inner being too dark to use, the following might help: Check Floyd1212's post about setting up Uimasking using Reshade. Takes a bit of effort to set up but did the job for my harrier.

Yeah I meant that somehow I will ignore what is right in front of me and try to keep playing without dismissing the interface

hey I was having trouble with the harrier so I put in a load of probably superfluous checks but seems to go ok for m e in multirole positions now ufcPatchAV88.lua

Nothing useful to note except I can see myself leaving the map with the overlay left on and getting increasingly confused and angry about why nothing works.

Just saying hi after a couple months playing starfield and bg3. i dont know how to fly any more

Yeah - if you set the stopper at 75 the nozzle will hold at 0.7500 etc. e: That did the job, thank you!

Could I please get some advice / a link to something I can modify for showing a rounded value for the Harrier Nozzles. The existing value in the script (487) reflects 0.0000-0.9999 so I gather I need to add a new formula into the export script that rounds 487 into e.g. 0.9700 = 97 nozzle degrees, and provides a new id number for the streamdeck plugin. I can then either display that value raw or further tidy it in the display text box. Its that or add 9999 labels into the plugin. Any tips appreciated!

What was the fix with broken mark points - I thought point 0 was meant to be removed and wasn't consistent across all systems, but its still there?

That was exactly it, thank you. I wasn't sure how to extend only the front so have just deactivated the rear UFC in the lua for now, but if there's a smarter way to manage it I'd love to know.

Its neat that the UFCs export so simply, but when I tried this the characters on each line don't completely fade out when they change, just leaving a big led smudge. Any ideas on how to fix this?

Come to think of it the black 'between' buttons on the MFDs would be good for this as well

Huh, so you can export the F15e UFC as well (e.g. replace CENTER_MFCD with UFC in wwtMonitor.lua to see). Not gonna get a 4th WW screen but maybe one of those tiny raspberry pi screens or an old phone might do it..

Sorry - the export script is a lua file that draws from various files and references in the F15e's main DCS folder and converts them to a format that the streamdeck plugin can read. The pilot's UFC used to be device number 8, and for whatever reason this patch changed it to 9. Same with all the mfds for both cockpits. Those changes stopped everything working in a similar script (for an external UFC) and can confirm these new numbers work. I thought I'd just post an updated script for here, but looks like other things have changed as well. I hope its still helpful in some way.