| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| | |
careminster
|
| |
| |
| |
| |
| |
| |
| |
| | |
shouldn't
* Fixes cases where Last Attachment Point doesn't get written when it should.
* Fixes Null Reference in BaseHttpServer when shutting down, null path provided.
* Drop then Wear retains Last Attachment Point
|
| |\ |
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
location in the hijacked variable KeyFrame.AngularVelocity. When steps in OnTimer <= 0.0, normalize the final position by Constants.RegionSize and move the object there. The hack here is KeyFrame.AngularVelocity probably isn't the right name for this variable because it's the un-mucked with keyframe position. When you determine the feasibility of changing the name without affecting the serialization of existing objects in world... It's simply a name change to KeyFrame.FinalPosition or something proper.
(cherry picked from commit e0399ccaec68889c12e4679b4d62142b49b379df)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
stack unwinding.. the faster it goes.
* Tweak XEngine so that it's partially functional again. It's still not great, but basic things work.
(cherry picked from commit 01c3be27460fd3f28efd17b8d6606b883350f653)
|
|\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | |
| | | | |
Conflicts:
OpenSim/Framework/Servers/VersionInfo.cs
OpenSim/Region/CoreModules/Avatar/Chat/ChatModule.cs
|
| | | |
| | | |
| | | |
| | | | |
the LLSD login code. This sends the data through the normal login channels and spits out a JSON object back that mimics the login response. Feel free to comment on the best way to set this up as a config option.
|
| | | |
| | | |
| | | |
| | | | |
it easier to write WebSocket service code that is resistant to Denial of Service attacks.
|
| | | |
| | | |
| | | |
| | | | |
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.
|
|\ \ \ \
| |/ / /
| | | /
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
OpenSim/Data/MySQL/MySQLSimulationData.cs
OpenSim/Data/MySQL/Resources/RegionStore.migrations
OpenSim/Region/ClientStack/Linden/Caps/WebFetchInvDescModule.cs
OpenSim/Region/CoreModules/Avatar/Attachments/AttachmentsModule.cs
OpenSim/Region/CoreModules/Avatar/Inventory/Transfer/InventoryTransferModule.cs
OpenSim/Region/CoreModules/World/LightShare/LightShareModule.cs
OpenSim/Region/Framework/Scenes/Scene.cs
OpenSim/Region/Framework/Scenes/ScenePresence.cs
OpenSim/Region/Framework/Scenes/Tests/ScenePresenceCapabilityTests.cs
OpenSim/Region/OptionalModules/World/NPC/NPCModule.cs
OpenSim/Region/ScriptEngine/Shared/Api/Implementation/LSL_Api.cs
|
| | |
| | |
| | |
| | | |
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.
|
| | |
| | |
| | |
| | | |
(cherry picked from commit 93abcde69043b175071e0bb752538d9730433f1d)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | |
| | |
| | |
| | |
| | |
| | | |
all threads are seeing the latest value and not a cached one.
There is a possibilty that some V2 teleport failures are due to the viewer triggered CompleteMovement thread not seeing the change of m_originRegionID by the UpdateAgent thread.
|
| | |
| | |
| | |
| | | |
debugging purposes
|
| | |
| | |
| | |
| | |
| | |
| | | |
Add parameter for setting the walking stopped threshold.
This fixes the slight jump when an avatar stops walking.
|
| | |
| | |
| | |
| | |
| | | |
This fixes a movement jitter that happens when an avatar is standing on a
tilted surface.
|
| | |
| | |
| | |
| | |
| | | |
This makes scripted object sounds and a few other things play by default instead of having to switch the viewer to adult
This reduces the support burden
|
| | |
| | |
| | |
| | | |
Collision Sounds.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
teleport protocol even if SIMULATION/0.2 is available.
This is specified in the MaxOutgoingTransferVersion attribute of [EntityTransfer] in OpenSim.ini, see OpenSimDefaults.ini for more details.
Default remains "SIMULATION/0.2"
Primarily for http://opensimulator.org/mantis/view.php?id=6755
|
| | |
| | |
| | |
| | | |
calling this method
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
and comment out later log message in ScenePresence.MakeRootAgent()
Need an info message since this is currently important in detecting teleport issue when not at debug log level.
CompleteMovement message occurs before MakeRootAgent() one did
|
| | |
| | |
| | |
| | | |
formatting cleanups
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
a root agent."
This reverts commit c7ded0618c303f8c24a91c83c2129292beebe466.
This proves not to be necessary - the necessary checks are already being done via QueryAccess() before cross or teleport
|
| | |
| | |
| | |
| | | |
avatars are not allowed to cross into a neighbour where they are not authorized, even if a child agent was allowed.
|
| | | |
|
| | |
| | |
| | |
| | | |
verb-noun is consistent with other similar methods
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
explicit that there is a problem if it still finds the agent to be a child if the sender wanted to wait till it became root
Add some comments about the mssage sequence, though much more data is at
http://opensimulator.org/wiki/Teleports
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
LLUDPServer.HandleCompleteMovementIntoRegion()
This is to deal with one aspect of http://opensimulator.org/mantis/view.php?id=6755
With the V2 teleport arrangements, viewers appear to send the single UseCircuitCode and CompleteAgentMovement packets immediately after each other
Possibly, on occasion a poor network might drop the initial UseCircuitCode packet and by the time it retries, the CompleteAgementMovement has timed out and the teleport fails.
There's no apparant harm in doubling the wait time (most times only one wait will be performed) so trying this.
|