| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
| |
02:34:51 2013)
|
| |
|
|
|
|
|
|
|
| |
megaregions.
This fixes the combined bounding box location for regions bigger than 256x256.
It also fixes the position on taking coalesced objects in the non-root regions, where position checks are properly done on rez instead.
It also fixes the megaregion land channel to return null if the land does not exist, which should probably also be done for the ordinary land channels rather than returning a dummy region.
Inspiration from Garmin's commit in http://opensimulator.org/mantis/view.php?id=6595. Thanks!
|
| | |
|
| |
|
|
| |
simply iterate through pending requests without unnecessary checks.
|
| |
|
|
|
|
|
|
|
| |
when they were deleted.
This was because AsyncCommandManager was handing an item ID to IHttpRequestModule.StopHttpRequest() rather than the expected request ID.
This commit also makes the http request asynchronous using BeginGetResponse() rather than doing this by launching a new thread
so that we can more safely abort it via HttpWebRequest.Abort() rather than aborting the thread itself.
This also renames StopHttpRequest() to StopHttpRequestsForScript() since any outstanding requests are now aborted and/or removed.
|
| |
|
|
| |
logout even when no teleport was active.
|
| |
|
|
| |
AttachmentsModule.UpdateUserInventoryWithAttachment()
|
| |
|
|
| |
the base.Name rather than its own Name.
|
| |
|
|
| |
actively writing, simply return null instead of first logging an exception.
|
| |
|
|
| |
InformClientToInitiateTeleportToLocationDelegate to correct spelling and bring into line with other ETM Initiate methods
|
| |
|
|
| |
into RezSingleAttachmentFromInventory from RezSingleAttachmentFromInventoryInternal() done in commit 023faa2
|
| | |
|
| |
|
|
|
|
|
|
| |
rather than actually attached objects
By checking against the grid's Avatar data, we can ignore viewer side attachments but still initiate these calls simulator-side.
Initiating simulator-side is always necessary for version 1 viewers.
This is a further commit to resolve http://opensimulator.org/mantis/view.php?id=6581
|
| |
|
|
|
|
|
|
| |
scripts in attachments.
This was because the script resumption in AttachmentsModule was firing the attach event instead.
Had to reinstate the code in 285bd3a do we can resume the scripts there instead, though the bug existed before its removal.
This is to resolve http://opensimulator.org/mantis/view.php?id=6578
|
| |
|
|
|
|
|
|
| |
now that we're telepoting in a different way."
Unfortunately fails on Nebadon's system right now. Needs investigation. May put in a temproary option for experimentation soon.
This reverts commit d87ddf50fcd674fbd9aa8b8556bf57f2d285a3ba.
|
| |
|
|
| |
part" and other related console commands
|
| |
|
|
|
|
|
| |
that we're telepoting in a different way.
On my own system, I can now eliminate the pause entirely and the reteleport happens whilst the teleport screen is still up.
Trying this change to see if this is true for other people.
|
| |
|
|
|
|
| |
teleporting between regions.
This appears to resolve issues on teleport where attachments disappear or become labelled as invalid within user inventory.
|
| |
|
|
|
|
| |
logging to be switched on and off.
Default is off.
|
| | |
|
| |
|
|
|
|
| |
simulator-side rez attachments call.
This is a further effort to reduce v3 viewer race conditions where this call may clash with the viewer signalling attachment wearing from its current outfit folder.
|
| |
|
|
|
|
|
|
| |
with the other attachments code, using TeleportFlags.ViaLogin check to fire if necessary.
This is to simplify the code (no tricky 'wasChild' signalling required)
and to reduce the risk of a thread clash between simulator-side attaching (necessary for v1 viewers)
and the viewer-side attaching the v3 viewers perform.
|
| | |
|
| |
|
|
| |
if module was enabled.
|
| |
|
|
| |
region is removed rather than base.AddRegion()
|
| |
|
|
|
|
| |
directly in a megaregion, in the same manner at the "teleport user" console command.
This is to bypass an issue with the HGLureModule which stops the auto-teleport from happening.
|
| |
|
|
|
|
|
| |
256m to be neighbours rather than regions up to 512 distant.
This looks like an off-by-one bug since the view distance was already only 256 on the west and south sides.
This reduces the number of child agents being logged into regions neighbouring a megaregion.
|
| |
|
|
| |
this fixes issues where second megaregion auto-teleport hangs on black teleport screen when HG is active.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
already had a child agent would stop the eq working for the agent in the new region.
This was because the calculation as to whether a new agent was needed in the receiving region did not take megaregions into account,
unlike the original calculation when the user first teleported into the region.
This meant that on teleport, entity transfer would create a new CAP but this would be ignored by the viewer and receiving region, meaning that the EQ could no longer be used.
This would prevent subsequent teleport, amongst other things.
Currently, regions up to 512m from a megaregion are considered neighbours.
|
| |
|
|
| |
with our own and add export permissions as well as a new definition for "All" as meaning "all conventional permissions" rather than "all possible permissions"
|
| |
|
|
|
|
| |
in statistics for monitoring/debugging purposes
These are recorded as 'entitytransfer' stats as seen by the "show stats entitytransfer" console command.
|
| |
|
|
|
| |
This is relevant to mega-regions where the borders are very different to a regular region.
Also adds some method doc and other code comments.
|
| |
|
|
|
|
| |
on different simulators work.
Also resolves an issue of multiple chatting if the originating simulators had more than one region and they were neighbours
|
| |
|
|
| |
commit 7471bc7
|
| |
|
|
|
|
|
| |
simultaneously logged out then do not continue.
This aims to reduce any side effects if the process tries to complete after the client has logged back in (e.g. it was delayed due to a slow destination region response).
This introduces a new Aborting entity transfer state which signals that the teleport should be stopped but no compensating actions performed.
|
| |
|
|
| |
neighbouring regions are in range.
|
| |
|
|
|
|
|
|
| |
TeleportFinish in order to avoid a theoretical race condition when teleporting to a neighbour.
If we do this after TeleportFinish, then it's possible for a neighbour destination to request the source to create a child agent whilst its still treated as root.
This closes the original presence which we don't really want to do.
This is probably okay (albeit with warnings on the console) but afaics there's no reason not to move the child agent signal.
|
| |
|
|
| |
completion just to be sure we're not using a thread cached version.
|
| |
|
|
|
|
|
| |
viewer couldn't/didn't connect with destination or if destination didn't signal teleport completion.
Also adds regression test for the case where the viewer couldn't connect with the destination region.
Also refactoring of regression test support code associated with entity transfer in order to make this test possible and the code less obscure.
|
| |
|
|
|
|
|
|
| |
AvatarAppearance
It looks like this was happening when AttachmentsModule.RezAttachments was doing a secondary set of each attachment to update with the asset ID (initially they only have the inventory ID).
However, with multi-attach this was appending a second copy of the same attachment rather than updating the data that was already there.
This commit requires both simulator and service to be updated.
|
| |
|
|
|
| |
around the world, change LogWriter to use DateTime.UtcNow rather than
DateTime.Now.
|
| |
|
|
| |
whether a worn object needs to displace an existing attachment on the same point if we are not using multi-attach.
|
| | |
|
| |\
| |
| |
| |
| | |
Conflicts:
OpenSim/Region/CoreModules/Avatar/Attachments/AttachmentsModule.cs
|
| | |
| |
| |
| | |
This also adds/extends regression tests for wearing attachments directly for the scene and attempting to reattach/rewear already attached objects.
|
| | |
| |
| |
| |
| |
| |
| | |
already occupied did not remove the previous attachment (current behaviour)
Regression was commit ccd6f4 (Tue Mar 5 23:47:36 2013)
Added regression test for this case.
|
