| Commit message (Collapse) | Author | Files | Lines |
|
list of all locations fresh for every scene presence on every frame, we will instead compute the list once every 50 frames and send to all connected presences at that time. Also, we only add 60 items to the list when there are more than 60 presences in the scene. For 1000 users, this change yields a 99.8% reduction in list processing and a 98% reduction in network bandwidth for coarse locations.
|
|
GetAvatars have been removed to consolidate locking and iteration within SceneGraph. All callers which used these to then iterate over presences have been refactored to instead pass their delegates to Scene.ForEachScenePresence(Action<ScenePresence>).
|
|
really don't need two methods doing the same thing, but differently.
|
|
really don't need two methods doing the same thing, but differently.
|
|
really don't need two methods doing the same thing, but differently.
|
|
This reverts commit 596af3f600462fb1e467714e5b898c10aa3d838b.
|
|
* It does this by tweaking the throttles on child agent connection to a megaregion and multiplying the land throttle by 50. (various bit and byte magic ensue)
* While, I doubt this will cause terrain crater sized potholes.. since it actually increases the bandwidth available for land in child regions when MegaRegions area active, more testing would be good.
* This, in theory, also shouldn't cause missing objects in child regions.. because all objects are in the root region anyway. As I said, more testing would be good.
|
|
|
|
miguel, and the fabulous bug reports by our community members.. The workaround fix for the "ERROR:metadata.c:3211:mono_metadata_token_from_dor: code should not be reached" bug in the RegionCombinerModule.
|
|
|
|
* Moves the mono_metadata_token_from_dor message to a different module on loading.
|
|
methods. Let's see if this avoids a mono bug that is making megaregions not work in mono. Long shot, but worth a try.
|
|
RegionLoaded() a two line function
|
|
* There's a slight chance that this could cause a problem with regular prim crossings.. but hopefully not. Revert if it does.
|
|
|
|
|
|
phantom after an import to megaregions.
|
|
before border crossing
* Fixes 'Inconsistent Attachment State' when teleporting into another region besides the SW most region slot on a MegaRegion.
* Fixes a host of other unintended attachment border cross edge cases that lead to Inconsistent attachment state.
|
|
* Yay anonymous delegate in an anonymous delegate.
|
|
|
|
* Rename the RegionCombinerModuleIndividualForwarder to RegionCombinerIndividualEventForwarder so there's no possibility that mono.addins sees any names similar
|
|
* 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
|
|
|
|
|
|
to replace the delegate
* RegionCombinerModule replaces this delegate and distributes the CoarseLocationUpdates through the client connection in the region where the user would be if it was a separate region.
* Fixes Mini Map display on combined regions.
|
|
* Breaks up the Client event registrations in Scene into methods of similar event types. The generic event registration registers all of the event types.
*Created symmetrical Un-Registration methods.
* Made the Registration and Unregistration methods public
* Hooks The events required for creating new prim and rezzing new prim into the proper scene.
|
|
own permissions events again.
* This commit fixes that and does what the last one intended.
|
|
virtual region scenes.
|
|
|
|
|
|
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.
|
|
additional borders that have infinite distances perpendicular to the cardinal of the border surrounding the entire combined region. Recalculates this boundary each time AddScene is called.
|
|
can figure out how to detect the fact that the system is done starting up new regions.
|
|
Infinite distances around the whole AABB of the region
|
|
|
|
perpendicular to the cardinal
|
|
|
|
|
|
|
|
movement could hinder another avatar's movement.
|
|
cardinal direction
* Some leg work in getting avatar teleports into 'virtual regions' moved to the proper region.
|
|
memory in _heightmap and using multiple heightmaps caused them all to overwrite each other and the last one was the heightmap for all of the regions. This fixes that. It also reduces the terrain resolution to half.
|
|
* May rename this later
|