Perhaps I didn't explain myself sufficiently.  The crashes/problems are related to the Bonjour service and iTunes.  You'll have to get that program resolved first before you can ever use FSX again.

 

Best regards,

Jim

Ok I discovered that the causing module in FSX is SweetFX, I've tried without GSX, and with a new version of FSUIPC (unregistred). This is the only thing that can cause, but now the question is How to fix that? (ENB series problems gone, now coming SweetFX problems without crash reports). Or what can be the next alternative(s), if is/are?

@@balan22 - Glad you were able to find your problem.  There's a long SweetFX post in the FSX Forum with configurations that seem to be working for others.  The FSUIPC4.dll, whether registered or unregistered, would not have had anything to do whether SweetFX works or does not work in FSX.  GSX would not have had anything to do with the crash too or how SweetFX works.  It is your configuration and only your SweetFX configuration (well, maybe if you have high display driver and/or fsx.cfg settings and your system cannot handle it).  Experimental programs like SweetFX can cause a lot of problems and the ENB module is one of the best examples. 

 

You used Bojote's site to come up with a FSX configuration and you have a lot of bad entries that just do not make and sense.  To start with.... [bufferpools] should be removed.  It works for some systems but not for all.  Do some research on this setting.  Look in the AVSIM Software and Hardware Guide for guidance.  ******* Bojote's fsx configuration program might work some of the time but it is definitely not right all of the time.  You need to know what tweaks he added and why he added them.

 

You do not have a widescreen monitor but you have wideviewaspect=true.  It should be false.  Texture_Bandwidth_Mult=78.  Strange number.  Should be 40, 80, 120 and no higher than 120.  I recommend 80.  TextureMaxLoad=30.  The default for FSX is 6 (without the line even in the FSX.cfg).  Do you know what placing this figure up 5 times from the default does to your system?  I would recommend removing this line or setting it no higher than 12.  Anything higher than that will definitely create problems.  Your Upper_Framerate_Limit=0 (unlimited).  Yikes!  Should be 30 and, for your system I would recommend no higher than 25.

 

AffinityMask=15.  Strange number.  Should be 14 or 84 depending on what you have enabled in your BIOS (see the AVSIM Software and Hardware Guide pinned at the top of the FSX Forum).

 

The SmallPartRejectRadius=4.0 is useless in FSX Sp1-SP2 and SWAP_WAIT_TIMEOUT was also changed with SP2 according to Phil Taylor, the lead developer on the FSX development team. Nick N recommends they be left out of the config.  Me too!

 

The max_async_batching_jobs will reduce the unsightly appearance of autogen popping up all the time.  Get rid of it.  It just takes up resources.  Instead, do as I do and add the following tweak to the [Terrain] section:

 

TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=1000
TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=800

 

Then you can max your autogen if you want and it won't affect performance too much.  Autogen is a known FPS killer. 

 

You have a very strange line in your FSX config that might have been caused by the Bojote tweaks:

 

[DISPLAY.Device.NVIDIA GeForce GTX 560 .0]  The line is right but note the space between 560 .0.  There should be no space.  It might cause problems, it might not.

 

If you want clearer textures, try high definition textures by changing the Texture_Max_Load=1024 (the default) to 4096 or 2048.  It will make a difference.

 

Hope this helps.

 

Best regards,

Jim

@@balan22 - Glad you were able to find your problem.  There's a long SweetFX post in the FSX Forum with configurations that seem to be working for others.  The FSUIPC4.dll, whether registered or unregistered, would not have had anything to do whether SweetFX works or does not work in FSX.  GSX would not have had anything to do with the crash too or how SweetFX works.  It is your configuration and only your SweetFX configuration (well, maybe if you have high display driver and/or fsx.cfg settings and your system cannot handle it).  Experimental programs like SweetFX can cause a lot of problems and the ENB module is one of the best examples. 

 

You used Bojote's site to come up with a FSX configuration and you have a lot of bad entries that just do not make and sense.  To start with.... [bufferpools] should be removed.  It works for some systems but not for all.  Do some research on this setting.  Look in the AVSIM Software and Hardware Guide for guidance.  ******* Bojote's fsx configuration program might work some of the time but it is definitely not right all of the time.  You need to know what tweaks he added and why he added them.

 

You do not have a widescreen monitor but you have wideviewaspect=true.  It should be false.  Texture_Bandwidth_Mult=78.  Strange number.  Should be 40, 80, 120 and no higher than 120.  I recommend 80.  TextureMaxLoad=30.  The default for FSX is 6 (without the line even in the FSX.cfg).  Do you know what placing this figure up 5 times from the default does to your system?  I would recommend removing this line or setting it no higher than 12.  Anything higher than that will definitely create problems.  Your Upper_Framerate_Limit=0 (unlimited).  Yikes!  Should be 30 and, for your system I would recommend no higher than 25.

 

AffinityMask=15.  Strange number.  Should be 14 or 84 depending on what you have enabled in your BIOS (see the AVSIM Software and Hardware Guide pinned at the top of the FSX Forum).

 

The SmallPartRejectRadius=4.0 is useless in FSX Sp1-SP2 and SWAP_WAIT_TIMEOUT was also changed with SP2 according to Phil Taylor, the lead developer on the FSX development team. Nick N recommends they be left out of the config.  Me too!

 

The max_async_batching_jobs will reduce the unsightly appearance of autogen popping up all the time.  Get rid of it.  It just takes up resources.  Instead, do as I do and add the following tweak to the [Terrain] section:

 

TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=1000

TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=800

 

Then you can max your autogen if you want and it won't affect performance too much.  Autogen is a known FPS killer. 

 

You have a very strange line in your FSX config that might have been caused by the Bojote tweaks:

 

[DISPLAY.Device.NVIDIA GeForce GTX 560 .0]  The line is right but note the space between 560 .0.  There should be no space.  It might cause problems, it might not.

 

If you want clearer textures, try high definition textures by changing the Texture_Max_Load=1024 (the default) to 4096 or 2048.  It will make a difference.

 

Hope this helps.

 

Best regards,

Jim

Thank You, I have done as you wrote and my FSX worked, now longer but then crashed to desktop without crash report. Now I really don't know what to do. I tried several times with different aircraft and addons but nothing helped. What should I do? Do I have to change the SweetFX's settings? As you can/could see my sweetFX settings aren't too crazy so...? 

I didn't read this thread entirely but only wanted to say that I was haunted by CTD's until I removed ENB mod and later SweetFX. I am now CTD free.

Hopefully someone familiar with SweetFX can help you.  Meanwhile, I would move the module to a temporary directory so you can enjoy FSX until you can find a solution.  There are several suggested and successful settings in the SweetFX posts in the FSX Forum.

 

Best regards,

Jim

I didn't read this thread entirely but only wanted to say that I was haunted by CTD's until I removed ENB mod and later SweetFX. I am now CTD free. 

Do you know a good 24 hour setting for SweetFX? I tried some settings but didn't really find the best. The best would be if the I could find the real night setting. Maybe something is wrong with my configuration within SweetFX

 

Hopefully someone familiar with SweetFX can help you.  Meanwhile, I would move the module to a temporary directory so you can enjoy FSX until you can find a solution.  There are several suggested and successful settings in the SweetFX posts in the FSX Forum.

 

Best regards,

Jim

Thanks you again I'll look for it 

I gave up on both of these mods once I've learned that I can finally enjoy FSX without CTD's, unfortunately at the expense of brighter nights but I can live with it. Performance and completion of flights matters to me more.

I gave up on both of these mods once I've learned that I can finally enjoy FSX without CTD's, unfortunately at the expense of brighter nights but I can live with it. Performance and completion of flights matters to me more.

I can understand you but I want something more REAL, therefore I really hate Microsoft. I experienced that Microsoft always just begins something but never finishes it. It's really annoying that you can't do anything.

 

Thanks  

Hopefully someone familiar with SweetFX can help you.  Meanwhile, I would move the module to a temporary directory so you can enjoy FSX until you can find a solution.  There are several suggested and successful settings in the SweetFX posts in the FSX Forum.

 

Best regards,

Jim

 

I tried with FXAA, but with the same result. I guess that something is behind the crashes, doesn't it?

But I can't find out what, because before I had FSX in compatibility mode this kind of crashes weren't. What may be the problem?

With ENB worked but just in compatibility mode. May I uninstall fully then back? 

I really don't see anything great about the ENB or SweetFX hacks.  Over at Guru3D.com where I think the ENB and SweetFX hacks originated, there are suggestions too.  It's strange you setup is crashing and others are having no problems.  I think placing FSX in compatibility mode could be the reason for your crashes.  FSX is fully compatible all the way up to Windows 8.  If you make it compatible for XP, then that's wrong as FSX was developed alongside Vista.  FSX was the reason why I immediately upgraded to Vista as I had heard Microsoft was supporting the new OS and there were advanced features that improved FSX performance over XP. 

 

 

 

May I uninstall fully then back?

 

I'm not sure what you mean by this statement.  Uninstall SweetFX or FSX?  To uninstall FSX you should follow the guide at the following link - http://support.precisionmanuals.com/KB/a87/how-to-uninstall-and-reinstall-fsx.aspx.

 

Best regards,

Jim

I really don't see anything great about the ENB or SweetFX hacks. Over at Guru3D.com where I think the ENB and SweetFX hacks originated, there are suggestions too. It's strange you setup is crashing and others are having no problems. I think placing FSX in compatibility mode could be the reason for your crashes. FSX is fully compatible all the way up to Windows 8. If you make it compatible for XP, then that's wrong as FSX was developed alongside Vista. FSX was the reason why I immediately upgraded to Vista as I had heard Microsoft was supporting the new OS and there were advanced features that improved FSX performance over XP.

 

 

I'm not sure what you mean by this statement. Uninstall SweetFX or FSX? To uninstall FSX you should follow the guide at the following link - http://support.precisionmanuals.com/KB/a87/how-to-uninstall-and-reinstall-fsx.aspx.

 

Best regards,

Jim

I mean while testing FSX the compatibility mode wasn't enabled so I ran without it, and yes gave better performance and I understood you. But my experience is that while in mode with ENB enabled the sim is running well but my only problem with mode is that GSX can't run in mode. So I have to fix this. I will completely uninstall the whole FSX. Gonna be long and tiring work. Now my FSX crashes after some hour (like 1:30...) but it's still not fixed.

Unfortunately you have to take the drastic action of uninstalling/reinstalling but sometimes it's the only solution to these strange FSX problems.  I recently went through it too when I had a SSD drive problem.  I am just about back up to where I was 3 months ago.  I took it slow and easy and even ran fsx a few days without any addons.  It runs great with no addons!  Then I installed Acceleration.  Ran that a few days then started installing the addons.  Good luck!

 

Best Regards,

Jim

After reading through all this my best guess is the shader cache. I can remember getting CTD's all the time and couldn't figure out why until I discovered deleting shader cache fixes weird CTD's with FSX.

 

Here's what you do for Win7 (Other OS's may vary, check your path):

 

Open notepad and paste the below code (with your windows username of course) and save as "FSX ShaderCache Deleter.bat" or something like that.. as long as it's a .bat (batch file) on your desktop or someplace you'll remember. Then with FSX closed, all you have to do is double clicky and viola, shader cache is gone and will be rebuilt next time you start FSX. I can't tell you how much this helped me. I found that this only need done after a major change to FSX or especially after a video card change or driver update. Good Luck. If you want, you can navigate to the folders manually and delete them that way, which ever way you feel more comfortable with. I personally like batch files.

 

Also wanted to ask if you have gone through the CTD forums here..

UIAutomationcore fix for CTD's via clicking menus etc..

and
 this thread here, might help you out like many many others:

http://forum.avsim.net/topic/402872-pmdg-737ngx-crash-to-desktop-when-choosing-end-flight-even-on-a-fresh-and-clean-windows-installation-some-interesting-facts-i-found/

@ Echo off

del "C:\Users\YourUserNameHere\AppData\Local\Microsoft\FSX\Shaders" /Q/S>nul

 

After reading through all this my best guess is the shader cache. I can remember getting CTD's all the time and couldn't figure out why until I discovered deleting shader cache fixes weird CTD's with FSX.

 

Here's what you do for Win7 (Other OS's may vary, check your path):

 

Open notepad and paste the below code (with your windows username of course) and save as "FSX ShaderCache Deleter.bat" or something like that.. as long as it's a .bat (batch file) on your desktop or someplace you'll remember. Then with FSX closed, all you have to do is double clicky and viola, shader cache is gone and will be rebuilt next time you start FSX. I can't tell you how much this helped me. I found that this only need done after a major change to FSX or especially after a video card change or driver update. Good Luck. If you want, you can navigate to the folders manually and delete them that way, which ever way you feel more comfortable with. I personally like batch files.

 

Also wanted to ask if you have gone through the CTD forums here..

UIAutomationcore fix for CTD's via clicking menus etc..

and

 this thread here, might help you out like many many others:

http://forum.avsim.net/topic/402872-pmdg-737ngx-crash-to-desktop-when-choosing-end-flight-even-on-a-fresh-and-clean-windows-installation-some-interesting-facts-i-found/

@ Echo off

del "C:\Users\YourUserNameHere\AppData\Local\Microsoft\FSX\Shaders" /Q/S>nul

Before the full uninstallation I'll try as the last chance, but thanks anyway

Before the full uninstallation I'll try as the last chance, but thanks anyway

If you think about it, SweetFX and ENB are causing the crashes yes? I used both and now use SweetFX every flight and fly for as long as I want. It is so quick and easy to do it's worth a shot and much better than re-installing everything. Most all of us understand the frustrations. :wacko: