Ansariel Hiller

What now? Turn an ancient Firestorm release into a modular viewer or start a new viewer? But again: Good luck with what you are trying to do! Seriously! Just thinking about the number of OpenSim users and how many of them actually provide patches for OpenSim compatibility...

The degree of a bug-free OpenSim compatible viewer is directly proportional with the availability of the OpenSim reference viewer. Regarding creating a modular viewer based on the current LL-based viewer code: Good luck with that!

I have a super brilliant idea: Create another account, something like InkScape20 aka Ink Scape 2.0 (which looks way more professional because of a higher version number), and login with the Linden Lab viewer for the first time, evading the Firestorm Community Gateway. Problem solved! P.S.: Did I mention InkScape20 would look far more professional?

Das war/ist ein Verbindungsproblem von Frankfurt rüber in die USA und hat nichts mit LL zu tun. Diverse andere Seiten, die in den USA gehostet werden, hatten ebenfalls massive Paketverluste und hohe Pingzeiten, z.B. latimes.com, cbssports.com, bitbucket.org... Seit ein paar Minuten scheint das Problem aber behoben. Aktuell keine Paketverluste oder unüblich hohe Pingzeiten mehr, auch Einloggen mit dem Main-Avatar geht wieder.

Oh the OP actually meant CPUs by Intel, AMD and ARM are affected in mulitple ways. If spreading news, do it right: https://googleprojectzero.blogspot.de/2018/01/reading-privileged-memory-with-side.html

Well... there is a setting to turn that off, but... yeah... I don't want to be accused of anything, so I better not say... :matte-motes-agape:

So... Added both options to Firestorm for next release!

Based on the XPOSE bug workaround I added to the Firestorm code recently, I could split that stop animation function in two: One function would just stop animations without revoking permissions, and the other function will additionally revoke permissions, too. So you wouldn't need to hassle with debug settings and have both methods at hand. That won't help anyone on another viewer though.

It depends. If you change the mentioned setting to false, invoking stopping avatar animations will not revoke script permissions granted to any objects in the current region. It will basically revert the function to the old behavior where it will stop animations, but if you granted permission to some griefer object for instance, it will retain the permission and can animate you over and over again. To make a long story short: You should know what you are intending when using the stop animation function. If there is an object (or griefer) constantly animating you, you should definitely set that debug setting to TRUE to revoke permission. If you don't need or want to do that, it should be safe to set that setting to FALSE.

As Firestorm dev I can say that this is clearly an XPOSE issue (incorrect way of triggering animations without prior check if animation permission is still granted). The issue on our JIRA leads to the conclusion that only the integrated pose stand in Firestorm 4.5.1 is affected, but as already mentioned previously, also stopping animations from the "Me" menu in any recent V3-based viewer will trigger this bug. While I have already worked around this bug in conjunction with the pose stand for the next Firestorm release, it will still happen whenever stopping animations from the "Me" menu is invoked - unless you set the debug setting RevokePermsOnStopAnimation to FALSE. That will stop animations, but leave all granted permissions to objects intact. This will work on any V3-based viewer.

https://secondlife.com/my/account/ip/index.php

With the official viewer? You can't! Options are evil so the official viewer doesn't offer that option. I heard Niran's Viewer will keep the "old" chat interface because Niran doesn't like the new one.

Use the steps described here to resolve the issue: http://wiki.phoenixviewer.com/fs_bake_fail

Clear the viewer cache: Open Preferences → Network & Cache. Go to the first path “Cache Location” and click the “Open” button behind the path. This will open a file explorer window displaying your current cache location. Logout (close the viewer) and then delete everything inside the folder currently displayed in your file explorer. Should you not be able to start the viewer to bring up Preferences, then locate the folder manually. In its default location, the folder is hidden on most OSs. To find it, you will need to show hidden folders. Now you need to locate the settings folder: Windows XP: C:\Documents and Settings\[uSERNAME]\Local Settings\Application Data\SecondLife Windows Vista: C:\Users\[uSERNAME]\AppData\Local\SecondLife Windows 7: C:\Users\[uSERNAME]\AppData\Local\SecondLife Mac: ~/Library/Caches/SecondLife linux: ~/.secondlife/cache Now continue as follows: Log back into SL, to a quiet region (try the Phoenix Support parcel or a Linden water region such as aich or hatton). On your inventory window, click “Recent Items”. Wait for your inventory to repopulate fully. The process may be sped up, if necessary, by typing random letters into the search bar. While inventory repopulates, do not teleport anywhere, and do not attempt to access anything in your inventory. Talk to people or surf the web. Watch as it repopulates. as long as you can see (Fetched…) at the top of the inventory window, it is still loading. Once inventory has repopulated, log out of SL once more, then log back in.

Syo Emerald wrote: For this kind of events I put everything I wear down and put a fullbody alphalayer on. Thats an easy way to know I'll pass every scriptscanner. I'd rather see that without the alpha layer!

Let's call it lazyness! For the mesh stuff they wanted to use the SSE2 pipeline of modern CPUs. But to be able to use them, you will need to align the memory that goes through the pipeline in a special way. The fastest way to do that was by using a different tool that allocates the memory whenever the viewer requests some, called tcmalloc. tcmalloc is so kind and aligns memory in proper way already, so you don't have to do that yourself. Unfortunately, it has several backdrafts, for instance crashes when TeamViewer or Skydrive or some other tool hooks into some Windows functions. This issue should hopefully be fixed soon as LL is trying to remove tcmalloc for quite a while already.

I already had that! Can I get a refund?

There is no general payment transaction log stored locally on your PC. The open_notifications.xml file contains only notifications that haven't been dismissed by you yet.

You might want to ask that question in the LSL Scripting forum: http://community.secondlife.com/t5/LSL-Scripting/bd-p/LSLScripting

You probably have Microsoft Skydrive or some other cloud storage tool installed. That is a (still) known issue with all mesh viewers at the moment. See here for solutions: http://wiki.phoenixviewer.com/cloud_storage

File an abuse report: http://community.secondlife.com/t5/English-Knowledge-Base/Filing-an-abuse-report/ta-p/700065

Click on the L$ balance in the viewer to update it directly from the server.

Edit the object and change the default action from buy to touch.

Might be too many notifications that are preventing successful login: Second Life Logs out During Login When you receive notifications, unless you dismiss them, they accumulate for later reading, in the small envelope icon on the lower right of the screen. Over time, they will grow in number. If you log out, these unread notifications are saved for when you next log in. If there are too many of them, processing them during next log in can cause a log in time out and you will be disconnected. The solution here is to delete the file with the saved notifications. Locate your SecondLife settings folder. If you do not see this folder, you may need to show hidden folders. On XP: C:\Documents and Settings\[YOUR USERNAME]\Application Data\SecondLife or use the environment variable %APPDATA%) On Windows Vista and 7: C:\Users\[uSERNAME]\AppData\Roaming\SecondLife (or use the environment variable %APPDATA%) On a Mac: /Users/[YOUR USERNAME]/Library/Application Support/SecondLife On Linux: ~/.SecondLife In this folder, open each folder which has the name of your SL account(s) and inside that, delete the file called open_notifications.xml - this will result in all past, unread notifications being lost.

Landing Normandy? Eat Soup?