Best Answer keithinhanoi , 18 December 2014 - 06:08 PM
@TigerWolfe - If those two lines I mentioned in my previous are not in skse_steam_loader.log, then the heap block memory fix setting in your skse.ini wasn't read, plain and simple. Even your test with Memory Blocks Log confirms this.
So, I will go out on a limb and say that you have discovered your problem right there.
A majority of the times I've seen people claiming the SKSE implementation of Sheson's memory fix doesn't work either:
- did not actually have skse.ini in the correct location,
- had not updated to SKSE 1.7.1, or
- had set Windows to hide file extensions, and accidentally saved skse.ini as skse.ini.txt (as Nozzer66 points out)
SKSE will look for the skse.ini file in ... Skyrim/Data/SKSE/
Alternatively, if SKSE's script files have been installed as a mod in Mod Organizer, the .ini can be kept in there, in a subfolder named SKSE, like this:
I would suggest this method for storing the skse.ini because then you can edit it directly in MO - just click on the INI-files tab as seen in the above pic of the mod info window, and then choose skse.ini to edit right in that window.
Until you see those two lines in skse_steam_loader.log, and verified that block 1 can go over 256, there is honestly no use in looking at other reasons for the CTDs.
If your skse.ini is in the correct location but the heap size lines are still not appearing in skse_steam_loader.log let us know, and we can help troubleshoot why it's not working.
Regarding your iMaxAllocatedMemoryBytes setting - with absolutely no personal offence meant towards you, that is a ridiculously high number, and although not necessarily CTD-inducing, will almost guaranteed lead to Papyrus stack dumping, which means at best you get massive script lag, and at worst lots of scripts won't run or finish - in other words, things won't work as intended or expected.
I have just posted about this and the myth about another supposed "magical" game-fixing .ini setting in the Correct Enblocal Settings thread, here. I highly recommend reading it.
(Post edited to add one more reason why the SKSE implementation of the memory patch may not work - thanks to Nozzer66 for the reminder!!)Go to the full post