Wostg

Yeah they sit in the same hub they always do (need a good labelling but) and until yesterday, DF's profile swapper (activate/deactivate 3x MIPs) was working fine. Pending further tests it seemed like OP might be onto something.

Thanks for noting this so clearly and for reporting to WW/DL. I thought something was off but had just put it down to usual complications. All I can tell you at this stage is a) i use DisplayFusion to keep monitor profiles of where everything is placed / deactivate the MIPs when not playing. As of yesterday it was having trouble activating and rearranging the monitors to where they should be b) loaded up the hornet on a default WW configuration and the middle display wasn't showing. Assumed a usb issue and packed up for the day.

Neat! Will have a play. e: doh blind good stuff with the torq

Legit got a little scared for that guy in his little cockpit, way above the clouds, just effortlessly connecting. Amazing stuff.

Awsome stuff next free minute I have I'll work on my breaks which seems like a good way to test if it's me or the stick

Could argument spoofing be included in say, av8b.lua - the argument for gear down in the Harrier could be converted into the gear down command and light in the pto2? Would mean more manual editing per module I guess.

Thanks - I think its a little better with the DCS 'special options' disabled but I'm still not clear I'm getting the range I (think I, as a poor noob F16 pilot) need. It's sitting on its own weight for now and has lifted up when I've wrenched it back. Feels like its got about 5mm-1cm of give fwd-&-back with the extension on. Tempted to take that off but its so perfect for helos I don't want to mess with it often.

For those using the F16 'force sensing' preset - are you finding it fine as-is or have you modified it? I use a vpc 10cm extension and am wondering if that's thrown it completely off, as I can barely pull up. This is bad. Am fine tuning within DCS but feels like it should be handied within the moza software - ie a firm tug should make the output hit the top edge of the rings? Appreciate any tips or presets, thanks.

You could explore the config files directly at: \DCS World\Config\MonitorSetup (take backups!) My 1Camera.lua shows the below. Maybe try editing it to width 3440 height 1440? _ = function(p) return p; end; name = _('1 Screen'); Description = 'One monitor configuration' Viewports = { Center = { x = 0; y = 0; width = screen.width; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect; } } GU_MAIN_VIEWPORT = Viewports.Center

Weird! And the Simappro settings are all green and showing the right settings>?

have you downloaded directly from https://www.synaptics.com/products/displaylink-graphics/downloads which may be more up to date than WW's installer

That's weird - but as well as changing the monitor option between one-monitor/ww, is the screen resolution set properly as well. Main monitor would show 1920x1080 (or whatever it is) WW's active (assuming underneath, in portrait 768x1080?) would increase that to 1920x2160. If it thinks its still at 2160 (or whatever) its trying to centre against that resolution

Who knows! Glad its working though Fair enough - I'm using the one linked above, which is pretty complete (via folders) but am going to start mixing and matching bits around shortly.

1) If you're using your own profile a) can I have it b) restore the old lua c) try disabling things that aren't the dcs-exportscript in exports.lua to find any conflicts. Especially try reverting everything to default - I've just noticed one app that requires even the --comments-- around the actual line to be just-as-they-put-it or it won't work. (???) 2) if you're using this profile https://www.digitalcombatsimulator.com/en/files/3331910/ you need to use the included lua file. I don't know if its missing anything from more up to date files, but it works

(not currently on sale, but handles montior woes)

Heading hold is on, and your pedals and cyclic are centred (or at least trimmed where you intended them to be) as shown in the controls indicator?

For a quick and dirty solution in dcs settings try some negative curve, which will put all the power into the first few degrees of movement.

It installed itself in the appdata because you literally instructed it to install in the appdata folder. It explicitly asks you whether you would like to keep it there every single time you update.

Glad its working, just use the numbers that SAP projects onto each monitor, have fun

I'd try and help but I'm having trouble following 1. Is the SAP list all green and confirmed? 2. Are all your screens in Windows Display (and Displaylink Manager I guess) set to extend (not to mirror)? 3. In DCS, is your monitor cfg set to WWTMonitor (or whatever it calls itself) 4. Is the resolution in DCS set to 3440x2464?

Dude remove what appears to be your name and phone numbet The screen numbers don't matter as long as you know which matches which

It might be worth making the jump to helios which generally has any given jet able to be configured, and also give you an idea of how to manually edit monitors.cfg. I had guessed Winwing would be waiting for the phantom dscg screen to be exportable, but it looks like helios can do it now, and you can probably make a custom HSI, altimeter etc for other screens,

Fantastic stuff

I told @slughead I'd do a more detailed guide but haven't had the time to test things as thoroughly as I'd like, so just to say: The Pico 4 works with HTCC (and thus with slugmouse) using its native handtracking via OpenXR if you: Use the ALVR server app to stream from your pc, instead of Virtualdesktop or Pico Connect. The UI is less friendly but plays and configures for DCS just fine. Remember to not have the bitrate set to 150 in order to be playable. Use the ALXR pico client apk on your headset. It can be copied across folder to folder (or via adb tools), then installed and run as an untrusted app. Its barebones but sees your hands well enough. Its using OpenXR although SteamVR is the active runtime in SteamVR. Here's a screenshot of rough settings that work, having followed the HTCC guides. Interesting to see that a 4th option is apparently coming I think via native steamlink support? which might hopefully allow for handtracking, passthrough, whatever else in one place.

Imagine so - what I need to do at some point is label them all. But honestly I haven't seen any firmware updates in a long time