Ansariel Hiller

There has never been a "daylight time" slider in official LL viewer, not to mention that it never changed the time of day, but sun angle.

Just unimportant other things like the operating system and other applications you might be running at the same time. Or silly things like vertex buffers for the rendered objects. I know, completely unimportant compared to cranking up the texture setting as high as possible...

Totally what you should NOT do - I suggest reading the tooltip...

Incorrect. A higher LOD only means the distances for the LOD thresholds are increased.

Sorry to disappoint you, but there are no AMD-specific optimizations.

On a side note: The names for the maintenance releases are diced out during the ritual drinking games in the weekly LL status meetings... 😂🍸

Thank you!

It's not about the tools, but reasons like users not wanting to update each week or some other short interval. It also has to do with providing support to such a large userbase and having dozens of releases out there. And something with a rule from LL regarding a maximum of the three most recent releases out there. Technically it wouldn't be a problem to do releases on a daily basis - the CI tool taking care of that and creating automated builds each night is doing so for quite a while already. The artefacts are just made available internally due to the aforementioned reasons.

I didn't remember that to be honest. So it's good to know. Thank you! But then it was also more of a general hint that it might be easier to provide such patches directly under LGPL, since then everyone can easily make use of them. I know Liru from Singularity usually doesn't mind re-licensing things either, but ya... What makes adding changes from Cool VL really difficult is, that you only provide a single diff for each week's change. I don't know if you commit such a change to repository as a single blob, but going through diffs that are several thousand lines long and include several different changes among lots of reformatting of code is extremely tedious and error prone. Sometimes I have a feeling you reformat code back and fourth to obscure the actual changes.

Looking at Cool VL doesn't really help the majority of TPVs out there at all, since Cool VL is under GPL license and except Singularity all other TPVs are under LGPL, meaning they can't easily re-use that code.

Settings backup won't help in this situation. The encrypted file with the credentials is part of a backup, but the viewer won't be able to decode it anymore because the Windows serial number is different after a Windows feature update if this feature update is basically an upgrade installation (most often the case with the H1 feature updates). Restoring the backed up file doesn't make any difference.

This - as for now until LL's change regarding the way credentials are encrypted locally - happens on Windows feature updates since on Windows systems the Windows serial number is part of the encryption mechanism and this serial number tends to get changed if you install a Windows feature update (which is basically a complete upgrade installation). So if you have been on Windows 10 19H2 and got "updated" to 20H2, this will trigger the loss of encrypted credentials. Updates from 20H1 to 20H2 won't cause this, since this update doesn't involve an upgrade installation. In contrast to some comments above, on Windows systems the MAC address of the first network adapter is NOT used for encrypting the local credentials store.

This one? Might still be time to make an updated animesh version of it... 😇

Thank you for your great work throughout all the years, Oz! Enjoy your free time - until @Jessica Lyon will hire you as lobbyist for Firestorm at the Lab! 🥳

For reference: Legacy body SCNR 🤭

I heard sculpties will be the next big hit... 🤪

True, Apple has to do the first step in trying to force people into using their proprietary new technology for better lock-in effects. If it were about evolution into a new technology, they could have simply switched to Vulkan and not Metal. But "outdated technology" sells much better than "we were too stupid to fix out OpenGL implementation and now want you to use our new proprietary thingy to make platform independent programming much more complicated" - killing two birds with one stone. Beside that: Who apart from hipsters really still want to use Mac after they annoyed the professionals with their ancient workstations without ways to upgrade them? 😂

Only because Apple deprecates it because they are too stupid to create proper implementations for a decade doesn't make it end of life!

That is partially incorrect: Opening an SLURL will result in starting the viewer registered with SLURL (which is usually the last one installed), but if there is already a viewer running, handling of the SLURL will be handed over to the running instance (under the premise that nobody changed the window of the viewer class, which might have done one AFAIR).

Most likely only the JIRA tickets from people complaining about not being able to use subfolders anymore.

@Vir Linden You can create normal folders underneath the (My) Outfits folder in the SL viewer, but additional checks added a while ago now prevent you from actually copy & pasting valid items into outfit folders - at least on the SL viewer since I fixed that in Firestorm long time ago. And since it was (and actually still is) basically not intended to have outfits in subfolders, the option to create normal folders underneath the (My) Outfits folder is actually wrong - the correct option would be "New Outfit" instead of "New Folder" here, which is the case in current Firestorm release. I changed it for next release to actually allow creating subfolders and then actual outfit folders inside them since you mentioned fiddling with it on the JIRA, but if you think outfit folders in subfolders should be a valid option, then you need to fix the outfits list: The outfits list in the My Appearance window only adds a category observer for the (My) Outfits root folder, so any changes to outfit folders in subfolders won't be reflected in the outfits list at all, showing wrong/inconsist/outdated data.

The TV most likely uses Shared Media, which - unlike it suggests - doesn't actually share whatever you are seeing what others are seeing. It's basically a web browser running inside the viewer using a prim surface for displaying its content. As Qie already stated, there is a direct connection from that browser in your viewer to whatever page it is displaying. Instead, the TV is apparently configured to display https://secondlife.com/my as start page - that applies to everyone basically turning it on. Then the web browser inside the viewer opens a direct connection to the SL account website. Since the viewer automatically creates a session with the SL website (e.g. for the search feature or web profiles), you will be automatically and already logged in, hence the TV is showing your SL account page. Your friend in his viewer will see his own SL account website.

Waste of money for SL - the only thing currently matters in terms of FPS in Second Life is raw single-core CPU performance.

"Most" most likely means "a few" here because after over 10 years I haven't seen any DJ actually doing it.

It's not going to work unless LL fixes the broken CEF implementation in the viewer. Firestorm's Windows and Linux version should work fine with Twitch though - I just don't know why somebody would want to watch that inworld...