[BUG-100791] Add OBJECT_AVATAR_COMPLEXITY to llGetObjectDetails

[sl-service-account]

The Avatar Render Cost reported by llGetObjectDetails(avatar_key, [OBJECT_RENDER_WEIGHT]) has been superceded by avatar complexity.

The ARC is limited to a maximum of 500,000, wheras complexity can go significantly higher. This prevents scripts from discerning between very complex avatars and extremely complex avatars.

Please add a new flag such as OBJECT_AVATAR_COMPLEXITY which scripts may use to get the avatar complexity.

Links

Related

• [BUG-4011] Changes to an attached object's scale or shape do not update Avatar Render Weight. #12132
• [BUG-4182] [Improvement] The new cap to Avatar Render Weight needs to be done post trend calculation to accurately reflect data as well as large changes. #13177
• [BUG-4010] Avatar Render Weights over 1 million are ignored by the ARW handler/server causing current OBJECT_RENDER_WEIGHT value to remain constant. #12131
• [BUG-100811] Remove 500k limit from llGetObjectDetails( OBJECT_RENDER_WEIGHT ) #332
• [BUG-134130] OBJECT_RENDER_WEIGHT does not return a usable value for avatars #2176

Original Jira Fields

Field	Value
Issue	BUG-100791
Summary	Add OBJECT_AVATAR_COMPLEXITY to llGetObjectDetails
Type	Bug
Priority	Unset
Status	Closed
Resolution	Not Applicable
Reporter	Casper Warden (casper.warden)
Created at	2017-06-06T13:07:48Z
Updated at	2017-08-13T16:39:03Z

{
  'Business Unit': ['Platform'],
  'Date of First Response': '2017-06-06T19:38:25.621-0500',
  'ReOpened Count': 0.0,
  'Severity': 'Unset',
  'System': 'SL Simulator',
  'Target Viewer Version': 'viewer-development',
  'What just happened?': 'The Avatar Render Cost reported by llGetObjectDetails(avatar_key, [OBJECT_RENDER_WEIGHT]) has been superceded by avatar complexity.\r\n\r\nThe ARC is limited to a maximum of 500,000, wheras complexity can go significantly higher. This prevents scripts from discerning between very complex avatars and extremely complex avatars.',
  'What were you doing when it happened?': 'N/A',
  'What were you expecting to happen instead?': 'Please add a new flag such as OBJECT_AVATAR_COMPLEXITY which scripts may use to get the avatar complexity.',
}

[sl-service-account]

Lucia Nightfire commented at 2017-06-07T00:38:26Z

It hasn't been superceded as it is the same data point.

The problem is, unlike with rezzed objects, the server is not being used to calculate physics cost, streaming cost, server cost, land impact and render weight for attachments.

LL opted to use trended data from multiple source viewers.

The data was also capped to prevent illegal tpv's from reporting incorrect low or high values.

This effectively made OBJECT_RENDER_WEIGHT useless as there is no guarantee that the number returned is a current or accurate value.

This has lead to issues such as BUG-4011 & BUG-4182.

Using the server to do the necessary calculations instead of the viewer would bring back stability and accuracy.

[sl-service-account]

Oz Linden commented at 2017-06-08T18:21:33Z

It is true that the server is reporting a value derived from the values reported by all nearby viewers. For various reasons, not all viewers will calculate exactly the same value, so it is not surprising that the servers value will usually not exactly match what any viewer reports.