Whirly Fizzle

There are no full meeting transcripts as far as I'm aware - much of the meetings are on voice. However Inara Pey covers each of the Bento meetings: http://modemworld.me/?s=bento+user+group

Are you using Webroot antivirus software? There is a known problem with Webroot being incompatible with Pipelining in the viewer. This causes frequent viewer crashes, raindow coloured textures & exploding mesh.

Duplicate of https://community.secondlife.com/t5/Land/Autoreturn-impossible-CRASH/qaq-p/3011168

You need to contact LL support and request that they remove the 2 objects called "ULTIMO" owned by Tareeza Toxx (object keys bc1e58c9-62f8-b195-9f06-745797259a49 and fc96d72e-83fd-6c36-b01b-8c45eef98fe9). File a support ticket here: https://support.secondlife.com/create-case/ Do not attempt to return or delete those objects or the region will crash & roll back. Make sure support understands they cannot delete those objects in the normal manner. Tell support those objects trigger https://jira.secondlife.com/browse/SEC-1558 I did AR the objects and request they were removed, however it's likely Governance won't remove them because they are rezzed by a group member who has rez rights on the land. Both objects were actually created by your friend & they are stuffed full of known region crashing objects so you may want to consider removing that person from your land group.

Glad the "Connecting to region.." problem is solved. Running through the other issues... AlexanderD Schumann wrote: 2. Viever doesn't load profiles, search and internal web-browser, which result loading just a blank page, all of them, with no message of error or whatsoever. This happened when I still had the luck to enter Second Life {before issue number 1 came up today}, I thought might be because of the Candidate Release but happens to occur even with the main viever's release as well, something I could check trying out the Support webpage in the log-in panel. Make sure that your antivirus software is not blocking slplugin.exe or llceflib_host.exe. If that wasn't the cause, then it's likely you are suffering from this bug: BUG-11265 - Profiles, Search and destination guide all go black when I try and use them This bug is fixed on the Maintenance-RC viewer, which you can download here: http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/4.0.2.311770 AlexanderD Schumann wrote: 3. Multiprocess — which is clearly related to the issue number 2, has been introduced even into the main viewer release — literally kills CPU performance... plugins were already a pain in the axx I had to live with till llceflib_host.exe appeared { you can check in yours Windows Task Manager }... I ran the viewer right now and checking the active processes on task manager I count 3 plugins already running and 5, I said f-i-v-e, llceflib_host processes without even logging in yet... a number that jumps up to 10 — at least! — as soon as I am in-world. That appears to be expected behaviour with CEF viewers, I've asked about this before. On average I have 10-15 llceflib_host.exe processes running & this can raise to ~30 if I'm around a lot of media content. I have yet to see a performance problem caused by this on my Win 7 or Win 10 box though. One thing to check is that all the llceflib_host.exe processes have stopped running after you logout of the viewer. Sometimes when the viewer crashes, the llceflib_host.exe are not cleaned up & remain running, which can start causing performance issues. If you feel the numerous llceflib_host.exe processes are a bug then best thing to do is to file a JIRA issue. AlexanderD Schumann wrote: 4. Viewers freeze — with consequent crash most of the times — anytime I right-click on several menus, like trying to open options on members from my friends list {to access profile, offer teleports, paying money... etcetera}, or even the Control Panel. This sounds like it may be CHUIBUG-222 - Long pause on first open of preferences or right-clicking a user in friend list Did you see this problem when you tested Firestorm? The bug is fully fixed on Firestorm as long as you were on the latest release. If you usually use the LL viewer though, the bug will be most severe on that viewer because you will have more chat logs saved. On the LL viewer the only workaround is to purge your saved chat logs or set chat logs to save in a new location. The bug is caused by having lots and lots of saved chatlogs - it's the number of files rather then the file size that causes the problem. AlexanderD Schumann wrote: 5. Mesh uploading crashes anytime skin weights gets selected for previewing the model. Hmm not sure what this one is. I can't reproduce it on the current LL viewer. There were 2 older bugs for this crash but both are now fixed. BUG-5335 - Certain dae files that used to display skin weights successfully now crash when ticking skin weights in model preview on ALL viewers BUG-8061 - Crash after selecting 'Skin weights' checkbox when uploading the second model File a JIRA issue for that crash & attach a repro dae file & be sure to also attach your log files

Windows 10 + Intel HD 3000 graphics should run Firestorm just fine if you install the 32bit version of Firestorm and then apply the Intel fix. You will only have this problem on viewers which use the Windows 10 manifest. That's Firestorm & Alchemy for sure. I'm not sure which other TPVs are using the Windows 10 manifest. The Linden Lab viewer doesn't yet use it but it looks likely to be added soon.

steph Arnott wrote: OK, odd that a freinfd i mine that works for LL says otherwise. Very odd that. Any how, not important. I probably shouldn't even bother to reply to this but anyway... you can view the JIRA groups you are in by going to your JIRA profile here: https://jira.secondlife.com/secure/ViewProfile.jspa Here are my JIRA groups: http://prnt.sc/aawo8s "contrib-agreement" group is for those who have signed a CA. "support-helpers" group is for those who regularly help triage on the JIRA. "jira-users" is the standard jira group everyone is in. "good-citizens" group I don't think is used now. support-helpers has replaced that. Those Residents who are in either the "contrib-agreement" or "support-helpers" groups can see JIRA issues set to Triagers & Reporters. Those groups do not give access to internal LL projects like MAINT. Those are Linden access only. It really isn't that important these days though. Most people leave JIRA issues set to Public security level which everyone can see. However a lot of older BUG JIRA issues were restricted to Triagers & Reporter without any means for the filer to change that so helpers need to see those to link, reference & mark as dupes etc. Feel free to believe your "Linden" friend though :matte-motes-sunglasses-1:

For close up shots of your avatar face, you want to zoom in the camera view using CTRL+0. CTRL+0 - zooms in CTRL+8 - zooms out CTRL+9 - resets zoom. For example: Here is a shot taken by zooming on on avatar face using the mousewheel to zoom in. Note the distortion. In this shot I zoomed in using CTRL+0

That issue is set to security level "Triagers & Reporter". When you file an issue in the BUG project, you'll see you can choose the security level to be None, Public or Triagers & Reporter. None seems to be no different to Public. Triagers & Reporter means only the filer of the issue and those in specific JIRA groups can see it. There are some Residents that can see issues set to Triagers & Reporter - for example those who have a CA on file with Linden Lab, third party viewer team members & those who have a history of helping to triage issues on the JIRA.

It's a bug - see BUG-10415 - [Valhalla] profiles and marketplace are asking for a login each session . If you tick the "Remember me on this computer" checkbox when you login to the web profile, it should keep you logged in every viewer session, however it does still sometimes lock the profile again when you haven't cleared CEF cache or viewer settings.

This commit made 2 days ago looks like it may actually fix your problem Fmeh: https://bitbucket.org/oz_linden/391-blizzard/commits/2046060fdd635f06358c582f0e1a232015f309f0

https://jira.secondlife.com/browse/BUG-9962 is a related issue. See especially the last few comments.

Ugh sorry, didn't notice that issue wasn't public. Title of the issue is "Avatars turning into solid colours when zooming close" with the same complaint as yourself basically. The issue was closed as Expected Behaviour with this comment: Oz Linden added a comment - 30/Nov/15 6:04 PM See also http://wiki.secondlife.com/wiki/Avatar_Rendering_Complexity The fact that zooming close causes this is because by getting very close you are loading a higher level of detail, increasing the cost of rendering the avatar.

Going by Oz's comment on https://jira.secondlife.com/browse/BUG-10803 , LL appear to consider this expected behaviour unfortunately. Currently you cannot fully disable seeing jelly avatars unless you totally disable imposters - which kills performance in busy places. That's a bug though & should be fixed before final release.

Also see this thread: https://community.secondlife.com/t5/General-Discussion-Forum/Anyone-know-what-these-bots-do/td-p/1349989

Ahh found it - the Peek360 service. http://nwn.blogs.com/nwn/2010/02/peek360.html

A few years ago there was this free service you could use to get a 360 degree panoramic photo of any region & it sent in a bot which came in, did those 30 degree rotations like that & then poofed & you got the image URL on a web page. I can't find the web page for that service anymore but possibly it's this.

It's a bug. https://jira.secondlife.com/browse/BUG-10415 - [Valhalla] profiles and marketplace are asking for a login each session

Prok, did you contact LL support about this yet? I'm curious who told you the cause was a crash report being sent in when the viewer was logging out. This is something I've never come across as causing a problem & I'm a bit doubtful that's the reason for the hang. As far as i'm aware no crash report will be sent in unless the session didn't end cleanly because of a crash, freeze or disconnect. It's quite probable certain stats do get sent in to LL at logout though, but I'm not sure about that. It certainly shouldn't cause a logout hang though. Do your alt accounts also suffer from the logout hang? Do you have any other weird symptoms while logged in or is it just the logout hang? Do you know how to read your session logs? This is likely to give a good clue about what's causing the logout hang. It should at the very least show you at what stage of the shut down process the hang is occuring. This wiki page tells you where to find your logs folder: http://community.secondlife.com/t5/English-Knowledge-Base/How-to-report-a-bug/ta-p/733545#Section_.3 The next time the viewer hangs at logout, before you relaunch the viewer, inside the logs folder, open the secondlife.log file in a text editor & nearish to the bottom, find this line "LLAppViewer::requestQuit: requestQuit" - this is where you clicked the X to initiate a logout. Check the timestamps for each stage & see where the hang happens. If you already relaunched the viewer then your previous session is logged in the secondlife.old file.

Ok login works. From the login screen, top menu bar, Advanced -> Debug Settings -> NoVerifySSLCert -> Set to TRUE -> Login This viewer is very very broken on SL though, good luck even getting your avatar to rez on it. It doesn't appear to support HttpInventory ,so - no inventory either. I can't tell what happens when I change body type - no inventory -> forever clouded avatar.

Jelli Kohime wrote: As for what feature I need? The morph effect when switching body types. Imprudence is the only viewer I've found that still does that. Huh - I have no idea what this is. You've made me curious enough to go & see if I can get Imprudence to login :smileylol:

Prokofy Neva wrote: I get this all the time, and worse, get it on avatar profiles. I can't see a profile unless I re-log in every time. This has got to be a bug. Sounds like a different pronlem if it's avatar profiles inworld. I suspect your bug is https://jira.secondlife.com/browse/BUG-10415 - [Valhalla] profiles and marketplace are asking for a login each session

JIRA issue filed: https://jira.secondlife.com/browse/BUG-11481 - SL website constantly loosing login information

It could possibly be this bug: https://jira.secondlife.com/browse/BUG-9699 which isn't fixed yet. There are steps to reproduce it in a comment near the end of the issue.

Prokofy Neva wrote: 2. Other people note intended to be banned may not be affected but *they are not likely in Second Life*. The chances that an IP ban affecting your RL neighbours 4-5 blocks away *and having them also play SL* is -- 0? 0.001%? It can happen though. We actually got bitten by this when we (meaning Firestorm QA) were testing the SLGO Onlive Firestorm viewer & it caused a bit of head scratching till we realised what was going on. We were testing region bans on alts and region banning an alt, who was using the SLGO viewer effectively banned every single person using that same SLGO viewer who wasn't an estate manager on that region. I suspect the same problem may happen to those using Bright Canopy.