Jump to content


Photo

ExpandSystemMemoryX64=?


Best Answer hishutup , 19 February 2015 - 09:26 AM

I forget what the function of expandsystemmemoryx64 was called but I can tell you that it would do little anymore and what it did do wasnt really needed to start with.
I think a related function is like a mem defrag but there is a post somewhere that showed what it was.
I spent some time looking for the post and I can't seem to find it at this time. Go to the full post


  • Please log in to reply
6 replies to this topic

#1 uncleseano

uncleseano

    Thane

  • Members
  • PipPipPipPipPipPip
  • 393 posts

Posted 19 February 2015 - 04:06 AM

There was a recent debate as to which setting this should be set to. Mine is now ExpandSystemMemoryX64=false but I fear im losing out. I am using SKSE 1.7.1 Stable.

 

What is the general idea?


  • 0

#2 hishutup

hishutup

    Daedric Prince

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 2,610 posts

Posted 19 February 2015 - 09:26 AM   Best Answer

I forget what the function of expandsystemmemoryx64 was called but I can tell you that it would do little anymore and what it did do wasnt really needed to start with.
I think a related function is like a mem defrag but there is a post somewhere that showed what it was.
I spent some time looking for the post and I can't seem to find it at this time.

#3 TechAngel85

TechAngel85

    Akatosh

  • Administrators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 12,514 posts

Posted 19 February 2015 - 10:33 AM

It is really not needed. It basically forced ENBoost to use certain memory space. Testing has shown it to provide lil to no benefit.



#4 TirigonX

TirigonX

    Guard

  • Members
  • PipPip
  • 191 posts

Posted 19 February 2015 - 11:44 AM

I've turned it off too. Setting it true caused rare but reproduceable CTDs for me.


  • 0

#5 hishutup

hishutup

    Daedric Prince

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 2,610 posts

Posted 19 February 2015 - 12:13 PM

Found it
https://forum.step-p...guide/?p=109854

#6 uncleseano

uncleseano

    Thane

  • Members
  • PipPipPipPipPipPip
  • 393 posts

Posted 19 February 2015 - 01:41 PM

Wonderful thanks guys, feelin better about having dropped it so. Silly lil thing that is it. Ok so, maybe that really random and unreproducable CTD was in fact from that single value. Thanks again guys!


  • 0

#7 jonny6101

jonny6101

    Prisoner

  • Members
  • 3 posts

Posted 27 October 2016 - 04:51 PM

According to Kranazoli, "ExpandSystemMemoryX64 primary goal is to fix memory fragmentation issues which is very problematic thing in almost all games, fragmented memory reduce amount of really available free memory." Setting this to true can free up some memory for other game processes to use. Of course, setting this to false allows you to change the setting of Sheson's memory patch. If you use the Memory Blocks Log (also by Sheson, great modder this guy) that should tell you exactly how much memory your DefaultHeap is using. If you notice that it is less than the default 512 MB, then Sheson recommends lowering the value in his patch to free up some memory for other game processes (good idea). In order to be able to do this, ExpandSystemMemoryX64 must be set to false. On a personal note, I don't really recommend setting the memory patch value for DefaultHeapInitialAllocMB any higher than 768 as this takes that memory away from other processes. It really is users preference and up to your individual mod list as to what you should do with these values.


Edited by jonny6101, 27 October 2016 - 04:53 PM.

  • 0


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users