Hey everyone,
I've emailed boris about this issue but thought i'd post this issue in the forums for further support.
So I discovered ENB yesterday, and have been playing Burnout Paradise (v0.0075b of ENB) virtually non-stop, this is a fantastic piece of software. However, the supplied effects.txt provided overwhelming chromatic abberration, so I removed it from the directory with great results, the game looks amazing.
I then downloaded a different effects.txt alongside a different enbseries.ini from a thread in this very forum, and placed them into the Burnout Paradise directory. The resulting graphics are far from what I expected, (intense blooming and oversaturation) and I then replaced the downloaded enbseries.ini file with the original that came with ENB in the zip file that I downloaded to install ENB.
Here is the problem: Ever since I introduced ENB to the downloaded version of enbseries.ini, ENB has decided to hard-code that enbseries.ini into itself and load those values upon opening Burnout Paradise. I have re-installed, deleted and re-copied everything, but nothing seems to work.
ENB is loading the values in the enbseries.ini I downloaded (and have since deleted - it isn't on my harddrive anymore) and completely ignoring the values inside the enbseries.ini which is in the Burnout Paradise directory. I have searched my computer, and there are no external files that I can see. I don't understand how ENB can use values that don't exist? How can it memorize the values within itself and disregard the true enbseries.ini file? Now I can no longer use ENB with burnout paradise, as it continues to load the previous values. There's nothing I can do to modify ENB's output.
Also, removing enbseries.ini from the directory and leaving solely the d3d9.dll file will still make ENB work with the "default" values, and will not create a new enbseries.ini file. The entire mod is working as though the enbseries.ini file I downloaded is still in the Burnout Paradise directory. Which it isn't.
Has anyone else had this problem? I've literally tried everything I can think of to fix it, I hope one of you can shed light on this.
ENB completely ignoring enbseries.ini and loading default
- Author
- Message
-
Offline
- Posts: 4
- Joined: 25 Jan 2013, 07:51
-
Offline
- Posts: 4
- Joined: 25 Jan 2013, 07:51
Re: ENB completely ignoring enbseries.ini and loading defaul
As it turns out, for some strange reason there was an alternative enbseries.ini that was being used. It was located in C:\Users\username\AppData\Local\VirtualStore\Program Files (x86)\Electronic Arts\Burnout Paradise\
There was nothing else in this folder but the enbseries.ini. It appears ENB automatically created this directory for the purpose of creating an external enbseries.ini file.
I have no understanding of this at all, so for those having the same problem - check your AppData folders. Anyway, it's started regarding the enbseries.ini file inside the actual burnout paradise directory so It's all good now.
There was nothing else in this folder but the enbseries.ini. It appears ENB automatically created this directory for the purpose of creating an external enbseries.ini file.
I have no understanding of this at all, so for those having the same problem - check your AppData folders. Anyway, it's started regarding the enbseries.ini file inside the actual burnout paradise directory so It's all good now.
-
Offline
- *blah-blah-blah maniac*
- Posts: 17558
- Joined: 27 Dec 2011, 08:53
- Location: Rather not to say
Re: ENB completely ignoring enbseries.ini and loading defaul
Mod don't make folders, it's game or some protection software changed default path. There is no solution to such issues with paths, not depends from mod.
_________________
i9-9900k, 64Gb RAM, RTX 3060 12Gb, Win7
i9-9900k, 64Gb RAM, RTX 3060 12Gb, Win7
-
Offline
- *sensei*
- Posts: 289
- Joined: 08 Dec 2012, 23:05
Re: ENB completely ignoring enbseries.ini and loading defaul
That's a windows feature failing with ENB for some reason. I suppose your Skyrim is installed into the "Program Files" folder? Windows tries to protect "Program Files" folder from... well, everything it seems. In short: when an application makes a request to write a file into the "Program Files" windows says "Ok", but actually stores the file in the "VirtualStore" folder.
_________________
i5 2500k@4.0ghz - 24Gb RAM - R9-290 4Gb Tri-X - SSD 240gb Intel 520 - Win7x64
i5 2500k@4.0ghz - 24Gb RAM - R9-290 4Gb Tri-X - SSD 240gb Intel 520 - Win7x64