No Transfer on textures will NOW allow you to transfer on prims!

Would of been nice to of been told!
I was informed by a new texture store.
As long as all the prims on your build are set to Transfer it no longer applies that a texture with no transfer will stop your build from being transferable
Ive been creating & selling txtrs for years and selling them with trans as once over it used to be if you applied just ONE txtr to your build that didnt have transfer ticked it stopped your creation from being transferable

Can I have some confirmation on this recent discovery?
We at TRU have tested it over and over linking prims texturing with no trans txtrs and passing the linked object about to each other and its fine. What ever perms you set on the prim is not effcted by the txtrs perms

WHEN DID THIS HAPPEN?>

The L$ TRU has lost to txtr resellers and ppl giving them to friends amounts to hundereds of dollars and we found out by a noob texture store!


Been asking for this for years and years as has many other txtr stores but LL wouldnt budge
Seems they have made some changes and we're in the dark

Is it just us in the dark? Has this been common knowledge for some time now?

I think it's may have been that way for the last few minor releases, since 17.0. But I was quite unsure if it was a bug that LL intends to fix, or if it is a new feature we texture artists should be overjoyed to see. Blaze had a thread in Texture Tips about it, and at the time we thought it was a temporary bug.

I can verify that using a "no copy/no mod/transfer OK" texture on an item does not inherently make prims textured with that texture also restricted. As a test, I took a recently imported wall texture, left it at the "no copy/no mod/transfer OK" import defaults, textured a wall with it, and then sold that wall, as full perms, to an alt of mine that does NOT have mod rights or any special group memberships. He was able to copy the wall with no issue.

I have not yet tried a no-transfer texture on a prim article, to see if the prims could still be transferred.

Ideally, if we could set our textures to "no-transfer/no-mod/copy OK", that would eliminate a lot of the texture swapping and stealing. Even "no-transfer/mod OK/copy OK" would be an improvement. We would need to test though to see if derivitive textures, like someone buying a wall texture and adding an alpha-mapped window, would still be possible. I don't think you can copy a no-transfer texture to your hard drive to modify it.

Blaze's thread: /109/45/192640/1.html

So essentially they now treat textures as they treat scripts inside of objects? that's great if it works and I'm glad that TRU will now have a better way to do things rather than having to rely on a notecard based agreement since now the software can back it up.

Personally, before we change the perms on tens of thousands of textures, I want to hear from the Lindens that this change was intentiuonal and will remain in effect.

It will be enough of a nightmare as it is to change the perms on all the textures TRU sells, but it would be obscene if we did so, and then had to deal with SL changing again, to work the old way again, rendering any restricted textures fairly useless again.

I got an error, changed a texture I had full perms on, ticked it as no trans, transferred to an alt, then applied to a prim. Prim shouted "Cannot edit this" every time I put the texture on it. It didnt suffer any perms problems, though.

so yeah... I'd be a bit wary, it may be a bug they didnt expect.

its not a problem as long as you have full perms on the texture. You have that by default because you're the creator. I generally work with textures I have uploaded myself, so I always have full perms, and always leave them at the transfer default permissions. It's never been an issue on prims transferred to other folks. I've been selling things like that since I started selling nothing new

To display a texture, the client has to download it into its cache. Thus, any texture that is displayed can be fetched out of said cache easily when you know how to do it.

Also, obtaining texture UUIDs is a pretty simple task. Once you have a texture's UUID you can stick it on a prim using a simple script.

Matter of fact:
Not a single texture is safe from being copied/used regardless of the permissions set on it.

Like it or not but that's the way it is.

considering that a lot of people like to embelish textures if they are no mod your taking out half the purpose of it

Also i had bought textures from tru from a guy that was making them 1024x1024 and have to export the entire set to make them 512x512 so if i can't modify i wont buy will probably make em myself

Not texturing a building with oversized textures

Also clothing makers like myself might by a texture from time to time and export it and use it in clothing as a style/pattern for it. Remove some of the permissions might as well stop making things like leather and other things which usually have to be heavily modified outside the game to make them actually useful
.

If i was buying say a 3d texture cause i wanted to build a house exactly with those textures and never change any aspects of em its fine however if i got a package with 1024 sized textures I would be asking for a refund if there was no way for me to fix em so they are the right size

just my two cents

what you loose on one end you gain on the other