Ah.... a fix!Just found this: www.classicwings.net/bloom.zipover at SO in a thread like this one.

Cool! Hope this works for all the white screeners! BEWARE though: the ini uses complete different settings!! So you might want to use this new dll with the ini from the 'old' rar!EDIT:On the other hand: maybe the new ini is even better... :(

The new .dll also makes bloom overpowered, even if you use the old .ini file! I guess the new .dll also changed the HDR :(. I have not gotten any problems yet, so I will stick with the old one.Edit: Wow it also reduces FPS a bit more than I like.

Pretty much my experience, I was wondering if it was only me...... Can anyone tell us what the fix is? Is it a reworked file, some different .ini settings? The zip seems to contain the same files as the original mod, so I am guessing it has been re worked. Will give it another go.....Dougal, what is "SO" ? I would be interested in looking at that thread... Do you have a link? thx

Sim-outhouse. http://www.sim-outhouse.com/sohforums/show...?threadid=15197

The new .dll also makes bloom overpowered, even if you use the old .DLL file!

I suppose you mean 'even when you use the old INI...? I won't be able to check it out until friday unfortunately... Maybe the overpowered bloom can be tempered with specific settings...

Well, this app really does not like my computer. Used the new files and first it crashed to desktop while loading the default flight saying it had run out of memory, then when it started 2nd time, same frozen performance, wierd artifacts etc. Needless to say, the 2 files were removed straightaway. Shame.

Just got the glitch. It is one of the weirdest I've seen, corrupting graphics even after exiting FSX. I guess it has something to do with HDR. Anyway switching to the new DLL!

The fix .dll is older (074) and does display perf reduction as well as different lighting.. The dll linked on the first page of the thread is 075Thats enough for me... no time to mess with it anyway.

The new .dll also makes bloom overpowered, even if you use the old .ini file! I guess the new .dll also changed the HDR :(. I have not gotten any problems yet, so I will stick with the old one.Edit: Wow it also reduces FPS a bit more than I like.

From what I gather this isn't a new or fixed dll but an old one...! Hence the extra loss in fps... Bummer...

I just tried the "fix" and it really screwed things up. Still had some white issues in full screen mode, I could see some stuff, but mostly white and frames became worse than a slide show. Still worked fine in window mode though. I'm starting to get the hint that this will not work in Windows 7 at all.

Agree that this add-on has a bit of a cost.I'm really liking Bert's and Randall's settings, only I can't tell the differences and I can't determine which is better. A little help??? :( Thanks!

Agree that this add-on has a bit of a cost.I'm really liking Bert's and Randall's settings, only I can't tell the differences and I can't determine which is better. A little help??? :( Thanks!

Just go with what looks good to you. I'm still playing around with my settings.

The older 074 version worked for me, wheras the newer one does not.OK here is my new .ini file for the older version (let's call it the v0.074 version as per what is displayed on startup).Couple of important points from my testing and tweaking:1. I found most of the tweaks from the newer 0.075 .dll also apply to the older v0.074 one, however, don't mix the two .ini files - just apply the 0.75 .ini tweaks on the same lines as found in the 0.74 .ini2. The [colorCORRECTION] section is IMHO the most important, and that's where you preserve a lot of the texture and colour quality, in particular these settings: DarkeningAmountDay=30 DarkeningAmountNight=15 ColorSaturationDay=13. The ColorSaturationDay=1 change is IMHO vital - anything less than 1 will reduce the colours to a dull desaturated look which sucks the life from the FSX textures. Anything more than 1 acts like a vibrance setting. I found 1 to be almost 1:1 perfect colour preservation, and 2 to create a very vibrant colour pallette. Anything more than 2 will look silly and cartoonish.4. These HDR .dll's really should not be used at dusk/night - I got a 5-6FPS hit at dusk/night and using SHIFT-F12 to compare, it looks better without it and performs better also. I think really this is a daytime effect and looks stunning from 2pm - 5pm (i.e. mid-late afternoon to pre-dusk). I expect post-dawn would look similarly nice as well5. Don't over-lighten the DarkeningAmountNight= value, because it will turn dusk/night into a washed out mess. I found a value of 15 gives me an almost 1:1 light ambience versus default6. The section[EFFECT]EnableBloom=1EnableOcclusion=0EnableReflection=0EnableMotionBlur=0EnableWater=0EnableShadow=0DepthBias=0only seems to recognise the EnableBloom=1 parameter. I tried EnableOcclusion=1 and I got CTD's. EnableMotionBlur=1 caused no crashes, but I did not see any motion blur effects. So I would leave only the first entry as it is. I have not played with the other parameters but I guess they were set to 0 for good reason ;)So here's my .ini for the (older) v0.074 HDR dll--------------------------------------------------[PROXY]EnableProxyLibrary=0InitProxyFunctions=1ProxyLibrary=[GLOBAL]UseEffect=1AlternativeDepth=1AllowAntialias=1BugFixMode=0SkipShaderOptimization=0QuadVertexBuffer=0[EFFECT]EnableBloom=1EnableOcclusion=0EnableReflection=0EnableMotionBlur=0EnableWater=0EnableShadow=0DepthBias=0[iNPUT]KeyUseEffect=123KeyBloom=120KeyOcclusion=121KeyReflection=122KeyCombination=16KeyShadow=119KeyWater=118[REFLECTION]ReflectionPower=100ChromePower=100UseCurrentFrameReflection=1ReflectionQuality=1ReflectionSourceSpecular=50ReflectionSourceTFactor=50UseAdditiveReflection=1ReflectionDepthBias=0UseLowResReflection=1ReflectionSinglePass=1UseEnvBump=1EnvBumpAmount=100EnvBumpOffset=100[bLOOM]BloomPowerDay=7BloomFadeTime=1000BloomConstantDay=1BloomQuality=0BloomScreenLevelDay=75BloomCurveDay=0BloomPowerNight=18BloomConstantNight=2BloomCurveNight=0BloomScreenLevelNight=20BloomAdaptationScreenLevel=40BloomAdaptationMultiplier=50BloomAllowOversaturation=1[sSAO]UseFilter=1OcclusionQuality=2FilterQuality=1DarkeningLevel=30BrighteningLevel=30IlluminationLevel=30AdditiveIlluminationLevel=30UseAmbientOcclusion=1UseIndirectLightning=1FadeDistance=50[colorCORRECTION]DarkeningAmountDay=30ScreenLevelDay=70ScreenLevelNight=1DarkeningAmountNight=15GammaCurveDay=0GammaCurveNight=-2ColorSaturationDay=1ColorSaturationNight=0UsePaletteTexture=0[PLUGIN]WeatherMod=0[WATER]UseWaterDeep=0WaterDeepness=20WaterQuality=0[sHADOW]ShadowFadeStart=40ShadowFadeEnd=80ShadowAmountDay=100ShadowAmountNight=30ShadowScreenLevelDay=60ShadowScreenLevelNight=20ShadowQuality=1UseShadowFilter=0FilterQuality=2ShadowBlurRange=30[ENGINE]ForceAnisotropicFiltering=0MaxAnisotropy=8ForceDisplayRefreshRate=0DisplayRefreshRateHz=60[MOTIONBLUR]MotionBlurQuality=1MotionBlurVelocity=0MotionBlurRotation=0--------------------------------------------------And some shots using the V key:These were taking during testing of various iterations of my .ini file, so the lightness and contrast varies a little between shots.Hope this helps folks who could not get the original .dll working.IMHO this is a wonderful addition to FSX and really breathes new life into the visuals. It's the bloom effect we were meant to have :)

Results are subjective, based on hardware installed and drivers.. tested the settings posted (thanks for the contribution John) Others may have better results. My 285 system uses the new DLL fine and without the perf hit but the result is not linear and therefore results are awesome in some scenes and not so great in others depending on several factors.It

Results are subjective, based on hardware installed and drivers.. tested the settings posted (thanks for the contribution John) Others may have better results. My 285 system uses the new DLL fine and without the perf hit but the result is not linear and therefore results are awesome in some scenes and not so great in others depending on several factors.It

I guess I will just follow from the sidelines, from a tech point of view, can anyone say why some of us are getting major graphics problems and how these are happening? Do you think it is an issue with specific drivers ? I was going to try swapping to the newest WHQL display drivers for my card (GTX280), but to be honest would rather not if not necessary. Does anyone else have any tips as to best drivers to use for FSX ? I am not into swapping drivers every time a new set appears. Thx, Mark