Dunno you guys, but my FSX+ENB almost always crash when handling menus and popus inside the sim.

Wonder if there is a fix for that since ENB is awesome and can't really skip it.

 

Thank you.

http://forum.avsim.net/topic/273341-heres-the-apparent-fix-to-fsx-crashing-win-7-x64/

http://forum.avsim.net/topic/273341-heres-the-apparent-fix-to-fsx-crashing-win-7-x64/

 

I already have that fix applied and my sim doesn't crash, except with NBE.

So what I'm asking is for a workaround for it, I don't know, maybe there is a tweak in the ini file, a different dll?

You can try copying "d3dx9_26.dll", "d3dx9_40.dll" and "d3dx9_43.dll" from SysWOW64 and put them into your FSX root directory. It seemed to have cured my problems with enb crashing but YMMV.

yep - its called SweetFX

Try deleting the version you are using (all files) and replace it from one of these:-

 

http://www.realenvironmentxtreme.com/forums/index.php?/topic/14771-natural-enbplus-download-included/

 

http://www.realenvironmentxtreme.com/forums/index.php?/topic/16014-sunlight-enbplus-download-included/

 

http://www.realenvironmentxtreme.com/forums/index.php?/topic/6396-bluesphere-enbplus-download-included/

 

The third one is nice. There are many versions around, some good, some not so good and some downright troublesome.

 

So, whatever route you take, lose the files you have onboard at the moment and start looking for others. JV at ORBX has some posted.

Try deleting the version you are using (all files) and replace it from one of these:-

 

http://www.realenvironmentxtreme.com/forums/index.php?/topic/14771-natural-enbplus-download-included/

 

http://www.realenvironmentxtreme.com/forums/index.php?/topic/16014-sunlight-enbplus-download-included/

 

http://www.realenvironmentxtreme.com/forums/index.php?/topic/6396-bluesphere-enbplus-download-included/

 

The third one is nice. There are many versions around, some good, some not so good and some downright troublesome.

 

So, whatever route you take, lose the files you have onboard at the moment and start looking for others. JV at ORBX has some posted.

Thought I would try again as I used to have crashes. Tried REX, works no CTD and looks sensational! thanks for posting this

Thanks Jordanchin and dogtrack, will try it next flight.

I used ENB on my prior rig with a GTS250, older drivers (182.xx's) and the older eNhancer (prior to Inspector) and never had any crashes or problems with ENB.

 

Then back in July I build a new rig with a GTX670FTW using the 301.42 drivers and Inspector and MSI Afterburner to control the fan speeds. I started experiencing some crashes while using ENB, which I never had a problem with on my last rig.

 

Turns out after doing some research that using MSI Afterburner in conjunction with ENB is what was causing the crashes. One I turned off Afterburner the crashes went away with ENB. 

So, in short, if you're using Afterburner or any software (other than Inspector) to control your fan speeds or overclock your GPU then it could be worth a shot to disable that hardware and see if your ENB crashes stop. Worth a try anyway.

Thank you, actually I was using an AMD card which I sold, I'm waiting for a new Nvidia atm.

Unfortunately nothing worked.

Still looking for a fix, thank you.

I use the payware program called Shade which does the same thing and so far no crashes.  It has a high learning curve though.  Think it is less than $10.  It might avoid many frustrations.

 

Best regards,

Thank you Jim, tried it already, unable to get even close to what ENB provides.

I found the "window to full screen" fix in the avsim guide, made a couple tests in windowed mode and sim didn't crash.

Do you guys run FSX in a window or fullscreen?

 

 

Do you guys run FSX in a window or fullscreen?

 

Always fullscreen mode.

 

I cannot give up on ENB. I just looks too amazing and realistic. Since it is always a "d3d9.dll" related error I am thinking of the payware program "DLL-Files Fixer" from this website: http://www.dll-files.com/fixer/ . Could this program fix the frustrating "d3d9.dll" error? What do you guys think?

 

Thank you