Difference between revisions of "Server Beta User Group"

From Second Life Wiki
Jump to navigation Jump to search
Line 11: Line 11:


* Second Life Server
* Second Life Server
** The main channel got an update related to Tuesday's voice maintenanceThere is nothing particularly notable about this update.
** The main channel updated to the server version that was on Magnum last weekThis project is preparatory work for future viewers, and adds support for improved texture and mesh asset fetching techniques.  
** [[Release_Notes/Second_Life_Server/13#13.09.05.280639]]
** [[Release_Notes/Second_Life_Server/13#13.09.05.280647]]
* BlueSteel and LeTigre
* BlueSteel and LeTigre
** BlueSteel and LeTigre moved to a new server maintenance project.  This project has several stability improvements and LSL bug fixes, and also closes a loophole used to defeat parcel autoreturn.
** BlueSteel and LeTigre are on the same maintenance project as last weekAside from updating to include the changes now found in the main channel, there was a fix for a newly-discovered crash mode.
** [[Release_Notes/Second_Life_RC_BlueSteel/13#13.09.05.280642]]
** [[Release_Notes/Second_Life_RC_BlueSteel/13#13.09.13.281045]]
* Magnum stayed on the asset-fetching project that it had last week.  This project is preparatory work for future viewers, and adds support for improved texture and mesh asset fetching techniques. This update should not affect any viewers which are currently available.
* Magnum got a new server maintenance project.  This project includes all changes found in the BlueSteel and LeTigre project, and also includes some extra changes. The extra changes include more crash fixes and addresses in which certain users on a parcel's "Allowed Residents" list would not be able to enter the parcel, due to other access settings.
** [[Release_Notes/Second_Life_RC_Magnum/13#13.09.05.280647]]
** [[Release_Notes/Second_Life_RC_Magnum/13#13.09.13.281049]]


=== Upcoming Stuff ===
=== Upcoming Stuff ===

Revision as of 11:10, 18 September 2013

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, September 19 2013, 3PM PDT at Morris🖈 on the preview grid, ADITI.


Agenda

Updates

  • Second Life Server
    • The main channel updated to the server version that was on Magnum last week. This project is preparatory work for future viewers, and adds support for improved texture and mesh asset fetching techniques.
    • Release_Notes/Second_Life_Server/13#13.09.05.280647
  • BlueSteel and LeTigre
  • Magnum got a new server maintenance project. This project includes all changes found in the BlueSteel and LeTigre project, and also includes some extra changes. The extra changes include more crash fixes and addresses in which certain users on a parcel's "Allowed Residents" list would not be able to enter the parcel, due to other access settings.

Upcoming Stuff

  • The llParticleSystem documentation has been updated to list some new features
    • Glow, ribbon effect, and blend options
    • These features have been supported by the simulator for several months now, but have not been supported by publicly available viewers.. until very soon
    • A viewer which supports the new effects will be made available at Linden_Lab_Official:Alternate_Viewers as a Maintenance viewer

Interesting Stuff

  • What does the fox say?

Any Other Items

When we have time and because it refers somehow to the new parcell access rules. I'd like to have a function in LSL which at least can determine, if a specified person is able to enter a specified position on the sim, or is able to move along specified path (given by two points in local cordinates), i.e. is able to cross every parcell along the path.

The reason is when you build a vehicle or a physically working teleporter, you face a problem: Although you can read the parcell flags and determine for example if a parcell uses ban list, but you can't determine if any sat passenger is on the list or not. So you get false positives and refuse teleport even if the vehicle would cross the parcell. Now, even if you are ok with that, you have to perform a large number of such checks to be sure at no position of your path you are entering a parcell or cross an edge of a parcell using ban list.

So i'd like to know if such a function is resonable, that takes two vectors and determines if the path connecting them is safe for objects, actually seat and wearing avatars to move along. A reasonable range of systems would benefit of it. Jenna Felton 15:41, 15 September 2013 (PDT)

Open Items

Minutes from Previous Meetings