I can't stand P3Dv2 without SGSS, it's impossible to read gauges clearly (as well as better clarity in other areas). However with 4xSGSS my fps plummets to single digits (8-9fps) when flying into Portland in FTX PNW. I turned down everything, and even at "Sparse" (with everything else to the left) I couldn't get above 15fps. The moment I disabled SGSS it shot back up to 50-60fps. Clearly autogen has a marked affect on fps when using SGSS. After that I was able to push my settings back up and keep it at around 18-20fps, which isn't great but good enough for the odd trip into these dense urban landscapes.

 

Is there going to be a fix for better AA? Never needed SGSS in FSX. Can I also run 2xSGSS & 4xMSAA? I've heard conflicting stories that you must use the same SGSS value as you do MSAA (e.g. 4 & 4, or 2 & 2). I guess I can try this myself, just I'm not at my flight sim machine at the moment.

 

i5-2500 @ 3.4Ghz + GTX770

Nvidia has to rectify the issue with proper driver support. That's a waiting game for now unless you have an AMD card.

 

I'm using 8xMSAA + FXAA and things are very crisp, to the point where it doesn't bother me (and I was an AA snob in FSX). But I realize FXAA makes some gauges blurry in some planes. So it's not the best solution for everyone.

So AMD cards don't have this issue?

I have a GTX 770 SC with a [email protected] and 4x MSAA + 4x SGSSAA works without a problem.

Without the following settings my GPU is only on about 60% load through the game, with it the GPU is fully used.

With the settings everything is fine, lower frames only in city areas, but that is even without AA and CPU capped on high scenery complexity / autogen settings:

 

Additional Prepar3D.CFG settings:

[Display]
TEXTURE_BANDWIDTH_MULT=1800
TextureMaxLoad=30
[Main]
FIBER_FRAME_TIME_FRACTION=0.05
[TERRAIN]
SWAP_WAIT_TIMEOUT=2
[JOBSCHEDULER]
AffinityMask=15

When in areas with low FPS I just lower the scenery complexity/autogen settings until it's fine.

 

Keep in mind, AA impact is influenced by the screen resolution. I'm using 1920x1080.

I'd love a screenshot of these cockpits without SGSS. I don't run SGSS and I don't have any blurry cockpits. So... I'm a wee bit confused.

I'd love a screenshot of these cockpits without SGSS. I don't run SGSS and I don't have any blurry cockpits. So... I'm a wee bit confused.

I don't know if the OP is having the same issue, but for me it is as follows (and you cannot see it on screenshots, as I'll describe below):

 

- It is not blurry cockpits per se, but the small texts (e.g. tiny scales in the instruments or small print on the cockpit) are kind of shimmery fuzzy.

- When your virtual head is not moving, you can't see the issue. So you can't see it in screen shots either.

- When you are moving your virtual head with normal controls, you also can't see it, because you are moving too fast.

- But when using TrackIR it is there because your head is always moving a little bit, even when you focus on one spot. That humble movement is enough for the fuzzy texts to appear.

- Some planes are more prone to it than others. From the stock P3D planes I see it most obvious in the A36 Bonanza.

- When I have SGSSAA enabled, I do not have the issue any longer.

Thanks for the explanation, I do not use TrackIR nor is it used in a training system. Explains why I have no AA issues.

The only way to antialize the instruments and cockpitreadings in DX10 and DX11 (nvidia, dont know personally amd) indeed is to use SGSSAA. No other antialiazing method has any effect on that. Sadly SGSSAA is extremly performance hungry, especially because you need 4xSGSSAA to get a really good effect. If you dont have a very powerful gpu its a nogo, because you get an REALLY SMOOTH (and i mean SMOOTH!) performance in v2.2.

 

@sOcks: it should technically be the best, to use 4xSGSSAA with 4xMSAA or 2xSGSSAA with 2xMSAA because of the algorythm, but there's nothing you can loose or damage simply trying it yourself.

 

My interimsolution is not to enable SGSSAA to keep that smoothness (max autogen!-never thought this would be possible some day, but shadows just in cockpit) and to disable dynamic head movement in order to reduce/eliminate at least that shimmering effect on the dials and instruments which most of the airplanes have. Stock A36 Bonanza really is terrible here..

 

To disable dynamic head movement in prepar3d.cfg:

[DynamicHeadMovement]

...

MaxHeadAngle=0.000000
MaxHeadOffset=0.000000
...

 

@WarpD: lucky man! but how does a blind man got his license?    (just kidding...)

I was just gonna post that the one plane I really see the fuzziness with with FXAA is the A36. 

 

But in the Carenado Cherokee I've been playing around with, it looks fine. 

I'd love a screenshot of these cockpits without SGSS. I don't run SGSS and I don't have any blurry cockpits. So... I'm a wee bit confused.

 

Not blurriness. Shimmering, and it's not just the cockpit. When zoomed out any finer details, such as reading small text in gauges is incomprehensible. I'll grab a couple of screenshots tonight and show you the difference. I have the problem regardless of whether the view is stationary or moving.  

Ok, see comparison below (I zoomed out more to give a better comparison, it looks a lot worse in motion, even when up close to the dials):

 

.........

Additional Prepar3D.CFG settings:

[Display]
TEXTURE_BANDWIDTH_MULT=1800
TextureMaxLoad=30
[Main]
FIBER_FRAME_TIME_FRACTION=0.05
[TERRAIN]
SWAP_WAIT_TIMEOUT=2
[JOBSCHEDULER]
AffinityMask=15

.......

Just wondering about this parameter.

TEXTURE_BANDWIDTH_MULT=1800

Spirit

Ok, see comparison below (I zoomed out more to give a better comparison, it looks a lot worse in motion, even when up close to the dials):

 

 

Because, as you say, it looks a lot worse in motion you can usually improve things

quite a bit by turning off all VC head momentum effects in your p3d.cfg file.

Also make sure VC Mipmaps is ticked in P3D settings.

 

gb.

That image is so small... I can't see any difference with my sad eyes. LOL :(

That image is so small... I can't see any difference with my sad eyes. LOL :(

 

:lol:

The picture is small, indeed, but one can clearly see the difference though....

 

I wouldn't recommend posting "better" pictures, because things could only get worse for you...

:lol:

 

edit:

@gboz: do you really see a difference w/o VC mipmaps? I tested that setting several times under different conditions and didn't see any difference and am wondering if i miss some usefull effect?