Leg2ion

Ok - set up a mission out of another runway - no problems whatsoever. Then did the same out of Sochi - the MFD blanking re-occurred. Looking at the MFD there appears to be some type of tile mismatch on the MFD - almost as if different data sets have been used? So, and never having used them before, installed Flappies raster charts/maps for the region (and oh my god they are awesome!!). Minor blanking still occurred - not as severe though - but definitely still there - just slightly further out to sea. Just ran the same 'mission' in A10 - no problems -so guessing AH/Map/Location related? MFD6.trk MFD5.trk

Hi @Floyd1212 - yep (and many thanks for the input - all suggestions appreciated) - emphasis on 'had' followed by slow repair with no improvement - so thus far have: Noticed issue. Reported. Removed Texture packs - no change. Slow Repaired - no change. Swapped to 'basic' 1 screen setup, no helios (viewports patched, viewports patching removed) no head tracking - no change. Included in this is no viewport exports at all - so no other screens involved. Moved back from DLAA to MSAA - no change. I am not using reshade - but if I recall the screenshots were with the CGTC pack installed so maybe that's why things appear different - re-installed after previously removing them with no change. My gamma - I think - set as 1.8. Used both the basic DCS launcher and the MT Launcher (though not sure if that makes any difference nowadays) - no change.

Hi @Lord Vader. So - binned off head tracking, helios and dropped to single screen (1920x1080) using the '1 Screen' profile available in settings. Flew the same - same results. Then, had another thought and uninstalled all the helios patches - just in case. Restarted DCS, same results. So - screenshots with/without blanking. Two tracks - #3 before removing Helios patches, #4 afterwards, and 2 x logs - 'dcs' for MFD3 and 'dcs2' for MFD4. One thing to note - and not sure if you can pick it up in the tracks - but the MFD screens did appear to jump in terms of video realtime. MFD3.trk dcs.log MFD4.trk dcs2.log

Ah - apologies. Different mission. Will have a play and see if I can replicate the issue and reply.

Also had an issue whereby I started in a HAS/Shelter - and dependent on my view was getting intermittent shadows/sunlight when I looked down out of the cockpit. Obviously I didn't save the track - but will see if I can replicate it in due course - unless of course that is a known as well?

Cheers @Flappie. I did say 'around'... Definitely not weapon related though? I guess the question is which version is correct - the lighter/brighter version or the more colourful darker version?

Sure I read elsewhere that this was linked to carrying certain weapons (though now cannot find that particular post) - and seeing as I have no weapons/power...?

Posted this here as unsure whether an overall 2.9 bug or related to the A10C2 (or Nevada for that matter)? Have seen a similar post where I believe it had been declared as resolved - possibly linked to the weapons being carried? I created a mission whereby my A10 was sat on the tarmac with no power no weapons in Nevada - purely so I could get some screen grabs of various instruments for Helios. Didn't pay much attention to things as I was zoomed in and trying to align my view squarely with the instruments, but there appeared to be a dimming overall around a minute after starting. So, went back into the mission, external view and zoomed out. Around 50 seconds in - bang - everything goes a little darker. Not sure whether it returns to normal as ran out of time - but have attached some screen shots (bottom one at mission start and upper after the dimming) and the trackfile. Dimming2.trk

Had a look through the various forums - but couldn't find anything on this. Set up a training mission in Caucasus - headed out towards the coast, and the sea intermittently blanks on the moving map during flight. All cockpit settings left on default from a hot start. I don't think this is the same issue reported for Kola where the map completely disappears due to scaling - it is almost like the sea has been cropped/photo-edited out using a lasso on an intermittent basis - and drops in and out. Only mods I had running was Taz tree mod and CGTC Caucasus Texture Pack. Screenshots and trackfile attached - along with a log file. Have just carried out a full (slow repair) - with no improvement. dcs.log MFD Blanking.trk

Mine defaulted to other payment (card or GPay I think) - so came out of the transaction, and then had the option to select paypal.

Hi @Morpheus - many thanks for that. Cracked it!

Yep - did that hence the ask. The two folders (circled) are not in my vfstextures folder.

Hi @Taz1004. Just looking at your tree mods - and noticed in the downloads there are two 'normal' uncompressed folders (Noisewinter and Noisewinter.min). What are these for - as cannot find similar folders in the DCS textures folders?

Absolutely - and have been flying over it recently.

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?