Leg2ion

Did you do a restart? FXO should be in the same folder as above. Not sure about the nvidia cache - never cleared them as far as I am aware.

@kmaultsby Check your PC power settings and make sure your power mode is set to performance. Anything other than that and I would get issues - so worth a quick look.

@hreich That is really good to hear - glad you sorted it!

Hi @Reggie Bigglesworth - bit (very!!) late but I did a RWR in my A10 Helios profile here if it helps any: Helios Profile - CDU, UFC, RWR and AHCP for A10C2

Hi @jonsky7 Oddly my 'front screen' often continues to display my taskbar until I click somewhere in the view. In addition - during 'first flight' quite often the task bar 'breaks through' into DCS World very very briefly. Really annoying and trying to hunt down the cause/solution.

Hi @Errorfinn. What is your setup, where are you exporting them to (physical monitor setup etc) and what does your monitor setup lua look like. Currently running extended view across 2 x 27" screens, helios with both MFDs (hot swappable with CPG position MFDs) and TEDAC on a touch screen and a further MFD export onto a smaller screen with no issues.

Hi @hreich. So whatever it was you did when transferring away from helios has somehow messed things. Can you retrace your steps. Either way - if it was working it isn't now - so need to try to fix it. If no longer using helios, like I said - for now discount the tablet - and just concentrate on getting 1 screen working correctly - so we can use that as a basis to expand things. Note though your monitor lua still has helios settings in it? Can you run helios editor, uninstall patches, close helios editor, move your saved game monitor setup and then just run DCS without running it through smartdesk? Understand it is frustrating but you aren't really confirming anything - just saying it isn't working. You seem to be using spacedesk - can you temporarily disable it or uninstall it for now and see how things go - as looking at the videos it starts full screen and then flicks over to a different resolution - so something is messing with things. Just seeing you are 'bringing DCS to front'. In addition - for now can you just align the screens (the two main screens and not use the tablet - so no software pulling the tablet into windows) horizontally in windows and see if that makes any difference - making sure you select the correct display resolution in Options and just switch to a single screen in monitors?

Really odd. What is your resolution set to in DCS Options? Unfortunately I cannot open your videos. You haven't got any screens set to display at anything other than 100%? For now try moving the monitor lua in the saved games (or renaming the MonitorSetup folder so it isn't recognised) into a folder where DCS cannot get to it - as DCS should default to displaying onto your main screen (I think) - just to discount any other stuff that may interfere with things? If it doesn't select 1 monitor under monitors in the options panel. Ideally we need to get the main screen displaying on one screen correctly - then look to expand out a step at a time to include the other monitors. Have you tried following the link I posted step by step?

Thanks @MadKreator! I guess if others have suffered the same issue will leave well alone. Sort of alleviated by adding this to my monitor setup: useAbsoluteFOV = false, FOV = 0.9642857142857143, which narrows my FOV slightly to 135o as opposed to 140o . Can 'make it better' by going further - best result is around 122o, but then I feel I'm sat so close to the MFDs they are unusable. The 135 is a good starting point - I find at 140 the CMWS box distorts stupidly when bridged across screens...

Hi @hreich. Not sure what display fusion is, nor space desk, and is there any possibility of not using them for now in case it is messing with the helios/dcs output? In terms of your monitor positioning in windows - is there any reason why you have them stacked on top of each other? With all that said and asked - with regards to the above - the Resolution you need to set in DCS Options needs to be 3840 x 2160 for either scenario - to take into account 2 screens wide and 2 screens high. Based on your 'windows' setup - DCS main will display as x in 0 to 1920, and y in 0 to 1080. The MFDs will be in display area x is 0 to 1920; y is 1080 to 2160. Can you just confirm when you hit identify you get 1 in upper left, 2 in lower left and 3 in upper right? I have attached 4 luas - though not quite sure of your current config? Test 1 is for Helios and Test2 you should be able to run without helios - both should display the MFCDs in the bottom screen and basically replicates what you sent, and then Test 3 and Test 4 - which is what you asked for. If you are getting screen squash - have you tried this (as posted in the link I attached in a post above - really worth a read as I think this will give you some easy instructions to follow also)? Fullscreen Squash If you wish, you can still run DCS in fullscreen mode. However, you may find that when you start DCS, it is all squashed onto your Main monitor. To get round this, simply left click anywhere on your secondary monitor and DCS will resize correctly. Pressing LeftALT+Enter is reported to also work. Test4.lua Test3.lua Test2.lua Test1.lua

Yes - but it doesn't align with your last graphic - as your lua indicates your MFDs are below your main screen with a y of 1085 - but your resolution in helios is showing a height of 1080? What I would do is add this line above 'UI mainview' - it will ensure the main view pre mission screen stays there: UI = { x = 0, y = 0, width = 1920, height = 1080 } Make sure your resolution is correct in DCS, (3840x1080) - if trying to display onto screen 3 as per the above, the lua you attached is pushing the screen down and out of sight and not to the right, so believe your MFDs should be positioned as below. LEFT_MFCD = { x = 1925, y = 5, width = 800, height = 800 } RIGHT_MFCD = { x = 3035, y = 5, width = 800, height = 800 }

Hi @hreich. Am assuming the screenshot is just on one screen and squashed across 1/2 the display? Can you attach your monitor setup lua? I'll try to assist...as initially it might be worth going back to basics. All the below assuming your monitor resolutions are 1920 x 1080? Step 1 - Create a 'MonitorSetup' folder in Saved Games/DCS/Config. Drop the attached into MonitorSetup. Step 2 - set your Resolution in DCS Options to 1920/1080. Let it restart, and then select 'hreich' from DCS Options, Monitors. Step 3 - DCS will restart again - and hopefully now your viewport in game will be just on that monitor - and monitor 2 and 3 will be ignored by DCS. Leave Helios out the equation for now. If that is correct, you can now move onto sorting out the MFDs and touchscreen. Looking at your various posts, which screens are you using, and what is where/doing what? As I said above - it doesn't matter physically where the screens are, what does matter for ease is how the computer sees them. If you are using all 3 screens in that config - you need to set the resolution in DCS/Options to 3840x2160 - as that will double the height so you can display onto screen 2 and double the width so you can display onto screen 3. If only using 1 and 3 - 3840x1080. You are basically creating a window frame that will cover all displays. (In this case mine is 7680 x 1080 - so 4 x 1920 wide) - my 3rd screen is touch for helios and the 4th holding my TM MFDs. Fairly certain you may want to leave Monitor Layout mode as 'From top left corner of desktop'. I'm certain we can get this sorted, just might take a bit of time with the back and forth. Basically the attached is the start, we can then look to add in the co-ordinates of the other viewports you want. hreich.lua

Hi @rob10 - I believe it is - yes, but if you're referring to the graphic in the link I posted it is misleading as it shows 2 to the left of 1 - but if you follow Jonskys tutorial all is well (I have just updated the link as there is a newer one updated in Nov'24). My physical setup is different to how the PC sees it - which is 1,2,3,4 all aligned - I have just set my viewports to display where I want them to based on the aligned screens - then where I place those screens doesn't matter. That said I have created an offset in my set up where my 'x' co-ordinate is to the left of the left hand edge of Screen 1 and is set at -960 - and my main viewport then displays across the entirety of screens 1 and 2. In essence once you embark on a voyage of 'tinkering', adding additional screens etc a 'MonitorSetup' folder in Saved Games/DCS/Config along with a custom monitor lua (and selected in Options/Monitors) is a must. I evolved from a single curved screen, to that plus a small 10.6 for TM MFD displays, then added a second curved screen then started dabbling in 'the dark arts' of helios so added a final 15.6 touch screen.

Apologies @Elf1606688794 - should have given some more info last night. I cannot find the lua you are referring to - do you have a location path. Just concerned if it is a core file and there is an update it may get overwritten. there is an easier way to do this. Create a 'MonitorSetup' folder in Saved Games/DCS/Config: I have attached a very basic 'Custom' lua based on a single 1920 x 1080 monitor. Drop that file in the monitor setup folder. When you then open DCS, go to Options, and Monitors, and you will see Custom in the drop down (it picks up the name contained in the file and not he name of the file). Select that custom file, and DCS will use the settings in that, with no fear of overwrite if there is an update. If you decide to start using multiple monitors/touchscreen/helios etc - this is the lua you look to modify for your own custom setup. Hope that explains things a bit better and helps - if you need any more assistance shout! Custom.lua

@hreich - check this post out by @jonsky7 - quite possibly the best (and easiest) set of instructions to follow: I am running 4 screens - 2 x 27" as my main viewport (screens 1 and 2), a small 10.6" for my TM MFDs (screen 4), and a 15" touchscreen for Helios (screen 3)- physically in this configuration: but as far as the computer thinks they are arranged like this: Might be worth looking at going back to basics - set up one monitor, then add the others back in - if you're having problems. Probably need to look at editing your monitor configuration file as well - I have never changed the file you refer to.

Not sure what imgui.ini is (or does) but I set my monitor/display positions by editing the monitor lua in saved games/dcs/config/monitor setup - then point DCS at it in the in game settings. If you always want it on monitor 1 you could try setting it to start on that screen? Assume you always want it on monitor 1 - does it matter if full screen or windowed?

Hi @PhantomBox. So - I run 2x27" screens (1920x1080) - which obviously - when aligned - give an issue of having a centreline bezel smack bang through the middle of a HUD - if flying fixed wing - which makes it a tad difficult to align aiming reticles etc when on guns. After A LOT of trial and error - have come up with a satisfactory solution that suits my set up - by offsetting my x axis into a non displayable area. So a 'normal' setup would be for the monitor settings would be something like this, which would centre the view across both screens: Viewports = { Center = { x = 0, y = 0, width = 3840, height = 1080, aspect = 3840/1080, dx = 0, dy = 0 } } To get around this I use this, so have basically added an additional 960 pixels to the entire width, then start my x value at -960 so my centreline view is offset to the left of centre by a quarter of a screen: Viewports = { Center = { x = -960, y = 0, width = 4800, height = 1080, aspect = 4800/1080, dx = 0, dy = 0 } } SO would this work for you (if your screens are same resolution as mine)? In a similar style to mine - but pushing things to the right, it would start the display at x=0,y=0, and then display across three screens - which you haven't got - so would end up with a left hand screen window view and the centre being displayed across your middle screen. It would still be trying to display the third screen, but as it is not there....: Viewports = { Center = { x = 0, y = 0, width = 5760, height = 1080, aspect = 5760/1080, dx = 0, dy = 0 } } In the AH - the IHADSS crosshair moves with the head/eye (in reality it is clipped to the pilots helmet) - and does take some getting use to, as in the real world obviously the pilot is simply looking at something so is 'eyesight/head stabilised', whereas in the simulated world it isn't as simple, as you are constantly glancing around/moving your head etc.

Hi @hreich Posted details of how I mounted my MFDs here: FYI I use both these and a touch screen for helios. Happy to assist where possible.

See you've (possibly) posted the same on Discord? TBH that may be easier to create yourself by downloading a full profile, then splitting it apart and copy/pasting the screens you want into a new profile? Lots of profiles here: Home · HeliosProfiles/Profiles Wiki · GitHub or Capt Zeen HELIOS PROFILE SITE

Hi All, Question I guess to all multi screen users. I am currently running 2 x 27" curved screens (1920 x 1080) - both screens 'merged' via the monitor lua to be one big main/centre display port - so in essence a 54" screen. This is coupled with head tracking. In my main screen definition I have created an offset so the hud isn't displayed down the centreline of both screens (and then obscured by the bezels) - so have defined the overall width as 4800 (and not 3940 as it would be for 2 screens) and then set my starting x co-ordinate as -960 - which positions my centreline with an offset to the left when viewed across both screens. When I pan my head/view, any buildings or wingmen seem to grow in length/distort when at about 45o to the right of centreline of the aircraft and again at around 90o. Is there any way to fix this, or any ideas what to adjust in the viewport/monitor settings that may reduce this a wee bit?

@Florence201 Cheers for the response. My ropey take off, basically I managed about a 20 foot transition to the left - though not sure at what altitude though was higher than the sangers at one point, did a 180 and set down again - badly. I will try a few more attempts (and try to recreate my premature landing!) as really want to get it to show the reported issues to give you something better to work with. Wingmen distance - that would make sense and possibly what I am seeing, but again will try to capture a bit more. Edit. So managed to replicate said ropey landing, wingman nearly took out the barricade as he put down as well, then once I was airborne he headed off in a different direction - but this time didn't keep going - and did turn and rejoin eventually. Track attached. M2_2.trk

Hi @Florence201. OK - so mixed results - got a track for the first one - which didn't show any real issues apart from during contact. Typing on a laptop whilst I can remember things so will upload the track later. First time around - flying along nicely together with wingman towards WP2 and 3 - got the radio message for Foghorn to tune the radio to the ground units. No wingman. Put mine into stable flight and went looking. Seemed my wingman had put himself into an orbit whilst tuning the radio, then was back on his merry way. I then did the same for a couple of laps of a field and he rejoined. We both then went into an orbit above the ground units, then headed onto WP4 and 5. Once we had contact - hit space, then directed wingman to engage. He took this as a direct order to seemingly head the other way - unless I am just being impatient and he was moving out to stand off out of harms way - then engage. Once I neutralised the targets (sounds impressive but forgive me - still learning and took an age) he came hotfooting back to rejoin. I then binned the mission as just wanted to try to capture the issue - which I don't think I did. Track attached. 2nd time - had a bit of a 'ropey' takeoff so we didn't depart together. Wingman spent ages catching up, and rejoined a minute or so before being instructed to tune the radios. Looked around - gone. F10'd (the map!) and this time found him heading off at about 30o towards what looked to be WP4 or 5. Once I reached the ground troops went into an orbit, and he hung a left and started heading back. Unfortunately my tail took a direct hit as I approached WP5 and game over. Unfortunately this is the one I backed out of too quick so didn't get a track. Next time will try to replicate the 2nd flight - though one thing and whether of any bearing is when he veered off course I was quite a way from the flight path line on the TSD. Edit - tried to replicate the issue and no joy -wingman played properly - apart from the veering off when Foggy gets a message to tune the radios, and when instructed to engage. M2.trk

Will do, hopefully time/work permitting will give it a go this week some time and provide some feedback.

Hi. Finally got around to running this campaign. Just flew M2 for the 1st time, and was heading for WP3 to meet up with the convoy. Happily cruising along at 1500 feet, investigating some external views and admiring a 2 ship in all its glory with the scenery/clouds etc. Every so often jumped back into the seat to ensure was still on track. Hopped back out - no wingman? F2'd and found him down in the weeds heading to 'somewhere'...no radio option to rejoin. Any clues? Side note anecdote...in M1, when receiving the message to check/use F10 to swap image and also check co-ords for the TIC, I hit F10 map - wondering why I was checking a map (to see my cab head off the screen at speed) to call radios etc. Complete mindfart!

Do you think this was the same time the pilot skins got broken? If I use a UK AAC livery, which had the AAC eagle and tactical flash on the arms - they are now overwritten with 101st AB patches?