It's good to have a support in this amazing tool.

I have problems Sweetfx and NVI. I always use FSX in full screen, but every time I minimize the screen to windowed mode, the FSX crashing ends without any message.
I have spent many hours and days doing tests and trying to find a clue to the problem and have come to the following conclusion:

If I have the sweetfx and activated nvidia inspector, the crash occurs.
I have tried various settings in removing vsync NVI and CFG file but no.
I have tried many profiles of NVI, and versions 1.3 and 1.4 of Sweetfx. The 1.5.1 version does not work for me.

Many others have the same problem I have. If we find the solution to this error, we will very happy to many others.

Windows 7 - 64bit
FSX DX9
Nvidia GTX 780
I7 3770 k - @ 4.4GHz
20 Gb RAM
3 screens - 23" (5760x1080)
REX4
ASN


Thank you very much for all the support you can provide us

Check if you have windows update KB2670838 installed. If you do, remove it, try again.

 

Another way to tackle this...

 

Go to: C:\Users\<user>\AppData\Roaming\Microsoft\FSX and open xml.exe. Disable all add-ons configured to run, try again.

I do not have it installed. I have my Windows Updates always OFF. Nor do I have antivirus or add any other that might complicate my game.
My computer is only for FSX. Nothing more.

Any other ideas friend?

I was recently experiencing crash almost immediately. This makes my tests easier.

1 - I went to the file as you indicate exe.xml as first test the add-ons that were there have disable.

Magic. does any crash. I make several test for 5 minutes, changing to full screen and windowed mode fine.

2 - enabled only couatl, and I have not crash.

3 - enabled EZdok, and immediately crash.

Apparently the problem is with EZdok.

4 - Then go back to enable the two (couatl, EZdok) to check, and surprise, and does not crash.

I do not understand what has happened. You have 20 minutes of testing and I do not get the crash.

If I say that some days ago ago was my crash at the end of a long flight of 2 or 3 hours. And for some reason it had increased at the beginning instant of FSX.

At the moment I have no errors. But I think everything goer suggests that may be the cause. I'll make a long flight with couatl and EZdok and see what happens. If I have crash, then I turn off my add and I'll be back to try long flight.

I will be announcing the results here. This is a major breakthrough. :rolleyes:

Thank you

Update

 

After several tests, enabling and disabling the addon I exe.dll, I can determine with certainty that the FSDreamteam couatl is who does not support the SweetFX.
All my initial tests were with FSDreamteam Airports (KLAX, PHNL, PHOG, PHLI, PHKO) all got the same result of crash.
I have done 2 flights at airports that are not FSDreamteam (KSEA, PANC, KDEN) and have not had any errors.

It is important to mention that I have left active couatl in exe.dll. What the crash is the set: SweetFX, couatl and parked on airport FSDreamteam.

Today I updated the addonmanagerX and couatl for retesting. But I must say that both were up to date.

It would be great to have feedback from someone else who has this combination of programs and tell me if you have had the same crash with the SweetFX and FSDreamteam.

When he thought he had found the reason for the crash, bad news. They are back.
Even with only 2 addons to disable the crash of SweetFX appeared.

And original appearance in FSX airports. That is, all my previous theory is not good.

I have managed to minimize crash by 70% making a neat trick you may be able to give us a glimmer of a solution.
I recorded as a simple and original default FSX airport (MROC) flight. When up FSX, access my default flight (MROC) with SweetFX on, then I do full screen tests and window mode and all good.

Then <World> <Go to Airport> and I am looking for the source of my flight plan airport. In my home airport, I repeat testing full screen and windowed mode and all good. I have had 2 crash of 15 attempts.
He had already made ​​several long flights such as KSEA to PANC (5 hours) to PANC to PHLI (6 hours) and all good. (Using my trick described above)
Today after a cut between PHLI and PHOG (Both of FSDreemteam) flight, when you move from full screen to window mode to close and save, crash.

This is what many other users have ignored the SweetFX. But I would not put it aside. I want him in my FSX, is valuable designs and color graphics giving. Help. :(

I will describe some important points for your feedback:

 

1- FSX.CFG  new file.
2 With or without NVI.
3- SweetFX versions 1.3, 1.4 and 1.5.1.
4 Different configurations sweetfx_settings.txt
5- SweetFX files in FSX main directory.
6- SweetFX files in another directory outside of FSX.
7-A .bat file that automatically deletes the shaders:
RD / S / Q "C: \ Users \ elee \ AppData \ Local \ Microsoft \ FSX \ Shaders"
RD / S / Q "C: \ ProgramData \ Microsoft \ FSX \ Facilities"
RD / S / Q "C: \ ProgramData \ Microsoft \ FSX \ SceneryCache"
RD / S / Q "C: \ ProgramData \ Microsoft \ FSX \ SceneryIndexes"
8- With ½ Vertical Refresh Rate Sync.
9 - No ½ Vertical Refresh Rate in Sync
10- Nvidia Driver 337.88
11- Nvidia Driver 340.52
12-With all the addons in exe.dll ON
13-With all the addons in exe.dll OFF
14-NO Flaps program.
15-NO MSI Afterburner
16-FS Recorder on or off.

 

versions:

1- NVI 1.9.7.2
2 NVI Settings suggested by you.
3 - Nvidia Driver 340.52 Only the driver. Without any additional component.
4- FSUIPC 4.934 Licensed
5- UIAutomationCore.dll File in the root directory of FSX. Version = 6.0.5840.16386

 

Programs:

1-    REX 4
2-    Active Sky Next
3-    My Traffic
4-    Radar Contac
5-    DNT Display
6-    FS Real Time
7-    Alacrity PC
8-    Shade 1.02
9-    FDC Live Cockpit
10-    FS Captain
11-    FS Passenger
12-    FS Global Ultimate (All)
13-    iFly 737
14-    GSX
15-    EZDok
16-    Flight Commander
17-    FS Recorder
18-    FTX Global

 

Some other modules:

1- Linda (For hardware VRinsight MCP-II Combo)
2 - Wideserver.dll
3 - iFly737ng.dll (iFly)
4 - LVLD.dll (Level d)

Very grateful for the help you can give me.

I had the same problem and I was able to stop it by enabling smaa in sweetfx.  Although its best not to switch tasks while running sweetfx and complex addons in general I have found.

I had the same problem and I was able to stop it by enabling smaa in sweetfx.  Although its best not to switch tasks while running sweetfx and complex addons in general I have found.

 

Just activate SMAA option in the file Sweetfx as you indicate

-------------------------------------------------------------------------------

#define USE_SMAA_ANTIALIASING 1

 

#define SMAA_THRESHOLD 0.20

 

#define SMAA_MAX_SEARCH_STEPS 98

 

#define SMAA_MAX_SEARCH_STEPS_DIAG 16

 

#define SMAA_CORNER_ROUNDING 100

 

#define COLOR_EDGE_DETECTION 1

 

#define SMAA_DIRECTX9_LINEAR_BLEND 1

---------------------------------------------------------------------------

testing now

I've had the same crash using SMAA within SweetFX :(

I'm using sweetfx with NI and everything is running fine. I also have couatl.exe. The crash may be occurring because you switch from full screen to window mode. FSX is funny like. That happens sometimes with mine so now I always fly in window mode and use the pseudo full screen app

I'm using sweetfx with NI and everything is running fine. I also have couatl.exe. The crash may be occurring because you switch from full screen to window mode. FSX is funny like. That happens sometimes with mine so now I always fly in window mode and use the pseudo full screen app

 

The title of this topic, may confuse now. I discovered along the way that the problem is not NVI.

 

Right, the problem only happens when you go from full screen to window mode or full screen to windowed mode.

 

I'm still trying to find a solution

 

 

DEVGRP, you also have 3 monitors in surrounding mode?

The title of this topic, may confuse now. I discovered along the way that the problem is not NVI.

 

Right, the problem only happens when you go from full screen to window mode or full screen to windowed mode.

 

I'm still trying to find a solution

 

 

DEVGRP, you also have 3 monitors in surrounding mode?

Yes I have 3 monitors but I'm not using surround mode. I have 27 inch monitors so one is good enough for flying

Yes I have 3 monitors but I'm not using surround mode. I have 27 inch monitors so one is good enough for flying

 

At some time I believed that the crash could be Nvidia surround system, but also did a test with one monitor. But the crash appeared when switching from full screen to windowed mode

I am now using pseudo to mitigate somewhat the crash if I have to make use of some outside the FSX addon. But still, when I finish my flight and step full-screen display mode (pseudo = Windows_Key + F11) again crash.

Adi, you can help pls.

I think the topic title is not right and maybe this is the cause that no contribution to the subject.
I'll close this thread and open a new one with the most correct title.

Sudden Crash of SweetFX - Fullscreen to window mode