I have been trying the bloom mod Enbseries for a while but can't seem to get it to work consistently. I get the message initially re. the installed mod (top left of screen) when loading the flight, but then to me it does not look as though the effects are implemented. Also, when I try to switch it off/on using F12 nothing happens.Has anyone else experienced the ShiftF12 not working with this mod, and could suggest what the issue might be.My hardware should be quite capable of handling this mod.Quad core, GTX260 graphics.Cheers,Stuart

I have been trying the bloom mod Enbseries for a while but can't seem to get it to work consistently. I get the message initially re. the installed mod (top left of screen) when loading the flight, but then to me it does not look as though the effects are implemented. Also, when I try to switch it off/on using F12 nothing happens.Has anyone else experienced the ShiftF12 not working with this mod, and could suggest what the issue might be.My hardware should be quite capable of handling this mod.Quad core, GTX260 graphics.Cheers,Stuart

When you first start up FSX, in the startup screen where you see the aircraft rotating, it should show that the mod is enabled. If you don't see this screen, then it is not installed properly. It does not work in DX10 Preview. Hope this helps.Best regards,Jim

Stuart, are you running dual monitors by chance? The ENB mod can't deal with more than one monitor, and the result is a lot like what you're describing. I know because I chased my tail for years over this one until I figured that out.

*******'s ENB Series files do not allow me to use Shift-F12. However, the other ENB Series files I have tried do allow me to use it.

*******'s ENB Series files do not allow me to use Shift-F12. However, the other ENB Series files I have tried do allow me to use it.

you can actually set the activate/deactivate key in the enbseries.ini. I would hazard a guess that ******* changed the key command. Try f1 instead.

you can actually set the activate/deactivate key in the enbseries.ini. I would hazard a guess that ******* changed the key command. Try f1 instead.

Ahh, I was not aware of that. Thanks for the heads up, Ping.

Thanks for all the advice.I do see the text in the top left of the screen, so the Enbseries is enabled.I'll investigate the ini file and alternative key commend.Cheers,Stuart

On the subject of the key commands, it's pretty clear that they must be controlled in this section:[iNPUT]KeyUseEffect=20KeyBloom=232KeyOcclusion=232KeyReflection=232KeyCombination=16KeyScreenshot=232KeyShadow=232KeyWater=232KeyShowFPS=232(the above is from *******' enbseries.ini)What keys do those numbers correspond to? Say I wanted to assign KeyUseEffect (I assume that being turn on/off the mod while in FSX) to my F5 key, what number would I need?

What keys do those numbers correspond to?

The clever thing for me to do would have been to google for it BEFORE posting :( , but I'll explain my findings for anyone wondering:The numbers in the [iNPUT] section are decimal codes. Below is a table listing the hex values of various buttons on the keyboard:http://api.farmanager.com/en/winapi/virtualkeycodes.htmlThose hex values can be converted to decimal values using this converter.*******' command is Shift+Caps Lock. From the hex table, we see that Caps Lock's hex value is 14. This converts to 20 in decimal, and the value in his .ini:KeyUseEffect=20The decimal value for Shift is 16, and this goes into the line:KeyCombination=16That completes the Shift+Caps Lock combination. If you want to change the command, just look up the hex value on the table, convert it to decimal, and sub it into the .ini. It's worked for me!