Wierd texture glitch

I have noticed that if I make a prim and texture it, then put the texture inside, if I remove the texture from inside, the prim reverts to the default wood texture. Is there a way to stop this happening? I can't even figure out why it does it, as surely the texture on the outside of a prim and the texture inside are to unrelated things?

I've just tried this in-world and, yes, the texture reverts to the default plywood when I delete it in the prim's inventory. I checked the permissions on the texture, thinking that 'no mod' or 'no copy' might be the issue but it makes no difference even with full perm textures.

Bizarre. I'm sure this never used to happen.

Try deleting the texture with a script instead of the client? Does that make a difference?

Using a script to remove the inventory contents has the same effect of replacing the prims visible texture with plywood. I don't understand why removing it with a script would be any different to deleting it manually?

Workaround seems to be to use llSetTexture afterward (couldn't find a way around it)
Here it is in JIRA http://jira.secondlife.com/browse/SVC-3931

I think the problem is that it just should not be happening and I'm pretty sure that it didn't until quite recently. How many builders would understand enough to set the texture with a script? I'm pretty much a scripting thicko myself (I had to search Scripting Tips for the script to remove items from inventory) but I would have thought it appropriate that a texture *on* a prim should be treated very differently to an item *in* the prim - even if that is just a copy of the same texture.

If the client was doing it, then there would be a difference. This establishes that it's a server restriction.

I would imagine that most builders would set the texture by dragging the texture onto the prim, or onto a prim face, or onto the image well in the edit box, rather than into the prim's contents. It's only necessary to drag it into the contents if it's no-copy.

I placed the texture on the prim by dragging it into the window of the 'Texture' tab (dropping it into 'Contents' won't affect the appearance of the prim anyway). Then I dropped a copy of the texture into 'Contents'. The prim's texturing reverts to default if that texture is deleted manually or with a script. I don't see why the system has been changed so this should be the case.

I'm confused. For what purpose did you do that?

I suspect someone figured out a way to get a no-copy texture out of a prim without removing the texture from the prim faces, and so to fix this minor exploit LL broke things in the other direction. File a JIRA, I'll vote for it.

I was repeating the process described by the OP, which demonstrates the problem.


The permissions on the texture are of no matter in this case: I repeated the test with full perm textures as well as versions of all the variant restrictions but it was still no go anyway I tried.


Day Oh already filed a JIRA. See post #5 above.

OK, then I ask the OP, why were they putting the texture in the prim in the first place?
Yes. I know that. That's why I wrote "went too far the other way".

Haven't you noticed that content creators quite often put copies of textures in objects they create? I've never fully understood the point of this but it happens and the real point is why should it be happening?

I have occasionally seen that, and assume that they got in the habit some time they were working with a no-mod or no-copy texture and are just cargo-culting it.

Which is why I thought it might be worthwhile actually asking what the purpose of this odd behavior is.

I have free vendors for mainland maps. Inside is a prim copy of the map, the full perms texture (if I have it) and a couple of other things related. If I revise a map after discovering something new or a mistake naturally I put the new one in and remove the old one. Every time I do this the prim reverts to wood.

The reason I give the texture out full perms as well as the other stuff is in case someone wants to save it to their computer and edit it, maybe adding their sims location or something. I don't think the why is very relevant either lol.

Thanks for that. I added my vote.

So you don't know why people do it for random objects either. I'm talking about situations where, for example, you'll find a house with the texture for some of the prims (but not all) inside the prim.

I presume that they do it for people who might want to customise the structure by adding partitions or add other new parts, so the customer can match it to the rest of the structure. Houses aren't my kind of thing, so I don't really know to be honest.

I find the whole house concept rather weird myself. Why would someone want to sit in house watching TV when they have the option to do exactly the same in RL?

Interesting question.

To play MST3K =)

That's the second reference to this I've read in as many days so I had to Google it.

Sounds like a fun concept.