| Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
of thread jobs, where one is good enought
|
|
OpenSim.Framework.
|
|
Util.cs routines to convert region coords to and from world coords or handles.
|
|
Relates to http://opensimulator.org/mantis/view.php?id=7337
|
|
(RegionFlags.Persistent but not RegioNFlags.RegionOnline) on startup and when an avatar completes a teleport.
This eliminates spurious network calls and failure reporting.
This is done by adding RegionFlags to the GridRegion returned data in a backward compatible way as an alternative to multiple IGridService.GetRegionFlags() calls
Using a simulator or a grid service older than this commit will just see previous behaviour.
|
|
problem diagnosis.
"show threadpool calls" now also returns named (labelled), anonymous (unlabelled) and total call stats.
|
|
reprioritization distance to be changed on the fly.
This governs when child agent position changes are sent to neighbouring regions.
Corresponding config parameter is ChildReprioritizationDistance in [InterestManagement] in OpenSim.ini
For test purposes.
|
|
|
|
the Util functions for converting world addresses to region addresses
and converting region handles to locations.
|
|
Routines in Util to compute region world coordinates from region coordinates
as well as the conversion to and from region handles. These routines have
replaced a lot of math scattered throughout the simulator.
Should be no functional changes.
|
|
|
|
neighbour region on root agent close.
This was introduced in git master d214e2d0 (Thu May 16 17:12:02 2013)
Caught out by the fact that value types used in iterators act like references and this was dispatched asynchronously.
Should address http://opensimulator.org/mantis/view.php?id=6658
|
|
neighbour rather than sending all closes concurrently on a separate thread.
This is to reduce race conditions where neighbours may be responding erratically, thus mixing up create and close agent requests in time.
This mirrors OpenSimulator behaviour on enabling child agents where each region is contacted separately.
|
|
|
|
|
|
the module code still sets up even if we're using one directly instantiated from the RemoteGridServiceConnector.
Also improves log messages to indicate which regions are sending/receiving various neighbour protocol messages.
|
|
This is done by making the kick user command call IClientAPI.Close() rather than routing through Scene.IncomingCloseAgent(), which also called IClientAPI.Close()
DisableSimulator for child agents is moved from IncomingCloseAgent() to RemoveClient(), this is not a functional change since IncomingCloseAgent() always ends up calling RemoveClient()
|
|
|
|
This is how it was originally. This stops a very long running alarm callback from causing a problem.
|
|
blacklist them for 2 min, so that we don't keep doing remote calls that fail.
|
|
concurrent uses of the same TCP connection, and even of the connections to the same server. So let's stop doing it. This patch makes movement much smoother when there are lots of neighbours.
|
|
a little bit.
|
|
57956c4b-ff2e-4fc1-9995-613c6256cc98>: Invalid character 'O' in input string messages
These are just the result of an attempt to canonicalize received messages - it's not important that we constantly log them.
Also finally get the deregister grid service message working properly
|
|
As far as I can see, the SCS is only now used for informing neighbours of up/down status and possibly sending child agent updates and close requests
|
|
All this is now being handled through IEntityTransferModule and SimulationService instead, and has been for some time.
|
|
not being used any more - it's now IEntityTransferModule and SimulationService instead
|
|
packet per prim. More to come as we change to make use of this.
|
|
ways to access the list/dictionary of child regions and locking was
inconsistent. There are now public properties which enforce locks.
Callers are no longer required to create new copies of lists.
|
|
once to each simulator rather than once to each region. This
should help with some of the delays caused by multiple outstanding
requests to a single service point.
|
|
receiving end is async. No need for so much concurrency.
|
|
|
|
|
|
halting visual behavior of large group deletes and eliminates the packet flood
|
|
|
|
|
|
neighbours.
|
|
crossing
|
|
attachments cross standalone region boundaries
lots of messy debug code here too which would need to be removed
|
|
attachments cross standalone region boundaries"
This reverts commit 5074d290e4aeb583560272cadc8ba09aa8337210.
This gets rid of the massive amount of scene object log spam - sorry about that, folks
|
|
attachments cross standalone region boundaries
lots of messy debug code here too which would need to be removed
|
|
teleport), then tell our neighbours to close the agents.. thereby disconnecting the user. Added a new CloseChildAgent method in lieu of CloseAgent. This has been a long standing problem - with any luck this will cure it.
|
|
teleportation to a remote region without a local connection to the asset server without timing out.
|
|
|
|
implemented correctly. Will review soon.
|
|
InternalEndPoint.Port). This class is complex enough as it is
* Changed the failed to inform neighbor message from a warning to info, since this will fire for every empty neighbor space
* Made the EnableSimulator/EstablishAgentCommunication log message more verbose and more clear about what is happening
|
|
incoming scene object
Add a read-only Attachments property to ScenePresence
|
|
|
|
the new AgentTransferModule, in line with what MW started implementing back in May -- ITeleportModule. This has been renamed IAgentTransferModule, to be more generic.
* HGSceneCommunicationService has been deleted
* SceneCommunicationService will likely be deleted soon too
|
|
|
