Keith, I can't promise any kiler settings, but here is my cfg file for enb. I've been using this one for several months and largely forgotten what tweaks I used. However, I found most of the stock cgf files had two problems. 1, they were to extreme and 2, they had a bit of a framerate impact. These tweaks made it more realistic for me and has no framerate impact. Just be aware that results are very system dependent, but if it doesn't give you what you want, just delete it. [PROXY]EnableProxyLibrary=0InitProxyFunctions=0ProxyLibrary=[GLOBAL]UseEffect=1AlternativeDepth=1AllowAntialias=1BugFixMode=0SkipShaderOptimization=0QuadVertexBuffer=0EnableShaders_3_0=1UseMRTRendering=0AdditionalConfigFile=enbseries2.ini[EFFECT]EnableBloom=1EnableOcclusion=0EnableReflection=0EnableMotionBlur=0EnableWater=0EnableShadow=0DepthBias=0EnableDepthOfField=0[iNPUT]KeyUseEffect=123KeyBloom=120KeyOcclusion=121KeyReflection=122KeyCombination=16KeyScreenshot=44KeyShadow=119KeyWater=118KeyShowFPS=106[REFLECTION]ReflectionPower=70ChromePower=70UseCurrentFrameReflection=1ReflectionQuality=1ReflectionSourceSpecular=30ReflectionSourceTFactor=30UseAdditiveReflection=1ReflectionDepthBias=0UseLowResReflection=1ReflectionSinglePass=1UseEnvBump=1EnvBumpAmount=70EnvBumpOffset=70ReflectionFlip=0[bLOOM]BloomPowerDay=4BloomFadeTime=400BloomConstantDay=1BloomQuality=0BloomScreenLevelDay=55BloomCurveDay=0BloomPowerNight=20BloomConstantNight=2BloomCurveNight=0BloomScreenLevelNight=25BloomAdaptationScreenLevel=30BloomAdaptationMultiplier=40BloomAllowOversaturation=1BloomMaxLimit=90[sSAO]UseFilter=1OcclusionQuality=2FilterQuality=1DarkeningLevel=30BrighteningLevel=26IlluminationLevel=32AdditiveIlluminationLevel=28UseAmbientOcclusion=1UseIndirectLighting=1FadeDistance=50UseForAlphaTest=0UseForAlphaBlend=0 DarkeningAmountDay=25ScreenLevelDay=60ScreenLevelNight=1DarkeningAmountNight=11GammaCurveDay=0GammaCurveNight=-2ColorSaturationDay=2ColorSaturationNight=0UsePaletteTexture=0[WATER]UseWaterDeep=0WaterDeepness=10WaterQuality=0[sHADOW]ShadowFadeStart=30ShadowFadeEnd=870ShadowAmountDay=80ShadowAmountNight=30ShadowScreenLevelDay=50ShadowScreenLevelNight=20ShadowQuality=1UseShadowFilter=0FilterQuality=2ShadowBlurRange=25[ENGINE]ForceAnisotropicFiltering=1MaxAnisotropy=16ForceDisplayRefreshRate=0DisplayRefreshRateHz=60[MOTIONBLUR]MotionBlurQuality=1MotionBlurVelocity=0MotionBlurRotation=0[PERPIXELLIGHTING]SpecularColorMin=0SpecularColorMax=100SpecularColorMultiplier=75SpecularGlossinessMin=0SpecularGlossinessMax=80SpecularGlossinessMultiplier=80[DEPTHOFFIELD]DOFQuality=2DOFNumberOfPasses=1DOFFocusRange=55DOFBlurinessRange=10

Thanks very much for this but I was more referring to killer settings for the new mod FXAA_PPI_Rev_37not ENB, cheers anyway. I am hoping to get as good as effect from FXAA_PPI_Rev_37.zip that I can get from ENB

Thanks very much for this but I was more referring to killer settings for the new mod FXAA_PPI_Rev_37not ENB, cheers anyway. I am hoping to get as good as effect from FXAA_PPI_Rev_37.zip that I can get from ENB

Keith I have a posted a snapshot of the FXAA with a Baron 58 and bloom to 6 check the cloud edges there is a dark line and even all over the aircraft.

Keith I have a posted a snapshot of the FXAA with a Baron 58 and bloom to 6 check the cloud edges there is a dark line and even all over the aircraft.

HI, yeah clearly something is not right there, as this is a new thing I dont know what to advise. It would seem to me that one particular setting is at an extreme. I dont think justr adjusting bloom would casue this. Suggest going back to default settings and starting over. Sorry cant be more help. When I get time I am going to invest some time and try and get some good settings and then post them here.

Keith, I can't promise any kiler settings, but here is my cfg file for enb. I've been using this one for several months and largely forgotten what tweaks I used. However, I found most of the stock cgf files had two problems. 1, they were to extreme and 2, they had a bit of a framerate impact. These tweaks made it more realistic for me and has no framerate impact. Just be aware that results are very system dependent, but if it doesn't give you what you want, just delete it. [PROXY]EnableProxyLibrary=0InitProxyFunctions=0ProxyLibrary=[GLOBAL]UseEffect=1AlternativeDepth=1AllowAntialias=1BugFixMode=0SkipShaderOptimization=0QuadVertexBuffer=0EnableShaders_3_0=1UseMRTRendering=0AdditionalConfigFile=enbseries2.ini[EFFECT]EnableBloom=1EnableOcclusion=0EnableReflection=0EnableMotionBlur=0EnableWater=0EnableShadow=0DepthBias=0EnableDepthOfField=0[iNPUT]KeyUseEffect=123KeyBloom=120KeyOcclusion=121KeyReflection=122KeyCombination=16KeyScreenshot=44KeyShadow=119KeyWater=118KeyShowFPS=106[REFLECTION]ReflectionPower=70ChromePower=70UseCurrentFrameReflection=1ReflectionQuality=1ReflectionSourceSpecular=30ReflectionSourceTFactor=30UseAdditiveReflection=1ReflectionDepthBias=0UseLowResReflection=1ReflectionSinglePass=1UseEnvBump=1EnvBumpAmount=70EnvBumpOffset=70ReflectionFlip=0[bLOOM]BloomPowerDay=4BloomFadeTime=400BloomConstantDay=1BloomQuality=0BloomScreenLevelDay=55BloomCurveDay=0BloomPowerNight=20BloomConstantNight=2BloomCurveNight=0BloomScreenLevelNight=25BloomAdaptationScreenLevel=30BloomAdaptationMultiplier=40BloomAllowOversaturation=1BloomMaxLimit=90[sSAO]UseFilter=1OcclusionQuality=2FilterQuality=1DarkeningLevel=30BrighteningLevel=26IlluminationLevel=32AdditiveIlluminationLevel=28UseAmbientOcclusion=1UseIndirectLighting=1FadeDistance=50UseForAlphaTest=0UseForAlphaBlend=0 [colorCORRECTION]DarkeningAmountDay=25ScreenLevelDay=60ScreenLevelNight=1DarkeningAmountNight=11GammaCurveDay=0GammaCurveNight=-2ColorSaturationDay=2ColorSaturationNight=0UsePaletteTexture=0[WATER]UseWaterDeep=0WaterDeepness=10WaterQuality=0[sHADOW]ShadowFadeStart=30ShadowFadeEnd=870ShadowAmountDay=80ShadowAmountNight=30ShadowScreenLevelDay=50ShadowScreenLevelNight=20ShadowQuality=1UseShadowFilter=0FilterQuality=2ShadowBlurRange=25[ENGINE]ForceAnisotropicFiltering=1MaxAnisotropy=16ForceDisplayRefreshRate=0DisplayRefreshRateHz=60[MOTIONBLUR]MotionBlurQuality=1MotionBlurVelocity=0MotionBlurRotation=0[PERPIXELLIGHTING]SpecularColorMin=0SpecularColorMax=100SpecularColorMultiplier=75SpecularGlossinessMin=0SpecularGlossinessMax=80SpecularGlossinessMultiplier=80[DEPTHOFFIELD]DOFQuality=2DOFNumberOfPasses=1DOFFocusRange=55DOFBlurinessRange=10

I'm a slow learner, have missed where this cfg's should be...!!! Can anyboby explain me where. Thank you.

I am very interested in this as, while I absolutely love the look of a tweaked ENB mod, it hates me and will go to a black screen at the worst of times. However, I just tried this and with the d3d9.dll in the FSX folder, FSX gives an error at startup and immediately quits. Has anyone else run into this or know where the problem may lie?

The same here. FSX will NOT open.

Cianpars, thanks for those enb cfg settings!

I have gone back to the default enb, but I will check the FXA as it has got some issue it may be just a sampling problem on my card.

HI, yeah clearly something is not right there, as this is a new thing I dont know what to advise. It would seem to me that one particular setting is at an extreme. I dont think justr adjusting bloom would casue this. Suggest going back to default settings and starting over. Sorry cant be more help. When I get time I am going to invest some time and try and get some good settings and then post them here.

keith, I found out what were those things on the cloud it was bool highQualitySharpen I had set it to 1, right now my bloom is at 7 but it does not look powerful like ENB but I am going increase it and check.

No such problem for me.I can only suggest the following Remove all ENB filesRemove all files and folders relating to FXAA_PPI_Rev_37.zipCheck FSX runsRe download FXAA_PPI_Rev_37.zipReinstall all files and folders from FXAA_PPI_Rev_37.zip directx9 folder to your main FSX directory

Thanks for your reply. I did all that and can verify it is the FXAA d3d9.dll that will cause it to not load. If that file is in FSX's directory, FSX will not start up

Thanks for your reply. I did all that and can verify it is the FXAA d3d9.dll that will cause it to not load. If that file is in FSX's directory, FSX will not start up

It happened to me when I by mistake put in the DX10 files. @Keith I set bloom = 9 looks nice and no fps hit or maybe 1.

Hmm, well I have a weird issue where the effects seem to be applied when looking at the free flight screen with the airplane preview, but when I launch a flight and actually get in-game I see no effects. Just the normal FSX display. Not sure what causes that.