| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
| | |
| | |
| | | |
Add some debugging logs on region creation to report region size.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
stack.
Implement both LoadTerrain and StoreTerrain for all DBs.
Move all database blob serialization/deserialization into TerrainData.
|
| | |
| | |
| | |
| | |
| | | |
compression base computation.
Complete replacement of float[] for terrain heightmap with TerrainData instance.
|
|\ \ \
| | |/
| |/| |
|
| |/ |
|
| |
| |
| |
| |
| |
| |
| | |
ObjectProperties UDP replies to viewer
Not yet shown that this is used or resolves a bug where not all textures appear on objects with an "XML with textures" upload from singularity 1.8.3
Proper texture entries are actually present and appear properly on relog, but not on select from viewer until at least one face texture is changed.
|
| | |
|
| |
| |
| |
| | |
Appears to be a never used method.
|
| |
| |
| |
| | |
if we sent immediately)
|
| |
| |
| |
| |
| |
| | |
static objects.
Reorder collision flag setting code for terrain to fit pattern used elsewhere.
|
| |
| |
| |
| | |
Signed-off-by: teravus <teravus@gmail.com>
|
| |
| |
| |
| | |
(The changes weren't visible before because updates to attachments aren't sent while the attachment is selected.)
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
the vehicle buoyancy if the vehicle is above its hover height.
This is a known misfeature of this vehicle flag which has been accepted
since it would break too many implementations. The problem is noticed
when creating a jetski-like vehicle that jumps over sand bars. A boat
normally is configured with neutral buoyancy and hovering at water
height. When it jumps the sandbar, it needs to have gravity applied
to get back to water level.
|
| |
| |
| |
| | |
Previously only the first object in the Coalesced Object was rezzed. Now all the objects are rezzed.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
* Break out common BasicDOSProtector code into separate class.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
HTTP Server handlers. XMLRPC Handler, GenericHttpHandler and <Various>StreamHandler
* Applied the XmlRpcBasicDOSProtector.cs to the login service as both an example, and good practice.
* Applied the BaseStreamHandlerBasicDOSProtector.cs to the friends service as an example of the DOS Protector on StreamHandlers
* Added CircularBuffer, used for CPU and Memory friendly rate monitoring.
* DosProtector has 2 states, 1. Just Check for blocked users and check general velocity, 2. Track velocity per user, It only jumps to 2 if it's getting a lot of requests, and state 1 is about as resource friendly as if it wasn't even there.
|
| |
| |
| |
| |
| | |
Constants into TerrainData.
Save compression factor with the terrain blob in the database.
|
|\ \
| |/ |
|
| |
| |
| |
| | |
shout-range, at the request of Singularity dev Liru-Dargon
|
| | |
|
| |
| |
| |
| |
| |
| | |
region modules to directly subscribe to chat and messages received by NPCs
Currently still requires INPC from NPCModule.GetNPC() to be cast to an NPCAvatar.
|
| |
| |
| |
| | |
LLClientView to use same. This passes a terrain info class around rather than passing a one dimensional array thus allowing variable regions. Update the database storage for variable region sizes. This should be downward compatible (same format for 256x256 regions).
|
| |
| |
| |
| | |
reference RegionInfo.RegionWorldLoc?.
|
| |
| |
| |
| | |
TerrainCompressor needed to replace the one in libopenmetaverse that doesn't know about the larger terrain packets.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
-- addition of varaible region size in X and Y
-- internal storage of heightmap changed from double[] to short[]
-- helper routines for handling internal structure while keeping existing API
-- to and from XML that adds region size information (for downward compatibility,
output in the legacy XML format if X and Y are 256)
Updated and commented Constants.RegionSize but didn't change the name for compatibility.
|
| |
| |
| |
| |
| |
| |
| | |
to denote terrain format revision.
Add terrain DB format revision codes to ISimulationDataStore.cs.
Setup so legacy compatible terrain storage and fetch is possible while
allowing future format extensions.
|
|/
|
|
|
|
|
|
| |
count number to integer world coordinates.
Added new methods RegionWorldLoc[XY].
Refactored name of 'RegionLoc*' to 'LegacyRegionLoc*' throughout OpenSim.
Kept old 'RegionLoc*' entrypoint to RegionInfo for downward compatability
of external region management packages.
|
|
|
|
| |
TestSameSimulatorIsolatedRegionsV2()
|
|
|
|
| |
the code that this is symmetric with CloseAgent()
|
|
|
|
|
|
| |
it clear that all non-clientstack callers should be using this rather than RemoveClient() in order to step through the ScenePresence state machine properly.
Adds IScene.CloseAgent() to replace RemoveClient()
|
| |
|
|
|
|
| |
HGEntityTransferModule.OnIncomingSceneObject()
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
also called by HGUserManagementModule
|
|
|
|
|
|
|
|
| |
LLUDPServer.HandleCompleteMovementIntoRegion() to fix race condition regression in commit 7dbc93c (Wed Sep 18 21:41:51 2013 +0100)
This check is necessary to close a race condition where the CompleteAgentMovement processing could proceed when the UseCircuitCode thread had added the client to the client manager but before the ScenePresence had registered to process the CompleteAgentMovement message.
This is most probably why the message appeared to get lost on a proportion of entity transfers.
A better long term solution may be to set the IClientAPI.SceneAgent property before the client is added to the manager.
|
|
|
|
| |
21:41:51 2013 +0100)
|
|
|
|
|
|
| |
debugging purposes.
This may reveal why on some teleports with current code, the UseCircuitCode message gets through but CompleteMovement disappears into the ether.
|
|
|
|
|
|
|
|
|
|
| |
Patch taken from
http://opensimulator.org/mantis/view.php?id=4905
originally by Greg C.
Fixed to apply to r/23314 commit
ba9daf849e7c8db48e7c03e7cdedb77776b2052f
(cherry picked from commit 4ff9fbca441110cc2b93edc7286e0e9339e61cbe)
|
| |
|
|
|
|
|
|
| |
to the receiving avatar's inventory once.
When a user gives an item, the user's client sends an InventoryOffered IM message to its simulator. This adds the item to the receiver's inventory. If the receiver isn't in the same simulator then XMLRPC is used to forward the IM to the correct simulator. The bug was that the receiving simulator handled the message by calling OnInstantMessage() again, which added a second copy of the item to the inventory. Instead, the receiving simulator should only notify the avatar that the item was offered.
|
| |
|
|
|
|
| |
log message
|
|
|
|
|
| |
This is to avoid massive numbers of 'no user found' logs when user IDs are missing for some reason.
UUID.Zero should not be used for any user ID.
|