Jump to content
Sign in to follow this  
adi518

Discovered fix for dx10 + sfx SMAA disable problem

Recommended Posts

Hey guys,

 

Not long ago, I posted here about this issue and recommended not to use sfx w/dx10. For those who might not remember, I said that when using dx10 mode + sfx, there's a problem where SMAA must be turned On or it darkens the whole scene, making your sim unusable. The major annoyance was that you either had to turn off sweetfx completely or stick to SMAA, which although allowing properly lit scene, overrides the perfect dx10 aa settings (causing jaggies) & increasing the load on the gpu.

 

GOOD NEWS! I found the fix!

 

At first, I was pretty sure this is a bug within sfx, and sfx's author CJ looked at me weird when I complained about it. So, here's the fix: upon installing sfx and it's cfg app. Turn OFF all features and leave ON only 'LIFT GAMMA GAIN'.

 

Throw in the following values:

 

1.1 / 1.1 / 1.1

1.5 / 1.5 / 1.5

1.5 / 1.5 / 1.5

 

Once you put these in, the scene will become properly lit again, and hurray! you have perfect AA and perfectly fine working sfx, without performance loss! Play around with the values until satisfied. Each row must have the same R/G/B values or a certain color might oversaturate the scene.

 

Suggested sfx features to play with:

 

1. LUMA SHARPEN

2. TECHNICOLOR
 

Also remember that you can create different presets. :)
 

That's all you need really... I suggest following the term 'KISS' - Keep It Simple, Stupid.

Share this post


Link to post

Well done, Ari! That's a real positive piece of good news!

 

Thank You!

 

All the Best,

 

pj



i7 4790K@4.8GHz | 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.

Share this post


Link to post

Adjust the settings. These are arbitrary values to get you started. I'll post a more refined set of values later.

Share this post


Link to post

I must say these suggestion is good flying at night and not during the day, it will be too bright.

 

The point Anthony - is that Adi has made it possible for everyone to start this version of SweetFX for the first time, without it immediately plunging the FSX into darkness.

 

This has been the most disconcerting problem for someone who has never played with SweetFX before, and most often results in them not bothering with it, or rolling back to the earlier releases - which is what I did. It's a great find, and is the result of some dedicated research.

 

Regards,

 

pj



i7 4790K@4.8GHz | 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.

Share this post


Link to post

Ok, here's a realistic set of values:

 

1.0 / 2.25 / 1.15

 

Input each, three times per row, from top to bottom.

 

I used 12:00 daylight as reference and toggled sfx on/off to compare with stock fsx.

 

11119247254_798fe6253a_o.jpg

Share this post


Link to post

New for REX4:

1.0 / 2.25 / 1.08
I also discovered this fix is needed on p3d2 as well:

1.0 / 2.25 / 1.15
More testing to be done, 1.15 might get lower to 1.08, not confirmed yet.

 

And an important note regarding usage of SFX:

 

I see many people claiming rex textures don't display in-game like they would in preview shots. Here's why: when you're changing the scene colors via sfx, say by using contrast modifications, you're creating a major difference to the textures! every small change in the values counts! using the values above, you should get near no modification to the original texture colors. I'm also working on fine tuning the values further. Stay tuned & enjoy! :)

Share this post


Link to post

Adi, can I just confirm you're using SFX version 1.5.1. I've just installed it and used the following settings (1.0 / 2.25 / 1.15) but get a green screen?

 

I only have LIFTGAMMAGAIN set in the config settings?

 

Any ideas.

 

Pete


40282618105572517s.jpg

 

 

Share this post


Link to post

Yes, I'm using 1.5.1.

 

You probably input the values incorrectly. It should be like this:

 

1.0 / 1.0 / 1.0
2.25 / 2.25 / 2.25
1.08 / 1.08 / 1.08

Share this post


Link to post

Ah Ha...That's what the problem was. I just copied the lines like this 1.0 /2.25/1/08 and did that three times...Wow, what a difference.

Thanks Again Adi.


40282618105572517s.jpg

 

 

Share this post


Link to post

@adi518

 

Well mate, bravo, well done! Really really good discovery. At least the text on cockpit displays is now readable without SMAA, nice.

 

Cheers!


Current system: ASUS PRIME Z690-P D4, Intel 12900k, 32GB RAM @ 3600mhz, Zotac RTX 3090 Trinity, M2 SSD, Oculus Quest 2.

Share this post


Link to post

Exactly! This fix is crucial to get rid of the useless SMAA. The SMAA doesn't make it near as clear as SGSS x4 or higher. It's an 'edges' only algorithm AA. Useless for FSX. The problem wasn't as obvious in dx9, but it was there as well.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...