Whirly Fizzle

Since the AIS3 changes, the viewer does some extra checks when you save an outfit. If something you are trying to save in the outfit is "bad" in some way and it fails the new checks, the outfit will fail to save & you'll get an empty outfit folder. When you are wearing items that fail to save as a new outfit, open inventory & expand the Current Outffit folder (COF). The COF will list everything you are wearing. Look for anything suspicious in the COF and remove it and then try to save the outfit again. Problem items would include - something listed in COF that is not actually worn. Unworn items in COF will not be bolded. Check for attachments showing as attached to an invalid attachment point or attached to the Bridge attachment point (if you are on Frestorm) and take those off and attach to a different attachment point. Check for any broken links in COF & remove them. If you cannot find what's causing the problem, this should fix it (though the fix may be temporary): LL viewer - Activate the Develop menu in the top menu bar with CTRL+ALT+Q. Develop -> Avatar -> Character Tests -> Test Male (or female). Then try to save this as an outfit (this should work). Then put everything back on you want to save as an outfit and try again. Firestorm Viewer - Go to Avatar -> Avatar Health -> Reset default male (or female) avatar. Then do the same as above.

Check if your Windows friends see the problem. If it's only seen on Mac, then it could be https://jira.secondlife.com/browse/BUG-8801

I guess he left...

No, actually you already have an issue at https://jira.secondlife.com/browse/BUG-10301 which is in "Needs more info" state. So click the "Info provided" button on your JIRA issue and it will fall back into their triage queue. This is what Grumpity told them to do on issue https://jira.secondlife.com/browse/BUG-10378 when they needed to be synced again.

You can sort of do this but it's a faff and the results are not in a pretty format and are likely not what you are wanting. However, for what it's worth: Open the viewers cache folder Find the inv.gz zipped folder that starts with your avatars UUID and unzip it. Open the .inv folder & open the .inv file inside in a text editor. Decide that was all pretty much useless and have a cookie instead

If you disable scripts on your land, does the problem go away?

Ejecting an avatar from a group will often fail to end their current chat session. They will be able to continue spamming until they either close the group chat window or relog. If it's a bot, that could take a rather long time for either to happen. Now that the spammer has been ejected there is no way for you to mute their group chat. This is an old bug, see https://jira.secondlife.com/browse/SVC-32 Best thing to do is to block the spammers ability to chat in the group using Moderator Options -> Untick "Allow Text Chat" BEFORE you eject or ban them from the group. However the "Allow Text Chat" option can be flakey, especially in large groups. It can often fail to work, but it's the only workaround there is until LL fix that bug.

You can't fix this yourself, its a bug' on the LL viewer. It was fixed on Firestorm - see http://jira.phoenixviewer.com/browse/FIRE-11266

Yes unfortunately you do. The Aditi password & inventory sync is broken. Until it gets fixed you will need to file a JIRA issue requesting that your password & inventory get synced over to Aditi. As far as I'm aware LL support still cannot perform the sync, it has to be requested on a JIRA issue.

Look for a scripted object, rezzed on your land that is using llUnSit. llUnSit(key id) If the agent identified by id is sitting on the scripted object OR IS OVER LAND OWNED BY THE SCRIPTED OBJECT'S OWNER, the agent is forced to stand up. http://lslwiki.net/lslwiki/wakka.php?wakka=llUnSit

I'm not 100% sure but I think the CoolVL Viewer still supports Mac 10.6, plus it has VMM support - http://sldev.free.fr/forum/viewtopic.php?f=3&t=14&start=120

All the QuickGraphics bugs are linked to https://jira.secondlife.com/browse/STORM-2082 Unfixed bugs from that list: BUG-9962 - Avatars often permanantly stuck as jellybabies even when Max complexity = No Limit BUG-10401 - Blocked avatars are always fully rendered when imposters are disabled & other odd new behaviour with blocked avatars. BUG-10398 - Graphics preset changes to None each time the Advanced Graphics floater is opened, even when no changes are made. BUG-10330 - Some avatars remain invisible until imposters are disabled.

Ardy Lay wrote: I seem to be having some difficulties with this release. Sometimes I will see an avatar impostored due to extremely high memory usage. When I select Always Render Fully their memory usage plummets to well below the default limit of 10MB. Yep, I have the same problem. This is what causes avatars to remain stuck as jelly babies even when maximum complexity is set to no limit. You have to disable imposters to never see a jelly baby. I filed this at https://jira.secondlife.com/browse/BUG-9962 It took me a while to work out it was only avatars with a high total attachment byte size that triggered the stuck jelly babies so the actual repro steps are in one of the later comments.

I don't think Singularity ever merged in that changeset, unsure about the other V1 based viewers. All V3 based viewers that are merged up to the current LL viewer will have the behaviour the OP is complaining about though.

Right, yeah you can't do this so easily now. There were changes made in the viewers (AIS3/SSA polishing fixes) which stopped you being able to add anything to the main outfits folder that wasnt a link & blocked being able to create subfolders within outfit folders & the whole thing ended up being a bit of a mess. Some of those behaviour changes have been reverted but it still isn't all fixed. On the latest LL viewer I can't actually find a way around it but on Firestorm, what you now have to do is create a new folder outside of the Outfits folder, put your non-link items in that and then drag or cut/copy/paste this folder into the main Outfits folder. Attempting to do it any other way will give you links. If you use the Appearance panel to change Outfits rather then doing it directly from the inventory folders, I'd advise against this though. If the main Outfits folder contains anything apart from viewer created Outfit folders containing links, the Appearance panel will act in unexpected ways - not recognising when there are changes to an outfit, not letting you save the outfit, getting stuck when making changes etc. If you want to structure your Outfit folders in more complicated ways the best thing to do is use the Clothing folder or another folder to do this and just disregard the main Outfits folder & appearance panel altogether. It just doesn't work well anymore.

Oz Linden wrote: Looking in the data logged to the simulator by your viewers in recent sessions, it shows high packet loss rates and ping times that are usually over a half second, and in at least one session over 3 seconds. For those sessions at least, you have a quite serious network problem. Are you using Webroot antivirus software? Webroot is known to cause severe slow loading of textures & mesh, bad packetloss and also very high ping sim times for some people. If you are using the enterprise version of Webroot, then you need to whitelist the viewers cache folder, which should fix the problem. If you are using the normal version of Webroot, it does not allow whitelisting by folder and the only option really is to get rid of Webroot. Your viewer logs should give a clue as to what's going wrong. You can file a LL JIRA &/or a Firestorm JIRA issue and include your logs after running a session where you experience this problem. Instructions for the LL Viewer: https://community.secondlife.com/t5/English-Knowledge-Base/How-to-report-a-bug/ta-p/733545 Instructions for Firestorm Viewer: http://wiki.phoenixviewer.com/file_a_jira

Best thing to do is to file a Firestorm JIRA issue and include your viewer logs after running a session where you reproduce the problem. See http://wiki.phoenixviewer.com/file_a_jira for how to do this. References this thread on your JIRA issue so I know it's you and I'll take a look.

Is this folder inside the main Outfits folder though?

The next release of Firestorm will no longer have this behaviour - see http://jira.phoenixviewer.com/browse/FIRE-16667 If you would like to try a nightly build of Firestorm containing that fix, leave me a comment on the above JIRA issue and I'll send you the installer. Let me know if you want the 32 bit or the 64bit build. Alternatively, apply to be a Firestorm beta tester & you will have access to the nightly builds.

Are you trying to paste inside an Outfits folder? Outfits folders should only contain links.

Your name still does not appear in web search, as said above it can take a day or so for this to happen. Get your girlfriend to paste this text into her nearby (Local) chat: secondlife:///app/agent/3c1f9119-d9ab-4716-b8f3-62ca95b7c74b/about This will give her a clickable link to your profile. If she right clicks on this link, she will see the options to add you as a friend and to send you an IM, http://prntscr.com/8ne61q Once added as a friend or you have an IM conversation open with each other, you will be able to teleport to each other. Just right click her name tab in the conversations window and you will see more options, including offer & request teleport. Once you are friends you can find each other quickly under Communicate -> Friends.

Sounds more like a viewer problem. The latest release of the LL viewer which was promoted earlier this week has the new mesh importer features - http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/3.8.4.305119 If your friend is seeing this problem on this viewer but it does not reproduce on an older viewer version, then she should file a JIRA issue.

The rift viewer still uses the old gpu table, which is no longer maintained and does not have the most recent graphics cards added to it. If you follow the instructions on https://jira.secondlife.com/browse/BUG-8771 to replace the gpu table with the one attached to that JIRA issue, you should be able to enable Advanced Lighting Model in graphics preferences, which will enable you to use HMD mode.

In addition to what Freya said, if you are using a Mac and you crash when attempting to upload any image in the viewer, see this wiki page for a workaround: http://wiki.phoenixviewer.com/mac_crash_upload

It sounds like its docked to the chiclet. Drag the notification well away from the notification chiclet to undock it. Then it will stay open. If it's docked, it will close as soon as it loses focus. Like this: https://gyazo.com/9abf5256c37eaaa87fa4f8aacde7b938