| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
already had a child agent would stop the eq working for the agent in the new region.
This was because the calculation as to whether a new agent was needed in the receiving region did not take megaregions into account,
unlike the original calculation when the user first teleported into the region.
This meant that on teleport, entity transfer would create a new CAP but this would be ignored by the viewer and receiving region, meaning that the EQ could no longer be used.
This would prevent subsequent teleport, amongst other things.
Currently, regions up to 512m from a megaregion are considered neighbours.
|
| |
|
|
|
|
| |
This allows one to retrieve information about agents from a particular region (name, id, position, etc.)
Similar to output from "show users"
See http://opensimulator.org/wiki/Remoteadmin:admin_get_agents for more details
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| | |
Check for the case where the fetched mesh asset fails meshing (degenerate
triangles or no physical mesh). In this case, the asset is marked 'failed'
and BulletSim doesn't keep trying to fetch over-and-over trying to get a
good asset.
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| |
| | |
This tells the viewer to enable the UI for export permissions.
WARNING: If your inventory store contains invalid flags data, this will result
in items becoming exportable! Don't turn this on in production until it's complete!
|
| | |
| |
| |
| | |
with our own and add export permissions as well as a new definition for "All" as meaning "all conventional permissions" rather than "all possible permissions"
|
| |/
|
|
|
|
|
| |
in a linkset.
llGetPrimitiveParams() works through PRIM_LINK_TARGET
Setting via llSetLinkPrimitiveParams(), etc. not yet implemented
|
| |
|
|
|
| |
arithmetic to compute the shortest path between the current tilt
and vertical.
|
| | |
|
| |
|
|
| |
requested quicker than the asset fetcher returns and thus falsely reporting that an asset was not fetched and defaulting the assset to a bounding box.
|
| |
|
|
| |
hull count for simple (non-cut prims) meshes.
|
| |
|
|
|
|
| |
in statistics for monitoring/debugging purposes
These are recorded as 'entitytransfer' stats as seen by the "show stats entitytransfer" console command.
|
| |
|
|
|
|
|
|
| |
currently with a 10 second delay before auto-reteleport to the correct location.
This now does a check for border crossing (required to trigger the teleport) immediately in SP.MakeRootAgent().
If left any later, it looks like the physics scene changes the position and stops the cross happening.
If done any earlier, nothing happens because the cross-code currently requires a PhysicsActor to be in place, thuogh it's probably not necessary for this case.
|
| |
|
|
|
| |
This is relevant to mega-regions where the borders are very different to a regular region.
Also adds some method doc and other code comments.
|
| |
|
|
|
|
| |
on different simulators work.
Also resolves an issue of multiple chatting if the originating simulators had more than one region and they were neighbours
|
| |
|
|
| |
commit 7471bc7
|
| |
|
|
|
|
|
| |
simultaneously logged out then do not continue.
This aims to reduce any side effects if the process tries to complete after the client has logged back in (e.g. it was delayed due to a slow destination region response).
This introduces a new Aborting entity transfer state which signals that the teleport should be stopped but no compensating actions performed.
|
| |
|
|
| |
neighbouring regions are in range.
|
| |
|
|
|
|
|
|
| |
TeleportFinish in order to avoid a theoretical race condition when teleporting to a neighbour.
If we do this after TeleportFinish, then it's possible for a neighbour destination to request the source to create a child agent whilst its still treated as root.
This closes the original presence which we don't really want to do.
This is probably okay (albeit with warnings on the console) but afaics there's no reason not to move the child agent signal.
|
| |
|
|
| |
completion just to be sure we're not using a thread cached version.
|
| |
|
|
| |
accidentally left on a few commits ago.
|
| |
|
|
|
|
| |
running regression tests (fire and forget calls launched on the same thread).
Also adds code comments as to why this pause exists.
|
| | |
|
| |
|
|
|
|
|
| |
viewer couldn't/didn't connect with destination or if destination didn't signal teleport completion.
Also adds regression test for the case where the viewer couldn't connect with the destination region.
Also refactoring of regression test support code associated with entity transfer in order to make this test possible and the code less obscure.
|
| |
|
|
|
|
|
|
|
| |
to fix viewer 3 issues if its own rezzing actions on login collide with the simulator side actions.
This resolves issues (at least in my tests with LL 3.3.4) where this can make attachments invisible until one zooms in on the avatar.
This doesn't affect version 1 viewers since this delay is shorter than the login delay.
This doesn't increase the login time since this part of the process was already being performed asynchronously.
This may be a temporary solution.
|
| |
|
|
|
|
| |
21:38:00 2013)
This break was not connected with the recent attachment code changes.
|
| |
|
|
|
|
|
| |
Scene.CompleteMovement() in order to make all multi-attachments appear on the destination region.
For some reason, sending updates before this will not have this effect.
This may be something related to some viewers (e.g. LL 3.3.4) or something OpenSimulator isn't getting quite right.
|
| |\ |
|
| | |
| |
| |
| |
| | |
seem to be lots of sculpties with this problem while the condition really doesn't
change region operation.
|
| |/
|
|
|
|
|
|
| |
AvatarAppearance
It looks like this was happening when AttachmentsModule.RezAttachments was doing a secondary set of each attachment to update with the asset ID (initially they only have the inventory ID).
However, with multi-attach this was appending a second copy of the same attachment rather than updating the data that was already there.
This commit requires both simulator and service to be updated.
|
| |
|
|
|
|
|
| |
SimExtraStatsCollector
and thus for the command 'show stats' because it is ugly and most of the information
is already output in the formatted printout that appears before.
|
| |
|
|
|
| |
around the world, change LogWriter to use DateTime.UtcNow rather than
DateTime.Now.
|
| |
|
|
|
| |
TerrainMeshMagnification controls number of vertices generated per
heightmap point. Default is 3.
|
| |
|
|
| |
contact processing threshold for static object as well as mesh terrain.
|
| |
|
|
| |
whether a worn object needs to displace an existing attachment on the same point if we are not using multi-attach.
|
| | |
|
| |\
| |
| |
| |
| | |
Conflicts:
OpenSim/Region/CoreModules/Avatar/Attachments/AttachmentsModule.cs
|
| | |
| |
| |
| | |
This also adds/extends regression tests for wearing attachments directly for the scene and attempting to reattach/rewear already attached objects.
|
| | |
| |
| |
| |
| |
| |
| | |
already occupied did not remove the previous attachment (current behaviour)
Regression was commit ccd6f4 (Tue Mar 5 23:47:36 2013)
Added regression test for this case.
|
| | |\ |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Grade, Other features when implemented should slow it down for now be Strong with Vertical Angular attraction setting and conservative with Angular Velocity on X axis)
Signed-off-by: Robert Adams <Robert.Adams@intel.com>
|
| | | |
| | |
| | |
| | | |
connection close issue by getting rid of the socket references * This adds a connection timeout checker to shutdown poor or evil connections and combats DOS attempts that just connect and make no complete requests and just wait. It also actually implements KeepAlive... instead of just understanding the connection header in the request... you can test by connecting and requesting a keepalive header and sending another request on the same connection. The new timeout checker closes expired keepalive sessions, just make sure you send the request within 70 seconds of connecting or the timeout checker will timeout the connection.
|
| | | |
| | |
| | |
| | | |
non-functional and largely commented out for many years.
|
| | |/
| |
| |
| | |
they have different memory management.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
capitalized like Avatars, Friends, etc.
Also fixes access time being set on assets rather than XAssetsMeta
This is to try and be somewhat consistent with other service tables that are mainly in this style.
No migration is supplied, since nobody should be using this service yet except on a test basis.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This only happens if access time is older than 30 days currently, in order to reduce database updates.
The idea is to give some idea of assets which haven't been accessed for a very, very long time.
These might conceivably be deleteable, though this will be a risk due to caching at other points in the chain.
This is actually currently much less useable on the xasset service since access time is on metadata rather than the data itself.
And many metadata entries may point to the same data. Probably need to address this.
|
