Whirly Fizzle

Without steps to reproduce the problem, it can't be fixed. Providing an image attached to your JIRA issue (when you file it) that shows degradation when uploaded to the marketplace is the best thing to do. Is anyone else seeing image quality problems when adding images to their listings?

I can't reproduce this. Can you upload an image to an image sharing site that looks fine (and share the image link) but gets degraded when you upload it to the Marketplace?

Did you still get disconnected when you were using your cellular connection? Do you also get disconnected when using an alt account? It's possible your main account has an inventory issue which can cause login to time out which will result in disconnection soon after login or you will get fully logged in but when your inventory fetches in the background it can cause a disconnect.

Do you have "Hardware Skinning" disabled in Preferences -> Graphics?

A couple of years ago I had to use my cell network to connect to SL for a couple of weeks & the data usage was pretty horrific & expensive Using Firestorm, I would easily burn through 1GB of data in an hour at a busy event, less on an empty region without much content & my draw distance at 20m.

Is there a reason you have bandwidth set so low?

A recent viewer change added support for up to 30 second sound upload, BUT as far as I'm aware the serverside change needed to support this hasn't been implemented yet. As far as I know, 30 sec sound upload is coming soon (tm) but I haven't seen any official announcement yet when this will happen. It's also possible that only Premium or Premium Plus accounts will be able to upload sound files over 10 secs in length.

That's fine. The viewer logs will still have the information needed.

It's in Viewer-Neko https://bitbucket.org/lindenlab/viewer-neko/ The commits tagged with SL-6109

Can you run a session on Firestorm that fails to launch with the video driver error. Then close the viewer. Then zip up the Firestorm logs folder - how to find your logs: https://wiki.firestormviewer.org/file_a_jira#how_to_give_us_your_logs Upload the logs.zip somewhere & send me the link. You can PM me the link if you prefer or send to my email: whirly.fizzle at phoenixviewer dot com.

If you are interested in discussions about SL topics, then there are several weekly Linden user groups that generally have some lively discussion: http://wiki.secondlife.com/wiki/Linden_Lab_Official:User_Groups

File your ticket under Land & Region -> Region offline. Explain why you need the region restarted. Region offline tickets are fast tracked & generally LL will restart the region within 1 hour. The longest I've ever had to wait is 3 hours.

Do the Gyazo images display ok in a different web browser? If they do, clear cache & cookies from the Gyazo site on the problem web browser. Possibly a browser plugin you have installed is causing the problem too. As well as Gyazo, which I mostly use for the quick & easy 60 second gif capture, I use ShareX Wulfie mentioned above (useful for longer gif captures when needed) & for screenshots I mostly use Lightshot, which is excellent & free.

A large, flat inventory structure causing slow logins during the "Creating inventory views" stage has already been mentioned above. If you contact LL support, they can run an inventory script that will deflatten your inventory if needed. If you login with a clean cache on the affected account & the login time is much faster, then you could likely do with getting your inventory deflattened - creating inventory views is instant when inventory cache is empty. Also a large inventory will cause slower logout times too - your inventory cache is compressed & updated during the logout process. How much this affects your logout time will depend on the size & structure of your inventory & how fast your system is - a slow hard drive will be noticeably slower when updating your inventory cache at logout. One thing that hasn't yet been mentioned is that the larger your inventory size, the more memory is taken up by your inventory. On a system that's struggling already for RAM, using an account with a large inventory really can cause poorer performance then using an account with a small inventory. Each inventory item (where an item is a loose asset or a folder) takes up roughly 7kb of RAM & this can mount up quickly for accounts with a large inventory. My main account has ~150k inventory & my alts all have less then 15k inventory. When using my main account, just after the login the viewer will already be using at least 1GB more RAM then any of my alt accounts & this is pretty much down to my mains large inventory size. Can you post your system information from Help -> About Firestorm - click the "Copy to clipboard" button & paste your system info here.

LL are aware of the problem because they already imported this bug report: BUG-228204 - Search not updating traffic count

If you want a birds eye view of the scene, you can make use of the CameraOffset debug setting. You must have shadows enabled for this to work.

@Caleb Linden This link requires a LL sign in.

What's the parcel music URL?

This is the best JIRA issue that gives an explanation of why this problem happens: BUG-40694 - Rez Failure due to Mesh Physics Shapes resulting in massive Inventory Loss over time ( a collaborative effort ) Beq Janus & Polysail tl/dr: the cause of the problem is a *****ty physics model on the mesh you are attempting to rez onto. The creator of said mesh needs to fix their physics model.

Ingrids Prefabs

If you are really paranoid about someone getting your IP, use a VPN. If you don't use a VPN then the following actions can leak your IP address to interested parties: Being connected to voice. (Can also reveal your inworld location at any time if you have voice enabled.). Playing parcel music streams. Playing parcel media or MOAP. Clicking on any scripted object, even with media disabled (probably low risk but it's possible). Clicking any URL posted in chat.

Congrats on the first "Second Life is gonna die" thread of 2020. 💣

It is not possible.

VWR-13228 - Object can obtain and retain permissions indefinitely without avatar's knowledge and no way of knowing who took it - possible security issue

If it's the problem described above you'll need to get LL support to fix it. What's the affected region name?