Czar

Just tested on "Driver Default" after posting the text above. Yep, mission loads in 50 seconds as well.

I just found that disabling "Shader Cache Size" on nVidia control panel (maybe there is something similar on AMD cards too) triples or even quadruples loading times in DCS. Consider enabling that function if your disabled it or keep at 'driver default'. I did disabled it for testing purposes and found out long loading times in DCS. Enabling at 5gb made DCS go from 3 minutes 50 seconds + at loading a mission to only 50 seconds. Probably same applies to leaving at 'Driver Default'.

Any chance of more people sharing screenshots of this map after the latest update? I think it is a big deal because of the new normal maps, other improvements and it would help this product grow in support as it has changed since the initial impressions.

It is resting! Pat on its back or clap a little and it will stand right up.

Use the sharpness slider to have a better image quality. Everyone experiences this. Who has a nVidia card has at least the advantage of using DLAA in DCS, me included. It looks great with decent performance and decent ghosting even at 40fps locked (personal preference). DLAA: ED should introduce FSRAA which is the DLAA alternative for AMD cards, if I got that right...

You can't prevent it. It is how they work. They take the previous frame(s) to help build up the next frames hence the performance gain and "trails" with using them. They also helps with aliased edges, hence their anti aliasing properties. With better algorithms in the future, these methods can be improved with less ghosting (trails). FSR is currently developed by AMD and for each subsequent release you can expect visual quality gains. TAA is the same. I don't know if it is developed and by who. There are .dll replacement for DLSS for newer version in forums. I don't know for FSR. Don't expect ghosting (trails) to disappear completely anytime soon as they are a by product of these methods. MSAA is ancient and uses algorithms specialized on contrast between pixels to reduce aliasing. It is a completely different tech made much earlier than temporal solutions made into commercial video games. MSAA also has an inherent incompatibility with PBR solutions, which are included in DCS. Worked great thousands of years ago. Today its use has been degraded every software that relies on PBR, IIRC.

Nice. Yes I use Notepad++ for ages now, no worries Export.lua under "...Saved Games/DCS/Scripts". Correct? Two dashes in front of Tacview related items inside that file. Thanks, Max!

Any tip how to do that, Max? Thanks!

ED needs to review all these cursor speeds and player accessibility on their modules. Make a menu to adjust these cursor speeds based on player preference and setups. I have a dedicated analog stick for these and still these cursors catch me off guard by different speeds on modules and in the modules systems themselves. The Viper FCR and HAD page cursor speed differences are also one of the biggest offenders. That HAD page cursor speed is nuts while the FCR is slow.

Great if there is a way to make dust fully volumetric as current clouds instead of being composed by many 2d textures. Any improvement to the current particles effects I like! (kind of needed too)

I have no crashes. Performance is the same.

There are often fixes in nVidia drivers that benefits all GPUs. Example being "Monster Hunter World" textures glitching and artifacts fixed on a driver earlier this year. If you only play DCS, sure, use 'that' stable driver you know it is going to work. I had no issues updating to the latest drivers always since DCS W debut and I usually run a budget but decent setups since, not latest and greatest. Here's an example of global fixes on the latest nVidia driver that affects all GPUs under support: I haven't updated it because I won't need it, or use those things, but I don't have a clue if the other person does. Performance wise it all lands on margin of error. I have an RTX 30 series and I won't keep using old driver just because. I'm usually helping people here with stability and not the other way around. Recent drivers had also meaningful fixes on productivity software. There are public extensive lists of fixes easily readable that you'll be missing.

ahh, I probably missed the news. Great if so, even greater to see it on their other modules. Thanks for the info!

This feature should be present on all modules that features Helmet + Visor use in real life. It is evolving to be a big oversight. The adequate filter to do that has been introduced by Razbam (not a simple brightness filter).

@DmitriKozlowsky See if unchecking 'fullscreen' to run DCS in windowed borderless mode solves the issue.

This is true overall. Game ready driver branch has the benefits of having more public releases in a given period of time. Eventually, when studio and game ready are on the same version, the differences of performance between both lies on margin of error. I used studio drivers for 2 years with DCS and had zero issues. Only for recent games you should look into game ready drivers and their recent fixes. DCS is outside of that sphere. About the issue: If you can easily reproduce the issue, try to record the video output with OBS and when the screen goes black, keep recording. If the recording file shows video normally when your screen went black, it is something external like monitor cables or connectivity to whatever display you're using. Blacks screens """generaly""" points at video driver crash and the reasons can be many, in my limited experience. Try to double check your GPU connectivity to the motherboard, PSU health and have a look at the Event Viewer (windows) for any kind of error pointing at the video component. Download some stress software to test the GPU/PSU to see if your system is stable. FURMARK - Tests more PSU than GPU, but stress the later too. (not useful for throttling analysis) It is very light and simple old software. No subscription or paywall bs.

I've never seen such issues (VKB here too). This looks like it is on your end. Do you have a gamepad connected in any way or another controller connected that's causing interference on the same binding?

Yeah... current Caucasus map feels like an alternative universe in comparison to the real place. Anyone with that civilian flight sim from that large company, take a flight on the region. Literally anywhere and fly bellow 10k ft, and that's just an approximation to what's really there. The differences are wild. Not talking about graphics lighting or tech, it is just 'what's there' instead of blank spaces and different buildings. It is a very rich region visual wise, both in human structures and nature.

Issue replicated on the Persian Gulf map under a covered parking spot. Core issue indeed.

...dang..... Thank you, Razor. I imagined it only after posting it and I think you're right. The small amount of times I've been in rain in DCS was often not from a hangar, just mainly on a carrier deck and the usual open ramps.

Rain effects of all kinds pass through the reinforced hangars roofs... or should I say: "not really rainforced"... This is a fair bit immersion breaking to say the least. Air base was 'Al Sahra Army Airfield'. One of those hangars that are connected to the runways ends through a dedicated taxiway for each. I presume it happens on all of those hangars.

noted. There is still a good time window. Likely I'll get it tomorrow.

I'm thinking about getting the Apache (finally)...

Welcome to the forums, awayvenus7! Additionally to the above tips.... If you want a certain FOV value while in mission: press 'esc' -> options -> system tab, and there you'll see the in cockpit current FOV value. Adjust the slider to a value you're comfortable with or to pair the same value to other aircraft you own and then save it, as mentioned, with Right Alt + Numpad 0 (zero), although is much more intuitive to fine tune it while looking in the cockpit with the zoom keys which are * and / as mentioned. Keep in mind you need to be looking centered in the cockpit before the keybind input for saving the new 'default view' (Right Alt + Numpad 0). This is the setting that will allow you to save the new POV with the keybind above. Later on you'll want to look into the bindings of 'zoom in slow', 'zoom out slow', 'zoom normal' and 'zoom in' commands on your hotas or controller for you to be able to zoom in and out whenever you want while flying.