Gliptal

Thanks for the guide, I finally budged and went with no MSAA and FXAA instead: I hate how the menus look, but ingame you can't notice the added blurriness on the textures anyways. It'd be nice if ED added FXAA internally, as to not affect the GUI. I managed to crank most stuff up, a lot more than I thought I could (60FPS @ 1080p running an FX8320 and a 1050Ti). The shadows analysis was especially great, since I can finally get nice and smooth shadows in the cockpit without losing frames (by setting "Terrain Object Shadows" to "Flat"). With that said, something that the pics don't show is a lot of shimmering on aliased objects going on, especially in the distance. Has anyone else noticed that?

They shouldn't really, my understanding is that once you're far enough from the ground you'd get flat shadows anyway.

Any pics on what FXAA does to the GUI and to the cockpt textures blurring wise?

Odd, I see no difference in the aliasing, and very minor differences in the textures (look at the lower border of some of the warning lights, and the compass). I honestly doubt the NVIDIA panel is doing anything, it's probably DCS being weird.

Yeah you're right, that can't be.

I suspect it's placebo and setting "Enhance Application Settings" disables the ingame MSAA pass. This would explain the FPS gain. I know at least one other game that does this. Take a couple of pics with your cellphone and compare aliasing.

Add VTB Export by default ON.

These should sound better:

There's a keybind which will turn on the RADAR on the second screen when in the cockpit: you have to press it every time you start a mission. It's been asked to make it by default on multiple times already. No joy yet.

Your dropdown with 2X, 4X, and CSAA refers to MSAA. FXAA is separate (as it is not technically true AA). FXAA does not have "levels", it's either ON or OFF.

Piston85 is right, FXAA does not have leves. What you're seeing there is the enhanced setting out of order, possibly due to the localization.

Allright, just making sure it's not on my end.

Any news? Need anything else?

Channel switch keybinds.

Put AF to 16X, any GPU after 2004 will handle it fine w.r.t. 8x

This changes rockets as well right?

So is it enhance or override to get FXAA to work? Also, screens may look different because due to the PP pass being applied later in the stack. Are you taking them through DCS?

No, that's exactly how FXAA works. You may want to try and add a sharpening filter through something like reshade, but the more PP effects you pile on top of each other the more artefacts you'll get.

They're there, although they're not tiered.

I use two keyboards, one mapped to the UFC on a tablet stand, the other mapped to the CDU.

Nice. Have you noticed a substantial decrease in image quality?

It still uses a green filter rather than actually enhancing visible light, but that may be not doable with a mod anyway.

Now that 2.5 has release, and given the amount of comments and questins regarding gamma and how it handles dark shades (i.e. cockpit panels and shadows), here is a quick comparison between using low gamma only, and higher gamma with NVIDIA's vibrance: - gamma 2.2 (default), vibrance 50% (default): - gamma 1.6, vibrance 50% (default): - gamma 2.0, vibrance 70%: - settings (mostly irrelevant): As you can see, the first shot has an unpleasently bright scenario, whilst the second one has a pitch black cockpit. The third one has the best of both worlds. Note that 70%/2.0 is a bit conservative, you may want to try 80%/1.9. - 1.6 50% (left) vs. 2.0 70% (right): https://cdn.knightlab.com/libs/juxtapose/latest/embed/index.html?uid=e211bfe2-0773-11e8-b263-0edaf8f81e27 - 2.2 50% (left) vs 2.0 70% (rght): https://cdn.knightlab.com/libs/juxtapose/latest/embed/index.html?uid=0a34f674-0774-11e8-b263-0edaf8f81e27 One caveat is that the default slider in NVIDIA's control panel applies the vibrance system-wide, meaning it will alter the desktop and any other application you may want to run. You can use this small tool to automate the setting: simply select DCS.exe, set your preferred vibrance, and leave the tool running in the background. When DCS is in fullscreen or the focused window, it will apply the vibrance (using NVIDIA's internal APIs); as soon as you tab out or close it, it will revert to the system-wide default. Also, added note, make sure "Dynamic Range" is set to "Full": you'll get a lesser quality image otherwise.

Here you are (renamed from .log to .txt to allow the upload). Let me know if you want me to test stuff. dcs.txt

MSAA on in NVIDIA, off ingame.