| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
it doesn't trigger an exception if the item hasn't been found.
In this situation we will now put out a slightly more meaningful log error message instead.
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| |
| |
| | |
desintation sim has no active script engines.
This involves getting IScene.RequestModuleInterfaces() to return an empty array (as was stated in the method doc) rather than an array containing one null entry.
Callers adjusted to stop checking for the list reference being null (which never happened anyway)
|
| |\ \
| |/
| |
| |
| | |
Conflicts:
OpenSim/Region/CoreModules/Agent/AssetTransaction/AgentAssetsTransactions.cs
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
When a slider parameter is changed, the viewer uploads a new shape (or other asset) and the item is updated to point to it.
Viewer 1 uploaded the data in the initial request itself, so the asset references was almost always correctly updated.
However, viewer 3/2 always uploads data in a subsequent xfer, which exposed a race condition where the viewer would make the item update before the asset had uploaded.
This commit shuffles the order of operations to avoid this race, the item is updated with the new asset id instead of the old one while the upload was still taking place.
A second race had to be fixed where avatar appearance would also be updated with the old asset id rather than the new one.
This was fixed by updating the avatar appearance ids when the appearance was actually saved, rather than when the wearables update was made.
|
| |\ \
| |/
| |
| |
| |
| |
| | |
Conflicts:
OpenSim/Region/Framework/Scenes/Scene.Inventory.cs
OpenSim/Region/Framework/Scenes/SceneObjectPart.cs
OpenSim/Region/Framework/Scenes/SceneObjectPartInventory.cs
|
| | |
| |
| |
| |
| |
| | |
reflect what it actually does
This also makes it consistent with some other methods that send data to the client.
|
| |\ \
| |/ |
|
| | | |
|
| | | |
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| | |
The only times when ParentGroup might be null is during regression tests (which might not be a valid thing) and when scene objects are being constructed from the database.
At all other times it's not possible for a SOP not to have a SOG parent.
|
| | |
| |
| |
| | |
Signed-off-by: BlueWall <jamesh@bluewallgroup.com>
|
| | |
| |
| |
| | |
AttachmentsModule.AddSceneObjectAsAttachment()
|
| | | |
|
| | |
| |
| |
| | |
currently hardcoded offset
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Apart from one obvious bug, this was failing because attempting to serialize the script from inside the script (as part of saving the attachment as an inventory asset) was triggering an extremely long delay.
So we now don't do this. The state will be serialized anyway when the avatar normally logs out.
The worst that can happen is that if the client/server crashes, the attachment scripts start without previous state.
|
| | |
| |
| |
| |
| |
| |
| | |
they use the defaults instead.
Some items had completely wrong permissions - this is easier than correcting them all.
The ability to set permissions in xml is retained since there are use cases for this (e.g. to create no-mod library scripts)
|
| | |
| |
| |
| |
| |
| |
| |
| | |
item xml files - always use PermissionMask.All instead (which was the existing default)."
There actually are uses for this. I will correct the perms instead since some entries appear to be wrong.
This reverts commit 667b54f5a2a04fa5a2859397868d270eab3913f1.
|
| | |
| |
| |
| |
| |
| | |
files - always use PermissionMask.All instead (which was the existing default).
Library items always need the same permissions, so it doesn't make sense to load them from the xml files. This just opens the door to permissions mistakes.
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| |
| |
| | |
If a user with a very large inventory right-clicks on their "My Inventory" folder, viewer 1 code will send a massive number of Fetchinventory requests.
Even though each is handled asynchronously via a pool thread, the sheer frequency of requests overwhelms the pool and freezes inbound packet handling.
This change makes the first Fetchinventory thread also handle subsequent requests, freeing up the other threads.
Further efficiencies could be made by handling all the items in a particular FetchInventory request together, rather than separately.
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| | |
This is to avoid problems with corrupt inventories where an inventory link target points back at the source's folder
No viewer has been observed to set these up as of yet. If this ever happens, we will need a more sophisticated solution to track sent folders within the recursion
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
recursively request that folder.
Currently, this should never actually happen but certainly best to handle this case
|
| |\ \
| |/ |
|
| | |
| |
| |
| | |
the same user. Extend TestGiveInventoryItem() to test giving back the same item.
|
| | |
| |
| |
| | |
supporting HG landmarks.
|
| |\ \
| |/ |
|
| | |
| |
| |
| | |
copy/pasting code with small differences
|
| |\ \
| |/ |
|
| | |
| |
| |
| | |
we're inspecting in order to send the required inventory folders
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
To get this to work, I had to disable the dupe link check I put in a couple of commits ago.
When the viewer adds wearables to an existing outfit, it first requests deletes of all the existing links before creating a new set.
Since these messages are async, the creates were being received before the deletes had a chance to complete, resulting in missing current outfit links.
However, the dupe check shouldn't be as important now that broken links have been fixed - it was the broken links that were causing the client to create dupes.
Tested on kokua 0.1.0 WIP and SL 2.6.3. I now have no problems managing outfits on my standalone.
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| | |
It appears that if the viewer requests a folder containing links, we must also send the folders that contain the link targets first.
This was tested with Kokua 0.1.0 WIP though I predict it will also work with other viewer 2s
|
| | |
| |
| |
| | |
id item slot
|
| | |
| |
| |
| |
| |
| |
| | |
I believe this is safe since there is a 1-1 correspondence between link item and worn item (i.e. you can't be wearing the same item at two spots simultaneously in one outfit).
This should stop lots of duplicate links being created when viewer 2 is used.
However, this doesn't prevent broken inventory links, which I believe is timing related since the effect is not consistent (e.g. keep relogging and the viewer should end up seeing them correctly) . I think we actually see this problem on viewer 1 as well.
It might be easier just to implement the Fetch*2 inventory caps which are documented at http://wiki.secondlife.com/wiki/Inventory_API. WebFetch* has been deprecated by Linden Lab since viewer 2.5.1 and according to the sl wiki, "has numerous bugs".
|
| |\ \
| |/ |
|
| | |
| |
| |
| | |
user's inventory. Also commented verbose debug message.
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| |
| | |
Addresses http://opensimulator.org/mantis/view.php?id=5444
Fix is to stop the asset transaction calling UpdateInventoryItem() since the caller is doing it anyway, which is more correct.
This did not effect scripts.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
do not receive this velocity.
This is a minimal fix for the 0.7.1 release, pending a non copy/paste solution.
This hopefully addresses http://opensimulator.org/mantis/view.php?id=5457
The bug was introduced in commit 3ba5eeb
|
| |\ \
| |/ |
|
| | |
| |
| |
| | |
RayEndIsIntersection byte
|
| | |
| |
| |
| | |
rotation it was stored with.
|
