I always use and it works fine for me, leave a couple of samples.

Wow it looks stunningly good, I already have SweetFX nicely tweaked to my satisfaction, 1 preset for day flight, another for night. I will throw Shade into the mix for sure, I can see from the screenies it really does add depth to the shadowing effects, thanks guys for the input

I tried it but it did eat my FPS by a substancial amount.

Some report no change but I'm going to have to go with Word Not Allowed on this one. On my system there was a pretty big hit.

I leave my setting, it looks great at night too, could see the stars and may have

 

Have to try them out thanks

Ah I see, in fact I have not seen any fps hit at all using SweetFx alone, did you mean that you see a big hit using Shade in combo with SweetFX?

There is a number of AA parameters in SweetFX_settings.txt. Do you still use AA setting in nVidia Inspector with it?

 

Thanks,

Dirk.

I am using DX10, I do have some settings for AA enabled in NI (I won't bore you with them here), and yes in SweetFX, I also enable SMAA and sometimes FXAA.

All

 

I absolutely LOVE SweetFX but I have had to dump it because of the constant crashes. It seems like only certain people are experiencing these, but after some extensive testing I can confirm that they are most definitely caused by SweetFX.

 

Does ANYONE have any idea on what might be behind these crashes, why only certain people get them, and more importantly, whether or not anything can be done?

 

And assuming there is no cure for those of us who DO experience them, are there any alternative products which give similar effects?

 

I hate flying without SFX but honestly now have no choice. Basically if you want to do anything with a menu in FSX or leave the FSX environment for any reason, it's a 95% chance of a CTD, and it's just not workable.

 

Thanks all

Martin

All

 

I absolutely LOVE SweetFX but I have had to dump it because of the constant crashes. It seems like only certain people are experiencing these, but after some extensive testing I can confirm that they are most definitely caused by SweetFX.

 

Does ANYONE have any idea on what might be behind these crashes, why only certain people get them, and more importantly, whether or not anything can be done?

 

And assuming there is no cure for those of us who DO experience them, are there any alternative products which give similar effects?

 

I hate flying without SFX but honestly now have no choice. Basically if you want to do anything with a menu in FSX or leave the FSX environment for any reason, it's a 95% chance of a CTD, and it's just not workable.

 

Thanks all

Martin

Check if you have this window update KB2670838, uninstall it if you have. KB2670838 is an optional update.

 

 

Check if you have this window update KB2670838, uninstall it if you have. KB2670838 is an optional update.

 

 

 

Yes, I saw about that in another thread. Uninstalled it and sadly no change.

Yes, I saw about that in another thread. Uninstalled it and sadly no change.

 

Yeah I'm unfortunately in the same boat as you, although I may be testing it in DX10 mode soon now that I switched.  Assuming I can figure out a way to translate the settings I used in DX9 mode to DX10.  The same settings file the lumasharpen and curves were wayyyyyy too strong in DX10.

I use DX9 and it seems to only be a small proportion of us who get these CTDs with SweetFX.

The annoying thing is there's no error message or warning. But if you click a menu item, or use ALT+ENTER to switch to desktop etc, you can pretty much guarantee a crash. So frustrating. At the moment I'm having to leave it disabled as I can't take the frustration of constant crashes mid-flight!

Hi everyone, first time poster here.

 

I'm having trouble getting fsx to run with dx10 enabled (because of the framerates being a lot better) with SweetFX

The problem I'm having is that the resulting image SweetFX produces just looks awful, and I have no clue how to fix it.

I tried fiddling with most settings but nothing improves it. I restarted with a clean fsx.cfg a couple of times and also tried the online fsx.cfg optimizer, which worked excellently when I was still running on dx9. All to no avail. I tried changing things in nvidia inspector, starting with a new clean slate every time I couldn't get it to work.

 

The best image I can come up with with dx10 on and sweetfx and nvidia inspector looks like this. What's going wrong?

I have a brand new pc with i7-3770K, 16gb memory and a oc'd Geforce GTX 670 Sig 2

On dx9 I can get it close to photo realistic but with low fps (15-24 on average)

On dx10 I can get high framerates (30fps capped), but without filters the image looks dull

dx10 with sweetfx drops fps to 18-20 again and produces the nightmare image you see below

 

This is with the new beta injector for sweetfx. With regular 1.4 you get an added problem that the image becomes way overexposed and bright.

 

WITH SWEETFX

 

I'm almost inclined to give up and just go with the no-shaders, default dx10 look which looks like this with me and is preferable over the mess above.

 

WITHOUT SWEETFX

A little followup to my previous post.

 

I have managed to get things more or less working by not using any of the SweetFX profiles I could find anywhere, none of them give decent graphics (and I've tried about a dozen of them). Instead I used the SweetFX configurator program and made changes myself.

 

Using this I came to realize though that SweetFX is not for me. The margins to get things looking right are tiny. Differences between 0.85 and 0.87 on a scale of 0 to 8 for example make a huge difference. The main culprit for messing things up for me at first were mainly the bloom and hdr settings. I fiddled with these settings and can make the image either too dark, too light or just right but with 'candy' colors. I'm not a fan of the look at all. It's not a natural look. The ground looks alright, but the sky has clouds with blue in them or even cyan.

 

When I finally had a preset that sortof looked alright, I went to a different time of day and things were messed up again. Not even starting to talk about nights where everything's pitch black.

 

I then wanted to make a screenshot and started Fraps (a screen capture program), which promptly removed all the effects from the screen.

 

I think I'm going to leave it at that and just enjoy flying. Spent 4 days off trying to get things working. First dx9 and enb, now dx10 and sweetfx. I'm done with it. The dx10 default look is fine and decent scenery makes a huge difference.

 

Shade doesn't seem to do anything either in dx10 mode for me. I guess I'll just have to wait for a proper dx11 flightsim, if that ever gets made.