ENB Bloom

[todayshorse]

ok guys, Shift+f12 activates, but on my imac, shift+f12 does all sorts of things your regular keyboard does not, even using the 'fn' key - in game it turns the volume down, f12 is a volume key as is f10 and f11, with the 'fn'key (the 'fn' key on imac makes the 'f' key do what it should so to speak) it brings up the ATC menu in game. Is there a way to change how you activate this ENB bloom thing??

[Daube]

You can edit the enbseries.ini.
There is a section where all the "keys" are declared for each effect. Each key is designated by a numer, and the correspondence between keys and numbers are given in the readme (or on the website, I think)...

I just checked. One of the text files embedded into the archives is nammed "key_codes.txt". All the codes are written there, in hexadecimal format (they have to be written in decimal in the enbseries.ini, so think about converting them first).

[todayshorse]

Hmmm ok

thanx Daube. I dont really know a lot about decimal and hexadecimal, but ill certainly look into it 8-)

[Daube]

Check the Windows calculator (in your "accessories" in the start menu).
If you switch to "scientific mode", then you get the buttons DEC for decimal, HEX for hexadecimal etc...
Click on "HEX", write the value (numbers and letters), click on "DEC", the value appears in decimal (normal numbers).  8-)

[todayshorse]

Well, thanx again Daube but i think this Bloom thing wether its active or not seems to have ruined my FSX! :-/

Constant 'Fatal Errors - Windows will restart this programme' type things....usually within a few minutes of starting a flight and then using the menu......hmmm

Turns out its somthing to do with d3d9.dll, so as i popped that in the FSX folder when i put the bloom thing in, its now gone. No more 'Fatal Errors' - anyone else suffered from this or did i install it wrong?

[Daube]

Yes the bloom module can cause some instabilities in FSX, especially when using a wrong version of the module or when using some high video card settings (for example, the bloom module doesn't like the high antialiasing values, if I remember correctly).

I recommend using the module that was made for GTA San Andreas version 0.75.
Version 0.74 of this module should be avoided, for example.