So, from what I read here, the enb HDR mod is the same as the enb series mod? Also, if they are the same, then why does it make my screen darker and a little blurrier, and it doesn't make it look like it has more light as in the angle of attack video?One last thing. When I do get the black screen, I press alt+control+delete and that fixes it for me. I think it will only work in windows vista and 7 because it works when I bring up the blue screen with alt+control+delete and then press cancel. Windows xp doesn't bring up this blue screen.

HiAnyone got a link to a download site for this HDR software?Thanks.

Hi Mike,http://www.mediafire.com/?jq0ouyd0mnjWorks fine with the HIGMEMFIX and FPS Limiter v 0.2 at my system.Best regardsJonathan

The thing is Scott, your experiences aren't necessarily the same ones that others will have with the enb. I can tell you that I 100% do not have any black screen/crashing issues when using it with highmemfix, regardless of how many times I need to access menus or alt+tab during a flight. As far as any image problems go, again there are others (myself included) that have completely managed to configure the settings to provide a realistic image, both at day and during the night, without any anomalies. It's very unfortuante for those of you who do have unresolvable issues, but I think we'd all get bored of FS if everything always worked perfectly!

Same here. Using highmemfix with ENB and FSWC with no problems anytime, including switching screeen from full to windowed.

You really get out of the ENB only what you're prepared to put in to configuring it. It's unfortunate that not everyone can come up with perfect settings, but it does take a hell of a lot of time to do. Of course the settings have to be tailored to an individuals personal preference of what looks realistic, monitor settings, as well as (most importantly) each sky texture that you use, as these will change the effects immensely. For this reason sharing .ini settings is virtually pointless unless the exact sky textures it was configured for are also shared. It does take a lot of work to get it configured, but is well worth it if you can find the time and energy to do so.

I agree 100% with that statement.I've spent an inordinate amount of time tweaking it and testing with a variety of different REX sky sets and weather conditions. I've even gone as far as taking real world photos of the sky and then tweaking the ENB mod to match that and to reflect what would be a good all around setting based on a normal day and regular fair weather. I'm to the point now that I don't think I can tweak it anymore or get anymore of a realistic look out of it based on real vs. compare photos.Unfortunately what settings work well and look realistic for one probably wont work the same for someone else if they aren't using the same sky textures and their monitor is adjusted differently. I've got mine dialed in pretty well now, but if I change the sky texture set then the sky wont look right at all until I readjust the ini. Getting the night time to look good wasn't that hard using fairly flat settings, but most of the ini's i've tried made the night look way too dark.It's a great tool and adds a lot of realism if and when you get it setup well.Sean Campbell

Guys:1. ENB is a DirectX **9** hook dll - it can't possibly work in DirectX 10 mode.2. I've seen no problems at all with Alt+Enter, HIGHMEMFIX=1 or using the antilag FPS limiter while using ENB. To get the antilag to work you have to use the PROXY section of the ENB ini to load it because the files normally have the same name since they're both d3d9.dll hooks. I just renamed mine to antilag.dll and used that name in the PROXY section. Works great (thanks to whoever that was in another thread who made me aware of that feature.)3. Black screens and stuff could also be the fault of the UIAutomationCore.dll thing - make sure if you're on Win7 x64 you have the replacement file for that - put it in your root FSX folder:http://dl.dropbox.com/u/28441/UIAutomationCore.zip

Guys:1. ENB is a DirectX **9** hook dll - it can't possibly work in DirectX 10 mode.2. I've seen no problems at all with Alt+Enter, HIGHMEMFIX=1 or using the antilag FPS limiter while using ENB. To get the antilag to work you have to use the PROXY section of the ENB ini to load it because the files normally have the same name since they're both d3d9.dll hooks. I just renamed mine to antilag.dll and used that name in the PROXY section. Works great (thanks to whoever that was in another thread who made me aware of that feature.)3. Black screens and stuff could also be the fault of the UIAutomationCore.dll thing - make sure if you're on Win7 x64 you have the replacement file for that - put it in your root FSX folder:http://dl.dropbox.co...omationCore.zip

My build is a week old, running highmem, and the FPS_Limiter 0.2, Im going to give the ENB a go tonight, I suspect I should be trouble free based on what i have read here, and else where. I will post my results for those interested. Is there another limiter named antilag FPS limiter that I should be using instead?

I remember Jesús Altuve saying ENBSeries breaks HIGHMEMFIX and that the ENBs dll needed to be patched for it to work.I removed it because FSX crashed on me day in and day out, and it's also puts quite an extra strain on the GPU, with very apparent effect on performance at high AA levels. I'm not trading SGSS for ENB, but that's just me

Doesn't ENB break Alt+Enter?

It does for me, and a few others with a system simliar to mine (namely, 64bit Win7).When I was on 64bit XP, I was able to change from full screen to windowed mode without issue, but ever since I installed win7 64bit, I get a CTD. I have tried numerous tricks to get it to work, but to no avail.I miss this effect, and seeing it in action on Nick's video around ORBX washington state makes me sad.

Guys:1. ENB is a DirectX **9** hook dll - it can't possibly work in DirectX 10 mode.2. I've seen no problems at all with Alt+Enter, HIGHMEMFIX=1 or using the antilag FPS limiter while using ENB. To get the antilag to work you have to use the PROXY section of the ENB ini to load it because the files normally have the same name since they're both d3d9.dll hooks. I just renamed mine to antilag.dll and used that name in the PROXY section. Works great (thanks to whoever that was in another thread who made me aware of that feature.)3. Black screens and stuff could also be the fault of the UIAutomationCore.dll thing - make sure if you're on Win7 x64 you have the replacement file for that - put it in your root FSX folder:http://dl.dropbox.co...omationCore.zip

Ryan can you elaborate on this a little more? what exactly am i putting in the proxy section?Jamal

Installed EMB, FSX crashed within 30secs I have a multi monitor setup which may be the cause.

@TabsWhere should I put the UIAutomationCore.dll for W7 x64 ?There isn't any dll. with the same name in the FSX folder, and on my C: drive there are 6 with the same name.Thank You!Jonathan Huschle

Hi Mike,http://www.mediafire.com/?jq0ouyd0mnjWorks fine with the HIGMEMFIX and FPS Limiter v 0.2 at my system.Best regardsJonathan

Thanks JonathanGot it, & using it. Thamk you very muchMike