| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
attachment code when created.
Regression from previous commit c2093ccc. Failed because NPCs don't set the ViaLogin flag
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
The symptom was exceptions while creating physical terrain.
Reduce default terrain mesh magnification to 2 from 3 because the
higher resolution uses a lot of memory and doesn't solve the terrain
smoothness for vehicles.
Added comments here and there and improved some debugging log messages.
|
| | | |
|
| |/
|
|
|
|
|
|
| |
with the other attachments code, using TeleportFlags.ViaLogin check to fire if necessary.
This is to simplify the code (no tricky 'wasChild' signalling required)
and to reduce the risk of a thread clash between simulator-side attaching (necessary for v1 viewers)
and the viewer-side attaching the v3 viewers perform.
|
| | |
|
| |
|
|
| |
if module was enabled.
|
| |
|
|
| |
region is removed rather than base.AddRegion()
|
| |
|
|
|
|
| |
directly in a megaregion, in the same manner at the "teleport user" console command.
This is to bypass an issue with the HGLureModule which stops the auto-teleport from happening.
|
| |
|
|
|
|
|
| |
256m to be neighbours rather than regions up to 512 distant.
This looks like an off-by-one bug since the view distance was already only 256 on the west and south sides.
This reduces the number of child agents being logged into regions neighbouring a megaregion.
|
| | |
|
| |
|
|
| |
this fixes issues where second megaregion auto-teleport hangs on black teleport screen when HG is active.
|
| |
|
|
| |
For debugging purposes.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
