Perrie Juran

Have you tried asking about this in the Inworld Support group? They are probably best equipped to help you.

Wow! All it takes is right click on the tool bar > unlock. Then you can remove all the buttons and/or add ones you like. Also not sure what your difficulty is with FS's inventory window. I do occasionally use LL's viewer and I find their inventory window clunky.

Check your Black list (which is different than your Block list). World Menu > Blacklist

This is the list of things Dullahan is needed for: Websearch Web profiles Built-in browser Splash Screen when the viewer is launched Media-based HUDs Avatar Menu - Choose an Avatar Destination Guide https://wiki.firestormviewer.org/fs_media Dullahan not functioning will not stop you from logging in.

Correct. The privacy features work at any height.

Ban line height for "no entry" or "pay to access" (in other words, "allow public access" is turned off, or "allow group access" is turned on, in the parcel options) is the parcel's ground elevation plus 50 meters (except, if the region has been set to "Block Parcel Fly Over" in which case the access controls extend to at least 4096 meters). If a user is explicitly banned by name, the height is the parcel's ground elevation plus 5000 meters. On current viewers this is visible to the full extent. https://wiki.secondlife.com/wiki/Limits Add into this mix Security Orbs with two second fuses and it is virtually impossible to fly my Flying Saucer across the Mainland. So yes it is time for Linden Lab to fix this. The ban lines should not be extending all the way into the Stratosphere. Maybe at best a couple of hundred meters. It's not like I am going to spy on you while flying across your parcel. So yes it is time for Linden Lab to fix this!

If you use RLVa check your RLV device. Thee is a RLV function that messes with hover height. You'd have to ask someone who knows more about RLV than me for details. I am only aware of this.

First, as to what SLplugin does: "slplugin is needed to view any media content in the viewer & the slplugin processes are launched & culled by the viewer as needed. There will be one slplugin process for each media instance the viewer is currently using - so for example you will have one slplugin launched to load the login screen image (which is essentially just a web page), another launched when you open a web profile, another launched when you open web search, another launched if you open the destination guide in the viewer & parcel media or MOAP objects inworld will each have their own slplugin instance. " Second, the usual cause of plugin failure is overaggressive Anti Virus. It is really nuts. You can be happily going along your SL way and suddenly the AV decides it doesn't like the plugin. This happens randomly with all three of the executables in the viewer, Slplugin, Dullahanhost & Voice. Hence the need to add them to the exclusion list in your AV. There may be other reasons for it failures but AV false flagging is by and large is the most common.

Why in the heck would any merchant use a 2048 texture for a group picture? It would make me question how much they pay attention to optimization.

<hijack> Regarding "Frames Per Second" I think there is a lot of misunderstanding. There was an excellent discussion in this old thread: Pay close attention to Masami Kuramoto's comments. </hijack>

Fascinating. But I would say this, these are user enabled settings so in that sense it does not happen automatically.

This will only pertain to the United States.

I rarely use voice. Most people find a Martian's voice too painful to listen to. Kind of a cross between Bob Dyan and a dying dog, only an octave higher.

There are too many Lindens who do not have a Second Life and yet are allowed to design things for it.

There is nothing stopping any one from self compiling a TPV viewer. One of the TPV rules is that they have to keep their code available in a public repository. Now the next question is how will LL deal with the other TPVs.