Difference between revisions of "Server Beta User Group"

From Second Life Wiki
Jump to: navigation, search
(Updates)
Line 6: Line 6:
  
 
=== Updates ===
 
=== Updates ===
* No simulator rolls happened this week
+
* No rolls for the main channel
* The backend service which group ban relies on did get updated to support group ban
+
* No rolls for RC BlueSteel
** Provided there aren't any problems, group ban may enter server RC next week!
+
** It's still on the AISv3 project
 +
* RC LeTigre got the group ban project
 +
** [[Release_Notes/Second_Life_RC_LeTigre/14#14.05.30.290506]]
 +
** Viewer download links are in the release notes
 +
** Everything else you need to know is in [[#Group_Ban_FAQ]]
 +
** Has anybody tried it?
 +
* RC Magnum is still on the experience tools project
 +
** This week's update had some minor changes related to experience tools themselves
 +
** [[Release_Notes/Second_Life_RC_Magnum/14#14.05.29.290425]]
  
 
=== Upcoming Stuff ===
 
=== Upcoming Stuff ===

Revision as of 15:30, 3 June 2014

This is the meeting tracking and progress page for the weekly Server BETA QA Meeting, moderated by Maestro Linden. Please contact him on AGNI for more information. You can join the Second Life Beta group for updates.

The next meeting is Thursday, June 5 2014, 3PM PDT at MorrisD on the preview grid, ADITI.

Agenda

Updates

Upcoming Stuff

  • LSL support for materials is in testing
    • Certain Aditi regions (DRTSIM-253 channel, presently) have LSL support for materials
      • Regions "roller-test102" and "roller-test103" are on this channel
      • This is still a work-in-progress - testing is still underway
    • Materials can be added to object faces with llSetPrimitiveParams() functions
      • [PRIM_SPECULAR, integer face, string texture, vector repeats, vector offsets, float rotation_in_radians, vector color, integer glossy, integer environment]
      • [PRIM_NORMAL, integer face, string texture, vector repeats, vector offsets, float rotation_in_radians]
      • [PRIM_ALPHA_MODE, integer face, integer alpha_mode, integer alpha_cutoff]
        • Valid alpha_mode options are PRIM_ALPHA_MODE_NONE, PRIM_ALPHA_MODE_BLEND, PRIM_ALPHA_MODE_MASK, PRIM_ALPHA_MODE_EMISSIVE
    • Materials can be read with the various llGetPrimitiveParams() functions
      • [PRIM_SPECULAR, integer face] returns [string texture, vector repeats, vector offsets, float rotation_in_radians, vector color, integer glossy, integer environment]
      • [PRIM_NORMAL, integer face] returns [string texture, vector repeats, vector offsets, float rotation_in_radians]
      • [PRIM_ALPHA_MODE, integer face] returns [integer alpha_mode, integer alpha_cutoff]
    • Behavior for both getting and setting materials parameters should basically correspond to behavior with PRIM_TEXTURE
    • The color vectors use 0.0-1.0 as the range, as with llSetColor()
    • The integer parameters for PRIM_SPECULAR correspond to the same values that you see in the build tool
    • Components of a material can be 'reset' as follows:
      • PRIM_NORMAL and PRIM_SPECULAR settings are set to 'default' values by setting the texture to NULL_KEY
      • PRIM_ALPHA_MODE settings are set to 'default' values by setting the alpha_mode to PRIM_ALPHA_MODE_BLEND
        • mask_cutoff is actually reset to 0 unless the alpha mode is PRIM_ALPHA_MODE_MASK
      • When PRIM_NORMAL, PRIM_SPECULAR, and PRIM_ALPHA_MODE settings are all set to 'default' values, the material is deleted from that prim face, and LI may be updated accordingly
    • Known issues
      • There is a viewer rendering issue, where the face will not be rendered and you'll see log spam (BUG-6187),
        • If the viewer has ALM enabled
        • and a prim face has a material on it
        • and PRIM_ALPHA_MODE is PRIM_ALPHA_MODE_BLEND (this is the default after a material is added)
        • and the diffuse texture does not have an alpha channel (e.g. plywood)
      • The version currently on Aditi lacks proper throttling, so there could be performance issues if scripts behave badly

Interesting Stuff

Any Other Items

Group Ban FAQ

  • What does group ban do?
    • The group ban feature allows certain group members to specify that certain avatars cannot join the group. When an existing group member is banned, they are also automatically ejected from the group.
  • Who can ban somebody from a group?
    • Only group members with the new “Manage ban list” ability can add or remove avatars from the ban list. By default, only group members in the “Owners” role have the Manage ban list” ability, although this ability may be granted to other group roles.
    • A group role with “Manage ban list” ability will also automatically have “Eject Members from this Group” and “Remove Members from Roles” abilities, as the latter abilities are required in order to ban a group member.
  • What are the limitations of group ban?
    • Group members belonging to the “Owners” role cannot be banned from the group (the same rule applies to ejection).
    • A group may have up to 500 avatars in its ban list. When a group hits this limit, some avatars must be removed from the ban list before others may be added.
    • Group bans are only enforced on simulators which support group ban. During the server RC phase, avatars banned from groups will still be able to join them from non-group-ban simulators (although such users may be ejected from the group at any time).
  • How do I ban somebody from my group?
    1. Login with a viewer that supports group ban
    2. Go to a region that supports group ban
    3. Ensure that you have “Manage ban list” ability
      • This information is found in the group info floater, under ‘Roles’ -> ‘ROLES’ -> ‘Allowed Abilities’ panel -> ‘Group Ban’ section
    4. To ban via the group member list,
      1. Open the group info floater’
      2. Open ‘Roles’ -> ‘MEMBERS’, and select the group members you wish to ban
      3. Hit the ‘Ban Member(s)’ button
      4. The selected group members will be ejected from the group and added to the ban list
    5. To ban any user from your group (a member or not)
      1. Open the group info floater
      2. Open ‘Roles’ -> ‘BANNNED AGENTS’
      3. Hit the ‘Ban Resident(s)’ button
      4. Using the people picker floater, find the avatars you wish to ban
      5. Hit the ‘Ban Residents’ button
      6. The avatars will be added to the ban list. If they were group members, they will also be ejected from the group.
  • How do I unban somebody from my group?
    1. Login with a viewer that supports group ban
    2. Go to a region that supports group ban
    3. Ensure that you have “Manage ban list” ability
    4. Open the group info floater
    5. Open ‘Roles’ -> ‘BANNNED AGENTS’
    6. Select the banned agents you wish to unbar
    7. Hit the ‘Remove Ban(s)’ button
  • Where can I test group ban?
    • Sims which support group ban will soon be available on parts of Aditi, and test viewers will be made available. Stay tuned for updates.

Known issues for group ban

  • Filter by name string under Group -> Roles -> Banned Agents is non-functional (viewer UI)
  • Adding a ban on an agent via Group -> Roles -> Banned Agents -> Ban Resident(s) button doesn't immediately update the list of banned agents (viewer UI)
  • There are no warning messages if you attempt to ban an agent who is already on the Banned Agents list (via Group -> Roles-> Banned Agents -> Ban Resident(s))
  • In the event of a revoked eject ability for a group member, you may see "You ejected user from group" in addition to the correct message "Unable to eject member user from the group"
  • In the event of double ban event the second banner also sees "You ejected user from group" in addition to the correct message.
  • Viewer Ban date doesn't display it in SL time (Pacific Standard Time) - instead, it shows the date in UTC (viewer UI)

Open Items

Minutes from Previous Meetings