|
bucky Barkley
Registered User
Join date: 15 May 2006
Posts: 200
|
09-04-2006 09:53
I'll shorten up a previous question ...
I want script access to a lot of inventory items - more than 50-75.
Currently, 1 prim/1 script/1 set of inventory runs out of memory.
What strategies seem to work well for access to a lot more (in chunks
of, say, 50 at a time?) - think of switching off sets of textures.
* are you throwing inventory into one big pot, and only looking at
a subset at a time?
* are you divvying it up into different prims, and switching off which
one(s) are the supplier?
* are you doing something else, such as a remote object that spits out descriptions
and keys via llSay()?
|
|
Strife Onizuka
Moonchild
Join date: 3 Mar 2004
Posts: 5,887
|
09-04-2006 09:54
It really depends what you are doing with the inventory. Why do you need to store the names in script memory?
_____________________
Truth is a river that is always splitting up into arms that reunite. Islanded between the arms, the inhabitants argue for a lifetime as to which is the main river.
- Cyril Connolly
Without the political will to find common ground, the continual friction of tactic and counter tactic, only creates suspicion and hatred and vengeance, and perpetuates the cycle of violence.
- James Nachtwey
|
|
bucky Barkley
Registered User
Join date: 15 May 2006
Posts: 200
|
09-04-2006 10:37
From: Strife Onizuka It really depends what you are doing with the inventory. Why do you need to store the names in script memory? Dialogs - I want the user to be able to easily browse the names within a current set of textures. I have a controller which maintains the list/mappings of descriptions to keys. |