1.10.1(0) and WINE

Your appearance is rendered client-side and then uploaded to the server as one single "baked" texture. That's why others see the same bug, because your client renders it wrong.

Thanks for clearing that up - I understand now.

Where is this elusive alpha-patch for Wine the gentoo crowd are mentioning? Sounds really great!

Edit: Perhaps I am imagining this.. I just reread the post I thought referred to an alpha-correction patch, and it actually said gamma-correction!!! (doh!)

No, it's not that good, but it seems OK if I don't change anything. If I need a change of clothes I need to use the native client or my (very slow) mac.

What was wierd about yesterday was that I looked OK to me, but not to others (where you running under wine?). At the meeting I was using only either the mac or Linux clients.

Are you sure? That seems to contradict the message I sometimes see on login that says "your clothing is downloading but others will see you correctly" and also the fact that I looked OK to me last night but other saw me bearded...you can't imagine how scary it is for a woman, not to know what she looks like to other people!

I thinks it's a two-way thing.

Clothing downloading means you are using the clothes the server knows; others will see that, too - from the server.

If you change clothes, that change goes to the server, and others see that, too.

If your client "loses" the alpha channel, it may send junk to the server, based on what it "knows".

However, since the object in inventory DOES have a proper alpha channel, when the client "recognises" this, it sends what it NOW knows to the server.

I guess what you see (normal) and what was sent to others by the server (bearded) are only the same really if you have been in appearance, to redo your local cache. Otherwise you see whats in your cache, and others see what the server has been told by your client, or what it remembers about your appearance from last time.

And yes, I am confused

There is an odd bit of update behavior that occures from the client side I have noticed. i.e. if you rez and other people are invisible to you, or partly rez'ed, you can change your currently active group and it fixes the issue. I suspect it triggers a forced refetch of the data around you for some odd reason, but it appears to be the trick for all clients. No idea if it will help with this one at all.

Well, I've tried everything suggested so far and a few other things as well but I'm still a toastie-head.

Shame really as I was getting rather good at avatar design just before the Linux client went u/s


/EDIT Just to add a little more info; if you clear the cache before starting, the av rezzes correctly *before* it turns into toastie-beard-head.

Just one more point.

The colour of tostie-heads skin on our faces is directly affected (along with our hair) by the hair colour control sliders.

This does not work the other way, the skin tone controls have no effect on anything.


The facial hair is always maximum beard and maximum eyebrows - also for female avs.

This isn't new data - it's the classic wine-alpha bug.

It is a well known problem with running the win client under Wine.

Here is how you fix it:

1 go to a quiet place with the win client
2 take off your clothes !!
3 logoff with the win client and log in with the linux client
4 click on change appearance
5 possibly you need to alter something like skin tone and save it
6 alter it back as you see fit.
7 put some clothes back on!
8 log back in with the windows client
9 do not touch your appearance or your clothes (or attachments?) or the bug will return!

I knew it was something I didn't understand. That confirms it!

A simpler fix for this problem seems to be:

1. Switch to the Linux native client.
2. Go to the Debug menu. (Use clt-alt-shift-D to turn it on, if necessary.)
3. Select Debug -> Character -> Rebake Textures

You may need to rebake each clothing piece or skin that has problems.

FYI, today I devised a workaround for the crash I started this thread with. If anyone else sees the same problem then let me know and I'll describe the workaround; I won't by default because it's slightly gnarly, involving editing the .exe file.