| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | | |
| | |
| | |
| | |
| | |
| | | |
in a root prim, the focus should remain on the root prim.
Matches behaviour just tested on the Linden grid.
|
| | | |
| | |
| | |
| | | |
camera-at value, rather than replace.
|
| | | |
| | |
| | |
| | | |
child prim with camera-eye set
|
| | | |
| | |
| | |
| | |
| | |
| | | |
prim and the root prim has no corresponding value set, then also set the root prim.
This matches behaviour just tested on the Linden Lab grid.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
prim does not, use the root prim offsets.
This matches behaviour just tested on the Linden Lab grid.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
prims moved camera/focus to wrong position.
For non-root prim, eye offsets now need to be made relative to root prim if either camera-at or camera-eye are set.
Probably a regression since November 2013 when all sits were made relative to root prim to match viewer expections (and fix other bugs).
Addresses http://opensimulator.org/mantis/view.php?id=7176
|
| | | | |
|
| | | |
| | |
| | |
| | | |
chat
|
| | | |
| | |
| | |
| | | |
chat both ways.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
child presence connection directly rather than routing through TestClient.
This code isn't relevant to this test and is already exercised by other tests.
|
| | | |
| | |
| | |
| | | |
to west.
|
| | |/ |
|
| | |\ |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
an exception when the service tried to read the data later on.
Signed-off-by: Oren Hurvitz <orenh@kitely.com>
|
| | | |
| | |
| | |
| | | |
because everything has worked so far, but it's the right thing to do.
|
| | | |
| | |
| | |
| | | |
These characters are used as placeholders for other characters: ": /". But we should search first for the exact string the user entered, and only if that fails then replace the characters and search again.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
anywhere in neighbouring regions.
This was due to a silent uint overflow in ScenePresence.UpdateChildAgent() corrupting child agent positions
when the child agent was in a region with a greater x or y map co-ord than the root agent region
Probably introduced in beeec1c.
This still will not function properly with very high region map co-ords (in the millions) but other parts of the code don't handle this properly anyway.
Looks to address http://opensimulator.org/mantis/view.php?id=7163
|
| | | |
| | |
| | |
| | | |
when sending group messages, not just those after get group members and get presence status, as applicable
|
| | | |
| | |
| | |
| | | |
Slightly simplify config comments.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
that of the groups module.
This is to allow us to get useful information on messaging without being overwhelmed by the rest of groups debug.
Enabled with [Groups] DebugMessagingEnabled = true in config (default false)
Or "debug groups messaging verbose true|false on the console" (similar to existing groups setting).
Done for both xmlrpc and V2 groups.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
notice with XmlRpcGroups messaging did not appear in the user's inventory.
This was because the "session ID" when the message template was copied was always replaced with the group ID, whereas a notice requires this to be the notice ID.
Instead just copy the "session ID" as is - other callers already have this set properly so replacing with group ID was redundant anyway.
Relates to http://opensimulator.org/mantis/view.php?id=7037
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Cross, because the permission checks are different.
Previously we used a heuristic of checking if the entry position is 0 to differentiate between Teleport and Cross, but that doesn't work anymore since we've started providing the precise entry position for cross, too. That's required in order to ensure that the user is allowed to enter the parcel that he's walking into.
|
| | | |
| | |
| | |
| | | |
isn't in the Suitcase
|
| | | |
| | |
| | |
| | | |
due to permissions (in QueryAccess and IsAuthorizedForRegion)
|
| | | | |
|
| | | |
| | |
| | |
| | | |
error messages.
|
| | |/
| |
| |
| | |
asset server is not the same as the simulator's asset server. Unfortunately this still continues to be wasteful -- new assets are created every time an attachment is detached, but the process of storing the new asset goes through the InventoryAccess module, which does all sorts of checks regarding the users' inventory.
|
| | | |
|
| | |
| |
| |
| | |
like copy-paste items in inventory.
|
| | |
| |
| |
| |
| | |
staircases. This change is required because of the change in the
avatar default shape from the capsule to the rectangle.
|
| | |
| |
| |
| | |
method
|
| | |
| |
| |
| | |
does not contain any mandatory parameters and won't be present on older installations.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
currently being used as a flag to orchestrate destination simulator threads on teleport.
If not reset, it's possible that teleports back and forth between simulators may not restart scripts in attachments.
|
| | |
| |
| |
| |
| |
| |
| | |
to restart attachment scripts before the source simulator's SP.UpdateAgent() thread had added them.
This commit changes the order of code so that attachments are re-added before the CompleteMovement() thread is released.
Relates to http://opensimulator.org/mantis/view.php?id=7148
|
| | |
| |
| |
| | |
EstateManagementModule relating to RAW file uploading.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
m_maxAssetRequestConcurrency mistakenly passed in as a timeout to SynchronousRestObjectRequester.MakeRequest()
For a long time, possibly forever, the m_maxAssetRequestConcurrency was mistakenly passed in as a 30 ms timeout rather than as a concurrent connection limiter.
This didn't come to light until the timeout was actually used in recent commit faf9ba53
Since this hasn't been operational for a long time and in release candidate phase, commenting it out for now though will need to revisit this.
Relates to http://opensimulator.org/mantis/view.php?id=7165
|
| | |
| |
| |
| |
| |
| |
| |
| | |
SynchronousRestObjectRequester.MakeRequest() calls with no timeout specified use the default HttpWebRequest timeout as previously.
I mistakenly thought that that default request timeout was inifite rather than 100 seconds, restoring previously behaviour.
As per http://msdn.microsoft.com/en-us/library/system.net.httpwebrequest.timeout%28v=vs.100%29.aspx
Relates to http://opensimulator.org/mantis/view.php?id=7165
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
rather than infinite timeout.
This both signals a problem with the URL and eventually frees the thread, rather than hanging indefinitely with no information.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
handle notices to offline users directly as known undeliverable messages rather than discarding or attempting delivery.
Offline notices can still be controlled with the [Messaging] ForwardOfflineGroupMessages setting.
Looks to address more of http://opensimulator.org/mantis/view.php?id=7037
Only for Flotsam now for testing, but if approach works should be possible with core offline notices as well.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
SynchronousRestObjectRequester.MakeRequest() methods with proper Timeout.Infinite (-1) instead.
Triggered by recent faf9ba53 though this was wrong in the code before, it's just that we didn't actually try to set the timeout given.
|
| | |
| |
| |
| | |
of xmlrpc and core offline IM modules
|
| | |
| |
| |
| | |
GroupsMessagingModule.ProcessMessageFromGroupSession()
|
| | | |
|
