Ardy Lay

Once upon a time, Second Life systems used the Resident's "last name" in a load balancing scheme. The load balancing had to be reworked when a last name became wildly popular. Since this change would take some time, the popular names were closed for enrollment and different names were rotated in. This put some granularity into the load balancing scheme again. I don't know that there is currently a technical reason for having time or quantity limits to enrolment into a last name, so, yes, it seems to be marketing driven now.

Yeah, wasted watt-hours, I suppose, but, the location seen by the eye is enough fresher to make a difference between winning and losing a competitive e-sports match and winning money to buy a 240Hz display to win the next one with! I'm not making this up. Lack of understanding does not alter facts.

In Second Life? Nothing. In first-person shooter games? You get to see slightly more up-to-date positions of objects and players.

Oh! Is that what all those GTFO signs floating around above the ground are? I thought I was being rudely told to stay away. I hate all that garbage on the map. What I mean by "overlays" is something that is only activated for the person looking at the map: Person Infohub / Telehub Land sale Events - General Events - Moderate Events - Adult Maybe an overlay could be added by providing a base URL to the data source and a toggle control to enable and disable it.

This is how you catch Second Life account scalpers.

Once upon a time, someone predicted that Linden Lab would stop development of Second Life Viewer because "more people use third party viewers than Linden's own viewer." Hasn't happened yet. I expect Linden Lab will restore World Map function. I have no clue what's taking so long. We have been told that it was highly dependent upon the service system architecture and that has been change dramatically. @Eddy OfarrelI have one suggestion: Metadata overlays If you can make your product better than LL's World Map then you may retain / gain users. Macro-overlays with things like continent names linked to the SL Wiki might be interesting. Shipping routes, race circuits, nautical and aeronautical navigation tools might be interesting. Some have asked for "community overlays" in the past but I am not aware of what those would be. Oh, and maybe ensure it works in the browser embedded in the Second Life Viewer, if it doesn't already. Something like a path-traveled and landmark plotter would interest me.

So, you don't know. Got it.

Does anybody know why avatars playing a common animation drift into synchronization after a while when viewed with Linden Lab's Second Life Viewer? I have been asked several times but can only call it a "happy accident" that resembles that described by the Kuramoto Model. This leaves me wondering what would be the mutual forces at work causing this drift into synchronization.

The region state saves are quite extensible in nature as they are compressed XML files that have, so far, been very compatible with new simulator versions. Buy Pass, on a per-parcel basis, is quite different than what I suggested for on-demand regions. I have only seen Buy-Pass, in the current form, used in four places over the years. One was a water park. One was a library. One was a theatre and I am not sure what the other was as the name of the parcel and what I could see from the border did not compel me to enter. I would expect use model and uptake for activating archived regions to be somewhat different.

Why would you assume I want to copy anything from Second Life to Open Simulator? I would want Linden Lab to have a product that allows the owner of a region to set it to a sort of "Buy Pass" state that allows it to be completely shut down until someone pays for it to be loaded so they can visit it.

I just played with Cool VL Viewer on another computer with another Second Life account. The World Map appears to be displaying the full-resolution tiles at all zoom levels except perhaps all the way out. That appears to have some sort of desaturated summary tile on display. Unfortunately, this approach resulted in the viewer ceasing to respond to OS service requests resulting it it being frozen from my point of view. It's "Cool" though. Just don't try to look at the whole world at once.

Would be nice if scarcely occupied meta-places could be archived for retrieval as depicted in Star Trek episodes with "holodeck" stories. Then, perhaps, we would not have to miss out on places that do not continuously rake in money to pay for continuous run-time resources. Imagine, if movie theaters had to have an auditorium for every movie ever produced because they had to be played continuously for ever or they would cease to exist. Unfortunately that's what we have been trapped into in Second Life. Too many wonderful places to visit in Second Life no longer exist because of the expense of keeping them playing continuously. (feature request)

Free things are free and good until they are no longer useful, perhaps due to being overloaded, or no longer free. They are costing somebody money to operate. When that someone cannot continue funding it themselves, they shut it down or attempt to charge. Nothing about Second Life is free. It is all paid for my someone. You may not pay for the parts you use but Linden Lab does, and it gets money from other residents that covers the costs of the parts that can be used without direct payment from the user. Likewise, any remote rendering client we have had available in the past has shut down because the money from paying users was insufficient to support the service, whether it had a non-paying tier or not. I "did the math" when considering either trying a remote client or purchasing parts to assemble a computer that would comfortably render Second Life locally. It was way less expensive for me to build the computer and pay for the energy it would consume, based on the number of hours I am on line daily. Using this data I formed the assumption that the remote rendering client would either cease to be free, impose strict usage limitations, or both. It did, for a while, then it was shut down due to insufficient cash flow from paying users. Since then a couple more attempts have been made to offer this service to Second Life Residents. The one I know of that survives is not specific to Second Life and is far from free. Speedlight is new, appears to be doing something that is not strictly installing an existing or slightly modified Second Life Viewer on a remote host and accessing it remotely. I hope Speedlight thrives in this endeavor. I won't be using it because I built a computer to run Second Life Viewer on, but Good Times to those that do use it!

From LL's viewer source: I have no idea what I am doing. This may not even be what you are talking about. I expected MAX_LOD_FACTOR to be equal to 2.0.

People only compare FPS? I know that's what's important to eyes and brains. Does anybody compare Ktris? I think it's a measure of how much geometry is rendered per frame and per second. All that geometry is, of course, from the objects rezzed and worn, and maybe from land water and sky? Is there a functional method in the viewer to NOT load textures? I see there is a switch in the menu, but does it work? It doesn't seem to stop all texture loading. Would be nice to be able to isolate the cause of long frame times between producing geometry and filling it with textures, or has the rendering method progressed beyond where those are separable?

Nobody mentioned agent collisions with other agents and with ground, objects and LARGE objects. How about investigating these and reporting on their effects?

Could this be due to _EXTREME_LOGGING_?

Is this a factor? Region Idling FAQ - Second Life Server - Second Life Community

Inventory is transferred in what I am going to call packages, because I need a name for them. The service is coded to put the entire contents of a folder, sans the contents of subfolders, into a single package. Each package is compressed and transmitted to the viewer. The Resident's computer has to receive and buffer the fragments of this package, then assemble any out-of-order fragments into proper order after detecting completion of the package. The Viewer then will decompress and parse the package of inventory items into records to be used by the Viewer's portion of the inventory representation. Somewhere in the Viewer is a TIME LIMIT to how long this process is allowed to take before some failure is assumed. Performance varies site to site and among Resident's computers. Some combinations can handle huge packages, some cannot. This MAY result in apparent random alternation between success and failure caused by changing network conditions. If the failure you are experiencing is caused by the inventory conditions Prokofy Neva described, then the action Prokofy suggested will resolve it. Linden Lab has studied this issue and has determined a safe quantity of inventory items per folder. Resolution can also be achieved if you have an alternative and better performing login option. This could be accomplished by changing rendering settings to reduce work load prior to logging in. This could also be accomplished by using a higher bandwidth Internet access solution. Unfortunately, knowing if these attempts will be successful involves some experimentation. This experimentation may not be something you wish to undertake.

Likewise, advertising online makes no sense if one makes the same assumption, in that "the majority of people" use an effective ad blocker. Has this stopped advertising? Unfortunately, no. 😉 Let the strutting continue, it's less harmful than online advertising.

Perhaps this is "the game" they speak of.

That's called a bribe collector. See ad blocking and malware blocking companies for references.

Meanwhile, the lawyer was writing up three patent applications and mailing them to himself via a post office in a small town in Utah whose postmarking machine is still not Y2K compliant.

What did the engineer make of this?

"Modern trends" is not much of a description. Can you expound upon this some? I would like to hear what would fix Second Life, and less about what didn't.