Release Notes/Second Life RC LeTigre/12

From Second Life Wiki
Jump to navigation Jump to search

12.06.23.260473

  • This is the Pathfinding Project.
  • Features and Changes
    • Havok's AI library has been added so that navigation meta data for an entire region can be computed. This data is called the "navmesh".
    • SL objects can be turned into "characters" which use the navmesh to navigate the world and avoid obstacles.
      • New LSL calls have been added to create/update/delete character behavior.
      • Characters cannot be used as attachments.
      • Characters are incompatible with some features, such as keyframed motion, being used as attachments, phantom, size changes, and others.
    • Not all objects in the world contribute to the navmesh calculations.
      • The terrain always contributes
      • By default objects are ignored for the navmesh calculations.
      • Objects may be flagged to modify the navmesh calculations in one of 4 ways:
        • "Walkable" objects add navigable zones to the navmesh.
        • "Static Obstacle" objects cannot be navigated, and create a hole in the nav mesh
        • "Exclusion Volume" objects are like static obstacles, except that they are phantom (meaning that pathfinding characters cannot move through them but other physical objects and avatars can)
        • "Material Volume" objects are phantom objects that can be set to change the walkability coefficients of an area of the navmesh
        • Material volumes and walkable objects have 4 walkability coefficients to determine how expensive they are for each category of character
      • Objects that contribute to the navmesh have special restrictions:
        • Objects that contribute to the navmesh cannot change their physical shape via LSL script (changing object position, shape parameters, scale, rotation, physics shape type, and linking/unlinking is generally blocked)
        • Objects that contribute to the navmesh can be physically changed via the build tool by avatars who have modify permission and if the avatar is in the same region as the object.
        • In other words: objects that contribute to the navmesh cannot be physically changed by avatars who are located in a different region than the object, and therefore such objects cannot be moved across region boundaries.
      • When the navmesh has been modified, either because the terrain has been edited or because an object contributing to the nav mesh was rezzed/modified/deleted, it must be manually regenerated.
      • The pathfinding project viewer can be used to modify the pathfinding settings in a region: http://wiki.secondlife.com/wiki/Linden_Lab_Official:Alternate_Viewers#Pathfinding
      • Parcels that are set No-Entry for objects will cut the navmesh at their borders -- characters will not be able to navigate across it.
    • The collision pipeline has been reorganized. This may affect avatar collisions/control, vehicle movement, and collision callbacks in LSL scripts.
    • The terrain collision shape has been changed from a "heightfield" to a "mesh" to provide more efficient collisions, ray-trace, and navmesh computations.
      • This may change some collision details. In particular see the "Known Issues" list below.
      • When changing the terrain its visible appearance will update immediately, but its collision shape will not.
      • The server will wait at least 10 seconds since the last change before computing the new shape, and the computation time may take several seconds.
      • Where there is a discrepancy between visible and colliding terrain shapes object and avatar collisions may appear incorrect.
    • Fix for PATHBUG-77PATHBUG-77 "llCastRay returns RCERR_CAST_TIME_EXCEEDED until the sim is rebooted"
    • Avatars which are sitting on an object can no longer freeze it by selecting it, if they don't have permission to freeze it while standing.
    • More details about pathfinding can be found at http://wiki.secondlife.com/wiki/Pathfinding and its linked pages
  • Known Issues
    • Fast vehicles can snag on the terrain (which now collides as a mesh shape instead of a heightfield)
    • Certain small physical objects can fall through the terrain surface
    • Mesh objects (such as vehicles) cannot physically cross from a pathfinding region into a non-pathfinding region, due to the upgrade to a newer version of the Havok physics engine
    • After the terrain is edited, the physics engine several needs to 'rebake' the terrain to reflect the new shape, due to the new physics modeling system.
    • PATHBUG-122PATHBUG-122 Ground Sit in a pathfinding region causes appearance to not match real location
    • PATH-784PATH-784 Editing the shape parameters of PHYSICS_SHAPE_TYPE_NONE child prims in navmeshy linksets via build tool incorrectly cause the navmesh to be marked dirty
    • PATH-651PATH-651 Pathfinding characters silently fail when crossing into a region with dynamic_pathfinding disabled
    • PATH-630PATH-630 llSetLocalRot() fails in the root prims of characters
    • PATH-538PATH-538 Character mass as reported by LSL scripts is bogus
    • PATH-536PATH-536 The simulator allows navmesh-contributing objects to be worn as attachments, which causes navmesh properties on the object to be reset.
    • PATH-351PATH-351 Ugly avatar animations are triggered when terraforming terrain that an avatar is standing on
    • PATH-345PATH-345 path_update event is not triggered (with parameters 0, then 1) when object crosses region boundary into the north or east and FORCE_DIRECT_PATH=TRUE



12.06.18.259948

12.06.09.259101

  • Scheduled 2012-06-14
  • This channel contains new simulator changes to help with infrastructure projects. There are no visible changes to behaviour.

12.06.04.258757

12.06.04.258754

  • This is an emergency deploy to fix a security issue. scheduled 2012-06-04
  • Features
    • No new features.
  • Bug Fixes
    • Fixes a griefing vector.

12.05.29.258159

  • Scheduled 2012-05-31
  • This channel contains simulator changes to help with upcoming infrastructure projects. There are no visible changes to behaviour.

12.05.11.256527

12.05.11.256527

12.05.07.255857

12.04.30.255166

12.04.20.254296

12.04.12.253726

12.03.30.252593

12.03.30.252593

  • This "maint-server" project. scheduled 2012-04-04
  • The explicit ban height for parcels is being raised to 5000m. This means that avatars that are explicitly banned from a parcel can not enter them unless they are at least 5000m above ground. This allows high-altitude fly-overs as before, but they must be done at a much higher altitude.
  • Bug Fixes
    • SCR-6 "llGetSubString can produce results that crash Mono scripts"
    • SCR-281 "recent release to agni (12.02.06.248938 I think) breaks llDeleteSubString behaviour."
    • Removed old unused server code.
    • Fixed several server crash modes.
  • This version is on BlueSteel as well.

12.03.26.252149

12.03.20.251556

  • This is again the "threaded region crossing" project. scheduled 2012-03-21
  • Features
    • Prototype threaded region cross for agents. Uses the new threaded RPC/thread state machine mechanism.
  • Bug Fixes
    • Fixed some crash modes that were discovered in the previous iteration of this project
  • Merged with Server Trunk: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Server/12#12.02.24.249991
  • This version is on all 3 RC channels, this week

12.02.24.249991

12.03.06.250637

12.02.24.249991

12.02.15.249527

12.02.02.248819

12.02.06.248938

12.01.27.248571

12.01.18.247990

12.01.13.247734

  • This "maint-server" project scheduled 2012-01-18
  • Features
  • New LSL function integer llSetRegionPos(vector position)
    The object with the script will move the root prim position to the given location. The position is any position within the region. If the position is below ground, it will be set to the ground level at that X,Y spot. The function has no delay or throttle.
    • Returns 1 if the object is successfully placed within 0.1 m of position.
    • Returns 0 and does not move the object if position is more than 10m off region or above 4096m.
    • Returns 0 and does not move the object if the object is dynamic (has physics enabled).
    • Returns 0 and does not move the object if the object can not move to position due to object entry rules, prim limits, bans, etc.
  • "frame_number" option added to llGetEnv()
    Returns an integer that represents the current 'frame' of the simulator. Generally only useful for specific debugging cases.
  • Bug Fixes
    • SVC-7466 A notecard holds more data than a script can read
    • SVC-7520 Keyframe motion doesn't move towards the correct position when specified time is not an exact multiple of 1/45 seconds
    • SVC-7485 llSetKeyframedMotion cannot stop animation if none is running ... sounds less important than it is ...
    • SVC-7493 Weird mesh land impact issue
    • Fixed several simulator crash bugs and potential memory leaks.
    • Fixed a notecard crashing bug.
  • Code also deployed to BlueSteel: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_BlueSteel/12#12.01.13.247734

12.01.06.247303

  • This "maint-server" project scheduled 2012-01-11
  • Bug Fixes
    • SVC-7540 Offline email notifications received but never delivered on login.
Retrieved from "https://wiki.secondlife.com/w/index.php?title=Release_Notes/Second_Life_RC_LeTigre/12&oldid=1169801"