Tag: 2018 Product Meetings

Sansar 2018 Product Meetings #50

Posted on by Inara Pey

The following notes were taken from the Sansar Product Meeting held on Thursday, December 13th, the last such Product Meeting for 2018. As usual, Eliot, the Sansar Community Manager hosted the meeting, with Ebbe, Landon, Aleks, Leslie, Kelly and Julia from the Lab.

High-Level Outlook for 2019

Plans are still being finalised for 2019 and Sansar, so there is some reluctance to talk in-depth about what is likely to be coming and when, however, some high-level bullet points for the platform mentioned in the meeting were:

  • Avatar improvements (e.g. face sliders, custom skins).
  • World (experience) creation easier.
  • Making it easier for people to collaborate and group themselves around “things”.
  • Improving the ability to make interactive content and games.
  • See Sansar be more event-driven.
  • Continue to ship updates at a high rate (the average for 2018 being one update per month).
  • Accelerate the rate of change that is being made with updates, as per that last three releases of 2018.
  • Continue to be responsive to feedback to updates and changes.

A major review of plans is taking place over the final working week of 2018, so early 2019 should see the Lab in a better position to offer some insight into what the year may be bringing to Sansar.

Attending Events

Sansar recently hosted its first ticketed event (sadly at a time far too late for most of us in Europe – hint, hint, Linden Lab) – Comedy Gladiators, hosted by Steven Hofstetter (read more here).  The event apparently went well, with the audience spawning multiple instances and able to see the activities on stage. However, one problem did arise in that people wishing to attend the same instance of the event at times found they couldn’t. The Lab is aware of this and looking to make changes that will allow people access the same instance of a popular event like this, and enjoy it together.

One idea is a “party up” system, that allows a party of named individuals access an instance together. This could be extended to things like team-based games / puzzles / activities, where you need to work as a group and / or work best with limited numbers – so each party of players accessing the game / experience would be delivered to a different instance, thus avoiding interfering with others who already have a game in progress.

In Brief

  • Sansar / Steam Desktop mode issue: there is an issue running Sansar via Steam in Desktop Mode that leaves the audio sliders in Settings non-responsive. This is being investigated by the Lab.
  • Improved camera(s) for 2019? a frequent request through 2018 has been better camera options for filming in Sansar. Idea put forwards include a true “flycam” mode that allows for free filming and avatar movement of the part of the person filming; the ability to create multiple (scripted) camera objects within a scene for filming (and the ability to cut between them when recording); having “flyable” scripted cameras, etc. Such ideas are being discussed by the Lab with no commitment (at present) on what might be delivered or when.
  • Freecamming when using a Sit Point: it is not currently possible to freecam (F4) when seated using the Sit point capability introduced with R28. This will be fixed.
  • “Bigger” Experiences: currently, the upper limit on experiences is 4km on a side (the equivalent area to 256 SL regions). There are currently no plans to expand beyond this, as it is the limit at which the physics aspects of the engine start to break down, and the Lab does not want to get into a Second Life scenario with having to work out how to stitch scenes / experiences together and cater for physically crossing being them.
    • Even working to the 4km upper limit is questionable at present, as Sansar does not have any means of LOD (level of detail) handling within it.
  • Finding Sticky Grab: the new “sticky grab” option introduced with R28 to prevent people picking up guns and then throwing them, rather than firing them (left mouse click), is currently a little obscure when setting it in Edit mode, so it is liable to be better surfaced in an upcoming release.
  • Improved Moderation: an upcoming point release (possibly to appear before Christmas) should allow user-to-user blocking (so not only can a troublemaker be muted, they can be blocked and vanish from your view  – and you vanish from their view).
  • In-client Store Improvements: it is hoped that 2019 will see the in-client Sansar Store achieve parity with the web version of the store (filters and filter options, etc).
  • Steam “Fall-off”: A lot has been made about the fall-off in incoming numbers of users from Steam. This was in some way expected, as at the launch on Steam, Sansar was featured on the Early Access home page (actually how I saw it had been launched), and also on the Steam VR section home page. Since the launch, Sansar is no longer front-and-centre on either page.
  • Avatar Rig: this will likely see changes in 2019. Work is already in hand to try to simplify it; other improvements will be made over time.

 

Sansar 2018 Product Meetings #48: Steam and release 28

Posted on by Inara Pey
LOOT Interactive NASA Apollo Museum

The following notes were taken from the Sansar Community Feedback hour held on Thursday, November 29th. A video of the meeting is available on the official Sansar Twitch channel, and timestamps referencing that video are provided in the text below.

Note that the entire discussion is not summarised here – general questions from the 47 minute point onwards are not included – please refer to the video for these. The focus of this article is the upcoming availability of Sansar on Steam and the the December R28 release.

Sansar On Steam

[3:00-5:44] If all goes according to plan, Sansar will be available on Steam from the end of week #49 (week commencing Monday, December 3rd). The platform has already gained initial approval from Steam, and should gain final approval during the early part of the week.

As I’ve previously noted, Sansar will be on Steam as an Early Access programme. As well as the client being available, there will be a dedicated forum and group on Steam.

Reminder: SandeX Closing

A reminder that as a part of making Sansar available on Steam, the SandeX will be closing on Tuesday, December 4th, 2018, and S$ to USD conversions will move to a fixed conversion rate model.

Please refer to Sansar extends to Steam; Lab to end SandeX for more on this.

“Sokoban” Puzzle Challenge

[5:48-8:40] To mark December, the Sansar team is going to be running a series of challenges through the month. These are intended to be fun items, rather than anything to be taken too seriously, and the first up is the Ugly Christmas Sweater Challenge. As the make implies, this is for clothing creators to make an ugly Christmas sweater and upload it to the Sansar Store. For those who can’t make clothing, some sweater templates may be placed on the Sansar Store that can be obtained, textured and used as entries.

Some of the Ugly Christmas Sweater challenge entries

[9:31-12:00] The second challenge is the Sokoban Puzzle Challenge.

Sokoban (“warehouse keeper”) is a puzzle video game in which the player pushes boxes or crates around in a warehouse, trying to get them to storage locations. An experience based on the game has already been created in Sansar, and users are being asked to create and submit their own levels t add to the experience – read Make A Sokoban Challenge for full details, including how to design and submit levels.

Upcoming Features for the R28 (December) Release

The following updates should be part of the R28 Sansar release, which is currently scheduled for some time between the 10th and 13th December 2018 – so it will be available after the Steam launch.

Teleport to a Friend

[15:59-17:35] This is being updated so that it will not work when trying to teleport to a friend in an unpublished experience, and will not show the experience name if you are in an unpublished experience and someone tries to teleport to you.  These fixes are temporary in nature, as they will not scale, so the Lab will be looking to make further changes to Teleport to a Friend in the future to prevent stalking.

Remember, this feature will teleport your avatar to the spawn point of the same experience as a friend, not directly to that friend.

Chat Updates

[17:39-19:00]

  • Nearby Chat and direct messaging (IMs) will have timestamps with the next release.
  • It will be possible to start a direct message (IM) with a friend from the Chat App without having to open the People App.
  • Japanese, Chinese, Korean, Russian and more will also be supported when typing.

[19:03-19:35] Some in VR have noticed the Chat App panel is “too far away” for them to comfortably reach and grab, forcing them to lean forward when trying to manipulate it.

Home Spaces

[22:24-23:35] The room in which avatars are placed when entering Look Book is to become a Home Space, and will include some light customisation options. The Home Space option will be developed over time to present users with a friendlier environment than the Atlas.

The Look Book “room” is set to become more of a Home Space environment with the next Sansar release, with some initial light customisation options

New User Experience

[24:09-25:28]  The next release will include some client UI “tutorialisation” for new users. This will include various call-outs identifying various parts of the client UI, but these will also be visible to established users the first time the client is run after the release has been deployed.

For the rest of on-boarding, new users will be dropped into the Home Space in the default grey avatar, and will have a list of recommended experiences (based on population within the experiences) they can be sent to.

Continue reading “Sansar 2018 Product Meetings #48: Steam and release 28” →

2018 Sansar Product Meetings #45: Look At Me release

Posted on by Inara Pey
Nirvania

Look At Me Release Feedback

  • Typing indicator:
    • Requests have been made to remove the box around the dots and just have the flashing dots when someone is typing.
    • It was also requested that the indicator not pop-up when typing “/” commands for emotes – but as was pointed out, the system has no way of knowing what is being typed until after it has been sent, making it difficult for the indicator to ignore “/” when input.
    • Other UI interactions can also incorrectly cause the typing indicator to appear over an avatar, which the Lab are looking to refine.
  • VR virtual keyboard:
    • Enhancements are already being planned – such as a “emote wheel” to make selection of emotes easier and not reliant on the commands being typed.
    • The Lab would like further feedback on the keyboard and how it might be improved, or options that might be added, if some of the keys should be re-organised, etc.
    • There have been instances where people opening the VR virtual keyboard in (first person view) have found their avatars unexpected walking forward without any of the keyboard buttons being touched.
  • Voice Reset issue: along with the new options to test microphone levels, there is an option to reset the voice stream. However, reports are that when used, the voice stream fails to reconnect.
  • Settings: it’s been noted that in VR, Settings > Control, no longer displays the VR controller options; users only get the desktop keyboard options.
  • UI Buttons:
    • Requests have been made to make them switchable between the left and right sides of the client window, depending on individual user preference.
    • There have also been concerns raised that on very high-resolution (e.g. 4K) screens, the buttons are very small and hard to see.
  • First person avatar view in VR: a preference for seeing the avatar hands an arms when using things like the revised client button set on the left wrist  has been voiced. Eliot noted that the default blue hands are used to cater for avatars that do not have hands and arms (e.g. they have tentacles), so they have a frame of reference when tying to use menus, etc.
  • Hi-Res Texture Streaming: a request was put forward to allow users to select whether or not they want to use the hi-res texture streaming when loading an experience. The point here being that some games – those against the clock, for example – might be dependent upon the scene being fully loaded and ready to go when the user is placed within it.
    • The lab noted there are some tweaks to make to the texture loading, and that in general, there is more to be done to the scene loading to improve load times.
  • Crash issues: there have been a number of crash issues associated with the release (and experienced at the start of the meeting). The Lab is gathering logs, etc., and investigating causes.

Custom Emote Issues

This is something the Lab is aware of. It’s also complex to describe but easy to witness. if someone has a custom animation enters an experience, other avatars of the same gender that are already using the same emote, or attempting to use the same emote, will adopt the same custom animation as playing on the new arrival.

So, for example, if a female avatar enters a room with a “floating” animation they’ve assigned to the “/sit” gesture, any other female avatar using “/sit” will also start to float, even if they previously had their own custom animation assigned to “/sit”. The effect is also cumulative: avatars will switch to play the last custom animation assigned to the emote, until such time as they reset through Look Book.

It’s been suggested that whatever bug causes this be annotated so that in future it might show how animations might be shared in certain situation (such as a “dance bomb” in a club hat could be triggered by (say) the DJ to get everyone doing the same dance – the Time Warp, anyone?).

Other Discussion Points

Avatar Deformations

People in VR are experiencing issues with their avatars being deformed in certain situations. For example, a tall male using the female avatar can find the avatar deform or adopts odd shapes, even after the height has been adjusted, almost as if the avatar is “too small” for the person using it. Another seems to give avatars massively broad shoulders, resolved by re-logging. The Lab is aware of these issues and investigating them. If anyone does encounter such issues, the request is to make clear notes on what they were doing  (steps taken) when the problem occurred and file a bug report.

Animation Preview

It’s been noted that there are some glitches with the animation preview capability, such as preview recordings now always playing back on the Sansar Store, or the entire preview playback glitches while playing.

New User Experience

The new default avatars

A part of the new user experience was deployed with this release. In short this:

  • Automatically assigns a unique account ID (seen after the @ symbol in name tags), base on the avatar name + a numeric sequence.
  • Delivers new users directly to a populated experience with a new default grey avatar.

It was mentioned at the meeting that new users will receive a tutorial on the client to get them started when first entering Sansar.

However, it was not clear in the discussion as to whether or not the tutorial aspect has been deployed with the Look At Me release. My own testing suggests it has not: while I was delivered to a populated experience with the new default avatar (see image, right), there was no associated tutorial. While I have reached out to LL to try to confirm the tutorial’s status, at the time of publishing these notes, I had not received any reply.

In Brief

  • Will Sansar support full body tracking? In time, yes, but not on the immediate horizon. The Vive trackers are helping with this, allowing data on hip and foot movements to be collected for use with IK, but Oculus is some way behind in their tracking systems.
  • Currently, when the Chat App is opened and there is available text, it will default to the top of the text (i.e. the oldest comment), rather than scrolling to the bottom of the chat and the most recently made comments. This is a known issue, and part of a number of bugs in the App the Lab will be addressing.
  • Rotating rigged and animated meshes: again requested, to help with bringing NPCs to life. This is apparently “on the list” but seen as a big task.

 

2018 Sansar Product Meetings #44: Steam – with audio

Posted on by Inara Pey
Wurfi’s Little Gallery – blog post

The following notes are taken from the Sansar Product Meeting held on Thursday, November 1st. These Product Meetings are open to anyone to attend, are a mix of voice (primarily) and text chat.

Given the recent announcement concerning expanding Sansar’s availability to Steam, the meeting focused on questions, comments and feedback related to this. Notes:

  • While some more general topics were raised, in a desire to abbreviate the length of this update, I’ve intentionally skipped topics were specific answers weren’t available in favour of focusing on the Steam feedback.
  • The order of these notes does not match the order of discussion in the meeting; topics have been grouped together for ease of reference.
  • Audio extracts from the meeting on the Steam change are included. But again, please note they concatenate comments made at different points in the meeting in an attempt to present them in a more concise order for easier digestion.
  • For those who prefer, the entire meeting can be viewed via Twitch.

On Steam

Why Steam?

  • LL believe that given the improvements made thus far, coupled with the remaining 2018 releases, will make Sansar an attractive proposition on Steam.
  • In being out at physical world events, Lab has hit the question of where people can “find” Sansar – with most asking the question pointing to Steam. Thus, Steam is seen as the place to be.
  • Also, Steam is – as the official blog post indicates – where the highest density of people with hardware that can meet Sansar’s requirements tend to be
    • As noted in my article on the decision, this is regardless as to whether Steam users are VR enabled or not, given Sansar’s Desktop mode.
    •  This is not to say that LL isn’t working to reduce the minimum hardware specs to run Sansar, however these are currently tied somewhat to the state of tethered VR, and may not be changing that much in the foreseeable future.
  • Some reports had headlined the Steam change as a “move”, implying Sansar will only be available through Stream. This is incorrect (hence why I referred to the change as “expanding” to Steam).
    • Sansar will still be available for download from the Sansar.com.
    • Linden Lab is in discussions with Oculus VR to make Sansar available through the Oculus Store.
  • The decision to use Steam is about trying to grow the Sansar audience and gain a much broader cross-section of feedback on how the platform could be improved.
  • With the launch of Sansar on Steam there will be a significant amount of ad spend to help promote Sansar and raise awareness of the platform.
    • There will also likely be new attractions in Sansar to encourage Steam users into the platform.
    • Closer to the launch date effort will be put into establishing a Sansar community on Steam, again to raise awareness that Sansar is coming to the service.
    • Sansar will be on Steam as an Early Access programme, which will hopefully set expectations among Steam users and help mitigate negative reviews.
  • There are no current plans to integrate Sansar with the Steamworks SDK.

Sandex, Fees and Transactions

  • SandeX is to be discontinued in order to achieve compliance with Valve’s requirements for Sansar to appear on Steam.
    • In short, the SandeX floating exchange rate for S$ purchases is too volatile for Stream, and the Lab’s position as a mediator did not fit with Steam’s model.
    • This means the Lab has to switch its position to selling S$ directly to users, who can then spend them within the platform.
    • Creators can then come back to Linden Lab to convert their S$ to fiat currency through the existing credit process.
  • Sansar Dollar purchases, conversion rates and fees:
    • The conversion rate for buying Sansar dollars will remain at 100/1 (100 Sansar Dollars for US $1.00).
    • The 250/1 (or legacy 143/1) rates will be applied to converting S$ back to USD when cashing out.
    • The legacy rate will be available through until at least December 31st, 2019, which is regarded as being the checkpoint date at which it might be changed.
  • Item sales fees:
    • The 15% transaction fee on the sale of items through the Sansar Store will be removed.
    • The transaction fee on gifting will remain.

  • The credit process for creators cashing out of Sansar will remain more-or-less the same as it is at present.
    • Steam will not be a part of this process.
    • It will not be possible for creators to convert S$ they have purchased back into US $ (so only amounts earned through the sale of goods can be converted).
    • The current fees involved in the credit process will be retained to cover charges the Lab faces in allowing cashing-out as a money transmitter.
  • Sansar Dollar purchases:
    • Buying Sansar Dollars through Stream will see a 30% fee charged by Steam in addition to the Lab’s fees.
    • The Lab’s fee on S$ purchases will also be 30%.
    • Buying Sansar Dollars directly through Sansar.com via credit card will not be subject to the 30% Steam fee.
  • The 30-day request period in credit processing is being introduced to meet with Steam’s transaction processing requirements. In short:
    • A consumer can purchase $S through Steam and immediately use them to buy items on Sansar.
    • Currently, the creator(s) receiving the S$ can then cash out in some 5 days.
    • However, LL will not receive any payment from Steam for the original S$ purchase for 30-60 days.
    • Therefore, the 30-day request period is being introduced to offer a balance between LL paying out to creators and receiving income via Steam from consumer purchases of S$.

There have been mixed feelings over the fee changes, with some creators feeling they are being hit with additional purchase fees and longer credit processing lead times. Others feel that overall, the move will be a net gain when considering the abolition of the 15% sales transaction fee plus the potential for a greater volume of users passing through Sansar and making purchases.

There was some confusion on the use of “eligible creators” in the blog post. The term was intended to indicate there will be no change in who can cash out from the current situation.

Goods Pricing

There was a brief discussion on whether the changes for Steam such have creators increasing their prices.

  • The legacy conversion rate of 143/1 (S$143 to the US dollar) is intended to match the current exchange rate for converting S$ to USD, and so creators shouldn’t need to feel an immediate need to alter pricing.
  • However, with the licensing system fixing the amount of royalties creators can obtain in perpetuity  on their licensed products once sold – and given at some point the S$ to USD conversion rate will become S$250 to the dollar – some creators might opt to alter their pricing structures now so as to compensate any loss of revenue as a result of the future change in the conversion rate.

Continue reading “2018 Sansar Product Meetings #44: Steam – with audio” →

2018 Sansar Product Meetings #43: October release preview

Posted on by Inara Pey
The Art of Drew Struzan: The Studio Experience

The following notes are taken from the Sansar Product Meeting held on Thursday, October 25th. These Product Meetings are open to anyone to attend, are a mix of voice (primarily) and text chat.

Native Sit Capability

The Sansar team is working on a native sit capability. This would allow avatars to (finally) sit on objects properly in Sansar (rather than using the awkward teleport + “/sit” command.

  • Will likely initially comprise defining a sit point and exit point on an object to allow sitting / standing using (initially) a basic male or female sit pose.
  • This would work on both static and dynamic objects, although it would potentially means that a chair (and its occupant) could be picked-up and thrown / tossed around, something the Lab is a little cautious about allowing.
  • However, the precise mechanism has yet to be determined.

Avatar / Avatar VR  Interactions

A further capability being developed in for users in VR to directly interact with one another via fist bumps and high fives and sense the feedback through their VR controllers.

October Release Preview

Note: although referred to as the October release, the next release for Sansar is now likely to be early in November 2018.

VR Updates

Button Remapping: The next release will see some of the buttons in VR realigned; the teleport function will no longer be a trigger button, but will be moved to the lower thumb button on each controller. This is to start exposing the trigger buttons for use to fire guns, potentially with the upper thumb button being used as a “reload” button, thus increasing the number of buttons being used by Sansar. Within the Sansar team, this work is being called “Project Pew! Pew!”.

IK Updates: the IK movement capabilities in Sansar have been improvements over the last couple of releases, so that avatars closely follow physical movements. These will continue with release #27, which will also allow VR users to see their own avatars in first-person view. The first version view does cause some clipping of the head, depending on how they are rigged. To help reduce this, the October will include documentation to provide guidance on rigging custom avatars.

Hand Gestures: the upcoming will allow hand gestures to be seen in the blue VR hands in third-version views, and the hands will show with custom avatars. So, if some in 1st person is looking down at their hands in VR, they will see the blue hands for manipulation (useful for avatars which may have things like tentacles are longer than the avatar arm). In the future it should be possible to hide the blue hands altogether, such as when a custom avatar’s hands are correctly rigged.

VR menus: the menus displayed in VR are being resized so they don’t dominate the scene when open.

VR keyboard: VR users will be able to call up a VR keyboard and type chat and direct messages, search the Atlas, etc. This will apparently include Swedish characters!

Custom Animations

The October release will allow creators to upload and sell custom animations. Initially, the capability will not include the ability to designate the emote command, so the existing emotes will have to be re-mapped to use  any custom animations on a per-avatar basis.

  • When purchased, the animation will appear in a new emotes library in the character editor, and the user can re-map an emote to use the animation from there. For example, if a custom dance is uploaded, it can be re-mapped to play using one of the existing dance emotes
  • Although this doesn’t mean emotes can only be used for similar animations, any of the emotes can be remapped to use any custom animation.
  • However, as this is on a per-avatar basis, emotes must be re-mapped if the avatar type is swapped from one gender to the other.

The Desktop Mode Menu

The Desktop Mode menu will change to the left side of the screen, and will offer fewer buttons, as the options have been distilled down to logical groupings. So, for example, Go will offer a sub-menu for the Atlas, Events, etc.

  • This is being done to make the UI more user friendly for new users.
  • There are no plans at this time to make the button positions configurable (e.g. left or right, top or bottom of the screen).

New User Experience Update

Starting with the October release, new users will be taken to an experience on logging-in to Sansar for the first time, and have a default avatar. The experience will be one of those currently populated with other people, the idea being to get new users interaction with other users as quickly as possible.

Which experience a new user is sent to will depend on a number of factors: whether it is public; how many are already in it (to avoid sending new users to an experience nearing its capacity and the possibility they may be re-directed to an empty instance); and those experiences that present a heavy  / long load time will also be avoided.

Permissions / Licensing

There will likely not be any changes to the permissions / licensing system in the next release.

Other Items

  • Additional dance emotes: “dance5″ and” will be added to Sansar with the next release, these will also be available for re-mapping to use custom animations.
  • Avatar skin sub-shader: this will initially only be applicable to custom avatars, not the Sansar system avatars – that will come in time. This will eventually allow people to change the skin of their avatars.
  • New typing indicator: this will be displayed in a similar manner to the speaking indicator, above those using text chat when they are typing. The indicator will be shown in both Desktop and VR modes.
  • New emissive shader.
  • Keyboard language options: Sansar will support a broader range of keyboard layouts beyond the English QWERTY layout, with support for around 20 languages.
  • Updates to Chat and People Apps, including working copy / paste of chat.
  • Client settings: new microphone / voice check option
  • Script updates:
    • scripted raycasting.
    • “motions of interia” API to prevent things like spinning gyroscopes toppling over.

In Planning

The Lab is still working on:

  • Providing more sliders for avatar customisation.
  • Offering the means to change attachment points, but there will not necessarily be an increase in the number of attachment points.

2018 Sansar Product Meetings week #42: licensing changes

Posted on by Inara Pey
Courtesy of Linden Lab

Note: This should have been a Product Meeting summary for week #42 2018. Unfortunately, my PC blue screened on me, some 45 minutes into the meeting, and I lost all audio to that point. As such, these notes focus only on the licensing  / permissions changes as reported in the official blog, with some additional notes from the meeting.

Licensing and Permissions

Following the R26 Thumbs Up release on Tuesday, October 9th, 2018 and the feedback provided, Linden Lab are making changes to the new Licensing and Permissions system. The full details can be found in the official blog post, and summarised below:

  • All items uploaded prior to the R26 Thumbs Up release are re-designated “Unlicensed” objects.
    • Unlicensed items will once again be editable as they were prior to the R26 release. This includes editing values in scripts, editing materials and all other object properties.
    • Unlicensed items can be combined and saved back to inventory, but they cannot be uploaded to the store and sold.
  • All items uploaded after the R26 deployment are designed as “Licensed” objects.
    • These will have fully editable properties  – including materials (so items no longer have to be set to Full Permissions in order to have their materials editable).
    • Unlicensed items can be combined with Licensed objects (e.g. an unlicensed script can be included in a licensed object) and saved back to inventory. However, the combined object cannot be uploaded to the Store for sale.

These changes will come into effect with a Sansar point release due on or around Thursday, October 18th, 2018.

An important point to note with the changes is that all objects uploaded since the R26 release will, by default have materials editing enabled by default as Licensed objects. Therefore, those items for which the creator does not wish to have materials editing enabled will have to be modified after the update has deployed.

Sample of updates properties editing on Licensed and Unlicensed objects. This was a work-in-progress at the time the images were captured, and the final design may be different on release. Credit: Linden Lab

Additional notes:

  • The official blog post on licensing also includes an FAQ that was a WIP at the time of writing this update, therefore please refer to that post for further updates.
  • There will be a further licensing / permissions update (most likely R28 in November) to surface what is, and what is not, an editable parameter on an object.or combined object.
  • As a reminder: all of the above, and the licensing / permissions system in general, only applied to “in scene” objects, Clothing and worn accessories are currently not a part of the licensing / permissions system, but will be added in the future.
  • To become Licensed products, any objects uploaded prior to R26 must be re-uploaded into order to enabled the ownership / license tracking on it.