The app will remember which slot you last saved/loaded so you'll never forget which one of your (possibly many) configurations you have active. This signifies that slot as the current 'active' configuration. When saving and loading configuration slots, you may notice that line will get highlighted. This will then enable this application to make use of those files when removing and even saving and loading. You can even add your own file names and folders list to this app, letting it use those uniquely named config files some mod authors like to use! If there are any left over files from any form of setups, just simply drag and drop the undetected files right onto the app and the 'files list' will update accordingly. You can then load them back in again when you feel you need something different, or to test out other configs with ease without losing your 'main' configuration setup.Īs far as I'm aware it removes ALL known versions of ENB, FXAA, ReShade and SweetFX config's.
It gives you 25 slots (or more if you use more than one config directory) to save your configs to. I got tired of having to look for the individual files used for both the ENB, FXAA, ReShade and SweetFX modifiers when testing them out, so I decided to write this small programme to find and delete all traces of all versions from a given directory. You can then load any saved configs directly to your game, quickly and efficiently. This app also lets you save your installed post processing configurations (ENBSeries for example) to a user defined destination. Maybe somebody here can shed a light on this, why this happens and how I can "solve it finally".This application can remove any known ENB, FXAA, ReShade and SweetFX configuration files from your chosen game directory, from the click of a single button. I don't say that it is an ENB bug no causilty but a correlation. I really would like to know the exact reason for this to happen. So for now, I've deactivated SSAO in the ENB settings and activated it in the Fallout ini.
I played around with the detailed options but without success. After some testing I found out that the ENB SSAO effect was the culprit in my case.
It was with a savegame that had a reproducable CTD at a specific spot that allowed me to do some testing after many many days of uninstalling, frustration, removing mods and (faulty?) textures, starting a fresh MO2 and so on. PRC ENB - Ultimate Immersion Preset (happend with several other presets, too)į4 and Mods (managed by MO2) installed on a secondary SSD Resolution 3440x1440 (with and without v-sync/fps limiter to 60 fps) I had random CTDs until yesterday and I want to share my solution.
0 kommentar(er)
