TES Skyrim 0.302

[Maeldun]

SA547
Boris isn't in the habit of performing silent updates and if he were to make such a change I am confident he would make it clear in a post. Your issue is caused by something else and incidentally, you can gain nearly the same amount of performance increase by leaving SSAO enabled and reducing scales. At least then you won't completely lose indirect lighting (which requires SSAO to be enabled).

Which explains why with 0.302 all the sudden the screen goes white and I have to turn on AO. For a long time I'm used to turning AO off for better gameplay performance and I was generally satisfied with this way.

[--JawZ--]

Actually he have made some silent updates in the past, but only when adding new features to allow new coding approaches, not something that is usable for a novice "ENB editor"/ENB usal user/ENB novice user. But never silent updates that causes issues without notifying it with a comment, never happened as far as I can tell from all silent updates I'm aware of.

And in this case I think it has more to do with end user setup error, as it is so far a single user posting such an issue and if it where in ENBSeries itself more people would have noticed this and reported it.

[number6]

First let me say that I am apprehensive about making this post since I just made a stupid mistake in this same thread, but it's the only thing that I can think of.

My game recently started to CTD upon loading heavy exterior cells. I assumed it was a mod issue and started reducing my load order. Nothing working and very frustrated, I finally tried reverting back to ENB .292 and eureka, it started working again. I tried several times switching between .302 and .292 and it's consistent in that .302 always CTDs and .292 always works. This is for a very heavy load order and heavy textures so the game is using two enbhost.exe processes to cover the memory. Here are my memory settings:

Code: Select all

[MEMORY]
ExpandSystemMemoryX64=false
ReduceSystemMemoryUsage=true
DisableDriverMemoryManager=false
DisablePreloadToVRAM=false
EnableUnsafeMemoryHacks=false
ReservedMemorySizeMb=512
VideoMemorySizeMb=12000
EnableCompression=false
AutodetectVideoMemorySize=true

I tried many different memory configurations with .302 and none will work without CTD for me. It looks like nothing changed with enbhost.exe recently, but maybe one of the new color filters or weather features is causing this? Boris, I'd like to run some test versions if you have the time to make them. Thanks for taking a look.

Edit: Actually, looks like there was a change in .279:

v0.279: Changed ENBoost memory manager by forcing memory statistics of the mod only to reduce issues with bad drivers and software.

[ENBSeries]

No changes made to ENBoost, so if any bug occurs, then it must happen for everybody and without any mods dependency. I can't fix things which i don't see.

[benhat]

boris, what do you think about SSAO "Sampling Range" parameter seperate for exterior/interior? i think, since the other parameter already are, it makes sense. my main point is about "indirect lighting" which gets better with higher sampling range in interiors.

[ENBSeries]

I will not do any changes to ssao/ssil, these are complete finalized effects and only replacement with radically new is possible.

[Hackfield]

First of all, I have deferred rendered disable, because I use msaa (sorry, but I can't play with aliasing, and neither enb's AA nor SMAA works for me, I still see the aliasing in fences and trees, even in loadscreens, and really annoys me)

For me, since 0.302, sometimes (probably half of the time) when I load a save, after the loading screen I get a completely black screen and an error, which is not displayed, but I can see it in the taskman.

This does not happen with 0.292, which loads perfectly every single time.

[ENBSeries]

Okay, but the only way to try to fix is via tests and as always all users with bugs will leave. Same story all the time.

[number6]

Not sure if my issue is the same as Hackfield's, but I would also like to test any versions that you make. You said that enboost.exe hasn't changed, but what about the release note from .279 that I quoted above?

[ENBSeries]

If you don't have issues with 0.292, why changes in 0.279 should bother you?