Wostg

Well y would be 2160 + 256 assuming the top of the buttons is cutting off that part of the monitor. X will be at the end of your other 3 monitors so somewhere around 2300 like mine. (assuming it starts at 0 or thereabouts) You'll see I've done lots of little changes to each to get them just right. Notably the tedac at the default of 752 was far too wide so I had to shrink it right down although it now looks fine in game. E: winwings default is TEDAC but whatever magic the patch in the linked thread does uses AH64_TEDAC instead. As opposed to RIGHT_MFCD etc

The changes ie tedac in the above are from the patch in this thread which may or may not be of help

You can start with the winwing monitors set up, then modify the wwtmonitor.lua file to match your setup (and save the file as a different name). Here's mine for the apache _ = function(p) return p; end; name = _('mlua1'); Description = 'MODIFIED FROM WINWING CONFIG' Viewports = { Center = { x = 0; y = 0; width = 3440; height = 1440; aspect = 2.388888888888889; } } UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center -- Both EUFDs on leftmost mfd AH64_PLT_EUFD = { x = 10; y = 1500; width = 740; height = 384; } AH64_CPG_EUFD = { x = 10; y = 1900; width = 740; height = 384; } -- ends LEFT_MFCD = { x = 776; y = 1696; width = 752; height = 762; } --formerly just TEDAC AH64_TEDAC = { x = 1615; --1544 y = 1706; --1696 width = 615; --740 height = 770; --760 } RIGHT_MFCD = { x = 2312; y = 1696; width = 752; height = 762; }

Stupid questions out of the way first - in the Helios Profile Editor you've got the DCS Monitor Setup tab configured how you want it, the DCS Additional Viewports tab is configured with the patches applied, the Monitor 1, 2, 3 etc tabs and the Interface status tab are all present and happy? If so try copying the Helios.lua from C:\Users\FLYDOC\Saved Games\DCS\Config\MonitorSetup to the main DCS World folder eg \DCS World\Config\MonitorSetup where all the stock monitor profiles should be stored.

There's this one definitely feeling something iffy on a 13900k

OP are you running a winwing ufc by any chance

Also edit the 'master backup' in the \SimAppPro\resources\app.asar.unpacked\Events\wwt folder and it will copy from there, so you won't have to make it read only. That should last at least until you next update SAP. (thanks Preston)

Will check it out - have edited the backup file in \SimAppPro\resources\app.asar.unpacked\Events\wwt as well

That's tobii's official solution now too That said, anyone having new issues about little bumps, I think caused by blinking? I mostly set my T5 to headtracking only, but everytime I blink (I didn't know I blinked so much, or maybe I do it more just becasue it makes me think about it) the tracker does a little bump and its getting really annoying. Eyetracking is turned off, and I've set substantial deadzones for all axes to test but still seems to be happening.

Or just try setting the f18 screen and see if it shows. Did polychop enable exporting? I know that for the f15e razbam had to switch it on in an early patch. Also write to winwing and ask them to add that screen display, maybe they can build in their button guide for the kiowas weird horizontal screen

Quick sense check please - I feel like this is doing better for itself without the shader now?

Just saying thanks for this thread and everything in the first post!

Thanks heaps for that - here's the above updated in case anyone wants it (I may have done some other tidying at some point to round off the numbers and try and reduce pauses/stuttering, not sure if anyone else gets that) ufcPatchAH64.lua

Cautiously waiting on Virpil's expected announcement, because as above, my totally irrational perspective is I could be tempted to spend too much money on a new hotas gizmo, but making me buy a new compatible desk mount? That's asking too much.

maybe they'd make some more to help shift their new product

Are these FFB bases going to be so heavy that they'll bend typical Winwing/Virpil/monster+generic rail desk mounts? TBH the idea of having to sit it on a stand that I can tuck away after playing is actually pretty tempting

Woops I read the Chinook's packed feature list in the newsletter as 'ED' instead of 'DCS' for some reason 'Unmatched helicopter flight dynamics that only DCS can provide.'

sick burn from ED in the patch notes lol, don't take that lying down polychop

... I assumed I had just forgotten how to set the pvi-800 etc correctly. I'll need to go over it properly but encouraging to know its not just me I guess

I took the buttons off one of them to use as a full rectangular map on the KA50 for a bit - I had thought that just editing the height in that lua worked - although simappro will try and revert it if you open it up I guess.

Are you telling me you don't do the five finger checks to the crew chief and programme in your take off speeds? Are you telling me I did this 75 minute tutorial for nothing???

I have the non-twisty rotor base with the ka50 grip, and it occassionally drops power or goes a bit odd until I pull the plug behind it in and out. I have both plugs (it is the one with the red extra usb right) in a powered hub, and have spent a long time making sure there's no twists or squeezes in the cables. So guessing its either a power supply thing or a design issue, but who knows. Assuming red is power supply I might try extending the black cable into the back of the pc directly and see if that solves whatever conflict may be happeneing.

foam tape or plumbers rubber tape - the stuff you have to scrape off the surface once it settles

One thing I think the F16 did best that I wish others copied, is have the full-blown training mission with the (sometimes too drawn-out) voiceovers, but then also replicates the same scenario as a mission, so you can skip the 5 minutes setup if you know more or less what to do and just want to practice your VFR landing or whatever

Hi just to add that I think the AI HUD is doing similar things as the ODU, was also running DLSS. Cheers!