Category: SL User Group Meetings

2018 SL UG updates #41/2: CCUG summary

Posted on by Inara Pey
A simple 5-minute (including uploading the textures) demo of EEP, replacing the Sun and Moon with Mars and Jupiter respectively, then adjusting their respective sizes &; putting them in the same quadrant of the sky

The following notes are taken from the Content Creation User Group (CCUG) meeting, held on Thursday, October 11th, 2018 at 13:00 SLT. These meetings are chaired by Vir Linden, and agenda notes, meeting SLurl, etc, are usually available on the Content Creation User Group wiki page.

Environmental Enhancement Project (EEP)

Project Summary

A set of environmental enhancements, including:

  • The ability for region / parcel owners to define the environment (sky, sun, moon, clouds, water settings) at the parcel level.
  • New environment asset types (Sky, Water, Day that can be stored in inventory and traded through the Marketplace / exchanged with others.
    • Day assets can include four Sky “tracks” defined by height: ground level (which includes altitudes up to 1,000m) and (optionally) 1,000m and above; 2,000m and above and 3,000m and above, plus a Water “track”.
  • Experience-based environment functions
  • An extended day cycle (e.g a 24/7 cycle) and extended environmental parameters.
  • There are no EEP parameters for manipulating the SL wind.
  • EPP will also include some rendering enhancements  and new shaders as well (being developed by Graham Linden), which will allow for effects such as crepuscular rays (“God rays”)
    • These will be an atmospheric effect, not any kind of object or asset or XML handler.
  • The new LSL functions for finding the time of day according to the position of the windlight Sun or Moon have been completed, and are more accurate than the current options.
  • EEP will not include things like rain or snow.
  • It will still be possible to set windlight local to your own viewer.

Resources

Current Status

  • Testing still in progress on Aditi, with test parcels for users still available.
  • Test region: Aditi EEP Testing (secondlife://Aditi/secondlife/EEPTesting/128/128/23).
    • Parcels cost L$1, but as Aditi funds are provided by Linden Lab, you are not paying for anything with your own money.
    • You MUST be using the EEP test viewer why trying to purchase a parcel on the test region – if you are using any other viewer, your purchase will time out.
  • Feedback via Jira (bugs and requests) and / or through comments on the forum feedback thread.
  • An update to the project viewer is expected soon.
  • Graham Linden is continuing to work on the shader support.

Bakes On Mesh

Project Summary

Extending the current avatar baking service to allow wearable textures (skins, tattoos, clothing) to be applied directly to mesh bodies as well as system avatars. This involves viewer and server-side changes, including updating the baking service to support 1024×1024 textures, and may in time lead to a reduction in the complexity of mesh avatar bodies and heads.

This work does not include normal or specular map support, as these are not part of the existing Bake Service, nor are they recognised as system wearables.

Resources

Current Status

The update to the Bake Service to support 1024×1024 textures has run into problems. Anchor Linden is working on fixes for the issues, and once these have been implemented then the viewer should receive and update as well.

Animesh

Project Summary

The goal of this project is to provide a means of animating rigged mesh objects using the avatar skeleton, in whole or in part, to provide things like independently moveable pets / creatures, and animated scenery features via scripted animation. It involves both viewer and server-side changes.

Resources

Current Status

  • The RC viewer updated on October 8th to version 6.0.0.520211. It had been hoped with would be the last RC version, but issues mean this will not be the case.
  • Performance issue:  BUG-225584 and forum thread. This is related to the new dynamic bound box used with Animesh. Vir is working on the issue, and Beq Janus from the Firestorm team has been involved in investigations as to the degree of potential impact. There have been one or two sensationalist blog headlines – best to read the forum thread and the bug report.
    • Part of the thread has spun away into handling attachments on Animesh. While this is not a part of the initial Animesh release, hopefully the discussions can be split off into their own thread.
  • Imposters issue: Animesh objects can imposter independently to avatars. This can result in an avatar rendering normally when seen by others, but any attached Animesh being impostered (or possibly vice-versa).
    • This is being fixed so that an Animesh attachment will now have the same imposter setting as its parent avatar. The update will be in the next RC update.
  • There is a Mac-specific graphics issue that can result in Animesh objects vanishing from the scene when crossing a region. This is also being worked on.

Animesh and the Marketplace

  • There has been some preliminary discussions in the Lab on how to make Animish distinguishable / locatable on the Marketplace (e.g. categories, etc.).
  • No decisions as yet, but the Lab is interested in feedback at CCUG meetings or through the Animesh feedback thread.
  • Problem here is the risk of confusion cross-over. Do trees animated via Animesh require their own sub-category under “Animesh”, should they have  an “Animesh” style sub-category under trees and shrubs (itself already a sub-category of Home and Garden >: Landscaping)?
    • There’s also the question of what to call an over-arching category: “Animesh” is a truncation of “Animated Mesh”, and has been used within the project, etc., but those unfamiliar with the project might be confused by it; so might “Animated Mesh” be preferable? A problem here is “Animated Mesh” itself is a little ambiguous in meaning.
  • Triangle counts have been suggested as an alternative, but this requires some form of automated count system for items uploaded to the MP, which in turn would require significant changes to the MP tools.
    • Even if a tri count could be auto-generated, would people take more notice of it or a given LI?

In Brief

  • A portion of the meeting was taken up with Blender / Maya specific conversations on bone placement for making taller avatars or for use in things like snakes and ropes.
  • There was some discussion on altering the axis rotation in the mesh uploader to match the likes of Maya and Substance Painter. As Vir noted in the meeting, there are an array of potential improvements that could be considered for the uploader – but as yet, a specific project hasn’t been defined to it – and any such project would likely be open for creator input.
  • Support for additional material maps: there has been various discussions (in the forums, etc), but SL supporting additional material maps – roughness, metalness, displacement, etc. Nothing official is on the table from the Lab,  but earlier in 2018, Kitty Barnett did some experimenting with displacement maps with the Catznip viewer – although this should not be taken to mean this is something that will be supported by Catznip or other viewers.
    • Vir hopes that Graham Linden will be able to give some thoughts on expanding material maps support in the future CCUG meeting.
Displacement maps, experimented with by Kitty Barnett earlier in 2018, might – if they could be implemented – add further depth to surfaces. For example: top left – a prim wall with a brick texture; top right: a prim wall with a texture and normal map applied, as we’re used to seeing in Second Life – some depth is added to the cement grouting between the bricks etc. Bottom centre: the same prim wall with the same texture added, but now using a displacement map: note the greater apparent depth between bricks and cement grouting, etc (highlighted).

 

 

2018 SL UG updates 41/1: Simulator User Group

Posted on by Inara Pey

Destiny Gardens; Inara Pey, September 2018, August 2018, on FlickrDestiny Gardens – blog post

Server Deployments

As always, please refer to the server deployment thread for updates.

  • There was no deployment to the SLS (Main) channel on Tuesday, October 9th, 2018. This remains on server release 18#18.09.20.519894.
  • At the time of writing, no deployment to the three RC channels are listed for Wednesday, October 10th, leaving them on server release 18#18.09.24.519940. However, during the meeting, Simon suggested a deployment might be made.

SL Viewer

The Animesh RC viewer updated to version 6.0.0.520211 on Tuesday, October 8th. This update includes the following updates / changes:

  • SL-966 scale and position offset limits are now enforced for Animesh objects. The current scale limit is 64m, offset remains at 3m
  • SL-1290 Issue with animations not rendering if they were stopped and started while host object is selected.
  • SL-9673 some HUDs collapse to low LOD when zooming.
  • SL-1350 Animesh angle offset lags when linked to rotating prim
  • SL-9773 attached Animesh objects visible in mouselook when “show me in mouselook” is unchecked.
  • SL-1291 Animesh selection highlights not showing in edit mode.

Note it does not contain fixes related to the performance loss issue reported in BUG-225584, and noted in my previous TPD meeting summary.

The remaining viewers in the pipeline remain unchanged from the end of week #40:

  • Current Release version 5.1.9.519298, dated September 5, promoted September 26. Formerly the Rakomelo Maintenance RC viewer – No change.
  • Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself):
    • Spotykach Maintenance RC viewer, version 5.1.10.520176, October 4.
    • Estate Access Management (EAM) RC viewer, version 5.2.0.520057, September 28.
    • BugSplat RC viewer, version 5.1.9.519462, September 10. This viewer is functionally identical to the current release viewer, but uses BugSplat for crash reporting, rather than the Lab’s own Breakpad based crash reporting tools.
    • Love Me Render RC viewer, version 5.1.8.518751, released on August 20.
  • Project viewers:
  • Linux Spur viewer, version 5.0.9.329906, 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 3.7.28.300847, May 8, 2015 – provided for users on Windows XP and OS X versions below 10.7.

In Brief

  • Region Crossings: see BUG-214653. In brief, several issues are related to message handling between server(s) and viewer. Assorted solutions have been suggested, with Simon linden noting, “Yeah at some point we may want to totally re-do that sequence of messages and get rid of all UDP traffic. It would probably be a little slower but having a more solid sequence would be better.”
  • BUG-216320 “Error when retrieving grid statistics page via llHTTPRequest”: this has been an issue since May, 2018, it had been hoped that the OS update would fix it, but currently there is still one component that needs to be updated in order to fix the issue.
  • The anticipated end date for the simulator OS update, which is key to the work in moving things to the cloud, is the end of 2018 or early 2019. After which there are the back-end services to update.

2018 SL UG updates #40/2: TPVD meeting – EEP and Animesh

Posted on by Inara Pey
“Red and yellow and pink and green / Purple and orange and blue / I can sing a rainbow” – Graham Linden demonstrates a rainbow effect in Second Life using EEP. Credit: Graham Linden

The majority of the following notes are taken from the TPV Developer meeting held on Friday, October 5th, 2018. A video of the meeting is embedded below, my thanks as always to North for recording and providing it.

This is again a short meeting, with lengthy pauses in chat, so the following is a summary of key points. Note that due to a log-in issue occurring before the meeting, the discussion proper doesn’t start until the 3m 40s point in the video, having been delayed to give people still having issues the opportunity to log-in and get to the meeting.

Simulator Deployment Update

The planned deployment of server maintenance package 18#18.0924.19940, scheduled of Wednesday, October 3rd was cancelled after a last minutes issues was found in testing.

SL Viewer

[3:40-6:56]

The new Spotykach Maintenance RC viewer updated to version 5.1.10.520176 on October 4th.

The remaining viewers in the pipeline remain unchanged from the start of the week:

  • Current Release version 5.1.9.519298, dated September 5, promoted September 26. Formerly the Rakomelo Maintenance RC viewer.
  • Release channel cohorts:
    • Estate Access Management (EAM) RC viewer, version 5.2.0.520057, September 28.
    • BugSplat RC viewer, version 5.1.9.519462, September 10. This viewer uses BugSplat for crash reporting, rather than the Lab’s own Breakpad based tools.
    • Animesh RC viewer, version 6.0.0.518949, August 24.
    • Love Me Render RC viewer, version 5.1.8.518751, released on August 20.
  • Project viewers:
  • Linux Spur viewer, version 5.0.9.329906, 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 3.7.28.300847, May 8, 2015 – provided for users on Windows XP and OS X versions below 10.7.

Of the current RC viewers:

  • Animesh appears to be the leading contender, but this is unlikely to happen “immediately” due to apparent performance issues (see below).
  • Bugsplat is currently awaiting a change to the updater to be merged with it, so will likely remain at RC status, and the update may appear in week #41 (commencing Monday, October 8th, 2018).
  • [32:06-32:53] The Estate Access Management viewer is largely regarded as feature complete, although estate holders / managers are being encouraged to test the viewer and offer feedback to the Lab.
  • Bakes On Mesh has received the required simulator update (maintenance package 18#18.09.20.519894). This should just leave the Bake Service update before the capability will be available on Agni (the main grid).
  • EEP is now officially available for testing on Aditi – see EEP testing and project viewer officially announced for more, and the additional EEP news below.

EEP

[10:00-25:50] EEP permissions may cause some confusion. Please see the EEP documentation on permissions for additional information.

  • EEP assets can be set to be Mod(ify) or No Mod(ify); Transfer or No Transfer, but they are always Copy.
  • No Copy is not supported because  – like avatar shapes –  it is possible to manually copy settings values, even if the asset itself is No Copy.
  • No Mod(ify):
    • Is respected for a fixed sky / water asset if it is transferred / sold.
    • Is not respected if the asset is subsequently used as a day cycle frame (presumably to allow blending with other frames in the cycle).
    • No Mod EEP assets cannot be edited and saved; however, Save As can be used with them to create a new asset based on them.
  • No Transfer:
    • Adding a No Transfer asset as a frame in a day cycle will convert the entire day cycle to No Transfer.
    • This prevents No Transfer assets a creator does not want re-sold from being used in day cycles created by others.

The permissions appear confusing in order to allow people to be able to create and sell sky and water assets; however, there have already be calls for EEP assets ignore permissions altogether. This would mean they would be freely exchangeable – much as windlight XML settings are currently.

This feedback has been heard by the Lab and will be taken back to the project, but in the meantime the request is that TPVs do not alter the assigned permissions with EEP assets, due to the additional confusion this would likely cause.

Adjustable Vertical Zoning

[34:06-35:00] Note that the project viewer version of the EEP viewer allows the vertical position of sky settings to be adjusted, rather than being fixed at 1,000 metre intervals. However, Rider Linden has indicated some refinement is required on setting the slider values.

The vertical layers for EEP sky settings are now adjustable. Select the default level to be adjusted, then use the slider.

Animesh: Performance Issue

[30:00-31:45] There is an apparent performance issue with Animesh, which may be connected to the needsUpdate patch added to the viewer as a part of the changes for dynamic bounding boxes – see BUG-225584.

It was always expected that Animesh might introduce some performance hits – although up until the changes to the bounding box nothing major had been encountered – and the degree of impact this issue seems to produce was not anticipated.

Diagnosing the problem has been difficult from the Lab’s perspective, as issues have so far only been reported on the Black Dragon viewer and Firestorm’s Animesh test viewers – with the former suffered a far greater impact than the latter.

Vir Linden has started a forum thread on the issue (as Jira comments are limited to supported users at present). He has also asked for specific testing using the official Animesh viewer as well. Those wishing to test and offer feedback are asked to do so via the forum thread (although for those with permission to comment on Jiras, feedback on the bug report will also obviously be accepted).

There is an upcoming update for the viewer, but it does not include any fix for this issue. As of the TPV meeting, it hadn’t been decided if the issue was sufficient enough to be classified as a blocker to the promotion of the Animesh viewer to de facto release status.

Other Items

  • [8:50-9:06] BUG-225557: “Attaching an object from the ground causes inventory loss under certain circumstances” can be nasty. The Lab are aware of the issue and will be investigating it.

2018 SL UG updates 40/1: Simulator and Governance

Posted on by Inara Pey

[Eclectica] A New Dawn; Inara Pey, August 2018, on Flickr[Eclectica] A New Dawn – blog post

Simulator User Group

Not a lot to report this week; some discussion on documenting throttles on various LSL requests (i.e. updating wiki entries to indicate those functions that have throttles, rather than providing specific throttle information), and the inevitable region crossing chatter.

Server Deployment Plans

  • On Tuesday, October 2nd, the SLS (Main) channel was updated with server maintenance package 18#18.09.20.519894, comprising the simulator update for Bakes on Mesh.
    • I believe this update still requires a Bake Service update (support for 1024×1024 textures).
  • On Wednesday, October 3rd, the three main RC channels should all be updates with service maintenance package 18#18.09.24.519940, comprising internal fixes.

SL Viewer

The following two viewers were updated on Friday, September 28th:

At the start of week #40, all other viewers remain as follows:

  • Current Release version 5.1.9.519298, dated September 5, promoted September 26. Formerly the Rakomelo Maintenance RC viewer – NEW.
  • Release channel cohorts:
    • BugSplat RC viewer, version 5.1.9.519462, September 10. This viewer is functionally identical to the current release viewer, but uses BugSplat for crash reporting, rather than the Lab’s own Breakpad based crash reporting tools.
    • Animesh RC viewer, version 6.0.0.518949, August 24.
    • Love Me Render RC viewer, version 5.1.8.518751, released on August 20.
  • Project viewers:
  • Linux Spur viewer, version 5.0.9.329906, 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 3.7.28.300847, May 8, 2015 – provided for users on Windows XP and OS X versions below 10.7. This viewer will remain available for as long as reasonable, but will not be updated with new features or bug fixes.
Rider and Simon Linden, seated, at a Simulator User Group meeting, with Mazidox Linden in between. Note Mazi is wearing Shrek ears – the Lab’s office and in-world indicator that someone committed an “oopsie” – in his case, testing the wrong thing.

Governance User Group

Governance User Group (GUG) meetings are generally held on alternate Tuesdays at 13:00 SLT. They are intended to provide a forum for the discussion and education of issues involving Governance.  They are chaired by the GTeam supervisor, Kristen Linden and are open to the public. Details on dates, times and location can be found on the Governance User Group wiki page.

The Governance Team is responsible for dealing with Abuse Reports, in-world abuse, forum reports, Marketplace reports, etc. It is not responsible for issues with accounts being compromised, account subscription delinquency, fraud, IP infringement, etc.

  • These matters cannot be discussed at the GUG meetings.
  • Issues relating to them should be reported through the recommended channels (e.g. Support for account-specific issues, via the DMCA process for IP infringements, content theft, etc).

Similarly, individual cases involving Governance issues (e.g. the outcomes of abuse report filings), cannot be publicly discussed.

Resources

Meeting CliffsNotesTM

  • General comment on L$ reclaims: somewhat related to fraud, despite notes above. If someone receives L$ amounts as a result of fraud or similar issues, when those amounts are reclaimed via the Lab, they will show up as a transaction record in the user’s account transaction history.
  • Visitor trackers – are these a violation? the Governance Team is aware they exists, and generally do not action reports relating to them (radar systems report more-or-less the same information, available from the mini-map).
    • Similarly, the Governance Team tends not to get involved with tar jars that record tippers names / amounts. The suggestion for those who do not wish to have their name recorded when tipping is to tip directly, avatar-to-avatar.
  • Warnings / Suspensions / Termination: Tommy Linden pointed out that the reason someone is receiving a warning or a notice of suspension / termination will receive “a specific reason” on why the action is being taken in the e-mail notifying them of the warning / suspension.
  • Bans and Termination: the Governance Team only ban / terminate as a result of in-world issues related to platform governance. However, users can be banned / terminated by other LL teams (e.g. fraud, legal / IP), depending on the nature of the infraction / activity.
  • Can SL users be banned for things placed on external blogs, etc? As far as the Governance Team is concerned – no.  It is recognised that the team have no jurisdiction over mediums and services outside of those owned by Linden Lab.
    • Users who believe their personal data is being incorrectly publicised via the likes of blogs, etc., on other services, or believe they are being defamed, are advised to go through the complaints process native to the platform in question, and not file an Abuse Report with the Lab.
    • Issues the Lab have with external services, websites, etc., that are felt to be violating things like the company’s brand usage, trademarks, or which might be seen as defamatory, are dealt with by the legal department.
  • Personal questions: asking personal questions – even repeatedly – is not actionable as an AR. No-one has to answer questions, and other avatars can be muted / block if they persist. However, if someone does repeatedly harass a user with personal questions, etc., even beyond blocking, the an AR for harassment can be raised.
  • 24/7 coverage: the Governance Team is “not totally” active on a 24/7, but are deliberately unpredictable in hours kept so that times when Governance may not be available can be easily calculated by potential troublemakers.
  • Does the GTeam track those banned from regions / parcels? No. The region / parcel capability is there for region / parcel holders to use. However, ARs can be a means to identify serial griefers.
  • Does the simulator save a copy of the simstate when an AR is filed? No, however, the logs, etc are available for review during an investigation  – providing the AR is filed within a reasonable time of the incident occurring.
  • Should specific sections of the TOS / Community Standards be quoted in an AR: they can be, but it is not a requirement. A clear description of the incident, with all relevant information and an accurate AR category filing is far better.
  • ARs against copybotting, IP infringement: these are not investigated, but attempts are made to educate on how to file a DMCA.
  • Nudity on Moderate regions: generally considered OK, but nudity with sexual connotations (e.g. sexual acts or a naked male avatar with an erection, in public places) can be AR’d.
    • Region / parcel holders are free to specify no nudity and / or no sexual acts on their regions, regardless as to the rating.

Next Meeting

Subject to confirmation on the Governance User Group wiki page, the next meeting should be on Tuesday, October 16th, 2018. However, the location may change.

2018 SL UG updates #39/3: CCUG summary

Posted on by Inara Pey
“All these worlds are yours….” An alien sky by Cube Republic, using the EEP test viewer

The majority of the following notes are taken from the Content Creation User Group (CCUG) meeting, held on Thursday, September 27th, 2018 at 13:00 SLT. These meetings are chaired by Vir Linden, and agenda notes, meeting SLurl, etc, are usually available on the Content Creation User Group wiki page.

SL Viewer Update

The Rakomelo Maintenance RC, version 5.1.9.519298, dated September 5th, was promoted to de facto release status on Wednesday, September 26th. This means all other viewers currently in the pipelines will be merged with this code and updated in the coming days.

Environment Enhancement Project (EEP)

Project Summary

A set of environmental enhancements, including:

  • The ability for region / parcel owners to define the environment (sky, sun, moon, clouds, water settings) at the parcel level.
  • New environment asset types (Sky, Water, Day that can be stored in inventory and traded through the Marketplace / exchanged with others.
    • Day assets can include four Sky “tracks” defined by height: ground level (which includes altitudes up to 1,000m) and (optionally) 1,000m and above; 2,000m and above and 3,000m and above, plus a Water “track”.
  • Experience-based environment functions
  • An extended day cycle (e.g a 24/7 cycle) and extended environmental parameters.
  • There are no EEP parameters for manipulating the SL wind.
  • EPP will also include some rendering enhancements  and new shaders as well (being developed by Graham Linden), which will allow for effects such as crepuscular rays (“God rays”)
    • These will be an atmospheric effect, not any kind of object or asset or XML handler.
  • The new LSL functions for finding the time of day according to the position of the windlight Sun or Moon have been completed, and are more accurate than the current options.
  • EEP will not include things like rain or snow.
  • It will still be possible to set windlight local to your own viewer.

Resources

Current Status

There will be a formal LL blog post on EEP testing at the start of week #40, which will include links to the current versions of the test viewer and also the SLurl for Aditi testing. I’ll be updating this summary with the details once officially made public. These will include the latest iteration of the viewer

Those who have been fortunate enough to attend the CCUG meetings have been able to get some advanced testing done, and there have been a number of additional bug reports and feature requests raised – use the EEP Jira filter to review all raised issues / ideas.

The latest version of the test viewer (made available at the meeting) will result in visible changes to cloud speeds. This will cause clouds in settings created using the initial version of the test viewer to travel much faster and to the north-east.

Another simple EEP demo showing how different textures used on the Sun or Moon within individual sky settings can be blended together when creating a day cycle & some of the motion effects – in this case the Sun (as Mars and Jupiter zig-zagging gently up and down). Oblateness is due to manual recording ratio, and is not representative of the texture shapes when seen in-world.

Cliff Notes on EEP

  • Graham Linden’s shader work has yet to be added to the viewer (so no crepuscular (God) rays, etc., as yet).
  • Firestorm uses a broader range of setting for atmospheric / water effects (haze, density, etc.) than the official viewer. This has led to windlights imported into EEP settings not displaying correctly (see BUG-225537) Rider had increased the settings range in EEP to match Firestorm.
  • Rider and Graham are discussing how procedural texturing might work in EEP(!)
  • EEP does not support the ability for anyone to create a new EEP settings object simply by saving the one they are viewing ( as can currently be done with legacy windlight settings). However, existing windlight settings stored locally in the viewer can be imported to EEP and converted.
  • EEP will break RLV controls on windlight.
  • The EEP test viewer can be used as an ordinary viewer on Agni (the main grid), but EEP settings cannot as yet be applied, and it may lead to a duplication of the EEP Settings folder when switching back to the test region on Aditi.

Cloud Perturbation

Rider hopes to be able to add a means to provide a degree of perturbation when non-seamless cloud textures are used, so that they don’t appear so tiled when viewed in-world.

Continue reading “2018 SL UG updates #39/3: CCUG summary” →

September 2018 Web User Group Summary

Posted on by Inara Pey

Peace of Mind; Inara Pey, August 2018, on FlickrPeace of Mind  – blog post

The following notes are taken from the Web User Group meeting held on Wednesday, September 26th, 2018.

These meetings are generally held monthly on a Wednesday at 14:00 SLT, and are chaired by Alexa and Grumpity Linden at Alexa’s barn. The focus is the Lab’s web properties, which include the Second Life website (including the blogs, Destination Guide, Maps, Search, the Knowledge base, etc.), Place Pages, Landing Pages (and join flow for sign-ups), the Marketplace, and so on and the Lab’s own website at lindenlab.com.

Marketplace

New Deployment – New Features

A deployment to the SL Marketplace was made on Wednesday, September 26th. However, due to some issues surfacing, it had to be rolled back, causing the grid status report of Marketplace Maintenance.

This is actually the update that includes more of the promises Marketplace updates, including:

  • Wish lists.
  • Follow favourite merchants.
  • A new drop-down of people a user must frequently sends Marketplace gifts to.

It will now be re-scheduled for deployment once the issues have been fixed.

Clean-up

The Lab will shortly be starting a clean-up of the Marketplace. This will most likely be done by running different queries with different criteria, and seeing what the results would be in terms of removed listings / stores.

For example, one query might be run against all users who have not logged-in to Second Life or the Marketplace in (say) 10 years or 6 years, and see how many items might be unlisted as a result. If the outcome is thought to be a manageable amount (i.e. not half the Marketplace potentially vanishing), then the query might be run, and the items unlisted. Then the process will be repeated over a shorter time period (e.g. say not logged in for 8 years of 4 years, depending on the original query). Other criteria, such as number of sales of an item over a number of years, or how frequently an item is flagged etc., might also be added to the mix over time.

This does mean that items that still work in SL, but the creator is no longer active in SL or the Marketplace, will likely vanish. However, as items are only being unlisted, and affected merchants will be contacted and advised where possible. So, they will always have the option to log-in to the Marketplace and re-list their items if they so wish.

Web Updates Release Notes

It is hoped that a location will be established for web property release notes, just as there are pages for release notes on SL wiki.

Automatic Landmark Updating

This is an age-old problem: how to automatically update store (or other) landmarks following a move. In 2012, Toysoldier Thor came up with the concept of the Virtual Landmark (VLM) – see here for the essentials – and which eventually lead to Darrius Gothly developing VLM for Virtual Worlds – see here for the essentials. VLMFVW are not ideal (I have not tested them in five years to confirm whether they still work), but at the time they did assist with the problem.

Unfortunately, having landmarks that can be remotely updated is seen by the Lab as requiring an entire new landmark system and (presumably) and entirely new asset type which would exist entirely independently of existing LMs (and so could cause confusion among users), so this is not something that is likely to happen in the short-to-medium term, if at all.

Date of Next Meeting

Wednesday, October 24th, 2018.