| Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
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)
|
|
two regions trying to add a user to the AssetTransactionManager at the same time. So have placed a lock around the Dictionary add.
|
|
|
|
|
|
|
|
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.
|
|
|
|
seperate container for this probably makes the limits easier to
understand
|
|
doesn't link into the rest of the code yet, and won't until it
is complete.
|
|
reference exception.
|
|
properties window
From Justin Casey (IBM)
|
|
*Fixed a 'statement out of order' error in the setting of the permissions that are sent to the client.
|
|
Should fix libsl login ability. No long breaks my login
to test environment.
|
|
make that time changable in a future commit), to use add a entry under the Startup section of opensim.ini , with: timer_Script = "<filename>" (the filename being the console "script" you want to be ran every 20 minutes). This hasn't been tested very much so..
|
|
|
|
|
|
|
|
* Various code convention compliance
|
|
show a user's client that it can't edit a prim if it doesn't have permission.
* Permissions is due for a big revamp. The current way it's done is a hack at best.
|
|
specific user.
* This helps people who have multiple records in their useragent table.
* This update should be looked at.. because really what it should be doing is initiating a grid wide logoff.
|
|
and then tries to save it to the database.. where it was going wrong, is the database had a check to do *nothing* when it got a null useragent. I made it delete the userAgent row. This should be a good enough fix to solve the problem. It still needs to be looked at by a DB guy
|
|
* Revert this once we get a working logoff.
|
|
Linux clients.
|
|
identified as the reason libsl can't currently connect to OpenSim.
Patch from Justin Casey (IBM)
|
|
is really happening the way we want it to.
|
|
* Various refactorings
|
|
that if you're editing an object on your client that you're not allowed to, it'll appear that it's moving to you, but won't actually be moving on the sim.
|
|
during the sim, regionup message.
*Added the main cause for the remoting error to the console display.
*This will make it easier to debug future remoting issues.
|
|
come up to give servers that host a lot of sims a long time to start listening.
|
|
|
|
|
|
have its own
* Locking on value, then changing it does not make sense - lock will happen on old reference
* Taking a local copy of the shared resource then locking on the copy does not make sense - lock will happen on copy
|
|
we are not requesting too much in one gulp.
|
|
issues. This includes the issue that MW described this morning.
There's a lot of little nit picky changes that make a world of difference.
|
|
|
|
that the Queue would come in by reference, but it didn't
appear to be.
|
|
make it easier to start breaking this up into
more discreet functional classes
|
