.Ini cuses a delay in opening buy/sell menu from npcs.

[aleksanderne]

Hi.

This simple line which i have used before in my ini, cuses the ingame buy sell menu to load very slow, delayd 10-15 sec.

Why?

iMaxAllocatedMemoryBytes=8589934592

[MShoap13]

That line belongs under the Papyrus Section and has nothing to do with how much memory Skyrim can address. It's how much memory the Virtual Machine Adapter (a.k.a. Papyrus/Script Handler) can address.

 

Quoted from CreationKit.com:

 

iMinMemoryPageSize

This is the smallest amount of memory the VM will allocate for a single stack page, in bytes. Smaller values will waste less memory on small stacks, but larger values will reduce the number of allocations for stacks with many small frames (which improves performance).

Default: 128

 

iMaxMemoryPageSize

This is the largest amount of memory the VM will allocate for a single stack page, in bytes. Smaller values may force the VM to allocate more pages for large stack frames. Larger values may cause the memory allocator to allocate differently, decreasing performance for large stack frames.

Default: 512

 

iMaxAllocatedMemoryBytes

This is the maximum amount of memory the VM will allocate in total for stack frames. If an allocation would push memory usage over this limit, the VM will instead wait for more memory to be freed. Increasing this value may improve performance in high-stress situations with lots of scripts running, but will use more memory. Note that it is possible to exceed this value temporarily while loading a save game due to slightly different allocation ordering.

Default: 76800 (75kb)

 

With that setting (8GB), Skyrim is never cleaning up scripts after itself. It could even be "running into a wall" with the Papyrus VM causing performance and stability issues... And since Skyrim is a 32 bit application it can't address more than 3.2 GB of System RAM, period.

Edited January 11, 2013 by MShoap13

[aleksanderne]

Yeah i know that it gose under the papyrus.

 

Wasn't there a patch allowing skyrim to use more?

 

I followed the ini creator on this website

http://online-source.net/tools/cfg-makers/skyrim-cfg-maker/

(if so that skyrim cant use more gig than the cfg maker needs to know of this.

 

I know manu users use the cfg maker, and its been update many times over.

So i find it a bit wierd that noe one has reported this on cfg maker's website.

 

But whats wierd is that i have used to have this pap setting to 16gb and it hasnt been a delay like this before.

[MShoap13]

That setting is not "Maximum amount of memory available to the game (in bytes)" as that "cfg maker" states it is. And no, there's no 32 bit application in the world that can use more, it's a limitation built-in to 32-bit. Yes, the 1.4 patch from Bethesda made LAA patches and such useless as the update included this, but no that won't let Skyrim use more RAM than what a 32-bit application can allocate to.

 

That setting is "How much RAM can the Papyrus (Script Handler) have before forcing it to clean up after itself". The default setting is 76800 (75kb); going much past 1 or 2 megabytes (1048576 to 2097152) is both pointless and a potential source of instability and performance problems. Papyrus is just the script handler, there's a LOT more going on in the game than these...

 

There's a lot of bad information out there regarding Skyrim Tweaks especially with memory and threading related settings.

Edited January 12, 2013 by MShoap13

[aleksanderne]

Yeah apparently there is.

Its good we have people like you than :)

Is there a place with a good description of each .ini setting?

 

 

You know a lot about ini settings it seems?

Could i ask for your help.

 

As i got 16GB 1866mhz memory i want to utilize this as best as possible.

 

What settings should i do?

I know its quit a comprehensiv question, but if you could list the settings i could increas to better utilize my mem that would be great.

 

Thank's a lot for your help.

[bben46]

This site has what I consider to be the best explanation of the Skyrim ini settings - and a lot more useful stuff - I recommend bookmarking it as you Will be back. http://www.tweakguides.com/ :thumbsup:

[MShoap13]

As BBen pointed out, TweakGuides.com (and more importantly, Koroush Ghazi, the guy behind that site) is one of the better sites to check for this kind of stuff.

 

However, Mr. Ghazi's Skyrim guide isn't available on TweakGuides. You'll find it here on Geforce.com though.

 

The STEP-Project.com forums aren't a bad place to discuss this stuff either.

 

You'll find Koroush's guide doesn't discuss the following settings because most of them have little to no noticeable affect on performance (if they aren't set improperly; setting them improperly can increase stutter/input delay/stability).

 

For the most part, "iNumHWThreads=xx" should only be messed with if you have more than four CPU cores (HT quad cores count). Even with a Hex/octa/HT-enabled CPU, you may see better results just omitting this line and using Process Lasso to set the default affinity of the program so that it only runs on the physical cores. You may see better results still, if you trim it down to two or three physical cores besides Core 0 (to free up I/O). This tweak is going to affect how smooth your game runs, not how many FPS it's reporting.

 

The "iHWThread#=xx" setting should probably be left alone. Believe it or not, Windows and Skyrim aren't completely incapable and if you use any external measures to set affinity, this is pretty much useless.

 

Some of the "bUseMultiThreaded____=" settings are useful (FaceGen and Trees) most of the others have no noticeable affect.

 

The other two Papyrus settings (iMinMemoryPageSize=xxx, iMaxMemoryPageSize=xxx) shouldn't be raised from default at all unless you're running a TON of scripts. Use powers of 2 here (256, 512) and start by doubling the min value, and if that feels smoother, double it again and test. I don't think pushing it past 512 bytes to 1kb is gonna do anything positive. The max value should rarely be raised outside of cases where your min value runs better beyond 512.

 

I personally run 256, 512, and 1048576 (1MB) for the "iMaxAllocatedMemoryBytes" setting.

 

/Edit: Disabling all Papyrus logging unless you're actively troubleshooting can have a pretty substantial affect itself. These are all turned off by default. The bEnableTrace setting has the biggest impact on stutter as it increases HDD usage.

Edited January 12, 2013 by MShoap13