Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Bad Anti-Aliasing with NVIDIA

Featured Replies

  • Commercial Member

Since there is much confusion surrounding FSX AA, I recap showing a method to apply FSX Anti-Aliasing and Texture Filtering correctly:

 

 

The problem of anti-aliasing in FSX is not well understood, FSX applies AA while the screen is being made up from smaller pictures with transparent backgrounds. To improve the stock FSX setup, we can use NVidia Control Panel and set Antialiasing Transparency to 2x, 4x or 8x.

 

First we set FSX to Anisotropic, and AA checked on. Then for most planes we can use NVidia Control Panel and set Antialiasing - Transparency Supersampling, try 2x then 4x, then 8x.

 

Here's what we get with no more processing:

Example 8x Supersampling but not sparse grid

 

Even with this setting, problems can come with certain planes looking jagged and instrument displays crumpled. Zoomed in looks just fine, but when zoomed out we have a crumpled display or aircraft model. To cure this we can set Sparse Grid Supersampling Transparency AA using NVidia Inspector (make sure to start with a default profile):

 

Example NVidia Inspector setup with 8x Sparse Grid Supersampling first try 2x, then 4x, then 8x.

(Note the vsync setup shown provides a very smooth display.)

 

So really we only need Sparse Grid for some planes, but whatever we do, we need Transparent AA to correct the layers of images as the screen is made up.

 

 

Furthermore, any picture can be dithered or anti-aliased post-process. This can be applied after the FSX screen is built, with or without proper transparency AA already in place. This can look OK, but with closer inspection doesn't hide the fact that the screen is made from poorly anti-aliased images placed together in the first place. We always need the application of the transparency AA whatever. A post process like FXAA will slightly soften the screen anyway.

 

The method I have shown works, and reliably. This may fly in the way of other established methods, but that's tough. Until those methods can be shown to work, and reliably, they are meaningless.

 

 

 

Regards

Steve

Steve Waite: Engineer at codelegend.com

  • Replies 104
  • Views 14k
  • Created
  • Last Reply

Top Posters In This Topic

I think anyone reading this thread could agree that Steve apparently is the king of all things FSX. Do you use "lol" as often in your Engineer writing as you do here on these forums?

Blake Williams

 

  • Commercial Member

I think anyone reading this thread could agree that Steve apparently is the king of all things FSX. Do you use "lol" as often in your Engineer writing as you do here on these forums?

You have such arrogance to imagine others stand behind your derogatory personal jibes. If you can't bring anything sensible to the table then you shouldn't post.

Steve Waite: Engineer at codelegend.com

  • Commercial Member

 

I can definitely tell you that with just the in-game AA, the edges looked much better with my AMD GPU than this shot.

Until you posted a better shot, my card's better than your card. lol

I think a 'lol' seems nice to show that I'm only being humorous. But hey, chaotic, Like I said, you could well be right about AMD cards. While many have naturally been speccing NVidia's in recent years, AMD have been Beavering away, progressing their hardware very well. Let's hope someone with an AMD can chime in.

Steve Waite: Engineer at codelegend.com

Really? Bert turned up, paid no attention to the information I provided, made no attempt to try it, or understand it, and dismissed it as if it made no sense. Then carried on about his document that mostly does not work because of a fundamental lack of understanding of the basics of FSX - and which can be tested in moments. There's only a post process that can work on an unfinished FSX screen, but it does not cover up the problems I was trying to discuss. If he's gone away all upset, well Boo-Hoo.

Well yes, really. As an unbiased observer to this thread, I would say he merely had a different experience to you. I've not seen him reply rudely, just disagree, which is his right.

 

On the other hand, you have been over assertive and rude.

 

Below is a prime example of what I'm talking about, a very immature response indeed...

 

 

If he's gone away all upset, well Boo-Hoo.

 

 

 

He hasn't gone away all upset, he's done what mature grown ups do, removed himself from a thread that has become less than friendly.

 

Your expertise is laudable, and it's fantastic you are willing to share it with us, but people will have different opinions, which is their right.

  • Commercial Member

Well yes, really. As an unbiased observer to this thread, I would say he merely had a different experience to you. I've not seen him reply rudely, just disagree, which is his right.

 

On the other hand, you have been over assertive and rude.

 

Not at all. I should not have to have been defending my comments from other's rudeness in the first place. If you can't stand the heat, get out of the kitchen. He went.

Steve Waite: Engineer at codelegend.com

I wanted to point something out after trying something in P3D.

 

AA doesn't work at all in my nVidia Inspector.

 

I tried 8x, I tried 16x, I tried 128x even and no changes in quality or framerates. I used the guide that was linked from nNick.

 

Yet, when I pop on full AA in P3D I get an acceptable amount of smoothness with white text on the cockpit aside (it flickers like crazy sometimes)

 

So I'm not sure what's going on, but AA isn't working at all in NI for me.

Nathan Allen Pinard

Virtual Pilot in Training

Composer/Sound Designer

www.nathanallenpinard.com

  • Commercial Member

P3D is more or less the same as FSX. Make sure to start a new profile with NVidia control panel. then in a new default NI profile for Prepar3D, make the same settings I showed for FSX above, in P3D set MSAA to 8 samples, anisotropic to 16x for example.

Steve Waite: Engineer at codelegend.com

Not at all. I should not have to have been defending my comments from other's rudeness in the first place. If you can't stand the heat, get out of the kitchen. He went.

 

He wasn't rude at all. No one would define his comments as rude.

 

He merely had a different experience to you.

 

When you sarcastically refer to his system as a "miraculous system" and post rolling eyes emoticons, I'm not surprised he doesn't want to engage with you any more.

 

We are all supposed to be friends here debating a common interest, there is no need for sarcasm, and unfriendliness.

 

 

I should not have to have been defending my comments

 

 

Yes you should, if you want to debate rather than to dictate, you should.

 

 If someone else has a different experience or opinion you should have to defend your position, it's called a friendly debate...

 

I hope you'll consider my words anyway, and perhaps respond better when others disagree with you.

  • Author

Yes but if you remember you wanted to know about NI setup and I gave you the hot poop, why not show some gratitude? Until you and Bert can post shots of the wonderful AA and texture filtering you go on and on about, I'm not interested. 

 

I already knew how to set up NVIDIA Inspector, all I wanted to know is whether I'm doing something wrong and I'm getting consistently worse anti-aliasing. Apparently I didn't do anything wrong, so I can only come to the conclusion that anti-aliasing in general is worse on NVIDIA.

 

You have the choice to believe or not what I'm saying, I'm not reseating my AMD GPU just to get a shot for you. I have plenty of FSX shots taken with my AMD GPU, but I'm sure you are going to doubt me again unless I take comparison shots of the same spot with both AMD and NVIDIA.

 

And I didn't say anything about texture filtering.

  • Commercial Member

My NI setup has been openly available for scrutiny from the outset, and only takes a few minutes to try. But my "idea about AA" was treated like some kind of fantasy, a little later it 'doesn't comply with NickN', like it's non-sense. I'm only interested in posting the technique, and having it fairly appraised. It was not.

 

Chaotic, If you can't step up with your shot or find another with an AMD card like I said then you will have to defer for the time being.

Steve Waite: Engineer at codelegend.com

But my "idea about AA" was treated like some kind of fantasy, a little later it 'doesn't comply with NickN', like it's non-sense

I don't recall anyone saying that... they merely had a different experience to you.

 

I guess that's not allowed.

  • Commercial Member

You're wasting your time, there's nothing stopping Bert setting it up and comparing like I do.

Steve Waite: Engineer at codelegend.com

You're wasting your time, there's nothing stopping Bert setting it up and comparing like I do.

I don't care about who's right or wrong, only attitudes to differing opinions. Only the way we respond to each other. Only about humility and friendliness.

 

Clearly I'm wasting my time.

 

It must be the UK heat at the moment. ;)

  • Author
Chaotic, If you can't step up with your shot or find another with an AMD card like I said then you will have to defer for the time being.

 

If nobody believes me that I was getting better anti-aliasing with AMD then why is this thread still going? That's why I made this thread, to find out what causes that, not to begin a discussion about which NVIDIA Inspector settings are the best (and clearly none are as good as the anti-aliasing I had with AMD).

 

If I am going to have to defer, I'd like this thread to be closed as well.

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.