Jump to content

JohnQGalt

Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by JohnQGalt

  1. For those having trouble with the memory fix, could it be a conflict with ENBoost? According to S.T.E.P. there's a problem:

     

     

     

    ExpandSystemMemoryX64 http://wiki.step-project.com/images/thumb/8/8e/Warning-Logo.png/20px-Warning-Logo.png Warning: It has been reported that this feature can conflict with "Sheson's Memory Patch 3.0" (now included with SKSE) by causing Skyrim to crash if the memory patch fix is used to increase Skyrim's initial heap allocation (Block 1 orDefaultHeapInitialAllocMB in skse.ini) higher than 512 in Sheson's Memory Patch or 768MB in SKSE. Therefore, if using the Sheson Memory Patch fix (either standalone or with SKSE), it is recommended to set ExpandSystemMemoryX64 tofalse. While this warning does not apply to everyone under all circumstances (me for example, running DefaultHeapInitialAllocMB=768), credible testing here on STEP supports the notion that setting EnableUnsafeMemoryHacks=truecan contribute to Skyrim CTD at startup when using sheson's memory patch. ~z929669 http://wiki.step-project.com/images/thumb/5/50/Ixian_Insignia.png/20px-Ixian_Insignia.png Talk 23:19, January 17, 2015 (EST)


    When set to true, this parameter changes some of Skyrim's memory allocation code to cache data at the 'top' of Skyrim's memory space (Windows default caches to bottom of memory space). According to Boris, this can reduce memory fragmentation and make better use of Skyrim's available memory, especially when running on 64-bit Windows; Vista or newer. Note:' for this parameter to work, ReduceSystemMemoryUsage must be set to true and EnableUnsafeMemoryHacks must be set to false (see below).

    ExpandSystemMemoryX64=(false, true)

    Please read these posts before posting support questions in the forums about this parameter! Don't be lazy!
    More of an explanation by Boris can be found here and by keithinhanoi here and here.

×
×
  • Create New...