| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
perms weirdness, let's all work together to find the real cause.
|
|
|
|
| |
non-script items to prim inventory
|
|
|
|
|
|
|
|
| |
* This means that you can take an object from a region and rez it somewhere else, with its inventory intact.
* As for earlier, at this stage only scripts can be placed in inventory
* This isn't an efficient implementation, a better one will probably need to come along soonish
|
|
|
|
|
|
|
|
| |
* Linkset status is now persistent
* Tweaked a physics child prim positioning hack to generate less database saves
* Re-factored physics object creation calls into ApplyPhysics. To create a new physics representation of an object or linkset, it's only necessary to call *group*.ApplyPhysics(bool m_physicalPrim). *lbsa has been waiting for this refactoring*
* We have collidable linksets now. (they don't become phantom anymore)
|
|
|
|
|
|
|
| |
* Cleaned up copyright notices in AssemblyInfo.cs's
* Added Copyright headers to a bunch of files missing them
* Replaced several common string instances with a static constant to prevent reallocation of the same strings thousands of times. "" -> String.Empty is the first such candidate.
|
|
|
|
|
|
|
|
| |
* It is now possible to edit and save scripts directly from prim inventories
* On saving, the script will be restarted in the region
* Doesn't appear that it's yet possible to drag inventory contents back to agent inventory. Not quite sure why this is yet - the perms all look very permissive.
|
| |
|
|
|
|
|
|
|
|
| |
is changed/updated/deleted (before the trigger only happened if the prim was moved).
This is still development code - experimental prim inventory persistence cannot yet be enabled by users.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
prims on region start.
No user functionality exposed yet - no ini switch to enable persistence or restore. A bit more initial work to do.
|
|
|
|
|
|
|
| |
and then patch these changes back in. Currently it's not quite ready for 0.5. The down side to this action, is that we loose some performance to the garbage collector for now. Given that the target date for 0.5 is *Two days* from now, I'm taking the initiative to work towards a real stable version.
* This update also fixes scripting and some weird physics reactions
|
|
|
|
|
|
|
| |
raytracing
* Ignored some bins
|
|
|
|
|
|
|
| |
above the 'hit' prim instead of buried in the ground somewhere.
* Various Refactorings
|
|
|
|
|
|
|
| |
* shortened references
* Removed redundant 'this'
* Normalized EOF
|
|
|
|
|
|
|
|
| |
after a server restart would not appear (though the script they contain would still be invoked). This
change fixes that problem.
|
| |
|
|
|
|
|
|
|
|
|
| |
correctly accepting prim inventory script updates.
No user functionality yet.
Refactoring to follow.
|
|
|
|
|
|
|
|
|
|
| |
attempt when the asset server is lagging by formalising the de facto polling.
This may not be the best solution in the long run, but should improve things for now.
This may also improve reliability when updating inventory item metadata (e.g. renaming an item) and in retrieving textures
for the main map view.
|
| |
|
|
|
|
| |
script to prim inventory
|
| |
|
|
|
|
| |
Works with LibSL rev>1532
|
|
|
|
|
| |
error in Scene. Affects 6 files and is Mantis#201
|
|
|
|
|
|
|
|
|
| |
race conditions such as that in mantis #190
* Make inventory messages more verbose. Hopefully they aren't now too verbose
* This may resolve some grid instability but it's likely there's much more out there.
|
| |
|
|
|
|
|
|
|
| |
object count on sim stats.
* Fixed a rare, but possible NullReferenceException
|
|
|
|
|
| |
Note: only tested in grid mode, and emptying trash is still not implemented.
|
| |
|
|
|
|
|
|
|
| |
* BACKUP YOUR PRIM BEFORE UPDATING TO THIS and then double check the prim permissions after applying it with a different avatar (then the master avatar or the prim owner avatar).
* Also, beware that any objects created under the old permission scheme may react oddly. They may automatically allow anyone to modify them, (which you'll then have to un-set).
* It's hacked support because when 'anyone can move is set', any avatar can modify the prim (texture, shape, scale, etc)
|
| |
|
|
|
|
|
|
| |
From Justin Casey (IBM)
|
|
|
|
|
|
|
| |
* Un-hackerized generating the client_flags
* Now handling the ObjectPermissions Update packet
* Warning: Backup your prim before updating. If you fail to do so and something goes wrong then, All Yr prim are belong to us!
|
|
|
|
| |
explicit
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
While exploring what it would take to get the 'new script' button working,
I encountered the fact, some way down in the rabbit hole, that if a user
renamed an item in their inventory and logged out (without a restart of
the simulator), on log in the new name was not preserved.
As far as I can see, this was because any updates which didn't occur
inside a transaction were ignored by opensim. This patch pays attention
to those changes. It generates a new asset when an item is updated and
changes the user's inventory properties appropriately. I believe this
behaviour is in line with the copy-on-write semantics used in the Second
Life protocol - perhaps it could be optimized if we knew for sure that the
only copy of the object was in the user's inventory.
This also means that if you rename an item (e.g. a script) before you drag
it into an object's inventory, the inventory will receive the item's most
recent name and description.
|
|
|
|
|
|
|
|
|
| |
SendInventoryItemCreateUpdate() in order to reflect the actual packet it
sends (UpdateCreateInventoryItem).
From Justin Casey (IBM)
|
|
|
|
|
|
|
|
| |
standalone mode it will mean that when you log off and log back on ,as long as the region server hasn't been restarted , your avatar will start with wearing the clothes that it wore on log off. In grid mode its even more limited in that wearing/removing clothes/body parts are only stored in the region server instance you are one. so if you are in a different region to your login region (which are on different region server instances), and then change clothes, those changes won't be remembered. So as said, its very limited but is a small step towards having proper appearance persist.
Just need to store this data out to a database.
|
| |
|
|
|
|
| |
inventory item. (hasn't been tested to make sure no conflicts happen if that new rezzed object is then taken back into inventory but don't think there will be any)
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
a couple of minutes that should fix that.
Some work towards persisting Avatar Appearance (what is being worn).
Added OnAvatarNowWearing event to IClientAPI that is triggered by AgentIsNowWearing packets.
stub code to subscribe to this event in AvatarFactoryModule.
Todo: code needs to be added to AvatarFactoryModule to save the uuids to a database and then read them back when that modules TryGetIntialAvatarAppearance() method is called.
Done some changes to Scene to make it easier to subclass it: including changed some private fields to protected and made some methods virtual.
|
|
|
|
|
| |
* Various code convention compliance
|
|
|
|
|
| |
* Various refactorings
|
|
|
|
|
|
|
| |
threadlocked code. ODEPrim was almost completely re-written.
Copy/Space test needed.
|
| |
|
|
|
|
| |
physics events.
|
| |
|
|
|
|
| |
OpenSim.ini.example in the bin folder for an example.
|
| |
|
|
|
|
|
|
|
| |
use Mono.addins for loading/management. (which is a pure .net solution so works on both Mono and MS .net, and is under the MIT license, will add the source code for the library later). I also suggest we look into switching to using Mono.addins for our Region module loading management.
A little bit more refactoring of Scene.
|