| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
added handler stubs.
|
| |
|
| |
|
|
|
|
|
|
| |
* To test, click the communicate button, then click the 'add' button and type a name. You will get a list of closely matching avatar names.
* Before this'll work on your sim in grid mode, the UGA needs to be updated. If it isn't updated, then you'll get a message on the sim console when searching like, 'got invalid queryid'.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
* Tagged Verbose("msg",...) as obsolete. Please use Verbose("AREA","msg",...) instead.
|
| |
|
| |
|
|
|
|
| |
used to, though)
|
| |
|
| |
|
|
|
|
|
|
|
| |
* Added SSL Option to User Server to allow logins to be done via SSL.
* Added sane handling for when Remote Admin Plugin configuration is not found
* Added some performance boosts to an area of libTerrain which was highlighted in profiling.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
before it's passed to ODE.
|
|
|
|
|
|
|
|
|
| |
SendInventoryItemCreateUpdate() in order to reflect the actual packet it
sends (UpdateCreateInventoryItem).
From Justin Casey (IBM)
|
|
|
|
|
|
|
|
| |
the loaded Sceneobjects (as per mantis request #53).
To use append "-newUID" to the end of the command, so new format is : "load-xml <filename> -newUID".
If you don't add the "-newUID", then the uuids in the xml file will be kept.
|
| |
|
|
|
|
|
| |
* Using the nearest neighbor method, interpolation coming soon.
|
| |
|
| |
|
|
|
|
| |
mpallari/_SomeOne_
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
* Renamed a few console messages to match the new "RADMIN" tag for remote-admin stuff.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
rezzing them in another region.
|
|
|
|
|
| |
a few other bits of refactoring.
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
| |
This also seems to fix the problem of Body parts not being persisted properly.
|
| |
|
| |
|
|
|
|
| |
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)
|
| |
|
| |
|
| |
|
|
|
|
| |
new set is created in the inventory database. Most likely still better to use some other script to populate the inventory database instead of relaying on this.
|
|
|
|
|
|
|
| |
grid, so likely to have problems on a larger grid with more people?
To use , both the user server and Inventory server need to be running this latest revision. (older regions should be able to still be used, just the user won't have inventory on them). Also and HERE IS THE BIG BREAK ISSUE, currently, so that the initial inventory details for a user are added to the inventory db , you need to recreate the accounts using the user server "create user" feature. It should be quite easy to manual populate the inventory database instead but I someone else will need to look into that) Also I've only tested using SQLite as the database provider, there is a Mysql inventory provider but I don't know if it works (SQLite is set as default, so you will need to change it in the inventory server config.xml)
|