2020 Content Creation User Group week #38 summary

Glitch Social, July 2020 – blog post

The following notes were taken from my audio recording and chat log of the Content Creation User Group (CCUG) meeting held on Thursday, September 17th 2020 at 13:00 SLT. These meetings are chaired by Vir Linden, and agenda notes, meeting SLurl, etc, are are available on the Content Creation User Group wiki page.

EEP Fixes

There is now only one major EEP issue out of the current batch that has been undergoing work that remains unresolved, and it is being worked on. This means the current Love Me Render (LMR) RC viewer (version 6.4.8.547427 at the time of writing) is close to being ready for update and promotion – although it is likely the current Bormotukha Maintenance RC viewer (version 6.4.8.548394) will be the next viewer to be promoted to de facto release status.

Project Jelly  – Jelly Dolls Improvements

  • Vir’s work in updating Jelly Dolls is now available in the Project Jelly viewer, version 6.4.8.547487 at the time of writing).
  • A number of bug reports have been filed on this, and fixes are currently with QA, so the hope is the project viewer will be updated “fairly soon”.

Mesh Uploader

  • It is likely the Mesh Uploader RC, version 6.4.8.548061 at the time of writing) will move towards release more-or-less as it is now, rather than being held over for significant updates.
  • There have been concerns over the design of the new tabs within the updated uploader and how discoverable some of the added controls really are.  However, the consensus opinion at the lab is to leave things as is, and if there prove to be significant UI issues with the updated uploader, to deal with them in a future update.
  • Things like the ability to specify pivot points within a mesh (e.g. for hinging doors, etc., rather than having the pivot point aligned through the centre of the object), requires simulator-side support, and so this won’t be dealt with until after the cloud uplift work has been completed.
  • So, as it stands, it is felt the Mesh Uploader RC is also in line for possible promotion alongside the Maintenance RC.

Bakes On Mesh

While Bakes of Mesh has seen the introduction of BoM clothing to a degree, the take-up has perhaps not been as widespread as might be the case, with some body / head makers yet to fully embrace it.  Two of the most commonly-cited reasons for this are:

  • Lack of full specular / normal map support (something that would require a further large-scale overhaul of the avatar Bake Service, so not easy to implement at this point in time).
  • The problem of established user behaviour and an unwillingness to change from that behaviour, It is claimed that people have become used to mesh bodies having multiple alpha cuts (which add to their complexity) and being able to “hide” specific parts of the body at will via a HUD-based, scripted system, and are unwilling to switch to the direct use of alphas, which need to be located and applied manually.
    • Some mesh clothing designers do actually provide a means to “auto hide” parts of a mesh body when their clothing is worn, but they appear to be in a minority of mesh clothing makers.

Cathy foil has been brainstorming how both of these issues might be resolved without the need to necessarily dramatically overhaul the Bake Service in the case of specular and normal maps, and so as to allow the easier application of alpha textures to mesh bodies that would enable more fluid “hiding” of body parts when wearing mesh items or BOM layers. Her solution is to both increase the number of alpha channels available for use with mesh bodies (which would not impact the Bake Service) and Linden Lab “borrowing” from RLV / RLVa to allow a HUD to be used to  apply clothing / alphas to a body directly from inventory, as she explains in the video below.

The alpha solution offered is perhaps not entirely ideal (what about alpha conflicts when mixing / matching clothing from different makers?), and it might be argued that – insofar as the use of the Outfits folder + the WEAR + ADD options for general folder use, that the wearing / applying alphas may not be as significant an issue as might seem to be the case – but again, this can depend on the user behaviour / the clothing itself and how it is worn.  Any “official” adopt of RLV capabilities, even if restricted to just your own avatar, would also seem to be questionable in terms of adoption by LL (if nothing else, the code would need to be contributed).

However, as there was little time at the meeting to go through the video thoroughly, this is a subject that is liable to be further discussed at future meetings – although for any work to proceed from it (or in relation to BOM in general), a feature request Jira will be required.

In Brief

  • There was an extensive (and theoretical, at this point), discussion on mesh bounding boxes (e.g. allowing different sized bounding boxes – with certain constraints – per LOD). However, I’ll save further reporting on this until there is a feature request Jira to which I can refer readers (hopefully by the next CCUG).
  • Vir asked a general question on whether people would like to seen the animation uploader receive and update pass, and if so, what they would specifically like to see.
    • Suggestions included:
      • Improvements to the preview panel for better tracking of offsets.
      • Running .ANIM files through the uploader (as long as this is not made compulsory, as some animators prefer not to use the uploader).
      • Suggestions focused more on being able to either edit uploaded animations or to use the uploader as a means of exporting your own animations to make change.
    • The conversation also encompassed animation priorities, and the ability to either change them or constrain them better. As priorities can be baked into a mesh, Vir suggested rather than a greater ability to edit and change priorities might be to have them set at runtime, rather than being an object attribute.
    • General feedback on animation improvements included the ability to made adjustments to animation speed on the fly, better pre-loading of animations in a sequence, etc.
    • Jiras on specific features / improvements have been requested to help determine what might need to be done, what the scope of work might be, etc., to help determine feasibility.
  • Date of next meeting: Thursday, October 1st, unless otherwise indicated on the CCUG wiki page.

2020 Content Creation User Group week #36 summary

Aspen Fell – The Notebook, July 2020 – blog post

The following notes were taken from my audio recording and chat log of the Content Creation User Group (CCUG) meeting held on Thursday, September 3rd 2020 at 13:00 SLT. These meetings are chaired by Vir Linden, and agenda notes, meeting SLurl, etc, are are available on the Content Creation User Group wiki page.

EEP Fixes

Love Me Render

  • The current Love Me Render (LMR) viewer (version 6.4.8.547427 at the time of writing) contains a number of EEP fixes (as well as other rendering updates) These include:
    • BUG-229107 [EEP] [Improvement] Ice level Slider Graduation.
    • SL-13539 [EEP] Large reflection on the water when facing certain angles.
    • BUG-228992 [EEP] Appearance lighting is broken when ALM is enabled.
    • BUG-228914 [EEP] Deferred Soften Shader fails to link when Atmospheric Shaders are disabled. This causes Debug viewer builds to crash.
    • BUG-228882 [EEP] Disabling glow rendering while ALM is off results in massive rendering flicker.
    • BUG-228781 [EEP] Specular color interpreted wrong (too bright) from point lights.
    • BUG-228581 [EEP] Specular map reflections are way too weak.
    • BUG-228840 [EEP] cloud texture is rendered backwards.
    • BUG-228431 [EEP] Water lighting is wrong at certain camera angles.
    • BUG-228752 [EEP] Sky turns black when render quality is lowered to Low-Mid.
    • BUG-225784 [EEP] BUG-225446 regression – HUDs are again affected by environment setting and BUG-225446 [FIXED] [EEP] HUDs are affected by Atmosphere & Lighting changes.
  • These a further EEP updates to come, likely in the next LMR viewer, which will hopefully be issued in the next week or so. These should include a fix  to allow horizon haze to modify the Sun’s light and tint when it is close to the horizon.

Additional EEP Issues

  • Moonlight: the Lab is also aware of a number of lighting issues related to the Moon (attenuation of moonlight through clouds, for example. Again, these will be addressed in time.
  • Mainland ambient lighting: users have repeatedly noted that the default Mainland environment remains darker than under Windlight.
    • This is the result of an error made during the EEP deployment that now requires a simulator-side configuration update to be made that is slightly complex in terms of implementation.
    • Essentially, a code fix needs to be made, and then a new estate setting added to the simulator code to manage it, together with code to ensure the update is correctly propagated to the affected regions.
    •  Currently, the resources required to develop, test and implement the required changes are all heavily engaged in cloud uplift work.
  • Density Multiplier issue: this is the result of the simulator restricting the multiple value. A fix for this is an upcoming simulator release.
  • Linden Water / performance issue:
    • As noted in previous CCUG summaries, rendering Linden Water appears to impact viewer performance to a greater degree than previously (leading to some simply disabling Linden Water rendering (CTL-ALT-SHIFT-7).
    • LL currently don’t have a solution for this, in part because the precise point in rendering where the bottleneck seems to occur is proving hard to pin down.
    • Some  suggestions for dealing with it were put forward at the meeting, including:
      • As there does not appear to be occlusion culling for water, perhaps auto-disabling Linden Water from being rendered in the viewer above a certain altitude (where the water generally isn’t visible anyway).
      • Or adding a special texture UUID that, when set via EEP in a region / parcel,  resulting in Linden Water rendering being disabled (CTRL-ALT-SHIFT-7, effectively) for all viewers within the region / parcel, rather than people having to manually disable Linden Water rendering. This could be helpful for major indoor shopping events, etc.
      • Note: both of the above were user-made suggestions, not ideas that have been implemented.
  • Specularity issues: EEP has altered specularity rendering such that specularity in point lights can appear too bright, and in Sun / Moon light, too dim. Fixes for this are in the currently LMR viewer referenced above, but there is some disagreement as to how well (or not) they correct issues.
    • Part of this may be the result of EEP making adjustments so the specularity in objects appears more realistic, but creators have previously had to manually compensate for a weakness in specular map rendering in the past.

ARCTan

  • Vir’s work in updating Jelly Dolls is now available in the Project Jelly viewer, currently availability as a project viewer (version 6.4.8.547487 at the time of writing). This work is also likely to find its way into a Maintenance viewer at some point.

In Brief

  • Date of next meeting: probably Thursday, September 17th, 2020.

2020 Content Creation User Group week #34 summary

Cascadia, June 2020 – blog post

The following notes were taken from my audio recording and chat log of the Content Creation User Group (CCUG) meeting held on Thursday, August 20th 2020 at 13:00 SLT. These meetings are chaired by Vir Linden, and agenda notes, meeting SLurl, etc, are are available on the Content Creation User Group wiki page.

SL Viewer

Currently, the official viewers remain unchanged from the start of the week:

  • Current release viewer version 6.4.7.546539, dated August 11, promoted August 17, formerly the Arrack Maintenance RC viewer – NEW.
  • Release channel cohorts:
  • Project viewers:
    • Custom Key Mappings project viewer, version 6.4.5.544079, June 30.
    • Copy / Paste viewer, version 6.3.5.533365, December 9, 2019.
    • Project Muscadine (Animesh follow-on) project viewer, version 6.4.0.532999, November 22, 2019.
    • Legacy Profiles viewer, version 6.3.2.530836, September 17, 2019. Covers the re-integration of Viewer Profiles.
    • 360 Snapshot project viewer, version 6.2.4.529111, July 16, 2019.

General Viewer Notes

  • The Legacy Profiles viewer has been further prevented from making progress due to additional web-side changes that need to be made to enable privacy settings (who can see your feed posts) to work correctly.
  • The Mesh Uploader has been integrated with further changes, and is currently being merged up to the current viewer release code base, after which it will go to QA. Providing it passes, it could be appearing as updated RC viewer in week #35. This viewer provides:
    • Additional information on meshes at upload, a-la those added to Firestorm (see: Firestorm 6.0.2: Animesh release, February 2019)
    • UI improvements to give better information on avatar rigging & related error messaging.
    • Improved error messaging overall.
    • It will also include various fixes (such as BUG-229032 “[Mesh Uploader] Use Joint Positions Option causes ‘Collapsed Joints/Bones’ for some Files”) that are currently being worked on.

Project Muscadene (Animesh Follow-On)

Project Summary

Currently: offering the means to change an Animesh size parameters via LSL.

Current Status

  • Still officially on hold.
  • Will include shape sliders for Animesh – although it should be remembered body shapes and sliders are intended for humanoid avatars, not animals, etc.

Using the JIRA

Complaints were raised about the need to raise Jira bug reports for issues that are “raised in chat”. Simply put:

  • Describing an issue (often loosely) in chat  – or Voice, which is often the medium for meetings – actually doesn’t mean the issue is captured and recorded. It also doesn’t necessarily mean the issue has been properly described, as those talking about it are not being encouraged to think about the issue in a structured manner or provide illustrations that can better help with understanding precisely where their problem lies.
  • The Jira system provides a means by which:
    • Information can be captured in a structured manner.
    • It can be illustrated.
    • It can be updated with further observations, feedback from others, etc.
    • It can be referenced, searched and cross-referenced, potentially helping other users understand a problem they are encountering and allowing the Lab to better understand the overall impact of an issue.
    • At the end of the day, issues reported by Jira stand a better chance of being fixed at some point that those just chatted about (which likely have a 0% chance).
  • Raising Jira reports – Bug or Feature Requests – isn’t actually hard. See:

ARCTan

Project Summary

An attempt to re-evaluate object and avatar rendering costs to make them more reflective of the actual impact of rendering either in the viewer. The overall aim is to try to correct some inherent negative incentives for creating optimised content (e.g. with regards to generating LOD models with mesh), and to update the calculations to reflect current resource constraints, rather than basing them on outdated constraints (e.g. graphics systems, network capabilities, etc).

As of January 2020 ARCTan has effectively been split:

  • Viewer-side changes, primarily focused on revising the Avatar Rendering Cost (ARC) calculations and providing additional viewer UI so that people can better visibility and control to seeing complexity.
  • Work on providing in-world object rendering costs (LOD models, etc.) which might affect Land Impact will be handled as a later tranche of project work, after the avatar work.
  • The belief is that “good” avatar ARC values can likely be used as a computational base for these rendering calculations.

Current Status

  • It now appears that Vir’s work in updating Jelly Dolls will now appear in the ARCTan viewer, when that eventually emerges, but may also (and possibly sooner) appear in a Maintenance RC viewer.
  • Overall, ARCTan has been held-up awaiting a fix for an Bake Service issue. Vir believes he now has that fix, and is waiting for it to be deployed to one of the Lab’s internal text grids so he can check to see if it works. Assuming it does work, the fix will be queued for deployment to the main grid and allow performance data gathering to resume.
  • Discussions are to resume regarding better UI elements to support information on complexity, etc., that users can understand and use.

In Brief

  • Animesh:
    • minimum default 15 Land Impact: it is apparently putting some creators off of trying to make Animesh items (notably breedables). It’s been suggested lowering this to 10 LI might help generate greater interest in Animesh creation. Right now, LL haven’t done enough analysis to determine how the figure might conceivably be changed, rather than just making an arbitrary adjustment.
    • Bakes on Mesh support: this has been discussed on a number of occasions. There are no plans to provide support for Animesh to use Bakes on Mesh in the foreseeable future, as it requires Animesh to be overhauled to have full inventory support, together with outfit support, and would also require a significant update to the Bake Service to recognise and support Animesh characters.
  • Date of next meeting: probably Thursday, September 3rd, 2020.

2020 Content Creation User Group week #28 summary

Wision, May 2020 – blog post

The following notes were taken from my audio recording and chat log of the Content Creation User Group (CCUG) meeting held on Thursday, July 2nd 2020 at 13:00 SLT. These meetings are chaired by Vir Linden, and agenda notes, meeting SLurl, etc, are are available on the Content Creation User Group wiki page.

This meeting featured a lot of general chat on possible features and / or performance improvements that might (or “should”) be made to SL, comparisons in the pros and cons of incremental changes over “radical” changes (e.g. the former can be turned around more quickly, but can be finite in pact; the latter can dramatically change/ improve SL, but on a time frame that means that when they are delivered, they’re not what users are looking for / they don’t actually deliver what had been anticipated), etc.

SL Viewer

Currently, the official viewers remain unchanged from the start of the week:

  • Current Release viewer version 6.4.3.543157, dated June 11, promoted June 23, formerly the CEF RC viewer – No Change.
  • Release channel cohorts:
  • Project viewers:
    • Custom Key Mappings project viewer, version 6.4.5.544079, June 30.
    • Mesh uploader project viewer, version 6.4.4.543141, June 11.
    • Copy / Paste viewer, version 6.3.5.533365, December 9, 2019.
    • Project Muscadine (Animesh follow-on) project viewer, version 6.4.0.532999, November 22, 2019.
    • Legacy Profiles viewer, version 6.3.2.530836, September 17, 2019. Covers the re-integration of Viewer Profiles.
    • 360 Snapshot project viewer, version 6.2.4.529111, July 16, 2019.

General Viewer Notes

  • The Tools Update RC viewer is on track to be promoted to de facto release status, possibly on Friday, July 17th, or more likely week #29 (commencing Monday, July 20th).
  • The Love Me Render viewer is still seeing additional EEP fixes added to it, as well as some other issues that are being looked into.
    • The upcoming version of the LMR viewer will include a fix for the EEP specularity issue (see BUG-228781 and BUG-228581).
    • BUG-229079 “[EEP] Density multiplier does not allow full range of settings to be saved/loaded”, requires adjustments to be made to both the viewer and the simulator code.
    • BUG-229031 “[EEP] Water has a large performance hit on EEP” has been accepted, an analysis has yet to be completed.

ARCTan

Project Summary

An attempt to re-evaluate object and avatar rendering costs to make them more reflective of the actual impact of rendering either in the viewer. The overall aim is to try to correct some inherent negative incentives for creating optimised content (e.g. with regards to generating LOD models with mesh), and to update the calculations to reflect current resource constraints, rather than basing them on outdated constraints (e.g. graphics systems, network capabilities, etc).

As of January 2020 ARCTan has effectively been split:

  • Viewer-side changes, primarily focused on revising the Avatar Rendering Cost (ARC) calculations and providing additional viewer UI so that people can better visibility and control to seeing complexity.
  • Work on providing in-world object rendering costs (LOD models, etc.) which might affect Land Impact will be handled as a later tranche of project work, after the avatar work.
  • The belief is that “good” avatar ARC values can likely be used as a computational base for these rendering calculations.

Current Status

  • It’s still not clear in the Jelly Doll updates will appear in an ARCTan project viewer or within a project viewer of their own. These are more generic Jelly Dolls that improve their rendering.
  • It might be preferable for the Jelly Doll updates to move to their own project viewer, as ARCTan is awaiting a Bake Service update, which is in turn held up due to the on-going cloud uplift work.
  • There was a scare that the ARCTan updates might cause a performance hit – although this might be down to a system configuration issue and is still being investigated.

In Brief

  • There is some background work going on to update the Second Life systems requirement page. Not so much because SL’s requirement have changed, but simply to bring them more in-line with modern systems.
  • The data the Lab does gather on client systems indicate that a lot of users are based on laptops using on-board graphics and “a lot on older systems”.
  • Next meeting: Thursday, August 20th, 2020.

2020 Content Creation User Group week #27 summary

Yes – Endless, May 2020 – blog post

The following notes were taken from my audio recording and chat log of the Content Creation User Group (CCUG) meeting held on Thursday, July 2nd 2020 at 13:00 SLT. These meetings are chaired by Vir Linden, and agenda notes, meeting SLurl, etc, are are available on the Content Creation User Group wiki page.

SL Viewer

  • A Custom Key Mappings project viewer, version 6.4.5.544079, was issued on Tuesday, June 30th.

The rest of the official viewers in the pipeline remain as follows:

  • Current Release viewer version 6.4.3.543157, dated June 11, promoted June 23, formerly the CEF RC viewer.
  • Release channel cohorts:
    • Love Me Render RC viewer, version 6.4.5.544028, June 30.
    • Tools Update RC viewer, version 6.4.5.544097, June 25 – this viewer is built using VS 2017 / a recent version of Xcode, and Boost.Fiber. It contains no user-facing changes.
    • Arrack Maintenance RC viewer, 6.4.5.544024, issued on June 24 – this viewer uses Viewer Manager 2.0.538279.
  • Project viewers:
    • Custom Key Mappings project viewer, version 6.4.5.544079, June 30.
    • Mesh uploader project viewer, version 6.4.4.543141, June 11.
    • Copy / Paste viewer, version 6.3.5.533365, December 9, 2019.
    • Project Muscadine (Animesh follow-on) project viewer, version 6.4.0.532999, November 22, 2019.
    • Legacy Profiles viewer, version 6.3.2.530836, September 17, 2019. Covers the re-integration of Viewer Profiles.
    • 360 Snapshot project viewer, version 6.2.4.529111, July 16, 2019.

General Viewer Notes

  • The Love Me Render (LMR) RC viewer is still absorbing fixes for EEP and rendering issues. Version 6.4.5.544028, dated June 30th includes a fix for BUG-225784 “BUG-225446 regression – HUDs are again affected by environment setting”. This viewer will hopefully in time include a fix for specularity issues (see BUG-228781 and BUG-228581).
  • It looks like the Legacy Profile viewer could be getting promoted to RC status very soon.

ARCTan

Project Summary

An attempt to re-evaluate object and avatar rendering costs to make them more reflective of the actual impact of rendering either in the viewer. The overall aim is to try to correct some inherent negative incentives for creating optimised content (e.g. with regards to generating LOD models with mesh), and to update the calculations to reflect current resource constraints, rather than basing them on outdated constraints (e.g. graphics systems, network capabilities, etc).

As of January 2020 ARCTan has effectively been split:

  • Viewer-side changes, primarily focused on revising the Avatar Rendering Cost (ARC) calculations and providing additional viewer UI so that people can better visibility and control to seeing complexity.
  • Work on providing in-world object rendering costs (LOD models, etc.) which might affect Land Impact will be handled as a later tranche of project work, after the avatar work.
  • The belief is that “good” avatar ARC values can likely be used as a computational base for these rendering calculations.

Current Status

  • Vir’s updates to jelly dolls have hit a couple of issues whilst in QA, but should still get rolled into the ARCTan project once he’s had a chance to fix them.

In Brief

Pathfinding Navmesh

  • A request was put forward to allow scripted access to rebaking a region’s navmesh (used with Pathfinding).
  • A use case for this would be something likes a procedural game where elements of the scene may be placed via script in accordance with progress.
    • As alterations to a scene impact the navmesh, this can upset NPCs using it.
    • Currently, the only way to rebake is via manual intervention, which can be missed.
    • Offering a scripted means would ensure the navmesh is automatically updated when required.
  • This type of scripted update has been requested in the past, and generally frowned upon due to the risk of potential abuse. However, risk could be mitigated by limited the scripting option to estate owners / managers, and using a throttle on the number of allowed requests.
  • That said, multiple rebakes of the navmesh can themselves have a cumulative impact on simulator performance and resources (particularly on Homestead regions), such that a region restart is required to correct matters, which might in some cases be as disruptive, so this would likely need to be re-examined.
  • Currently, there are no plans to work on Pathfinding in the short-to-medium term, however, it has been requested that the idea is written up as a feature request for review by the Lab.

Other Items

  • There as been a request for the viewer to support Scalable Vector Graphics (SVG) image format (see: BUG-229007). However, this would require an extensive overhaul of the graphics pipeline (which currently uses JPG2000) in order to ensure all texture handing had a code path for running SVG. So this is not a likely target for a project.
  • There was a general discussion on the animation system and file formats (.ANIM and .BVH) including long-standing requests to overhaul the system and provide overrides for priority, speed, start / stop frame, etc., and more informed control of easing out/in to the animations. Currently, there is no work being planned for the system, however.
  • A request has been made to allow for scripted interrogation on how people are using EEP. The specific use case would be a game or similar, where a specific environment has been set (e.g. fog / reduced visibility) and the system could query incoming systems to ensure the viewer is set to Use Shared Environment, and if not, advise the user they need to change their setting. Not clear if / how this will be addressed.
  • Next meeting: Thursday, July 16th, 2020.

2020 Content Creation User Group week #25 summary

Thermae, May 2020 – blog post

The following notes were taken from my audio recording and chat log of the Content Creation User Group (CCUG) meeting held on Thursday, June 18th 2020 at 13:00 SLT. These meetings are chaired by Vir Linden, and agenda notes, meeting SLurl, etc, are are available on the Content Creation User Group wiki page.

SL Viewer

  • It had been planned that the next viewer to be promoted to de facto release status would be the Love Me Render (LMR) RC viewer. However:
    • LMR is being held over pending the inclusion of various EEP bug fixes, including a fix for the HUD issues (see BUG-225784) and a fix for the specularity problems (see BUG-228781 and BUG-228581).
    • This means the next viewer that will likely be promoted will be the CEF RC viewer, and this could be promoted in week #26 (commencing Monday, June 22nd).

Viewer Caching

  • Work is continuing to try to improve viewer caching.
  • First outcome of this work is liable to be a viewer that has improved VFS caching (the system used to cache information on in-world objects). This will be a complete replacement of the VFS cache with a new format that retains data better and is more performant.
  • The next element of work after the VFS update is liable to be an overhaul of the viewer’s texture caching.

ARCTan

Project Summary

An attempt to re-evaluate object and avatar rendering costs to make them more reflective of the actual impact of rendering either in the viewer. The overall aim is to try to correct some inherent negative incentives for creating optimised content (e.g. with regards to generating LOD models with mesh), and to update the calculations to reflect current resource constraints, rather than basing them on outdated constraints (e.g. graphics systems, network capabilities, etc).

As of January 2020 ARCTan has effectively been split:

  • Viewer-side changes, primarily focused on revising the Avatar Rendering Cost (ARC) calculations and providing additional viewer UI so that people can better visibility and control to seeing complexity.
  • Work on providing in-world object rendering costs (LOD models, etc.) which might affect Land Impact will be handled as a later tranche of project work, after the avatar work.
  • The belief is that “good” avatar ARC values can likely be used as a computational base for these rendering calculations.

Current Status

  • Vir now trying to roll the jelly doll updates into the rendering cost calculations and performance measurements.
  • One thing the core work on ARCTan has been awaiting is a fix to the Bake Service for errors arising when calculating height offsets with complex mesh items, which can result in the avatar bake failing. The fix for this is in place, and the updated Bake Service should be exposed to a simulator RC for testing “fairly soon”. The change itself should have no visible impact other than to correct the rare instances where the issue occurred.

In brief

  • There have been reports of avatar bakes taking longer to complete recently.However, it is not clear if this is an actual issue; LL have not noted any Bake Service processing issues, and also note that users may be noting a perceived “slowing” due to changes made a while ago to try to prevent avatars de-clouding fully nude (e.g. due to latency between the viewer and the CDN, or local caching issues, etc.).
  • In terms of avatar rezzing, there is also work being put into reducing the instances of rigged mesh elements rezzing offset / incorrectly sized related to an avatar (e.g. clothing appearing off to one side and rotated to be on its side; gigantic heads rezzing, etc.).
  • Next meeting: Thursday, July 2nd, 13:00 SLT.