Wostg

@nick_thain That's very nice of you! I'm mega impressed that through the others' work we're able to get so much more use out of this kit, certainly made me a lot happier with my ridiculous purchase and actually taught me a couple of things too. For my part I wouldn't ask for anything (I get real stupid at sales time) but if you really want to, throwing a few bucks at your local cancer charity is always a good idea (not to guilt out the others, I'm sure they'd love an f4 and a kiowa lol)

Yeah that was a terrible response, absolute clownshoes. That said, a 20 minute enforced-wait is never going to happen but I have embraced fixtaking as a part of gameplay and it is 'neat'.

Thanks for this - I would have just said use the Displaylink app but in truth it often decides not to let me change a particular screen for whatever reason

Assuming you're working with the XL profile (DCS site down for me rn for some reason) - would you be willing to move things around to 5x3 pages? Doesn't have to be in any sort of order, I can tidy it up into something functional for myself and maybe even others. Really wish SD would give a storage area, or even allow XL size on the phone app. I've asked them a dozen times.

Been playing with helios instead of the WW monitor exporting so I could stick some gauges on unused mfds, works very well with the UFC.

Been thinking about this for the phantom, you'd need a monitorscfg. Lua that covered winwing and helios, or just disable them in simappro and use helios entirely. Let us know how you get on Edit: Ok the UFC works fine, and Helios does all of the monitors that you set up. Once that is selected in DCS there should be no conflicts.

I just thought they were going to redesign the UI so the new player might have any idea what to do when they load up e.g. there are tutorials for the su-25t that are actually pretty good

I now agree something is up with the latest version, I was getting huge system slowdowns eg youtubes would not play at all, mouse crawling across the screen until I killed SAP. Will send something through to them but yeah hard to send evidence aside from 'it bad'

I've been trying to rebuild an old BS3 profile but I don't think it's communicating at all, more than just the list populating. ...But, it does work on the BS2, how about that.

Fwiw they're pretty responsive with their ticket system. They'll probably ask for a video that you can take with your phone and upload to the chat window

ufcPatchKA50.luaUpdated KA50 again, made sure it works from cold start in multiplayer.

Look forward to checking this out Fondly remembering that brief bug in multithreading that caused the shkval to be full HD colour...

Ka50 above has it under 'variometer' , displayed on the scratch pad. Most of that is to get rid of an annoying jiggle between 0 and - 1 when on the ground

Here's my updated KA50 that tidies it up a lot and uses more accurate numbers from whatever source seemed best. I took out the PVI display but put the range to target on the scratchpad next to the VVI, which felt like the PVI's best use there.

try: -- To go with all the other local ='s to remove asterisks from strings local com1Raw = UFCL06NoSpace local com2Raw = UFCR07NoSpace local function removeAsterisks(str) return string.gsub(str, "%*", "") end -- Replace com1 and com2 with: com1 = removeAsterisks(com1Raw) com2 = removeAsterisks(com2Raw)

Oh right I think that was why I put them in option1 in the first place so you could show the asterisks. I know one of the scripts has a bit to remove any instance of a special character so I'll have a play with that over hte next couple days

Eagerly awaiting the new build If there are any bodgey fixes that don't involve building from source in the meantime I'd appreciate it!

I think so?

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