Alpha failures with Release 6.4.19.559046 (64bit)

[Eddy Vortex]

I've updated the offical viewer to Release 6.4.19.559046 and noticed my alpha layers aren't working anymore, even after multiple relogs.  Any insights on this?

[Lucia Nightfire]

That is the Love Me Render 5 release candidate viewer, a collection of graphics fixes.

File a bug report with as much information as possible.

[Eddy Vortex]

Thanks. I just filed it: https://jira.secondlife.com/browse/BUG-230789

[Psyche Starling]

Thank you! This is happening to me too. I was beginning to think I'd lost my mind. I filed a support ticket about it but they weren't sure why it was happening. 

[Dan Linden]

I am not able to reproduce this bug yet. If anyone has more details about how to trigger this bug, please leave a comment on https://jira.secondlife.com/browse/BUG-230789.

[Nathan Zetkin]

OK I have tried every SL viewer that is currently available and it is an issue on each one, Sometimes my alpha is good for about an hour and then it just stops working, I have a SLink Redux body which is made for BoM and the alpha's have all worked great up until now. The is a recent change that broke it.

I think it might be cache related but the cache is so horribly broken as it is. Your avatar should remain in the cache until you change it, you should never see your self as a cloud after tping. But sometimes even tping a short distance on the same sim turns you into a cloud.

Again this is not a problem for other people who all see me fine, it's just very annoying.

 

Edited May 25, 2021 by Nathan Zetkin
typos

[Psyche Starling]

Someone by the name of Whirly Fizzle has a really detailed response on the bug forum. Apparently Slink bodies can cause it! Whether you're the one wearing it, or someone else shows up wearing one. There may be some other objects that cause it too. 

[Nathan Zetkin]

Apparently it affects Maitreya as well, it's not just the Slink body

[Nathan Zetkin]

[Ardy Lay]

Try https://releasenotes.secondlife.com/index.html

6.4.19.560171 - LMR 5  Thursday, May 27, 2021  has a fix for that.

[Nathan Zetkin]

Yay!!! It's fixed. Good work Lindens, Thank you Dan Linden for taking a look into this!

[Ardy Lay]

Aww, hell:

[KjartanEno]

@Ardy Lay That happens to me on Linux with WINE, but only after the default viewer gets updated to a newer version. I'll be able to test LMR 5 until the next default viewer update, whenever that may be.

[Ardy Lay]

Instead of clicking "OK", because it's not OK to replace a working viewer with a known defective viewer, I closed the window and relaunched.  Then the downloader still downloaded something in the background then tried to interrupt me for permission to install, which I denied.  I thought the argument --channel "NoUpdateMe" would stop automatic updates as it is not a valid channel to the updater.  @Dan Linden Dan, we may need a little help here.

[Dan Linden]

Sorry for the late reply, but the first thing I would check is to verify Preference > Setup > Willing to update to release candidate is checked. If it's unchecked it will try to update to the Release viewer.

[Ardy Lay]

8 hours ago, Dan Linden said:

Sorry for the late reply, but the first thing I would check is to verify Preference > Setup > Willing to update to release candidate is checked. If it's unchecked it will try to update to the Release viewer.

That was probably it, Dan.  I did it again and this time it certainly was that box unchecked.  A few days ago I manually downloaded and installed 6.4.20.560520 - Viewer UI and launched.  The updater immediately went to work DOWNGRADING to 6.4.19.560171 - LMR 5, I think it was. Thanks for the tip!