| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| | |
|
| |
|
|
| |
Also removes small bug where calling this method would add 1 to LPS, evne though all callers already did this.
|
| |
|
|
| |
instead of searching the task inventory manually.
|
| |
|
|
|
|
| |
SceneObjectPartInventory.GetInventoryItem(string)
Also gets llStopAnimation() to call KeyOrName rather than duplicating logic.
|
| |
|
|
|
| |
Corrected to stop animations using the animation UUID similar to llStopAnimation.
See http://opensimulator.org/wiki/OsAvatarStopAnimation
|
| | |
|
| |
|
|
| |
not before.
|
| |
|
|
| |
return earlier to simplify method
|
| |
|
|
| |
at SceneObjectPartInventory.ApplyNextOwnerPermissions().
|
| |
|
|
| |
reason "Communications failure" no matter what the destination region actually returned
|
| |
|
|
|
|
|
|
|
| |
before the source region has finished cleaning up old agent data and structures.
If this is allowed, then the client usually gets forcibly logged out and data structures might be put into bad states.
To prevent this, the binary state machine of EMT.m_agentsInTransit is replaced with a 4 state machine (Preparing, Transferring, ReceivedAtDestination, CleaningUp).
This is necessary because the source region needs to know when the destination region has received the user but a teleport back cannot happen until the source region has cleaned up.
Tested on standalone, grid and with v1 and v3 clients.
|
| |
|
|
|
|
|
|
|
|
| |
of always true no matter what the callee actually returned.
This was due to two things
1) SimulationServiceConnector.QueryAccess was always looking to the outer result["success"].
But if a "_Result" map is returned (which is certainly the case right now), then the true success is _Result["success"], result["success"] is always true no matter what
2) If QueryAccess was false at the destination, then AgentHandlers.DoQueryAccess() was never putting this in the result.
The default action of SerializeJsonString() is not to put false booleans in the JSON!!!, so this has to be explicitly set.
|
| |
|
|
|
|
| |
taking place, rather than just (falsely) logging that we're not going to proceed.
An oversight from recent commit 9ab0c81
|
| |
|
|
| |
to the destination scene actually succeeds.
|
| |
|
|
| |
module once rather than repeatedly via scene presences
|
| |
|
|
|
|
| |
leave the user unable to teleport since the transit flag was not being reset.
This moves the 'already in transit' check further up and resets the flag if dns resolution fails and in the new required places.
|
| |
|
|
| |
Signed-off-by: BlueWall <jamesh@bluewallgroup.com>
|
| |
|
|
| |
Signed-off-by: BlueWall <jamesh@bluewallgroup.com>
|
| |
|
|
| |
file on OAR save
|
| |
|
|
| |
lookup rather than the region handle.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
allow an immediate teleport back.
This is to help relieve a race condition when an agent teleports then immediately attempts to teleport back before the source region has properly cleaned up/demoted the old ScenePresence.
This is rare in viewers but much more possible via scripting or region module.
However, more needs to be done since virtually all clean up happens after the transit flag is cleared .
Possibly need to add a 'cleaning up' state to in transit.
This change required making the EntityTransferModule and HGEntityTransferModule per-region rather than shared, in order to allow separate transit lists.
Changes were also required in LocalSimulationConnector.
Tested in standalone, grid and with local and remote region crossings with attachments.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
includes database region store migrations for mssql, mysql, sqlite
enable/disable this module:
Cap_EnvironmentSettings = "localhost" (for enable)
Cap_EnvironmentSettings = "" (for disable) at ClientStack.LindenCaps section (OpenSimDefaults.ini file)
or owerwrite in OpenSim.ini
mantis: http://opensimulator.org/mantis/view.php?id=5860
Signed-off-by: BlueWall <jamesh@bluewallgroup.com>
|
| | |
|
| | |
|
| |
|
|
| |
MODULE] strings, though all these are currently commented out anyway
|
| |
|
|
|
|
|
|
|
|
| |
console scene(s)
This includes prim count, script count, avatar count, etc.
Information is currently the same as "show stats", though show stats can only show one scene at a time because it listens for the latest outgoing stats packet (a bad approach that needs to change).
Might be better to tie this module into the other stats module to display arbitrary stats rather than fetching directly from scene.SimStatsReporter.
Console command is "show scene" because "show region" already exists for the grid service, which is unfortunate.
Might need to make a distinction between "scene" relating to a live scene and "region" relating to more static region data (url, coords, etc.)
|
| |
|
|
| |
ConsoleDisplayTableRow and ConsoleDisplayTableColumn
|
| |
|
|
|
|
| |
list form.
Convert "show region" to use this structure rather than hand-constructing
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
AddRegion()
The reference is not guaranteed to be there when AddRegion() is called but will definitely be present at RegionLoaded() if it's going to be present at all.
|
| | |
|
| |
|
|
|
|
|
| |
llAttachToAvatar() or osForceAttachToAvatar() would wrongly have next permissions come into play when they detached that object and rezzed it in scene.
This is because the attachments module code was setting the 'object slam' bit by using PermissionMask.All
Solution here is to route the attachment item creation call through the existing inventory code in BasicInventoryAccessModule rather than copy/pasted code in AttachmentsModule itself.
|
| |
|
|
|
| |
This is to eliminate possible race conditions if two teleport calls are made concurrently, where at least one is a local teleport.
This is pretty much impossible on a manual user teleport but can happen on script-invoked teleports.
|
| | |
|
| |
|
|
| |
Outfit folders are a type of system folder whose details are allowed to change.
|
| | |
|
| |
|
|
|
|
| |
saved) will have a size larger than 256x256
Not yet read. Do not rely on this information yet, it may change.
|
| |
|
|
| |
rather than copy/pasting the necessary calculations in lots of places.
|
| |
|
|
| |
so that it's easy to tell whether they refer to the root region connection or a new region connection
|
| |
|
|
| |
root region of a megaregion relative to an added region
|
| |
|
|
|
|
|
| |
of over-inflated.
This was previously over-inflated because adding a region to the NE of the root region resulted in double counting of regions already added.
An accurate extent will also be necessary for other purposes.
|
| |
|
|
|
|
| |
more than one megaregion in a simulator, separated by water.
Rename IsRootRegion() to IsRootForMegaregion()
|
| | |
|
| |\ |
|
| | | |
|
| | |\ |
|
| | | |
| | |
| | |
| | | |
for the tip.
|
