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.
- A Custom Key Mappings project viewer, version 184.108.40.2064079, was issued on Tuesday, June 30th.
The rest of the official viewers in the pipeline remain as follows:
- Current Release viewer version 220.127.116.113157, dated June 11, promoted June 23, formerly the CEF RC viewer.
- Release channel cohorts:
- Love Me Render RC viewer, version 18.104.22.1684028, June 30.
- Tools Update RC viewer, version 22.214.171.1244097, 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, 126.96.36.1994024, issued on June 24 – this viewer uses Viewer Manager 2.0.538279.
- Project viewers:
- Custom Key Mappings project viewer, version 188.8.131.524079, June 30.
- Mesh uploader project viewer, version 184.108.40.2063141, June 11.
- Copy / Paste viewer, version 220.127.116.113365, December 9, 2019.
- Project Muscadine (Animesh follow-on) project viewer, version 18.104.22.1682999, November 22, 2019.
- Legacy Profiles viewer, version 22.214.171.1240836, September 17, 2019. Covers the re-integration of Viewer Profiles.
- 360 Snapshot project viewer, version 126.96.36.1999111, July 16, 2019.
General Viewer Notes
- The Love Me Render (LMR) RC viewer is still absorbing fixes for EEP and rendering issues. Version 188.8.131.524028, 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.
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.
- 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.
- 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.
- 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.