Update: the 43-bit viewer KDU issues has been updated based on feedback from Ansariel Hiller.
The following notes are taken from the TPV Developer meeting held on Friday, March 16th 2018. A video of the TPVD meeting is embedded below, my thanks as always to North for recording and providing it. Time stamps in the text below will open the video in a new tab at the relevant point of discussion.
This meeting was somewhat extended – lasting 1 hour 30 minutes – as a result of the presence of Ebbe Altberg, Linden Lab’s CEO, who commented on some of the item of discussion that came up at his session at VWBPE 2018 (see my notes and transcript here), as well as more broadly discussing Second Life and Sansar.
[0:17-2:20] There have been no further updates to the current release, RC and project viewers in week #11, leaving the pipeline as follows:
- Current Release version 18.104.22.1682803, dated February 23, promoted March 1 – formerly the Nalewka Maintenance RC – No change
- Release channel cohorts :
- Project viewers:
- Linux Spur viewer, version 22.214.171.1249906, dated November 17, 2017 and promoted to release status 29 November – offered pending a Linux version of the Alex Ivy viewer code.
- Obsolete platform viewer, version 126.96.36.1990847, May 8, 2015 – provided for users on Windows XP and OS X versions below 10.7.
- The Media Update RC viewer is unlikely to be promoted to release status in the immediate future, as it has some Windows 7 update issues which need to be resolved.
- The Love Me Render viewer is making good progress, although it also has the Windows 7 problem.
- [7:30-8:30] This viewer also has a KDU issue which can cause the 32-bit version of the viewer to crash when uploading textures larger than 512×512. One workaround for this until fix is obtained – depending on how long that takes – is for an older version of KDU to be used for 32-bit viewer versions.
- Despite the issues with it (see my update here), the 360-snapshot project viewer is not getting a lot of attention.
- Animesh project viewer is getting close to a possible RC release and the Animesh project close to a move to the main grid.
- The Bakes on Mesh viewer has cleared LL’s QA, so a Bakes on Mesh project viewer for use on Aditi should be appearing soon.
New Viewer Caps
[3:51-7:04] The lab is introducing two new viewer caps they’d like TPVs to adopt quickly:
- One will be used when the viewer first logs-in to read all of the deferred IMs received while the user was off-line, which are being moved from UDP delivery to HTTP in an attempt to overcome issues of off-line IMs failing to show.
- The second is to read the correct set of abuse report categories from the server, so only valid categories are displayed within the viewer, allowing users to more correctly file ARs, rather than using invalid categories held viewer-side.
General Discussion with Ebbe
Highlights only – refer to the video for the full discussion.
- The Lab is looking to try to pivot the SL economic model away from a heavy reliance on land fees, and then in time hopefully reduce the cost of land.
- This will see a shift from land to revenue generation through fees in other areas.
- The Lab cannot simply drop land fees and raise fees elsewhere, the two have to be balanced, so while the Lab is hoping to “aggressively” tackle pivoting revenue generation, they will also be cautious in making changes.
- The hope of reducing land fees can be seen in the reduction in Mainland fees.
- [10:50 via Oz and Linden] The Mainland price reduction has already seen a significant uptick in interest for abandoned Mainland, with support being “overwhelmed” with requests.
- There is currently nothing planned for Private region fees, simply because the Lab has to be cautious around revenue.
- It might be a case of (a) fee increase(s) elsewhere first, followed after a time by consideration of what can be done with Private region fees.
- It is however, something the Lab would like to do.
- The steps must be measured not only to safeguard LL’s revenue stream, but also so as not to upset the SL economy.
- For this reason, the Lab will take a little time to measure the Mainland restructuring before they make other changes, so that they can more accurately measure cause and effect between different types of change.
- These ideas were also discussed that the VWBPE session with Ebbe – see my transcript notes (with audio from that session) for more.
[15:39-18:36] A general overview of Sansar – which is still is Creator Beta – including the drive this year to gain an audience for Sansar, plus improvements to the VR aspect of the platform. Most of this is covered in my weekly Sansar updates. For Ebbe in particular, the Sansar team is at a point where he feels comfortable pivoting attention away from that platform and back to Second Life, including spending more time in-world.
Sansar and SL
- A re-iteration that Sansar was never intended to be a replacement for Second Life.
- Both products now have completely separate teams working on them
- At VWBPE 2018, Ebbe indicated that the core SL team – engineering, development, operations, support – is “close to” 100 in number.
- There is an area of overlap between the two products, but there are also very clear differentiators.
- Proof that Sansar isn’t a replacement for Sl is the level and speed with which LL has continued to invest in SL (overhauling the viewer and simulator build mechanisms, bringing more performance and stability to the platform) and to add new capabilities (Bento, Animesh, Bakes on Mesh, EEP, rendering enhancements, etc.).
Moving SL to the Cloud
- Progress is being made.
- Experimental regions have been run in the cloud, and they worked.
- There are a lot of functional limitations that must be addressed before regions users can access can be run in the cloud.
- The regions did achieve a reasonably high concurrency level (precise number not given).
- Much of what SL does natively – dynamically spinning-up a new set of inventory management servers or a new set of log-in services, etc. – is similar in nature to a lot of what cloud service providers do, so a lot of the back-end work involved in moving to the cloud is taking what the Lab have, and adapting it to run within the infrastructure of the cloud.
- It is a massive engineering undertaking that will take time.
- Once completed, it is hoped operating SL in the cloud will allow LL to offer benefits to users, which might potentially include:
- Reduced costs for regions that are spun-down and stored to disk when no-one is using them, should this be explored for Second Life
- Ability for simulators and services to be more geographically based (e.g. simulators used largely by an audience in South America could be hosted in facilities in South America)
- Ability to potentially have a broader cross-section of land product based on server types, with a broader range of performance / pricing.
- It is hoped that, for the most part, users won’t be aware of services being switched from the Lab’s dedicated infrastructure to running within a cloud infrastructure
- Some non-user facing services are already running in the cloud.
- The work will be done progressively, and not a “flipping of the switch” for “everything”.
- There is not end-date for the work. The Lab is approaching it as aggressively as possible, but there are a lot of technical hurdles to be cleared along the way, some of which will only become apparent as attempt are made to shift things and put them into production via the cloud.
- To deal with potential issues / hurdles, it is possible that further ahead, there is a simulator RC channel “in the cloud”, while others are still running on the Lab’s own infrastructure.
- Also see Ebbe’s comments from VWBPE 2018.
Upcoming New User Experience
[1:01:23-1:07:11] The Product Team is doing a lot of work with the new user flow, and are getting close to where they can start experimenting with ideas.
Part of this work involves a themed learning island reached via a new user clicking a themed ad which takes them to a themed landing page on the SL website, where they can sign-up, obtain an avatar in keeping with the theme, and are delivered to a learning island that also follows the theme.
This approach will be tested alongside the current on-boarding routes.
- The lab spent over a year building a “fairly sophisticated” tracking system to gather data on new users and see how they are doing, i order to try to learn more about on-boarding / retention.
- The Lab’s data / testing suggests new user retention is no better in welcome areas with greeters, than for those without greeters.
- A test the Lab carried out using a (non-public) browser-based means of accessing Second Life from sign-up (no need to download the viewer) also did not achieve better retention than the “traditional” sign-up and download route.
- [32:10-34:07] Mirrors in SL: the inevitable discussion – and no, mirrors aren’t in Sansar!
- [34:08-37:08] SL and VR: re-cap of why the VR viewer was dropped from Second Life – unable to maintain the comfort-level VR frame rates (90 fps). Also segues into a discussion of the Sansar / SL Edit mode differences (also see Ebbe’s comments from VWBPE 2018).
- [37:10-37:40] Sansar benefits to SL: Oz confirms that some of the rendering work with the atmospheric shaders to improve SL’s appearance is leveraging lessons learned with Sansar.
- [38:35-43:50] Texture caching: the project to improve the viewer’s texture caching is still very active, and once completed, the Lab plain to look at other aspects of how the viewer caches data.
- [44:17-47:09] Linux Viewer: no real change from my last update.
- TPV have the same problem as LL re: Linux developers.
- LL would like to see more from the Linux community get involved.
- Suggestion is for Linux users to try running the Windows viewer under Wine.
- [47:10-49:25] OpenGL and GPU/CPU divide: discussion on updating SL’s OpenGL version, which is already under consideration at the Lab. Broadens into a discussion of modifying SL’s rendering capabilities to make more use of more GPU shader capabilities for calculation (rather than being reliant on the CPU), and the risks (to users) this entails (as many SL users don’t use more modern hardware with GPUs capable of taking the load).
- [51:58-59:58] Community Gateways: Discussion on the Community Gateway programme and attracting users. Includes mention of partners, Place Pages, etc. Ideas raised seen as something that could be put to the SL Marketing team under Brett Linden.
- [1:12:52-1:14:14] Feature Requests: when filing a Feature Request JIRA, it is better to keep the request focused on a single idea which can be easily digested. Multiple ideas should be submitted via separate JIRAs so that meaning don’t become confused / the JIRA becomes to complicated to understand, etc. Multiple JIRAs around related ideas can also be related via identifier.