texture in object vs UUID

I am wondering... which is quicker to load from script serverside? A texture inside the object, or UUID ?

What type of limits are on a texture UUID?

i was always curious about that too.
why some people use uuid and others textures. see it in alot of things, vendors so on

I don't think it makes any practical difference really. I've not seen this tested in a hardcore manner, but casually speaking, load times seem to be the same for me whether the item is being referred to by name or by UUID. They all refer to a single item on the asset server after all.

Less chance of texture theft when using UUIDs.

One advantage to doing it with UUIDs is that you don't have to have a huge inventory of texture items in the object. Even if you make the permissions on those textures really restrictive, someone can rip them out and use them in one of their own projects, which you may not be happy with. However, if your script just refers to the textures by UUID, no one can use that texture for anything else.

As mentioned above I find it helps not to have a huge amount of things in contents, so I tend to use UUID's where feasible ( If i have one or two textures I will put them in )

Reason for this is editting time - with 100 textures in a prim it can take half an hour upwards to go through and edit all the perms ( if you forget - as opposed to 5 minutes in inventory )

And editting one sinlge thing in the contents becomes a pain as you have to wait for the whole contents to reload before you can move onto editting the next.

Speed wize - I have always been under the impression that textures in the prim load faster - but that could just be an outdated urban myth.

Cool. I was told that you had to be online for a script to give an object via UUID, so I was worried that if I stay offline, the textures woudn't load.


I was guessing that the UUID is just a line of text in the prim file and adding texture objects just made a list of UUIDs inside the object.