F**cking Texture Application!

Fun trick:

Go into build mode. Rez a cube. Go to texture select. Select a texture. Click okay.

Expected results: I dunno, every fucking side has the texture applied?

Observed results: 4/6 sides are picked at random to flash the texture in. The other two don't stick.

WHY IS TEXTURE SELECTION TOO HARD TO DO FOR SECOND LIFE'S BUILDING TOOLS?

I already have to put up with half a dozen other monumentally-fucking-annoying building bugs (rotation imprecision? Axes not updating when typing in numbers? more texture fucking weirdness? Come on now) in my daily runs. Now I have to fucking manually apply every single fucking texture face one at a time to make sure they stick?

You'll probably say packetloss. Fine, great, 0.1% packetloss between here and California. It shouldn't be doing this on a single six-sided cube. Even if there IS packetloss, it shouldn't be so fault-intolerant that it causes the textures to spas out.

Other fun trick: select, oh, 500 prims. Try to apply a texture on all of them. Notice how only 80% of them stick. Now, find the other 100 prim faces that are visible and are still fucking plywood.


#@$%@#%#%^#$@!@#!@#$!@#

Fuck.

And how.

Yep, I noticed, been happening a while now... I thought it was me...

Glad it's just not me.

Prevailing wisdom is that it's UDP packets or something freaking out and not applying the textures.

Whatever. This shit's been going on, and getting worse, since like 1.5. It's making building anything with a texture a pain in the ass.

If I can't even texture a single cube properly there's something seriously fucked with the network code.

Doubly so if the server won't update the texture after I select it AGAIN; there seems to be a 5-6 delay before the server allows another change in the texture after it screws up the first time.

Maybe we should all just learn from Maxx Monde and forget textures, just make everything shiny...

Yup, and the linked objects, when moved, are snapping back to the original position, again.

FIX DA BUGS ALREADY, KING PHILIP!

Highly aggrivating yes.... select bunch of prim surfaces... then SPAM the crap out of the apply texture , um this isnt to good is it

It is almost certainly that these are caused by requests to the central asset system to change an attribute of an asset that are getting silently dropped because the asset server is overloaded way beyond its design limitation and SL wasn't coded ever expecting the database to return "No can do".

Either something monumentally clever will need to be done to fix this - if my conjecture is correct - or this problem will continue to worsen until the expected but "undeclared" SL 2 rewrite is made.

This phenomenon has been noticed by others for a least the last year and has continually worsened. Many of LL's self critical public statements usually contain a reference to the poor scalability of the centralized asset server design decision in an otherwise highly scalable system design. Indeed, many of the undocumented server-side changes over the last year appear to be priority tweaks to better handle the demand on the central asset server.

These things are called "bugs" in the trade.


They are not "fun" to work on.

So they never get any attention payed to them.

Instead things like "floppy" prims are fun to work on.

And we see we get more "bugs" as a direct result of floppyness.




LL ....( insulting comment removed ) .... FIX the bugs.

There are now so many that building in SL has become a bloody chore where if you are not paying ABSOLUTE attention to what you are doing you can lose a days work in one move. ESPECIALLY WHEN TEXTURING.

These are the exact symptoms I've been experiencing for just over a year now - since the day 1.6 went live. And is a lot of the reason I stopped building.

Doing it on a single cube is way less fun tho. Try tinting or texturing a complex linked object to all one color about 3 or 4 times and you end up with some really psychadelic funkeh stuff.