It's tough getting the right amount of bloom. I believe I'm using NickN settings for bloom, but I am wondering if there are others ones out there that other prefer (perhaps one that doesn't darken the night too much.) Post your enb-bloom settings here!

I too am looking for one that doesn't darken it up too much at night. I have to turn ENB off when the sun goes down.

Get rid of that thing, causes too many problems, and it´s weird looking, "vaseline lens" - the real world does not look like that!U want a "Playboy Centerfold Sim", huh???

Get rid of that thing, causes too many problems, and it´s weird looking, "vaseline lens" - the real world does not look like that!U want a "Playboy Centerfold Sim", huh???

If it weren't for the ENB mod, I would not enjoy FSX NEARLY as much as I do. The original look is very gamey. ENB can make FSX look extremely beautiful.

Get rid of that thing, causes too many problems, and it´s weird looking, "vaseline lens" - the real world does not look like that!U want a "Playboy Centerfold Sim", huh???

I agree with you. While it tends to double my FPS, textures don't look even half as sharp as they do without it.

If it weren't for the ENB mod, I would not enjoy FSX NEARLY as much as I do. The original look is very gamey. ENB can make FSX look extremely beautiful.

I agree 100%, I can't imagine not flying without it.However, I dont go for those overdone looking settings either where the ground is super dark and over saturated, or the clouds and/or white surface reflection is overly bright. I like to use it, but prefer to keep the settings fairly muted to make it still look believable. I've tried the settings from Tim at REX, John V. at ORBX, NickN's, and FengZ's. Tim's and John's were a bit overdone for my taste, I used Nick's for a while, then moved to Feng's. In the end, I ended up taking the settings I liked from each of those users and tweaking myself. I've gone to the lenght of comparing my settings to ariel photos, videos I 've made when flying, and ariel pics i've taken to get a pretty good baseline for a good all around look. I've spent who knows how many hours tweaking that thing, which fortunatley can be done on the fly without having to restart FSX everytime, but I think after all that time i've got a pretty good setting that looks good in a wide variety of settings and weather.Every now and then I will hit F-12 to shut it off to compare my settings, but for me the difference without it is night and day. My thanks to who ever the fellow was that originally made this available or known to use in FSX.

I agree 100%, I can't imagine not flying without it.However, I dont go for those overdone looking settings either where the ground is super dark and over saturated, or the clouds and/or white surface reflection is overly bright. I like to use it, but prefer to keep the settings fairly muted to make it still look believable. I've tried the settings from Tim at REX, John V. at ORBX, NickN's, and FengZ's. Tim's and John's were a bit overdone for my taste, I used Nick's for a while, then moved to Feng's. In the end, I ended up taking the settings I liked from each of those users and tweaking myself. I've gone to the lenght of comparing my settings to ariel photos, videos I 've made when flying, and ariel pics i've taken to get a pretty good baseline for a good all around look. I've spent who knows how many hours tweaking that thing, which fortunatley can be done on the fly without having to restart FSX everytime, but I think after all that time i've got a pretty good setting that looks good in a wide variety of settings and weather.Every now and then I will hit F-12 to shut it off to compare my settings, but for me the difference without it is night and day. My thanks to who ever the fellow was that originally made this available or known to use in FSX.

Have you documented your settings by any chance? Would love to see them if you have them. F12 shuts ENB off? Hmm have been using that keystroke to center my TrackIr for years now. Is the F12 command something added by default or is it coded somewhere within a .cfg or .ini?Thanks,Robert

Have you documented your settings by any chance? Would love to see them if you have them. F12 shuts ENB off? Hmm have been using that keystroke to center my TrackIr for years now. Is the F12 command something added by default or is it coded somewhere within a .cfg or .ini?Thanks,Robert

I've never posted them since it seems like it's always a work in progress. As soon as I think I have it like what I want, I go and tweek it again, lol. I think that I am pretty close and I can drop you a PM sometime with my settings. The only problem is that it may look different on your rig depending on how your monitor is setup.Yes, the F12 command is default in the ENB ini file, as well as some other key commands to take screen shots and display an FPS window, however I dont know how the numbers listed for the key translate to the actual keyboard keys. I have accidentally hit some of those keys at somepoint though because screen shots have shown up in my root FSX folder and I have also turned on the FPS counter and had to exit the flight since I couldn't figure out which key I accidentally hit.I always have to make sure that I dont assign any FSX or addon a/c commands to F12 so that I dont turn it off accidentally.

I tried it to see what all the hype was about....then promptly removed it. Did not see anything that was remotely realistic in any of the "pre sets" that I tried, including the NickN and Orbx settings.I have not seen that 'sheen' over saturated with light effect anytime I have flown in the RW. I find ENB makes FSX look MORE like a game. Each to their own of course.....

I'm using John Venema's settings with the day bloom values slightly reduced to eliminate that "blown out highlights" type look near the horizon:[bLOOM]BloomPowerDay=4BloomFadeTime=400BloomConstantDay=1BloomQuality=0BloomScreenLevelDay=75BloomCurveDay=0BloomPowerNight=18BloomConstantNight=2BloomCurveNight=0BloomScreenLevelNight=20BloomAdaptationScreenLevel=40BloomAdaptationMultiplier=50BloomAllowOversaturation=1BloomMaxLimit=100Only section that matters, the rest are off.

I wanted more of a nightime effect suggesting flying under a (near)full moon - darker than dusk but light enough to not run into a hill or mountain...[bLOOM]BloomPowerDay=4BloomFadeTime=500BloomConstantDay=0BloomQuality=1BloomScreenLevelDay=60BloomCurveDay=0BloomPowerNight=20BloomConstantNight=2BloomCurveNight=0BloomScreenLevelNight=30BloomAdaptationScreenLevel=40BloomAdaptationMultiplier=50BloomAllowOversaturation=1BloomMaxLimit=75Loyd

I've tried a half-dozen different enb-bloom settings and the frame-rate hit forces me to remove them. Some are not as bad as others, though. Is there a setting that anyone is using that does not have a significant hit in FPS? If so, please share!Thanks!

I've tried a half-dozen different enb-bloom settings and the frame-rate hit forces me to remove them. Some are not as bad as others, though. Is there a setting that anyone is using that does not have a significant hit in FPS? If so, please share!Thanks!

I gain a significant amount of FPS when using ENB. I stopped using it, because it made my textures less sharp, like I was viewing them through some sort of filter or lens. I believe I still have a copy of the .zip, I got it from an FS website, but it is labeled GTA: San Andreas when in you start FSX. It was like going back to FS9. :)

I gain a significant amount of FPS when using ENB. I stopped using it, because it made my textures less sharp, like I was viewing them through some sort of filter or lens. I believe I still have a copy of the .zip, I got it from an FS website, but it is labeled GTA: San Andreas when in you start FSX. It was like going back to FS9. :)

I've tried a half-dozen different enb-bloom settings and the frame-rate hit forces me to remove them. Some are not as bad as others, though. Is there a setting that anyone is using that does not have a significant hit in FPS? If so, please share!

I wonder if the problems you two have with it are due to the settings your using in the [GLOBAL] and [ENGINE] sections being set improperly. More specifically these settings in bold as taken as an example from John Venemas ini posted over at ORBX.[GLOBAL]UseEffect=1AlternativeDepth=1AllowAntialias=1 <- Nick has it set to 0 or off in his ENB guideBugFixMode=0SkipShaderOptimization=0QuadVertexBuffer=0EnableShaders_3_0=1UseMRTRendering=0AdditionalConfigFile=enbseries2.ini[ENGINE]ForceAnisotropicFiltering=1 <- Nick has it set to 0 or off in his ENB guideMaxAnisotropy=16ForceDisplayRefreshRate=0DisplayRefreshRateHz=60 <- Set to match your monitor refresh rateIf you compare these with what NickN has in his ENB setup guide you will notice that in the [GLOBAL] section he keeps AllowAntialias=1 set to =0 (off) and in the [ENGINE] section ForceAnisotropicFiltering=1 set to =0 (off). Also noted in Nick's ENB guide is to make sure that you have the DisplayRefreshRateHz=60 set to the correct value.On my rig with the AllowAntialias=0 <-set to off and ForceAnisotropicFiltering=0 <-set to off, as well as the DisplayRefreshRateHz= being set to match my screen, I get the same texture quality and FPS with the ENB turned on as I do with it off.Possibly the combination off these parts of the ENB ini settings, as well as the texture filtering settings used inside FSX and in nHancer/inspector, could explain the varience in performance between users?Maybe or maybe not, but it something you could test to see it it makes a difference in FPS and/or texture quality.

My thanks to who ever the fellow was that originally made this available or known to use in FSX.

I found a readme written by Boris Vorontsov who seems to be the one that was working on the mod for GTA.I have been reading with great interest over the last few days and thought that I would have another look at this mod. I finally had a chance today and found the enbseries.ini was not in my root FSX folder, I copied the .ini over from a back-up folder and applied the changes to the .ini, deleted my shader cache. When I press F12 the sim reverts to the top-down map view and Shift+F12 does not seem to do anything. There is a section named [iNPUT] but the values are numeric and not defined as using the "F" keys, after a search I found the valuea are called ASCII Codes and they are designated as follows:F1: 112 F2: 113 F3: 114 F4: 115 F5: 116 F6: 117 F7: 118 F8: 119 F9: 120 F10: 121 F11: 122 F12: 123 Now you can change the .ini file accordingly. **EDIT** After making a few settings adjustments things look good.