| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | | |
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.
|
| |_|_|_|_|_|/
|/| | | | | | |
|
| |_|_|_|_|/
|/| | | | | |
|
| |_|_|_|/
|/| | | |
| | | | |
| | | | | |
neighbours.
|
| |_|_|/
|/| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
|\ \ \ \
| | |_|/
| |/| |
| | | |
| | | | |
This merge was very conflicted. I think I got them all, but I can't be sure.
I had to merge to master or risk divergence to the point of unmergeability.
|
| | |/
| |/| |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
with 2 simulators. Everything seems to be working, including border crosses. TPs (prim crossing) need love now.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
* CommsManager.AvatarService rerouted
|
| | |
| | |
| | |
| | |
| | | |
* HG is seriously broken here
* Compiles. Untested.
|
| | |
| | |
| | |
| | | |
UserProfileService.
|
| | | |
|
|/ /
| |
| |
| |
| | |
* Started rerouting calls to UserService.
* Compiles. May run.
|
|/
|
|
|
| |
can now determine if a connection is from login, teleport or crossing.
Needed for a meaningful banlines implementation
|
|
|
|
| |
Signed-off-by: Melanie <melanie@t-data.com>
|
| |
|
|
|
|
| |
ScenePresenceAnimator class
|
| |
|
|
|
|
| |
neighbours in the grid service modules.
|
|
|
|
|
|
| |
completely functional.
Also fixed the notification of the message server in standalone -- that server doesn't usually exist.
|
|\ |
|
| |
| |
| |
| | |
teleport around now. (but it still doesn't fix the inconsistent attachment state when teleporting into region slots that are not the south west region on megaregions)
|
|/
|
|
| |
minimally. A few bugs to catch now.
|
|
|
|
| |
the scene itself but SceneCommunicationService, for now. Beginning to clear the code from using Region.Communications. grid stuff.
|
|
|
|
| |
to try to mitigate a mono assert. Same functionality done a different way.
|
|
|
|
|
|
| |
* Changed the Destination ID to 0 in the TeleportFinish Event (why did we have it as 3?)
* Added border based trigger teleports
* Fix MakeRootAgent border cross tests for ensuring that the position is inside the region to use the borders to figure out if it's outside the Region
|
|
|
|
| |
method. This off by one error showed one extra row of neighbors on the north and east side
|
|
|
|
|
|
| |
neighbors. There still may be issues with crossing into the mentioned neighbors of the virtual regions. This makes regions larger then 512x512 (3 virtual regions) display fully to clients.
* Uses a grid request multiple times, so the more regions are in the instance, the longer logging in takes. Consider this temporary until there's a RegionInfo request similar to the MapItem Request.
|
|
|
|
| |
* Move the neighbor region lookup to another method from where it was before in EnableNeighbourChildAgents.
|
|
|
|
|
|
| |
right in the new border framework.
* This also contains some inactive preliminary code for disconnecting combined regions that will be used to make one root region a virtual region of a new root region.
|
| |
|
| |
|
|\ |
|