Hello 

 

I installed SweetFX in FSX but seems that this program does not changed anything.  SweetFX log says this message: 

 

full path: C:\FSX\

redirecting CreateDevice

initialising shader environment

device->GetBackBuffer failed

redirecting CreateDevice

initialising shader environment

redirecting device->Reset

initialising shader environment

 

If it helps I am running FSX with Processor: Intel® Core i5-3330 CPU @ 3.00GHz

Core speed: ~2993 MHz, NVidea GForce Experience , driver it is updated.

 

I am intrigued with "device->GetBackBuffer failed" message error. Is there any cure for that? 

 

Thank you.

 

 

not sure if it will help because my system is very different from yours, but i had no effect at all with sweetfx until i disabled 'anti-aliasing' option in FSX.

 

also make sure you have some effects enabled in the settings.txt file, by default it think most are disabled.

 

i also have the 'getbackbuffer failed' but now it works, so i guess we can ignore that message (too technical to understand :rolleyes: )

 

---

 

from sweetfx troubleshooting guide

• Antialiasing
  • Some games use a postprocessor step for antialiasing, and this can overwrite SweetFX’s changes to the image.
  • Try turning off ingame antialiasing. SweetFX have a SMAA filter that can compensate (sometimes even better than the original, and with less overhead

---

I turned off antialiasing but had no good result. Without antialiasing I have too much flickering. Also the message "device->GetBackBuffer failed". Thanks for your answer anyway. 

FSX doesn't use a post-processing version of AA, but you may have it enabled in Nvidia Inspector....

 

Look for "Nvidia Pre-defined FXAA Usage" and make sure it's set to "Disallowed",

 

and to be safe, just below is "Toggle FXAA on or off. " Make sure it's off.

Paul and all

 

I changed my Nividia Control Panel to FSX in this way:

 

anisotropic filtering................... off

antialising - fxaa.........................off

antialising - gamma correction.....off

antialising - mode.......................Use global setting (application - controlled)

antialising - setting......................Use global setting (application - controlled)

antialising - transparency............Use global setting (application - controlled)

 

Now, my SweetFX log reads this way:

 

full path: C:\FSX\

redirecting CreateDXGIFactory1

redirecting D3D11CreateDeviceAndSwapChain

removing D3D11_CREATE_DEVICE_SINGLETHREADED flag

redirecting CreateDXGIFactory1

 

I am not sure if it means SweetFX is working fine or not.

Anyway I noticed that without filtering and antialising option in the FSX menu I have a flickering and kind of blocky images. I usually use anisotropic option.

 

Thank you!

DX10 update test

I have dx11 version, thanks.

if I also I have DX11 in W8 and I had to just update the DX

I give up SweetFX but had success with FXAA tool. 

In my first changes I changed saturation and add bloom. I liked the sky color more blue, but aircrafts with white fuselage looks like too much bright.

Also, the problem is that it´s a frame killer. From 60 fps to 15... 

I was using FXAA withouth problem until installation of PDMG 737NGX. It causes ctds after that.