[You know you've spent too long in SL (or the Forum) when you...]

I've tried to alt-zoom in RL to look around wall corners - sadly it doesn't work...

[Long hair on men?]

I've had some good luck lately with long hair from Truth. Currently wearing the Indigo hair pretty often for an 80's rocker look, and also sometimes Euphoria for a straighter look. They cut into the back a tiny bit but not majorly noticeable.

Echoing the mentions of No.match and Raven Bell - have used their hairs a fair bit. I've gotten some good use out of Exile hair as well.

I'm going to give that back deformer for Jake a try - didn't know that existed! That should expand the options quite a bit.

[Have your Alpha Modes changed to "None"?]

On 7/1/2022 at 12:34 PM, Jenna Huntsman said:

I've just dropped by the location in that LM - I notice that the object in question is scripted - for the sake of argument, have you tried removing the script from one of those problematic objects and see if the problem reoccurs?

Thanks for taking a look and that is a great observation. I'll check into if any of the other affected objects were scripted or not, and try removing some of the scripts for alpha masked objects to see if that changes the behavior in any future occurrences.

23 hours ago, Qie Niangao said:

Yeah. Just a note that the fact the fix is in the viewer means that only viewers with the fix are safe to use in regions where the account has permission to modify anything with alpha-channel textures. Earlier versions could corrupt those texture settings and that would be visible in viewers patched and unpatched alike. That said, because this all is so long ago now, one would think nobody would now enter a region while still using an unfixed viewer, so the question remains whether the fix was fix enough.

This is a great point - and even if folks are not using very old viewers they could be using less mainstream viewers which may not have received the needed maintenance update for some reason.

[Have your Alpha Modes changed to "None"?]

Digging into this a bit more I confirmed the following: 

BUG-11333 was supposedly fixed in the "Maintenance Dawa" release on February 3rd, 2021, per the release notes here: https://releasenotes.secondlife.com/viewer/6.4.12.555248.html

Firestorm merged the "Maintenance Dawa" code as of version FS version 6.4.13.63251, per these release notes: https://wiki.firestormviewer.org/changelog:firestorm_change_log_6.4.13.63251?s[]=dawa

Since we're seeing the issue in Firestorm 6.5.3 we can assume the bug was possibly not fixed after all, or a more thorough fix needs to be implemented. It seems odd to me that the code on either the viewer or server side would even allow such powerful object alterations sim-wide without the user explicitly going into edit mode with the objects, or a user script directly pushing the changes.

@Linden Lab What's the best way to get this looked at again? Could we have BUG-11333 re-opened or should we file a a new bug in the Jira? I think an issue which can randomly corrupt the visual experience of an entire region for all users should be a pretty high priority to resolve.

[Have your Alpha Modes changed to "None"?]

Adding a bit more info about Nova's report above - I was in the sim as well and saw the same issue - the texture settings were altered for several objects across the sim without any intervention by us, as in this closed bug: https://jira.secondlife.com/browse/BUG-11333

We're both running Firestorm 6.5.3 (65658). Example location: http://maps.secondlife.com/secondlife/Noctilucent/186/153/21

Here's a screenshot of what we saw before I fixed it by switching "Alpha Mode : None" back to "Alpha Mode : Alpha Masking" :

This also happened on the same sim about a couple weeks ago in a much worse incarnation, with many of the trees on the sim affected.

[Old Timer Alert!]

Old timer checking in - 19 years, 2 months, recently breached 7000 days - wow. I took this "then and now" photo at the Sacred Ground henge site in Natoma for the old-timey feels. Looks like I shrunk with age - I was a giant in my earlier form for some reason!