Whirly Fizzle

If the viewer you are using does not have multi-threaded file pickers, you will get disconnected if you leave the file picker open for too long. The LL viewer only has a multi-threaded file picker when uploading a mesh model, not when uploading images. Some TPVs have multi-threaded file pickers for image upload & elsewhere. I'm not sure if any TPV has threaded pickers working on Mac & Linux. Firestorm only has multi-threaded pickers on Windows. ref: http://jira.phoenixviewer.com/browse/FIRE-5782

ChinRey wrote: But I swore never ever to file a JIRA again!!!

That seems normal to me. Flexis are one of the most expensive objects to render. As far as I'm aware, this is still the correct formula for calculating avatar complexity: http://wiki.secondlife.com/wiki/Mesh/Rendering_weight

They have a bug report for that crash: https://singularityviewer.atlassian.net/browse/SV-1407 May want to point them at the Firestorm fix for it: http://jira.phoenixviewer.com/browse/FIRE-4794 http://hg.phoenixviewer.com/phoenix-firestorm-lgpl/rev/e3e781423746

Is this the correct URL for the Mage magazine Youtube playlist? I'm able to view this playlist & watch the videos okay using MOAP on Firestorm, default LL viewer & the LL Valhalla (CEF) viewer on Windows 7 64bit.

Singularity has the option to crash or not to crash when an llerr is hit in the code. When you hit an llerr condition, the viewer is supposed to force crash. If you click Yes, you will crash. If you click No, you probably will not crash and can just carry on. However, if you hit an llerr condition, things have already gone badly wrong & choosing not to crash at that point can lead to all kinds of funky behaviour for the rest of the session. You are also very likely to just crash shortly after anyway. If you choose No, save anything important you are working on & relog as soon as possible.

Those are new feature requests though, not bugs with CEF. It's worth filing a feature request on the JIRA. Now is the best time to do it while it's still a project viewer.

Thats fixed upstream already, https://bitbucket.org/callum_linden/viewer-cef/commits/461f0bcd7673c7859dd6b3b70d1bc5d5fe1b9e3d JIRA issues: BUG-10431 - [Valhalla] Shared media sound does not fade with distance BUG-10426 - [Valhalla] Shared media/MOAP sound does not stop playing after leaving the region.

There are a number of people suffering from frequent TP disconnects on the HTTP RC viewer (http://wiki.secondlife.com/wiki/Linden_Lab_Official:Alternate_Viewers). If you are using that viewer you may find that's the problem. It should be fixed if you roll back to the default release viewer from https://secondlife.com/support/downloads/ Relevant JIRA issues: BUG-10598 - logged out when tping from one LM to another BUG-10607 - [CoreHTTP] Teleport issue failed at region and disconnected from SL viewer BUG-10624 - [CoreHTTP] I am not able to teleport anymore. Teleport goes slowly. BUG-10625 - [Core-HTTP] Attempting an intra-parcel TP when a forced landing point is set leaves TP screen hanging at "Requesting teleport" instead of showing "Could not teleport closer to destination" error.

If you mean the ability to block ad-hoc conference chats from everyone or just those initiated by non-friends, then you cannot do this on the Linden viewer, only on TPVs. All you can do on the LL viewer is enable "Only friends & groups can call/IM me" under Preferences -> Chat. I'm not sure if this option even limits conference chat though as it's technically a group chat. Try it and see anyway. I was too lazy to login and check it On the LL viewer you could also set yourself to Do Not Disturb mode on the LL viewer under Communicate in the top menu bar. DND mode will block all communications though, even that of friends. If you want to block receiving actual group chat on a per group basis, then you cannot do this on the LL viewer either. If you close the group chat window with the X, that group chat should not open again for you that session though, unless you manually open it yourself. That behaviour is a little flakey however.

Firestorm has it. Preferences -> Move & View -> Movement -> Double click on land...

I'm curious if the driver crash still happens if no web browser is open while running an SL viewer. Some people with Nvidia cards have found this driver crash is triggered by having a website page open displaying flash content while running an SL viewer - Chrome browser in particular seems to trigger the crash most easily. For those that use Firefox, disabling hardware acceleration for flash can fix the problem. I have another friend who suffered badly from this driver crash on her Win 7 system. Her card was factory overclocked and on the advice of Nvidia support, she set the card back to the default clock for that card and it totally fixed the problem.

You'll need to keep the organiser below these limits: Max 10k items in a single prim of the linkset - 10k per folder in the TMAT. Max 30k items in the whole object. If you want to wear your organiser as a HUD (like you can do with the TMAT), I think the limit for contents in a worn attachment is 10k in total. Any higher and you will not be allowed to attach it. If you have the TMAT though, be vary careful even getting close to these limits because the whole thing will just break once the limit is reached.

Someone else having the same problem: https://community.secondlife.com/t5/Second-Life-Viewer/Display-Driver-Error-Win10/td-p/2976130

Which viewer are you using? Make sure you do not have your own text colour and object text colour set to a colour that matches the window background too closely. LL viewer: Me -> Preferences -> Colors. Firestorm: Avatar -> Preferences -> Colors -> Chat Color.

Yeah, this is affecting other texture organisers too - see https://jira.secondlife.com/browse/BUG-10570 There was a change made on Tuesdays server roll which now limits the total number of object contents to ~30k. The number of object contents you can have in a single prim is 10k. (I don't think this limit is new). The total number of object contents you can have in a linkset is ~30k. (This seems to be new since Tuesday). There is also now a limit to how many object contents you can have in an attachment. If it is over the limit, you will not be able to wear that attachment.

Is your ISP Charter? Seems a few prople with that ISP are having the same problems. For example see https://community.secondlife.com/t5/Technical/teleport-crashes-and-connection-issues/qaq-p/2975631

Do you have the same problems when logging into a different region? If this only started after the rolls this week it's possible your region came back online with capabilities failure, which would cause all your symptoms. If it's a caps fail issue then everyone else logging into that region will also have the same problems. If logging into a different region fixes the problem then your home region needs to be restarted again. If you have the problem no matter which region you login to, then see Qie's advice above.

MAINT-5193 is the internal issue for https://jira.secondlife.com/browse/BUG-9140 You can see the internal issue MAINT number by looking under the History tab on 9140.

Aeon already filed the problem on Magnum with vehicle scripts resetting on region crossing. https://jira.secondlife.com/browse/BUG-10576 Going by http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_Magnum/15#15.10.23.306550 , Magnum has an extra "Blocks griefer attack method" fix. Magnum is running 15.10.23.306550 & BlueSteel & LeTigre are running 15.10.23.306566. Above says all RCs are on the same code though, so... your guess is as good as mine

Are you actually seeing an "Unable to decode the file storing your saved login credentials" error when you switch between the 2 connections on the same computer? Your login credentials are saved in the bin_conf.dat file (which is encrypted) located in your user_settings folder. On Firestorm you can get to that folder directly from Preferences -> Network & Files -> Directories -> Open Settings Folder.

Make sure you do not have "Select only my objects" enabled. In the top menu bar of the viewer, Build -> Options -> Select only my objects -> Untick that.

They are probably rigging to an attachment point. Have a look at https://jira.secondlife.com/browse/BUG-10543

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. Be aware that the Rift viewer will not work with the latest Oculus runtime though: https://jira.secondlife.com/browse/RIFT-184 - Doesn't work with Oculus Rift Runtime 0.7x

This video tutorial should help you: