Second_Life_1-23-0-118378_ReleaseCandidate problems

Try going into PREFERENCES (CTRL-P) and Graphics, click the ADVANCED button in the lower right, then uncheck ENABLE VBO.

Hope that does the trick, I was getting some weirdness myself when I logged in today.

What do you mean? Is there a relationship?
Thx

The reason they're changing the way avatars with unbaked clothing texture show up was because people were downloading the raw clothing layers of clothes that hadn't been baked yet. By requiring the texture to be baked, people will have to at least buy the outfit before they can rip it off... though that won't happen until 1.23 is a required download.

Sorry to be so dense. But are you saying that this happens when someone is wearing a skin that they did not pay for? Are only 'paid for' skins baked? I can't imagine that my friend would do this.
Thx,
BT

Oh, sorry.

Currently, when someone first logs in, their client downloads all their clothing layers and "bakes" them into a single set of textures. That way when someone looks at you they only need to download the combined textures... not all the clothing layers separately and combine them themselves. Other people around them wouldn't see them until this was finished, except their client is allowed to download those textures as well and bake them locally until the official baked texture is finished. That's why it says "your clothing is still downloading but other people can see you normally".

Once this change is made you will only be allowed to download your own textures unbaked, so if you want to rip an unbaked outfit you'll have to buy it.

They're turning an optimization into a kind of security-by-obscurity trick to make clothing creators think they're actually doing something effective against pirates.

It's only a secondary thing, it's really part of a more ambitious plan. The real change later on is to dump the current texture system and replace it with a more streamlines version that uses HTTP instead of UDP, and reduces the variety of places the system has to look to find object and avatar assets.

The overall plan is at http://wiki.secondlife.com/wiki/Texture_Pipeline_Improvements

The avatar portion of the plan is this:



Simplification of the rendering pipeline is the primary goal there, and the protection thing is only a "somewhat" because there are of course still multiple workarounds.

The default baked texture is apparently still a work in progress, or if it is is already in place, 1.23 is not rendering it. It's possible that somebody decided that Ruthclouds were good enough.

The "move through texture pipeline" part isn't done yet either. When that gets implemented a lot of this ghost business should go away.

Another part of avatar improvement that isn't brought up in the texture thing is the set of changes that will restore avatar alpha masking. And it's a really important one, because ultimately the removal of the public unbaked textures also does away with the clothing layer system, except locally for that avatar. That's the biggest hardcoded limitation getting in the way of letting a jacket be worn on the undershirt layer, or adding an arbitrary number of layers. That would make it way easier to implement VWR-1449 (461 votes).

I would take a ruthcloud over a human skin. Now if the default skin was something cool and digital, that would be a different matter.

I am so happy that I am too stupid to be a criminal.
BT

I was rooting for something like Peter Gabriel's lightbulb suit, the particle thing is lame. There is also some test code in the viewer to render avatars as plywood cubes, that would have been a good second choice.

I think I get it.! In other words, unless I am listed as the creator (or owner?) of the texture, I will not be able to download and bake. However, if I am getting dressed, my av has to download all of its clothing textures and bake them...I am never the creator of my clothing, so I would still be downloading textures that I did not make.

How does my downloading and baking ever get to be accessed by someone near me. How can they see what I am downloading and backing to my client. It would seem they always have to download and bake themselves?

I don't suppose i need to understand this, but I recently bought red hair instead of blond, so I can't stay quite as dumb.

BT

Once you are baked, your viewer uploads the composite textures back up to a mini asset server on the sim. Once those baked textures are out there, other viewers are supposed to use those in preference over the separate pieces.

Unless you're *wearing* it, you won't be downloading and baking it. Currently you can download and bake textures from any avatar you can see.

The baked texture is uploaded back to the sim.

Well I am happy to have found this thread! Since downloading 1.23 I have also had:

1. Spiders for eyelashes
2. Camming in on tiny prims is a nightmare
3. Frequent crashes
4. Stop error last night/blue screen of death
5. My parcel won't come up in search unless Adult Content is allowed, all because I have five objects on the entire sim that say "sex bed" in the description

I did report the adult-content filtering issue in jira because a lot of parcels are unfairly being omitted from search results should one object contain the word "sex", it seems.

I'm rolling back to 1.22 for now...

the only thing i could say that needs to be fix are: the zoom bug. which can be exampled here: http://www.youtube.com/watch?v=Cxd8vT-_lzc
and the fact that sometimes parts of my body disappears or somebody else body disappear.
everything else i'm fine with it. maybe they can cut and paste part of the code that was in the last viewer and apply it to this viewer.

Analysis 1: are we a very negative userbase?
seems like this release only bring negative responses, nothing of the good things about this release is mentioned by the users, like the bug fixes and enhancements, because the public's heart hurts because they can see many improvements that can be done and they suggest hoping that they could be applied and they never get into the releases. linden lab don't have the legal obligation to say anything about their internal process to the public or to apply anything the userbase suggest, like at&t or microsoft or sony, under that defense linden lab does whatever they decide in their meetings, and many public suggestions never get to the meeting table. the only ones they have to respond to are the investors. users got a resentment against linden lab because they ignore their great ideas, and they give the ideas because they love second life, if they didn't they wouldn't care. so in revenge for the frustration linden lab get those negative comments.

Analysis 2: not release candidate material
why did they release this version if they knew it had this problems and people would complain? maybe it was because a long time was passing that they didn't release anything. i remember they were going to release it but pull it back because it had some problems. maybe they should have release it as a beta, for users to test to see what problems they find and get some feedback.

well guys, i have good news: this is a release candidate, not a final. that means they are going to bring us at least another release candidate.

The problem is that most of those bug fixes are only bug fixes compared with the 1.23.0 version, and many of the enhancements don't actually improve things... they're part of the "Adult Content" press.

Because they've given themselves a hard deadline to get the Adult Content code out, and they have to hit that come hell or high lag.