TES Skyrim 0.251

[Oyama]

Saberus
Are you just working with the right shader ?
I know it sounds like a noob question , apologizes if so.
Lenz related codes have been ported to enblens from enbbloom some time ago.

[Jafin16]

Boris
Ah, I see it now. Very subtle. Thanks Boris!

[keithinhanoi]

keithinhanoi
ExpandSystemMemoryX64=false set because of some shit like Avast, to stop users bother me. But actually nothing changed.

Good to know!

And I promise to never bother you because I don't need to use crap like Avast, since I know which download button to click!!!

[jonwd7]

keithinhanoi
ExpandSystemMemoryX64=false set because of some shit like Avast, to stop users bother me. But actually nothing changed.

Except you'd be wrong, and you know you're wrong, so stop going on the defensive and blaming it on everyone else. None of us have "some shit like Avast".

I did absolutely nothing between the switch from 0.246 to 0.250 except for switch to the SKSE alpha, and lo and behold I can no longer use "ExpandSystemMemoryX64=true".

You said that you "compiled SKSE" yourself and that nothing is wrong. Did it dawn on you that you either didn't compile it correctly or you're not using 'skse_loader.exe' to load the game? The SKSE site has binaries to download you know. So the fact that you had to "compile it yourself" is suspect. It's an unnecessary step in replicating the issue. You should instead use the same binaries everyone else is using.

All I have to do is turn ExpandSystemMemoryX64=true. I run "TESV.exe" (NOT skse_loader) and what do you know, the game doesn't crash. I run "skse_loader.exe" and what do you know, the game crashes.

Is anyone blaming you? No. It's clear that the memory patch in SKSE alpha and your ExpandSystemMemoryX64 cannot work together. Instead of getting angry and saying we're wrong, how about investigating it properly instead of cussing at us.

And even sadder is that you talk about us in the SKSE thread at Bethsoft as if we're a bunch of morons, when you yourself haven't confirmed the issue correctly. If you resent us so much maybe you should stop.

[prod80]

jonwd7
Why not report to SKSE team, and use normal SKSE again and leave alpha for what it is ::: ALPHA
Alpha is meant for testing, not for stability. There will be problems. Boris is not at fault. Why does SKSE team even bother with memory features when ENBoost is around already boggles my mind.

Allocation higher 1st block... neat! To fix what? Users installing 4K LODs ending in ILS? How about picking normal size for LOD in first place and understand how game works.

This whole memory shit is just a joke, only ENBoost seems to do what it does, and SKSE/Sheson is building on its functionality. If their patch won't work with ENBoost speak to the people who wrote it, not to Boris. I see no post whatsoever of you in that thread. I use ExpandSystemMemoryX64=true, I even use sheson's .dll stuff just for seeing if there was a difference, and I tried without on win7 x64 and my game doesn't crash. So obviously something on your end is wrong or in SKSE Alpha for some users, maybe its not even related to SKSE's addition of sheson's code...

I also dont see 100s of raging posts going on with the function of ENBoost stopped to work. Neither in the SKSE forum. Boris will word it how he pretty well pleases, he already took the entire shitstorm on him when adding advanced features like ENBoost, so yes, he's fed up with it.

You even say it yourself:
"I did absolutely nothing between the switch from 0.246 to 0.250 except for switch to the SKSE alpha, and lo and behold I can no longer use "ExpandSystemMemoryX64=true"."

Why would Boris need to investigate this according to you is beyond me. Be happy that at least he tried.

/out

[sheson]

@jonwd7

Before starting to point fingers consider this: lots of people including me use skse 1.7.0 alpha and enboost 0.250 or 0.251 and there are no problems.

There is something else in play and it is not ENBoost with ExpandSystemMemoryX64=true or SKSE. What you see is a symptom not the cause.

[jonwd7]

jonwd7
Why would Boris need to investigate this according to you is beyond me. Be happy that at least he tried.

If you bothered to read my post, I'm pointing out that like always he defaults to who is "to blame". No one is to blame, and if you read that, you'd understand that if he's going to assign blame and make such claims then maybe he should actually look into the issue properly before doing so. Because Boris is putting the burden of proof on himself by making an absolute claim.

How just because SKSE is in "ALPHA" makes SKSE somehow more "at fault" is beyond me. It's again, not about BLAME, it's about the simple fact that something is preventing them from working together, and Boris is rejecting that notion with a defensive "it's not my fault, you're an idiot, you're using shit like Avast".

@jonwd7
Before starting to point fingers consider this: lots of people including me use skse 1.7.0 alpha and enboost 0.250 or 0.251 and there are no problems.

Only thing I'm pointing at is Boris's behavior. He believes that any bug report = the world is out to get him. He takes the defensive, and then he calls us names, belittles us, etc. until the next release where he realizes that we were (in some way) right.

It's very simple, skse_loader + ExpandSystemMemoryX64=true == crash, TESV.exe + ExpandSystemMemoryX64=true == no crash, skse_loader + ExpandSystemMemoryX64=false == no crash.

Whether or not you personally have the issue just implies that there is another INI setting at play, not "shit like Avast" as Boris so eloquently put.

And again, not sure how I'm "pointing fingers" if I clearly state that no one is to blame in the matter. You can't expect to have a dozen programs all touching memory allocation.

[jonwd7]

@jonwd7
Before starting to point fingers consider this: lots of people including me use skse 1.7.0 alpha and enboost 0.250 or 0.251 and there are no problems.

I took two minutes to figure out the cause:

Code: Select all

[Memory]
DefaultHeapInitialAllocMB=512
ScrapHeapSizeMB=256

Works. These are the default (vanilla) values in SKSE.ini. I know you know this obviously.

This doesn't work:

Code: Select all

[Memory]
DefaultHeapInitialAllocMB=768
ScrapHeapSizeMB=512

Meaning, anything but the defaults becomes useless, because they don't work with ENB's ExpandSystemMemoryX64=true. If the values are at their defaults, they're not doing much of anything anyway.

Does anyone need to fix this? No. I don't care because I'd rather use your memory patch than Boris's. I've had ExpandSystemMemoryX64 set to false since the first moment I installed 0.250 and it crashed, and I don't plan on using ExpandSystemMemoryX64=true again.

[sheson]

I will say this again: the problem you see is not just with ENBoost or SKSE. There is something else at play.
It may have to do with the fact that you set values in inis without understanding what you are doing.

Why not try the recommended values?
[Memory]
DefaultHeapInitialAllocMB=768
ScrapHeapSizeMB=256

You are jumping to conclusions after 2 minutes of "testing"...

This post concludes my offtopic discussion in this thread.

[thalixte]

Just to add my own experience. I am currently using skse 1.7.0 alpha + enb 2.51 with

Code: Select all

[MEMORY]
ExpandSystemMemoryX64=true
ReduceSystemMemoryUsage=true
DisableDriverMemoryManager=false
DisablePreloadToVRAM=false	
EnableUnsafeMemoryHacks=true
ReservedMemorySizeMb=256
VideoMemorySizeMb=0
EnableCompression=false
AutodetectVideoMemorySize=true

in enblocal.ini, and

Code: Select all

[Memory]
DefaultHeapInitialAllocMB=1024
ScrapHeapSizeMB=512

in skse.ini and i have no more CTDs. Sheson's fix works like a charm, as well as enboost, and there is no conflict between them.

The thing is, i had CTDS even with those fixes, but most of the reproductible CTDs were gone. Reminding CTDs were caused by a conflict between vivid landscape and moss rocks. This has since been corrected with a compatibility patch. But CTDs can still occurs due to bad meshes edits in some mods, or due to mod incompatibilities.

So, skse 1.7.0 alpha with sheson's fix and ENBoost do the job, if they are correctly configured. Check skse_steam_loader.log to be sure that sheson's fix is enabled, and check the memory block allocations with vmmap.