| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
|
|
|
|
|
| |
scripts non-modifiable (but still copyable, etc).
Users should not be given the impression that they can modify these items.
This still does not solve the issue where library items cannot be dragged into prims or user inventory any time after they are initially seen.
Curiously, manually copying and pasting still appears to work.
On the surface, this seems to have something to do with library item caching on the client, since deleting the cache allows drag to work again once
Not sure what the exact problem is.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Signed-off-by: Melanie <melanie@t-data.com>
|
|
|
|
| |
the texture was changed
|
|
|
|
| |
Signed-off-by: root <root@grid00001.t-data.com>
|
|
|
|
| |
remove OpenSim.Framework.UndoStack
|
| |
|
|
|
|
|
|
| |
than the object's own zero speed.
As per http://opensimulator.org/mantis/view.php?id=5575
|
| |
|
|
|
|
| |
SychronousRestObjectPoster.BeginPostObject() to the identical SynchronousRestObjectRequester.MakeRequest()
|
|
|
|
|
|
| |
the end.
Tidy up GridCommon.ini.example
|
| |
|
|
|
|
| |
effects and return object
|
|
|
|
|
|
|
| |
AvatarFactoryModule.SetAppearance()
Baked texture set not yet checked, nor persistence of data in avatar service
This is a foundation for later npc related tests.
|
|
|
|
|
|
| |
item id isn't found.
making this query is legitimate and so the log line can cause false positivies. It is up to callers to log an error if appropriate.
|
| |
|
|
|
|
| |
CanGetAgentInventoryItem() to improve code readability
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This matches the ability to disable the memory part
This is controlled through the FileCacheEnabled parameter in FlotsamCache.ini
Default is true, so existing installations are not affected.
Improved fcache command feedback when various caches are disabled.
Re-enabled test for flotsam cache with file caching disabled.
|
|
|
|
| |
already been done for the memory cache
|
|
|
|
| |
Disabled temporarily since file system caching disrupts subsequent test runs
|
|
|
|
|
|
|
| |
always to enter that parcel.
This is patch http://opensimulator.org/mantis/view.php?id=5567
Thanks Snoopy!
|
|
|
|
| |
the scene presence exists
|
|
|
|
|
|
| |
user expectations.
It also matches the default setting in the OpenSim.ini.example file
|
|
|
|
|
|
| |
This now creates an avatar but appearance is always cloudy.
Move doesn't work.
Really, creating an NPC should only involve a ScenePresence rather than doing anything with IClientAPI, since an NPC has no viewer to communicate with!
|
|
|
|
|
|
| |
on login/logout, since it's a bit noisy on the console.
Please uncomment if/when this is still needed.
|
|
|
|
|
|
|
|
|
|
|
| |
rather than just saying "destination not found"
Instead of performing the 4096 check when the region is linked (and subsequently removing the link), leave the link in place and perform the check in the entity transfer module
This allows us to explicitly tell the hypergridder why the teleport failed (region out of range).
It also allows people on regions that are within range (on a large source grid) to teleport.
The Check4096 config parameter in the [GridService] section is replaced by a max_distance paramter in a new [EntityTransfer] section in OpenSimDefaults.ini
Since the parameter is in OpenSimDefaults.ini no action needs to be taken unless you want to increase this limit. It could also be decreased.
The check is being made in the base entity transfer module, since I believe the viewer problem occurs both on extremely large grids and while hypergridding.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
RemoteGridService connector. Timeout is currently set at five
minutes. Negative results are not cached.
The result is that operations like send an instant message do
not have to go through the grid service every time.
|
|/ |
|
|
|
|
| |
as well as item id and asset id
|
| |
|
| |
|
|
|
|
| |
some issues with the zoom level -- TBD.
|
|
|
|
| |
http://opensimulator.org/mantis/view.php?id=5516 once and for all. Moral of the story: don't send AgentOnline/Offline to viewers with a zero-length array.
|
|
|
|
| |
Also, increased the timeout on UserAgentServiceConnector, StatusNotification again.
|
| |
|
|
|
|
| |
not do DNS lookup, and use that for friends notification.
|
|
|
|
| |
instead keep track of which map blocks each client has seen in the region, and reset exactly those when the client closes.
|
|
|
|
| |
its own, clear both memory and file caches
|
|
|
|
|
|
|
|
|
| |
config-include/FlotsamCache.ini.example. Enable the flotsam console commands even if FlotsamCache.ini isn't present.
For the most part, defaults are made to match those already in FlotsamCache.ini.example.
The one exception is that the 48 hour file timeout from the code is used instead of the 0 hours that was in the example file. This can be tweaked if necessary.
Most importantly, the default cache directory is now ./assetcache (as in FlotsamCache.ini.example) rather than ./FlotsamAssetCache (as was the internal code default).
Therefore, if you were using flotasm without using the config file, then please rename your cache directory or start using the ini file and change the default there if you want to keep using your existing cache.
|
| |
|
|
|
|
| |
and reset only exactly the map blocks that had regions in them. WARNING: this fetches all the regions from the Grid service, so there is a chance that this is a really bad idea in large grids. Pushing it for testing.
|
| |
|