• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: MISC-884
Type: New Feature New Feature
Status: Closed Closed
Resolution: Won't Finish
Priority: Normal Normal
Assignee: Unassigned
Reporter: Jessie Azure
Votes: 2
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
4. Second Life Misc Issues - MISC

New Beacon Request: Show Temporary Objects

Created: 13/Jan/08 04:31 AM   Updated: 27/Mar/08 01:59 AM
Return to search
Component/s: Miscellaneous
Affects Version/s: None
Fix Version/s: None

Issue Links:
Relates
 


 Description  « Hide
While some of the current standard debugging tools and Estate Manager options we have available are helpful, they all lack the ability to find an object with the "Temporary" parameter set.

Using http://jira.secondlife.com/browse/SVC-1166 as backup, the reason for my suggestion is quite simple - temporary prims are counted in the regions 15,000 total. Objects such as bullets aren't the primary concern though, as they are normally killed without any hassle. The main issue a lot of Estate Managers may be finding is their residents unfairly using the regions object count with temp-rezzers.

A parcel has an assigned prim allocation, based on 'land size in m2' x 'region bonus multiplier', and this total should be binding. However, one of the most annoying issues to deal with is hearing a resident in a region tell you they have been experiencing horrible "lag" over the past few days, and are now getting a blue dialogue error message: "Cannot create object - Server full". I'm not siding either way with the TOS argument, nor am I condemning or encouraging the use of temp-rezzers (or other "free prim" devices), but when your Covenant states that they are disallowed, there should be an easy way to identify them.

To put it into perspective, I'll give an example: A region has a 'limit' of 15,000 prims. Splitting a region up into 15 equal parts should allocate approx 1,000 prims per parcel. The residents of 10 parcels choose to place 1,000 objects each on their own parcel, and 4 parcels remain unsold with no objects. This gives the region a total usage of approx 10,000 objects so far.

The owner of the last region decides they are not happy with the 1,000 prim limit, and finds an effective - though not ideal - workaround. Using a temp-rezzer for the 500 prim house, another for their 1,000 prim boat, their 300 prim helicopter, 2 cars at 600 prims a piece, plus normal non-temporary furniture and fittings of 700 prims. They now have taken 3,700 of the regions total count. Should the last 4 parcels be sold, the region now has 300-ish free prims to spare for all 4 - even though all 4 are promised with 1,000. But this is only half of the issue.

Most temp-rezzers actually rez a new copy of an object at a set interval. As most temporary objects have a life of about 60 seconds, many temp-rez scripts are set to rez the object every 45-55 seconds, to ensure that there is no noticeable flicker or empty space when the old object dies, and the new one takes its place. Depending on the size, complexity of linked prims, textures, scripts etc of the cyclic rezzed object is directly related to how poor the region responds at the exact moment it's dying and rezzing again. Script, Images, Sim Time (physics) and Total Frame Time are the worst Times to be affected, spiking to unreasonably high figures. This, in turn, draws the Sim FPS and Physics FPS of the region down, bringing with it too, the Time Dilation. Regions become very slow, very fast during these times; you can't move, can't fly, can't build, chat is delayed, region crossings or teleports have reduced success. Sure, it only lasts a few seconds.. but a few seconds every 45-60 seconds.

The current method I personally use to find temp-rezzers on our land, is enabling "Show Updates", and hoping to catch a cluster of green. Not a reliable method, and not very time efficient, I know. Estate Managers tools may show the script if you're lucky, but as residents are getting smarter, they push the boundaries more.. and start calling the rez script something anonymous like "Sit pose 1" or "John's script" to avoid detection.

Perhaps the usefulness of having it as an actual "Beacon" in the View drop down menu goes - it may not be too popular. But at least adding the option into the Estate Managers Tools menu, I predict, would be a very welcome inclusion to many Estate and Private Island owners.

(PS: Apologies on the long post.)



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Harleen Gretzky made changes - 30/Jan/08 07:55 PM
Field Original Value New Value
Link This issue Relates to SVC-1166 [ SVC-1166 ]
Jessie Azure made changes - 27/Mar/08 01:59 AM
Resolution Won't Finish [ 2 ]
Status Open [ 1 ] Closed [ 6 ]
Sue Linden made changes - 13/Nov/08 11:52 AM
Workflow jira-2007-12-22a [ 51147 ] jira-2008-11-14 [ 78649 ]
Sue Linden made changes - 13/Nov/08 04:25 PM
Workflow jira-2008-11-14 [ 78649 ] jira-2008-11-14a [ 85760 ]