MSAA not working / Rift S / Latest OB?

[Hippo]

HI. I've just gone from Rift CV1 to Rift S, and had been away from DCS for a few months. Now I'm going through the usual tweaking / testing, and it could just be me, but when I turn on MSAA I can't see any difference. I'm also running MSI Afterburner for performance monitoring, and there is no difference there either. On the CV1 turning on MSAA made a big difference to the image and to the performance.

 

Is anyone else seeing this, or is there some setting I've missed?

 

Running 2.5.5.40647 (not Steam).

 

In non-VR, MSAA does work.

Edited December 11, 2019 by Hippo

[Svsmokey]

Interesting...do you have any AA enabled in the Oculus software ? Maybe it's overriding the DCS setting ?

[Chapa]

Have you quit/restart DCS ?

[Hippo]

I thought the Oculus AA setting only applied to Home. Anyway, tried changing it, but nothing.

 

I have restarted, makes no difference. I don't remember ever having to restart for MSAA to take effect.

 

I'll say that it could just be me - but I just can't discern any noticeable difference when I turn MSAA (x4 or x2) on.

 

I am assuming from your responses that turning on MSAA makes a noticeable difference for you.

[Hippo]

And further issues... tried the C-101CC Nevada practice mission. Get severe artifacting in cockpit when I turn on 4xMSAA. Anyone else seeing this?

 

Only in the Rift S, it's fine in non-VR.

[Svsmokey]

Coming from a CV1 to the S , i left MSSAx2 on as before , and show the expected result in the graphics . Haven't tried turning it off yet .

 

Even if the graphics are indistinguishable to you , Afterburner should show a massive difference .

 

Have you tried a repair of DCS ?

 

How about Nvidea AA settings ? Application controlled ?

 

I'll run a test later with MSAA off & report back .

[dburne]

I thought the Oculus AA setting only applied to Home. Anyway, tried changing it, but nothing.

 

I have restarted, makes no difference. I don't remember ever having to restart for MSAA to take effect.

 

I'll say that it could just be me - but I just can't discern any noticeable difference when I turn MSAA (x4 or x2) on.

 

I am assuming from your responses that turning on MSAA makes a noticeable difference for you.

 

That is correct.

 

MSAA working fine on my end for my Rift S.

[Hippo]

Thank you all for replying. I now have MSAA working, with expected performance drop. Not sure why or how - it "just started" working. Apologies for any inconvenience.

[Chapa]

MSAAx2 and MSAAx4 makes a difference but more than 80% of the effect is done by MSAAx2.

In non VR mode, it was not needed to quit/restart DCS but I found it necessary to do it in VR.

 

I had the same issue than you at the beginning...

 

Instead of MSAAx4, you can set MSAAx2 in game and in nvidia control pannel or nvinspector set:

 

- Antialiasing-Mode: Enhance the application setting

- Antialiasing-Setting: 2x [2x Multisampling] (2x displayed in control pannel)

- Enable Maxwell sample interleaving (MFAA): On (Multi-Frame Sampled AA (MFAA) in control pannel)

 

It has the same effect as MSAAx4 but at the cost of MSAAx2 in performances (near).

 

An easy way to compare the settings is to launch the F18 free flight caucasus instant mission, F4 view and look at the sidewinder.

[Hippo]

Instead of MSAAx4, you can set MSAAx2 in game and in nvidia control pannel or nvinspector set:

 

It has the same effect as MSAAx4 but at the cost of MSAAx2 in performances (near).

 

Many thanks for that, what a great tip. Since VR I haven't been in to nVidia settings as I didn't think they did anything in VR. But this certainly appears to work.

 

It does indeed appear to need a restart in VR - I don't recall that being the case before. I'm sure I did restart before - but I could be wrong.

[Chapa]

You're welcome!

 

I have the feeling that there are sometime bug that don't trigger new settings... (anistropic filter is sometimes capricious... and need restart... sometimes not)

 

I took the habit now to quit/restart for every change and when I change textures settings, I also delete the fxo and metashaders2 subfolders in Saved Games\DCS folder.

 

I lost too much time during tuning, thinking everything was ok to discover at the next startup that something was wrong again...