| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
| |
always grant access to an avatar entering the region if requested.
|
| |
|
|
| |
1 rather than version 0
|
| |
|
|
| |
against a literal number
|
| |
|
|
| |
and have it appear 5 regions over bug by limiting the stored position in the asset to Constants.RegionSize. The stored position in the asset gets overwritten anyway by the rezzing routine, but at least this way, there's no chance of the objects border crossing before the rezzing routine finishes.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| | |
have been in this commit slipped in. If the last heartbeat is more than
2 seconds ago, kill that thread and start a new one. Untested.
his commit adds support to let the first heartbeat complete unconditionally,
since it is almost always longer.
|
| | |
| |
| |
| |
| | |
is too high up for that type of stuff. It needs to be at the
connector/handler level
|
| |/ |
|
| |
|
|
|
|
|
| |
* Breaks up the Client event registrations in Scene into methods of similar event types. The generic event registration registers all of the event types.
*Created symmetrical Un-Registration methods.
* Made the Registration and Unregistration methods public
* Hooks The events required for creating new prim and rezzing new prim into the proper scene.
|
| | |
|
| |
|
|
|
|
| |
right in the new border framework.
* This also contains some inactive preliminary code for disconnecting combined regions that will be used to make one root region a virtual region of a new root region.
|
| |
|
|
| |
and idle performance.
|
| | |
|
| | |
|
| |
|
|
| |
borders! yay
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
perpendicular to the cardinal
|
| |
|
|
| |
movement could hinder another avatar's movement.
|
| | |
|
| |
|
|
|
|
| |
cardinal direction
* Some leg work in getting avatar teleports into 'virtual regions' moved to the proper region.
|
| |\ |
|
| | | |
|
| | | |
|
| |/
|
|
| |
* Use List<Border> for each cardinal to allow for irregular regions.
|
| | |
|
| |
|
|
| |
and a lot of cleaning.
|
| |\
| |
| |
| | |
inventory-connector
|
| | |
| |
| |
| | |
Handler - ref mantis #4010
|
| | | |
|
| |\ \
| |/ |
|
| | |
| |
| |
| | |
* also re-trigger panda
|
| | |
| |
| |
| | |
* Also re-trigger Panda.
|
| |/
|
|
| |
Redirection of the RootFolder property is still todo. This compiles but probably inventory will be inconsistent.
|
| |
|
|
|
|
|
| |
starting to work! - but can't be activated incrementally, the flip needs to be global for all inventory ops.
* Added a base inventory connector that does common processing of inventory among all reference connector implementations. E.g. AddItem requires additional processing before being forwarded to service.
* Added if (m_Enabled) upon RemoveRegion
|
| |
|
|
| |
sizes. * Now, what's available of the terrain will show and it'll be truncated if it's larger on Linden Clients. Parcel minimum is 64 (256/4) for the client to accept it.
|
| |
|
|
| |
256m limitation within the OpenSimulator framework, however, the LLClient ClientView does not support regions larger then 256 meters so, if you try and make your region larger by setting Constants.RegionSize = 512; in OpenSim.Framework.Constants.cs, the terrain will not display on clients using the LLUDP protocol
|
| |
|
|
|
|
|
|
| |
* Uses mantis #3811 as a base (thanks jhuliman) with changes.
* E-mail regarding interface changes sent to the opensim-dev list
* Archive: https://lists.berlios.de/pipermail/opensim-dev/2009-July/007219.html
|
| | |
|
| |
|
|
| |
attachments on teleport.
|
| |
|
|
|
|
|
|
|
| |
linkset, made each of those prims rotate around its own centre rather than around the geometric centre of the selection like they should do (and like the client expects).
This involved adding a new OnUpdatePrimSingleRotationPosition event to IClientAPI so that we can get the changed position from the client.
Btw adding new events to IClientAPI is really tedious where you have to copy the change across to at least 5 or 6 other files.
[Note this doesn't fix the bug where any rotation changes to the root prim (but not the whole linkset) cause rotation errors on the child prims.]
|
| |
|
|
|
|
|
|
|
|
|
|
| |
manipulates the physics Scene.cs
* Remove the draconic locking around adding an avatar to the Scene
* Handle an extreme error case when border crossing fails and user uses map to teleport to a different region on the same instance causing control commands to go to a child agent.
* Make the Set Appearance method use the proper 'remove from physics scene' method.
* It *may* help border crossings.
* It *may* help the 'on avatar rez' lag, that people have been seeing the past week.
* It may also cause physics to crash more often on failed teleports (though.. I think I got the cases covered).
|
| |
|
|
| |
containing all the prims in the group is used for working out the rezzing point. So that none of the child prims are underground. Or at least thats what it is meant to do, still needs more testing and there are still some issues with link sets getting rezzed too high above the ground/target prim.
|
| |
|
|
|
|
|
| |
or half in the prim they are being rezzed on top off. This is currently only correct for single prims (not link groups) and unrotated prims. Next step is to fix for link sets and rotated prims.
This needs a lot more testing to find use cases where it might be wrong (like half way up a hill?)
|
| |
|
|
|
|
|
| |
them troubleshooting options and telling them to restart the simulator. This situation, hopefully is temporary and generates an exception when sqlite users first start OpenSimulator because of an unexpected condition in the database layer. Restart and all is well.
* Added a user friendly message to the 'No IInventoryService available' condition with troubleshooting options.
|
| | |
|
| | |
|
