I'm still using V2.4 and unless this was resolved, or there is a different AA algorithm that gets AA anywhere near as decent as I saw in FSX way back when, I'm likely going to hold off on moving on to V3 and hunker down until 64-bit P3D happens, if it happens.  I'm also loath to give up QW757 which I use w/ FSCaptain and I understand it doesn't work in V3, QW757 that is.  I have no idea of FSCaptain does.   I've made peace w/ the other limitations in P3D but this is a big one especially in the USA regions during the now cloudier season.  My solution has been to keep cloud draw distance to 60 and density to the lowest, and that's tolerable but still it chokes in places.  It seems intuitive that their most be a flag of sorts that cloud textures *should* have that prevents SGAA from being applied, but I don't really understand it.  It would be nice to know if this issue has been greatly addressed since 2.4.  2XSGAA is another coping strategy, but 4X is preferred.  I'm using a single GTX Titan.

 

Thanks in advance

With many clouds and 4 xSGSS setting my frames still drop like in V2.5.

Overcast with ASN and cloud draw distance set to 90 miles I still get only 20 fps depending on the angle of view in the 777 despite of a GTX 980.

So concerning this point I saw no difference to V2.5.

    Agree with Severn, performance still drops in heavy clouds. I don't see 64 bit fixing this, as you will still need a good cpu to process the data. whether it'll be x64 or x32, makes no difference. Maybe down the road, nVidia/AMD, will come up with a new form of AA for dx12.

Considering AMD's Mantle is at the core of dx12, I expect AMD to step back into the light, as far as gpu performance in games.

 

just my .02c.

 

regards, Craig

Thank you, I'll hold pat then for now. I have a good GPU, reasonably good still. But in my mind the issue is that cloud textures shouldn't require much if any AA applied to look correct and therefore the solution to this is not best dealt w/ by increasing processing power but by changing how AA is applied to cloud textures, so to decrease processing demand. This seems so obvious that I have to guess somehow, some fundamental way, it's not possible to do--i.e., it's baked into how all texture the graphics engine processes must respond, so w/o a total rebuild in the engine or a massive improvement in GPU processing power we're stuck w/ the really, really bad bottleneck.

 

I'd love to hear some expert comment on this perplexing and apparently persisting issue.

I remember reading in one of Rob Ainscough's posts a while back that LM had actually looked at working on excluding clouds from AA. I believe LM cited issues with comparability as the reason they did not go ahead with it. This was back in V2.5.

 

I was hoping that we may have had this with V3 but unfortunately not. Without some level of SGSS I find it difficult to achieve the level of AA I am satisfied with.

 

Michael M

Flew a short flight in the NGX yesterday with a solid overcast rendered by ASN. Problem was not FPS, but horrible stutters. However, if I turned off SGAA (2x) in Nvidia Inspector and MSAA (2x) within P3D v3, stutters went away. Also, my GPU load (GTX 970) was 99 % during the stutter fest, so I suspect that was the problem.

 

So no, these issue have not been resolved.

<p>'<span style="color: rgb(40, 40, 40); font-family: helvetica, arial, sans-serif; line-height: 22px;">my GPU load (GTX 970) was 99 % during the stutter fest, so I suspect that was the problem.'</span></p>

<p> </p>

<p>This bottleneck is the other giant elephant in the room beside VAS depletion which apparently was addressed some in V3. $200 more for this? No thanks!  The last thing this needs is 3-way SLI to solve this software design problem.  Pathetic, really.</p>

I've also found the P3D AA quite lacking, but I'm tolerating it for now.

 

This is with 4x sgaa 4x msaa and 8x AF @ 1440p My frames were a solid 35 area.

I'm using 2X DSR (no SGSS) with almost no performance impact in dense overcast with OPUS.

   It is not LM's job to provide better AA processing, that is for MS, (direct x) and the gpu manufacturers. LM are just using the tools they have been given. By that, I mean, ESP, DX11, and all of the warts that go with them. DX12 has some rather interesting new tech under the hood, but LM will have to, once again, rebuild the graphics engine from the ground up to implement it. I would love to have better AA inside P3D3; maybe in 2 years, we'll see that in a LM flightsim. On the bright side, 2016 is "steam"-ing just around the corner.

  Again, just my .02c.

 

regards, Craig.

The amount of AA mainly depends on the quality and kind of textures for the aircraft panels or scenery. For example, Carenado Kingair C90B shows horrible shimmering at the panels with P3D internal AA. This can nearly completely eliminated using 4 x MSAA P3D internal and 4x SGSS in Nvidia Inspector. But then fps drop from 100 fps to 70 fps (@ unlimited). Still good fps, but 30 % drop.

 

Therefore, you must do a comprimise when you have such shimmering aircrafts / sceneries: my current setting is 8x MSAA internal and 2 x SGSS in NI. Still shimmering, but fps drop is only to 90 fps. There was one thread by Word Not Allowed, suggesting to use 8 x SS transparency in NI, but that does not work with heavy shimmering panels.

   It is not LM's job to provide better AA processing, that is for MS, (direct x) and the gpu manufacturers. LM are just using the tools they have been given. By that, I mean, ESP, DX11, and all of the warts that go with them. DX12 has some rather interesting new tech under the hood, but LM will have to, once again, rebuild the graphics engine from the ground up to implement it. I would love to have better AA inside P3D3; maybe in 2 years, we'll see that in a LM flightsim. On the bright side, 2016 is "steam"-ing just around the corner.

  Again, just my .02c.

 

regards, Craig.

 

Since AA is perfect in a lot (if not most) games I'd say MS and the GPU manufacturers have done their job...? Nothing wrong with the tools, it seems to me.

    AA works in most games designed, from the ground up, over the last 3-4 years. P3D is a patchwork of technologies dating back to the last century. Besides DTG, who else is spending money on such old tech, and being successful? LM have been doing their best to turn the pig into a beauty queen. They have added new functionality/capabilities into v3, that was not possible in ESP/FSX. (ie, see the user video of P3D3 running on 3x4k screens, aka, that's a lot of pixel pushing...) There is much that can be improved in P3D, but I do not expect to see a brand new, built from the ground up sim, coming from LM in the near future. The most I expect to see from LM is; dx12, and x64, before the end of the decade. This is only my opinion. I do not keep up on the latest AAA gaming titles, so I am most definately out of the loop on that tech. 

 

  Regards, Craig

just got V3 here, and AA is working much better then V2.4 I dont even need 4XSGAA clouds look stunning.