Mustang

Bump up for this old thread - thought I'd revisit SSAO to see how it performs with the latest DCS openbeta, I'm really pleased to say it performs quite nicely now and looks very good too, the FPS drop is negligible and the effect although subtle does a good job at shading those areas that should be shaded :thumbup: I had it running during my Twitch stream earlier tonight, alot depends on how keen an eye you have for details but I can definitely see it working

Again, still broken in todays OB patch.

Depends it varies from monitor to monitor, some are designed for full RGB while others aren't, it's best to check first.

Yep this is especially helpful for those nighttime missions in DCS, I reckon many people have the incorrect setting and this makes darkness overkill.

http://www.lagom.nl/lcd-test/black.php Test limited and full with this image, the one that shows all the correct black range is the correct setting for your screen - on my screen if I select full the first 15 squares are pitch black, with limited there is a gradual transition to a lighter shade.

Have you had a look at changing the output dynamic range in NVCP? If you have it on full, try using limited (which is recommended for HDMI)

Someone here asks a similar question, see the replies https://forums.guru3d.com/threads/help-deciding-which-card-to-keep-1080-ti-or-2080.428969/

https://www.userbenchmark.com/UserRun/21252662 <--- specs

I went to an RTX 2080 8gb (ASUS Dual OC) with the same CPU as you and I get exceptional performance in DCS, and the RTX features are extra useful with OBS as I stream on Twitch. It wouldn't make much sense staying with the 1080 range, just my opinion. P.S these RTX cards are stellar overclockers, got mine at GPU 2100mhz and 8000mhz on the GDDR6 RAM (16000mhz effective)

There is supposedly Reshade (post processing effects) now available directly via the GF Experience software in this version, however some people are reporting that DCS World is not supported which is quite disappointing - especially for VR users who could benefit from effects such as SMAA. Here is a rundown from nVidia themselves

Image sharpening, will be interesting to see how this affects DCS

Here comes that driver with built in Reshade ability https://forums.guru3d.com/threads/geforce-game-ready-driver-441-08-download-discussion.429173/ https://www.nvidia.com/en-us/geforce/news/geforce-gtx-16-series-super-game-ready-driver/ GeForce Game Ready driver 441.08 includes the following changes Adds support for GeForce GTX 1660 SUPER GPU Adds support for image-sharpening from NVIDIA Control Panel Added Image Sharpening control to the NVIDIA Control Panel->Manage 3D Settings page. Increases the level of sharpness, detail, or clarity of images in games and applications Adds support for G-SYNC compatibility with NVIDIA Ultra Low Latency Mode Added Ultra Low Latency G-SYNC+ V-Sync feature Provides tear-free, low-latency gaming using G-SYNC displays. To enable, set Low Latency Mode to Ultra, turn on V-Sync, and enable the G-SYNC display. Adds support for 7 new G-SYNC compatible monitors Adds support for ReShade filters within GeForce Experience Adds support for HDMI 2.1 VRR.

Very, image quality is great, check out a recent stream I did where I use these settings

Example, I use 4xMSAA in DCS options and then select 4xSGSSAA in NV Profile Inspector

Try using different SGSSAA levels with nVidia Profile Inspector alongside your ingame MSAA, works very well to iron out the jaggies.

Thought this would interest some :) https://videocardz.com/newz/nvidia-to-add-reshade-filters-to-geforce-drivers

Yeah I can never understand why the heck ED decided to remove that feature, gutted to see it go :( I remember thinking to myself that this was too good to be true, and sure enough come the next update the pilot shadows were gone and all the pit shadows were semi see through messes again.

Thread bump for awareness.

[Mustang] F-5E

Disappointed to still see this bug in todays openbeta, will wait yet again to see if the next patch fixes it.

So you tried other aircraft and they're still bugged?

It seems to be fixed in todays openbeta 2.5.5.38040, at least when I was in the Hornet :thumbup:

Yep, damned if they do and damned if they don't, always been this way.