Jump to content

Break the 128 array elements limit


niston

Recommended Posts

About 3 months ago I was cleaning out my game directory (it was a mess) and I found the ll_fourplay.ini file. I had no idea what it was and thought it was a virus or something. I did my usual Google search and found out that it was created by AAF. I found a post that discussed how this number can be manipulated and benefit the game. I am not a programmer so my eyes pretty much glazed over the post.

 

Mine has been set up as follows:

 

[Custom Arrays]
uMaxArraySize=2000

Should I change that and lower that number. I ask this in that whenever I create even a single settlement, my game performance decreases exponentially. With each settlement created, performance within settlements decrease and eventually that becomes a game wide issue. I do have a MOD that allows me to build more than the game cap allows for a settlement. I use to set it at 30, but realized that I really did not need that much and since I was having settlement problems, I do not go over 4 times.

 

My question is two-fold, 1. should I reduce the uMaxArraySize?

Because this ini is in there, is there anything else I need to do or is it automatically benefiting my settlement building?

 

I did find this blog on the site that should not be mentioned:

 

https://$%^&*00/topic/81889-devtestbeta-ll-fourplay-community-f4se-plugin-v40-2021-06-01/page/8/

 

Just replace the symbols with the name of the website.

 

P.S. niston, I have seen your avatar before in several posts. Just love that actor.

Link to comment
Share on other sites

My question is two-fold, 1. should I reduce the uMaxArraySize?

Because this ini is in there, is there anything else I need to do or is it automatically benefiting my settlement building?

 

The increased array size will not automatically benefit anything. It allows arrays to potentially grow beyond 128 elements, but something has to happen to cause the array to grow that big.

 

To keep it really simple, scripts generally use arrays in one of two ways:

  • Fixed-size arrays. The size is set in the script and it won't grow or shrink. These are never bigger than 128, otherwise they wouldn't work in the vanilla game.
  • Dynamicaly-sized arrays. These are created with an initial size of zero, and the script adds to them as needed. Again, though, since the game is designed to work with the 128-element limit, the array won't grow past that unless you do something really unusual - a massive settlement with tons of vendors, etc.

If a settlement build works within the 128-element limit, it will work exactly the same, consume the same amount of memory, etc, with a 2000 element limit. It won't grab more resources just because it can.

 

AAF needs arrays of that size because of the way it loads and stores animation data from its XML configuration files. Most scripts never have any need for that many elements.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...