Whirly Fizzle

This usually happens when you are trying to save something "bad" in the outfit folder which fails the AIS3 checks. While wearing the outfit that will not save, open your inventory & expand the Current Outfit folder. Look for anything in the Current Outfit folder that is a broken link (delete those), anything in there that shows as not actually worn (delete that link & wear that item again) or anything that shows as attached to an invalid attachment point (take off & reattach to a valid attach point). Once the problem link is removed, the outfit should save. If you can't spot what's wrong, replace outfit with any default Library avatar, check this will save as an outfit, then change into the outfit you want to save again - hopefully it will then save.

Hmmm that effect looks like RenderResolutionDivisor. If you don't see the Advanced menu in the top menu bar, activate it with CTRL+ALT+D. Advanced -> Debug Settings -> RenderResolutionDivisor -> Click the "Reset to default" button.

Do you have Iolo system mechanic installed on your computer? This software can cause any shape you create or edit to go missing from the database. If you do use this software, go into the NetBooster tool and select "Restore original settings" and the problem should be fixed. The shapes already missing from database can not be recovered however. See these JIRA issues: https://jira.secondlife.com/browse/BUG-10198 https://jira.secondlife.com/browse/BUG-10428

Where exactly is your profile image missing from? I'm seeing your profile image in all locations it should appear. Your profile image displays under Websearch Everything & Websearch People, legacy search People, legacy profile, web profile & the mini profile icon & http://world.secondlife.com The direct link to your profile image that search uses is http://secondlife.com/app/image/2b7859ab-963b-4a30-a463-c03b924c7608/2

File a support ticket asap with Linden Lab support here. Tell them you believe you have been paid stolen L$ and they will sort it out. It's probable LL will lock your account while they investigate, so don't panic if they do that. I suspect your suspicions are correct. I looked up those names and one of them had a "Hacked by XXXX" in their profile and on next page refresh the name went to "Unavailable" - so that account has been deleted or locked already. It appears that the 2 accounts that paid you were hacked accounts themselves.

I'm guessing you mean Singularity viewer 1.8.6? The downloads for Singularity can be found here.

I think the fix is lurking in viewer-lion somewhere. The pull request (which was declined) is still visible https://bitbucket.org/lindenlab/viewer-lion/pull-requests/28/maint-6139-alpha-masked-textures/activity# I can't actually find the commit though, so not sure what's going on there.

There's a bug report for that at https://jira.secondlife.com/browse/BUG-10830

If it that bug I gave above, I don't know of any workaround or any viewer the bug is fixed on. Pretty sure any viewer that has the materials feature will have that bug. The LL viewer & Firestorm certainly both have that bug. You could try Singularity viewer, the render code may be different enough to not have this bug.

Are you on a Mac? Kinda looks like https://jira.secondlife.com/browse/BUG-8801

Try the new Maintenance-RC viewer , it has a fix for this bug.

Do you have Nvidia ShadowPlay enabled? If so, disable it. ShadowwPlay will cause frequent viewer crashes just after launch - see BUG-11530 Do you have an Asus system with the Asus ROG Gamefirst software installed? If so, disable or uninstall Gamefirst - this software is known to crash the viewer on launch and it can also cause an actual system crash when the viewer is launched. If that doesn't help, file a JIRA issue with Firestorm & include your log files - logs should show why you are crashing.

ChinRey wrote: Where are all the true fanatics?

Is your groups list totally empty and your friends list there but all the names show as "Loading..."? If that's the case, try logging into a different region & see if everything is back to normal. If this problem only happens when you login to a certain region, the region likely needs a restart & it's probably caused by capabilities failure on that region.

Are you using the Linden Lab viewer or a TPV that has the new coroutine changes? If so, you may be getting hit with this bug: https://jira.secondlife.com/browse/BUG-10391 There is fix for this bug that just went into the new Maintenance-RC viewer, which you can download here: http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/4.0.4.314012

What do you mean by "random rendering failures"? What exactly isn't rendering correctly? Mesh, textures, avatars, something else?

Bobbie Faulds wrote: I have a problem in the SL viewer keeping my Windlight settings. I always have to reset them when I log in. FS has all the Windlight settings at your fingertips. That's actually expected behaviour on the LL viewer - they changed the behaviour a while ago to deliberately do that, believe it or not. You can easily fix it though, at least they added a new debug setting so you can go back to the old behaviour. Activate the Advanced menu in the top menu bar with CTRL+ALT+D. Advanced -> Show Debug Settings -> EnvironmentPersistAcrossLogin -> Set to TRUE. Profit. Ref JIRA issue: https://jira.secondlife.com/browse/BUG-8739

Wear alpha layers or system layer underwear under your prim/mesh clothes.

Quicktime also comes bundled with the viewer... I'm really curious if LL are going to remove Quicktime support from their viewer & if TPV's will do the same. You can play QuickTime media with a CEF enabled viewer without Quicktime actually being installed on the system. Actually I was wrong there. After blitzing Quicktime from my Windows 7 box, Quicktime media will no longer play on either the LL viewer or Firestorm viewer. I can see the viewer bundled quicktime plugin launches in my viewer logs, but the media screen remains white. newview/llviewermedia.cpp(2112) : 2016-04-15T20:37:48Z INFO: LLViewerMediaImpl::loadURI: Asking media source to load URI: http://ia802606.us.archive.org/34/items/TheFastandtheFuriousJohnIreland1954goofyrip/TheFastandtheFuriousJohnIreland1954goofyrip_512kb.mp4 llcommon/llprocess.cpp(731) : 2016-04-15T20:37:48Z INFO:#LLProcess LLProcess::LLProcess: SLPlugin.exe (3512): launched cd "C:\Program Files (x86)\FirestormOS-Release\llplugin": "C:\Program Files (x86)\FirestormOS-Release\SLPlugin.exe" 58251 llplugin/llpluginprocessparent.cpp(1029) : 2016-04-15T20:37:48Z INFO:#Plugin LLPluginProcessParent::receiveMessage: plugin version string: QuickTime media plugin, QuickTime version 0 llplugin/llpluginprocessparent.cpp(1038) : 2016-04-15T20:37:48Z INFO:#Plugin LLPluginProcessParent::receiveMessage: message class: base -> version: 1.0 llplugin/llpluginprocessparent.cpp(1038) : 2016-04-15T20:37:48Z INFO:#Plugin LLPluginProcessParent::receiveMessage: message class: media -> version: 1.0 llplugin/llpluginprocessparent.cpp(1038) : 2016-04-15T20:37:48Z INFO:#Plugin LLPluginProcessParent::receiveMessage: message class: media_time -> version: 1.0 llplugin/llpluginprocessparent.cpp(600) : 2016-04-15T20:37:59Z WARNING:#Plugin LLPluginProcessParent::idle: timeout in exiting state, bailing out llcommon/llprocess.cpp(850) : 2016-04-15T20:37:59Z INFO:#LLProcess LLProcess::kill: killing SLPlugin.exe (3124) llcommon/llprocess.cpp(1036) : 2016-04-15T20:37:59Z INFO:#LLProcess LLProcess::handle_status: SLPlugin.exe (3124) exited with code -1

Does this only happen when you login to a certain region? Those symptoms could be caused by logging into a region that has capabilities failure. If this is confined to one region, the region needs to be restarted. If you are having the same problems no matter which region you login to, it could be a DNS problem at your end (which leaves the viewer unable to get caps) or you may be timing out during login so you login in a semi disconnected state or another connection issue.

Theres a fix for this in QA & the Maintenance-RC viewer will hopefully be updated soon to include that fix. https://bitbucket.org/lindenlab/viewer-bear/commits/62122bc8954258c4e63f955080ccbce2779bb854

There is an old bug that when an avatar is ejected (or banned) from a group, they are often not removed from the chat session, so they can continue to spam until the close the group chat window or relog - see SVC-32 This bug is still not fixed. There is one workaround, but it doesn't always work - block their ability to chat in the group first and then ban them. Also see https://jira.secondlife.com/browse/BUG-9227

That's the "Cheesy Beacon" feature :smileywink: Activate the Advanced menu in the top menu bar with CTRL+ALT+D. Advanced -> Highlighing & Visibility -> Cheesy Beacon -> Untick that.

Oh yuck. File a support ticket now at https://support.secondlife.com/create-case/. Include that image you posted here. LL support will be able to fix your multiple system folders.

Arden Sirnah wrote: Christin73 I didn't know there were more viewers but the LL and Firestorm. :matte-motes-big-grin-squint: There are indeed! All the compliant third party viewers are listed in the TPV directory here. Best thing to do is try each one for a few days and see which suits you best. Any of the viewers in the "Active Full Viewers" section are worth trying. Avoid the viewers in the "Out Of Date Viewers" section. Those have not been updated for a long time & do not support all current SL features.