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.

DX10 and FSAA: some personal observations

Featured Replies

  • Replies 151
  • Views 42.5k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Hi Rich: The "Cloud thing" fix removes AA when it comes to cloud creation - which makes for a lower graphics load, and probably slightly higher fps. The issue is that SGSS is applied to the whole scre

  • jabloomf1230
    jabloomf1230

    The vast majority of these obscure FSX.cfg  entries do little or nothing of value, except make FSX more unstable. What's even more bizarre are the online "calculators" that make ridiculous assumptions

Jeroen, thank you so much for starting this topic and sharing your findings with us.

 

My only problem, I got a bit lost with all those abbreviations. Could somebody please enlighten me what FSAA, TGSSSAA, ... correspond to? Can't find them in the dx10 fixer nor Nvidia Inspector.

 

Harry

- Harry 

9800x3D (Strix x870e-E)  -  64GB RAM (DDR5 6000, CL 30)  -  RTX 5090, 34'' 1440p OLED HDR  -  Windows 11 Pro (1TB M.2)  -  MSFS 2024 (MS Store, 4TB M.2).

 

 


My only problem, I got a bit lost with all those abbreviations. Could somebody please enlighten me what FSAA, TGSSSAA, ... correspond to? Can't find them in the dx10 fixer nor Nvidia Inspector.

 

The two most important abbreviations you should know (at least when it comes to the Fixer and Inspector) are:

 

- FSAA (often also simply abbreviated as AA) stands for FullScreen Antialiasing. In the Fixer you set this using the DX10 Anti Aliasing option.

 

- SGSS stands for Sparse Grid Supersampling which is one of the modes of Transparency Supersampling as you find it in Inspector (nVidia).

 

You set FSAA (or AA) using the Fixer and then set SGSS using Inspector, making sure they fit together will (see my posts on the first page).

 

You don't really care about what all the other things stand for as long as you know about these two. At least imho.

 

FSAA is mentioned in the Fixer manual (DX10 Anti Aliasing) but SGSS isn't, which is a pity because it is needed to get good graphics imho. Just a simple note about it would have helped a lot of people, I think.

Great dont need AA, real clouds are soft so sounds great to me Paul

 

Really? So running FSX with anything less than SGSS is acceptable to you. That being said, if you want to remove any kind of shimmer you need to run SGSS in NI, which renders the cloud shader fix useless according to reports here.

 

I did some testing with Word Not Allowed's old cloud test, following his instruction specifically. The results are not good on my end. Specs can be seen on the side there, and I am using TML 1024 and LOD 4.5, mostly default config, except AF 14 HT disabled and BP=0.

 

dx9 using 8xS and 2xSGSS in NI and AF set internally (best visual to performance ratio on my system) 

25-28 fps and no stutter.

 

dx10 using Fixer 4x and 4xSGGS set in NI and AF set internally (most closely matches visuals of dx9)

15-18 fps and stuttery mess.

 

The only way I can achieve the same fps and stutter free experience in Word Not Allowed's cloud test, is to set 4x in Fixer and disable SGSS in NI....which results in shimmerfest in the VC and outside.

 

I concur that that dx10 is inherently smoother, and I can perceive it, particularly as a trackIR user. I also perceive it when banking. But, I am still not convinced that everyone is running as smoothly as they think.

Intel i7 10700K | Asus Maximus XII Hero | Asus TUF RTX 3090 | 32GB HyperX Fury 3200 DDR4 | 1TB Samsung M.2 (W11) | 2TB Samsung M.2 (MSFS2020) | Arctic Liquid Freezer II 280mm AIO | 43" Samsung Q90B | 27" Asus Monitor

Thanks again, but what is the meaning of TGSSSAA which was mentined on page 3 in this thread?

 

Cheers,

Harry

- Harry 

9800x3D (Strix x870e-E)  -  64GB RAM (DDR5 6000, CL 30)  -  RTX 5090, 34'' 1440p OLED HDR  -  Windows 11 Pro (1TB M.2)  -  MSFS 2024 (MS Store, 4TB M.2).

 

 


Word Not Allowed's old cloud test

 

... is probably not real-world flying 99.9% of the time. With your kick-&@($* machine, 4xSGGS should be child's play in almost any situation.

[email protected] - ROG Strix Z790-E - 2X16Gb G.Skill Trident DDR5 6400 CL32 - MSI RTX 4090 Suprim X - WD SN850X 2 TB M.2 - XPG S70 Blade 2 TB M.2 - MSI A1000G PCIE5 1000 W 80+ Gold PSU - Liam Li 011 Dynamic Razer case - 58" Panasonic TC-58AX800U 4K - Pico 4 VR  HMD - WinWing HOTAS Orion2 MAX - ProFlight Pedals - TrackIR 5 - W11 Pro (Passmark:12574, CPU:63110-Single:4785, GPU:50688)

Jeroen, thank you so much for starting this topic and sharing your findings with us.

 

My only problem, I got a bit lost with all those abbreviations. Could somebody please enlighten me what FSAA, TGSSSAA, ... correspond to? Can't find them in the dx10 fixer nor Nvidia Inspector.

 

Harry

 

TSGSSAA - a term I made up: Transparency Grid Sample Super Sampled Anti Aliasing; I assumed most could figure this one out.

 

BTW, I found the term FSAA misleading since recently it's usually associated with FXAA (at least when it come to nvidia), and at first that is what I thought the OP was writing about.  But then again, the OP has demostrated elsewhere in this thread his less than full technical knowledge of the subject matter at hand.

CPU: AMD 9800X3D PBO MB +200 CO -25| Motherboard: MSI MAG X870e Tomahawk WiFi | GPU: MSI RTX 5090 Ventus 3X OC | RAM: G.Skill 2x32GB DDR5 6000 cas 30 | M.2 SSDs: Samsung 990 EVO Plus 2T, WD Black SN750  M.2 1T | Hard Drive: WD Black HDD 6T 7200 | Optical Drive: LG Bluray writer, internal | Cooling: Thermalright Phantom Spirit 120 EVO | Case: Fractal Design Focus G | PSU: NZXT C1200 1200W

Win 11 Pro 64|HP Reverb G2 revised VR HMD|Asus 25" IPS 2K 60Hz monitor|Saitek X52 Pro & Peddles|TIR 5 (now retired)

Any particular reason why you are "having a go" at Jeroen, Rod?

Christopher Low

AMD Ryzen 7 9800X3D CPU / 64GB DDR5-6000 RAM / 12GB Nvidia RTX 4070 Super GPU / Gigabyte X870E Aorus Elite Wifi 7 / 1+2TB Samsung Evo Plus M2 Nvme

UK2000 Beta Tester

... is probably not real-world flying 99.9% of the time. With your kick-&@($* machine, 4xSGGS should be child's play in almost any situation.

 

You would think....but alas does not seem to be the case. More work on my end, may be required.  

Intel i7 10700K | Asus Maximus XII Hero | Asus TUF RTX 3090 | 32GB HyperX Fury 3200 DDR4 | 1TB Samsung M.2 (W11) | 2TB Samsung M.2 (MSFS2020) | Arctic Liquid Freezer II 280mm AIO | 43" Samsung Q90B | 27" Asus Monitor

You would think....but alas does not seem to be the case. More work on my end, may be required.

I too have a fast system - i7 4700k OC'd to 4.3GHz, 16GB RAM, Windows 7 64-bit, NVIDIA GTX 660 Ti - and here's the frame rates I'm getting sitting on the runway at Misty's Place (version 7, part of the excellent Return to Misty Moorings scenery, with OrbX PNW and Tongass Fjords... it's a resource heavy place for some reason)... all with LOD set at 4.5000 and maximum texture size at 2048 unless noted otherwise... all with moderately complex and dense cloud cover (saved Opus weather theme)...

 

DX9 -- 24 to 29 fps, minimal typical FSX stutters, no shimmer or jaggies

 

DX10 (FSAA 2X, SGSS at 2) -- 22 to 30 fps, no stutters but significant shimmer and jaggies

 

DX10 (FSAA 4X, SGSS at 4) -- 16 to 22 fps, no stutters but feels sluggish, minimal shimmers and minimal jaggies

 

P3D (LOD 6.500, max textures at 4096) -- 18 to 23 fps, smooth, slightly sluggish, no shimmer or jaggies

 

The performance is kind of disappointing. I have Word Not Allowed's tweaks applied and using the NI settings suggested by Word Not Allowed for DX9 and P3D and the NI settings suggested by Paul and Jeroen for DX10.

 

Any suggestions? Is it my GPU?

 

Thanks,

 

Scott

It would be easier if you were to copy your fsx.cfg, Scott, and rename it as "Scot_fsx.txt" and then use the "More Reply Options" down in the bottom-right corner of the posting window to attach it to your reply. That way we can give you a much more accurate appraisal of the issue you are having.

 

Secondly - I would like to see a screenshot of your Inspector settings, please. Without having both pieces of this information we would only be guessing at the very best - and anyone can guess at what's wrong - right! :rolleyes:

 

All the Best,

 

pj


i7 [email protected] | 32GB RAM | EVGA RTX 3080Ti | Maximus Hero VII | 512GB 860 Pro | 512GB 850 Pro | 256GB 840 Pro | 2TB 860 QVO | 1TB 870 EVO | Seagate 3TB Cloud | EVGA 1000 GQ | Win10 Pro | EK Custom water cooling.

It would be easier if you were to copy your fsx.cfg, Scott, and rename it as "Scot_fsx.txt" and then use the "More Reply Options" down in the bottom-right corner of the posting window to attach it to your reply. That way we can give you a much more accurate appraisal of the issue you are having.

 

Secondly - I would like to see a screenshot of your Inspector settings, please. Without having both pieces of this information we would only be guessing at the very best - and anyone can guess at what's wrong - right! :rolleyes:

 

All the Best,

 

pj

 

Thanks Paul!  I have attached my fsx.cfg file and the screenshot for NI that I'm using in DX10.  

 

Scott

Here you go Scott. I've made a few moderate changes and suggestions. One of the issues is that you are loading an enormous amount of "trusted" software, and I think it contributes to the issue.

 

Providing your cooling is adequate, I would also move the proc up a point or two: 4.3-gig is still "mid-range" for FSX, as it likes single-core (ie nowadays 4 cores, HT off, and perhaps with an Affinity Mask of 14 or 15 set).

 

A further performance 'assist' can be gained by not loading the scenery areas where you never fly in - e.g perhaps Africa, Asia, the UK, Europe, etc.. These can be unticked in the Scenery Library (or "Scenery Config Editor" from here.) (Great program - will fix scenery config errors, too).

OK! 

 

Good luck, and all the best,  :smile:

 

pj


i7 [email protected] | 32GB RAM | EVGA RTX 3080Ti | Maximus Hero VII | 512GB 860 Pro | 512GB 850 Pro | 256GB 840 Pro | 2TB 860 QVO | 1TB 870 EVO | Seagate 3TB Cloud | EVGA 1000 GQ | Win10 Pro | EK Custom water cooling.

Here you go Scott. I've made a few moderate changes and suggestions. One of the issues is that you are loading an enormous amount of "trusted" software, and I think it contributes to the issue.

 

Providing your cooling is adequate, I would also move the proc up a point or two: 4.3-gig is still "mid-range" for FSX, as it likes single-core (ie nowadays 4 cores, HT off, and perhaps with an Affinity Mask of 14 or 15 set).

 

A further performance 'assist' can be gained by not loading the scenery areas where you never fly in - e.g perhaps Africa, Asia, the UK, Europe, etc.. These can be unticked in the Scenery Library (or "Scenery Config Editor" from here.) (Great program - will fix scenery config errors, too).

OK! 

 

Good luck, and all the best,  :smile:

 

pj

 

Thanks very much Paul - you are such a resource and so friendly.  I appreciate your help and can't wait to test it out after work.  

 

Did you attach a modified fsx.cfg or NI settings?  I couldn't find them...

 

Thanks again,

 

Scott

Just wanted to post a quick note of thanks to Jeroen for his original post.  Have followed his guidance and set up the Fixer and NI as recommended, using 8x FSAA and 8xSGSS.  Cured all shimmering except for a small amount on the VC screen of the Reality XP GNS 530.  Everything else looking great in the cockpit of the A2A 172, which had been a real challenge to me when it came to taming the shimmers.  I'm now beginning to get the point of this DX10 thing.  I don't have a lot of free time and would have been hard-pressed to test out all the Inspector setting combinations, so this was a huge help.  Again, many thanks!


Alan Ampolsk

"Ah, Paula, they are firing at me!"
-- Saint-Exupery

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.