Leg2ion

Thanks for the suggestion - I did think that, but Norton is pretty good at highlighting any issues as they occur - and then allows you to exclude them on the fly. I can't see why I would get the warning against some modules set in the Caucasus and not others?

As an update just ran a slow repair - no change - Missing module:Caucasus still present - though appears to be against v2.3 of Agile Spear. Log file post repair now also attached in post above.

As requested - PSA. I did a full un-install/re-install when the combined single version was released, and a repair around 6 weeks ago. No mods installed (apart from Helios) and never had any issues with Av (AFAIK). TBH I forgot Agile Spear was a purchased mission - just unsure why I have an A10C version in the A10CII folder, as since I did the re-install I haven't started any campaigns, and on some of those available why the Caucasus module is unavailable, and on others it doesn't highlight the same error. Its either there or not? (And definitely there as just repeating some of the training missions). dcs.log dcs after repair.log

Not sure if this is the correct place - but going with the 'Issues that don't seem to fit anywhere else.' Is there a definitive list of Campaigns that come as default - as I appear to have 5 versions of Agile Spear - 2 listed under the A10C and 3 listed under the A10CII? The A10C v2.3 version is duplicated in both A10C and A10CII. In addition - a number of campaigns - when hovered over - display 'Missing Module: Caucasus'. Have similar for a F18 campaign but 'Missing Module:PersianGulf'.

Unfortunately I didn't see any difference between high to ultimate, just moving from balanced/power saving to either of them fixed my issues. Like I said - long shot but worth a go - can but try it and see if it helps. Another 'trick' may be to exclude DCS from any antivirus you are running.

What are your PC power settings on? Had similar issues (albeit non-VR) which was fixed when I upped my power plan to either high or ultimate. Balanced or power saver didn't cut it. When I monitored my FPS in the balanced mode it would be stable then every 6 seconds or so would spike (downwards) causing a stutter. Long shot but might assist. So right click and select display settings, left hand choices select power and sleep. Select additional power settings, then high performance or ultimate from the choices given.

All sorted and redownloading as I type. Many thanks!

'New' module badge? Is there a difference between 1.0 and 2.0? Have the same issue - suddenly appeared after adding some custom squadrons after a fresh install (troubleshooting another display issue) so thought it was something I did...Stupidly, oh so stupidly, I uninstalled it in the vain hope all would be reset...

I did think that but the other smaller monitors (my mistake - 10.6 is actually an 11.6) are both 16.9 1920x1080. Just been back into the specs on Amazon etc and confirmed, and also aligns with the recommended resolution windows is detecting. The only anomaly is on screen 4 (the 11.6) where the scaling is set to 125% - but again this hasn't been an issue in the other modes. The only other difference I can see would be the refresh rates, but again why only in TAA, and why across the two screens that are set to main with the same rate? The fact the issue 'has got a bit better' since I moved the screens all in line wouldn't necessarily indicate a refresh rate issue, as why has the display issue now moved? The only other thing I can think of is that both 27" screens are gsync compatible (though not entirely sure what they are actually set to if I'm honest) - though again why only in TAA?

Ah - that makes sense - too simple! So 1 and 2 are my 2 x 27" curved screens, 3 is my 15.6 touch and 4 is my small 10.6 for Cougar MFDs - all running at 1920 x 1080. Report out of Helios is as per the below - so would indicate all are aligned: null

Hi @silverdevil Not sure what windows display properties you are after? Happy to post them but just need to know exactly which settings? That said - might be on to something (again - I think!). So - (either with DLAA, MSAA or off in settings) with my offset of -960 present in my DCS viewport monitor setup file, and my centre viewport display then set as 4800 so it extends across both 1920 screens, the -960 being lost to the left side but centring my view away from the midway point of both screens - all is OK. Once I set it to TAA I only get cockpit display in screen 1 and halfway across screen 2 - so it appears TAA will not except the width setting and it also appears to subtract the 960 from the far right of the screen - remaining black. Below photo shows the black area - but the training mission commentary is in the correct position. If I play with the x setting - so say halve it to -480 - the black area then halves - with only a quarter of the screen being black. If I add the additional negative figure back on to the screen width (so where I have 4800 to account for 2 x 1920 plus the 'negative' 960, add 960 on again to make it 5760) the double screen is then full of cockpit (although in this setup the screen then extends onto screen 3 in black). In either of the above scenarios - if I move my head so a map or similar moves across the black area I get superimposed ghosting. VID_20240225_122630.mp4 It appears TAA will only extend out to the right of the main screen and either not accept changes to y values outside a screen dimension (i.e. where I was pushing the main view down a screen width - and then the main view being entirely missing), nor x values deviating away from x=0 for my main viewpoint. If I set x = 0 and width at 3840 (and y equalling 0 and not -1080 to push it down as per my original initial setup) all works as advertised. Seeing as this all works OK in the other AA modes does this point at TAA implementation in DCS - or my setup? I am thinking TAA/DCS?

Hi @silverdevil Many thanks for following me on this - very much appreciated. I thought it best to delete all my other posts on this and try to bring it together into one. Yes - I checked the windows monitor settings, and they are exactly the same as shown, so: As I use Helios - I try to get the windows monitor positioning exactly as shown in Helios (makes it easy to figure out what goes where) as I use screen 3 for the both A10 and AH64 touch controls. I did note that when I had screen 3 to the left of screen 1, with screen 1 set as main I could set my main view to -960 to offset my central position across the 2 large screens, but helios didn't like the set up when trying to position touch displays - flagging it as outside the displayable area. (This wasn't a problem when it was above screen 1 and set as main). Hence I moved it to its new (normal/logical) position. I had also tried using TAA before I went anywhere near Helios in case it was that causing issues - but again still experienced the black partial screens. My monitors are now as the above, Helios mirrors this, and I am for the most part set back up with my various viewport exports. All still works ok under DLSS/DLAA and MSAA, just TAA sees things go weird - with no real reason I can see. Have also seen there appear to be two other users with same/similar issues to the partial screen blanking (though nothing else I could find on the major ghosting I am seeing):

Hi @thechaps16. Did you manage to get anywhere resolving this? I have similar, with either some odd ghosting (of instruments only) on a black screen with no cockpit/scenery being displayed at all, or not all the view being displayed as per your photo - though only using 2 screen set up for the main cockpit view. Posted here:

Apologies, as realised I have posted duplicates so have consolidated everything below and will delete my others. My issues started when MT was rolled out, along with the new video modes - so not sure if this is a MT issue, a graphics issue or a combination of both (or neither!?). I have (had) a bit of a weird set up - 4 screens - a small 15.6 touchscreen for Helios (that has to be the main screen as far as the PC is concerned otherwise it loses its touch ability), then under that 2 x 27" curved screens in line for the main cockpit view along with another 10.6 screen for 2 x MFD exports in the following config: My centre view point is around the 'Curv' text in screen 1 - which I achieve by offsetting the x viewpoint by -960. So my main viewpoint is x=-960, y=1080, width = 4800 (2x1920 plus the 960)/height = 1080. I 'think' I set it up this way as if I positioned Screen 3 to the far left, with the -960 x value I would get scenery floating around behind the helios instrument panel - which was very distracting. If I get rid of the negative value the centre viewpoint now has the screen break right down the centre. With the above if I select TAA once the mission is loaded the screens (1&2) blank and I get a very weird pitch black screen with instruments displays ghosting across the screen when I move my head: VID_20240220_182032.mp4 If I select single screen the TAA psychedelic effect disappears, so this could be a screen position issue possibly caused by my odd setup - though unsure as to why that would be? So, I have now reconfigured my monitors to this: All is good in DLSS, all working as advertised (apart from the scenery displaying behind my helios instruments due to my 'offset'). However, as soon as I select TAA, I now get the correct view in Screen2 - so half a cockpit (RH), but Screen 1 is blanked out and displays the map and instrumentation as in the video. So went the whole hog, and in light of the unified version being imminent (now out) - uninstalled my complete set up - stable and beta, archived all my presets/settings etc, and did a complete re-install of stable. Then re-arranged my screen set up, so now have the following - having moved my touchscreen into a more traditional position and now setting screen 1 as the main screen - so everything 'flows' to the right of screen 1 in terms of x positioning: Now if I select TAA I have a proper display in screen 1, but around a third of screen 2 (on the right) is blank. It seems whatever I do screen wise it causes issues with TAA, so is it a TAA issue? All works ok with DLAA/MSAA - so unsure where to go next, having re-installed the entire program, and having set my monitors to a more conventional set-up?

If so that explains why it doesn't work (I hope) - but then also get the same/similar on NIS (Nvidia Image Scaling) - where the only thing displayed is the instruments on a black screen as per my video.

Think I have nailed the above! WIth NIS I just get an image of the monocle display (in AH) that blooms to bright green on a black background. TAA with FSR I get no world - just dark screens with floating/ghosting instrumentation. So this just leaves me with MSAA or DLSS. Any ideas? VID_20231206_172655.mp4

This began at the last update to the OB version (for me anyway). I noticed I was having some glitches when starting a mission, and then noticed when I was launching into DCS OB the version was being shown as multi threading. This was launching via the shortcut on my desktop, which first checks with the updater, then on into DCS. Quick workaround and point the shortcut at the main non MT version. However, since the last stable patch this now happens in that version also? So, have the shortcuts been set now to default to the MT exe In addition having issues with the latest AA modes in MT. Is there a full and frank description of pros/cons of each, what works best with Nvidia or AMD etc. Away from the PC at the moment but when I flashed it up the other day got some weird hallucegenic ghosting of MFD readouts on a black screen - but cannot remember what settings were. If it happens again will take some photos to upload.

Why not upload it to 'User Files'?

Thanks @Raptor9 - thought I had broken my stable whilst messing around with viewports after the last update.

Apologies if there is already something on this - as found a few posts that seemed to conflict with each other? Neither the IDM, Preset (and corresponding WCA) switches on the EUFD panel are working in the stable version. All appear functioning in the Beta version. Is this still WIP for the stable?

Quick odd update - though unsure if of any relevance? My DCS World Open Beta shortcut on the desktop was pointed at "D:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS_updater.exe", and not "DCS.exe". Having read the post about checking whether you are in MT or 'normal' DCS (beta), I opened the game from the DCS MT OpenBeta shortcut and verified - yep - in the MT version - said so in the lower right corner. I then launched from the standard beta shortcut, and also ended up in the MT version? Then navigated to the open beta bin and I launched directly from the DCS.exe in the OpenBeta bin no flashing was experienced (though was a quick check) - but hopefully that may help others that might be getting thrown into the MT version and not set up for it? Hope the above makes sense?

Also getting this on odd occasions. Sat on the runway, controls go unresponsive/locked and the tarmac goes purple. Can swap between seats, change MPD screens etc but no reaction to any other inputs. Will try to get a track next time it repeats.

OK - understand the post to say videos are useless, but I cannot record a track as the attached happens while the mission is loading. It happens as the 'preload' counts to 1 on the load screen, pauses then flashes through multiple screens - I am guessing another 59 in time with the count to 60? Happens on beta/MT but not stable - so probably not the latest Nvidia drivers. In addition as this happens the graphics cards fans ramp up - so definitely a draw on the card which doesn't happen as the load screen moves through the preload sequence in stable. VID_20231026_172851.mp4

That sounds similar to what I am seeing, but it happens while the mission is loading so I cannot take a track. My left hand screen displays the loading splash screen, the RH screen is blinding white then flashes between multiple cockpit views quickly in succession, then all is normal. Happens in any map, any aircraft. In addition the MFD/helios screens start displaying data before the mission is flyable - which I haven't noticed before. Latest Beta, latest Nvidia drivers. Issue not present in Stable.

Running 2 x 27" curved screens, as the mission loads the RH screen displays a cockpit view, then blooms almost white, then darkens and flashes between multiple views. Once in mission all is OK. Updated to the latest nvidia drivers prior to the beta update and all is ok in the stable - just affecting the beta after yesterdays update.