| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
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).
|
|
|
|
|
|
| |
Fixes Mantis #3893
|
|
|
|
| |
if the collisions will affect health if the avatar is invulnerable. (saves 3 loops)
|
|
|
|
| |
revision until further testing can be done.
|
| |
|
|
|
|
|
|
|
| |
correctly.
So next step is to clean up that code and wait for bug reports.
|
| |
|
|
|
|
|
| |
Still more work needed to get linksets to rezz correctly (not in the ground)
|
| |
|
| |
|
| |
|
|
|
|
| |
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?)
|
|
|
|
| |
event trigger rather than triggering the event once for every localid in the derez packet.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
the ball rolling on replacable modules. No user functionality yet
|
|
|
|
| |
joint rotation quaternion and provides a property so consumer doesn't have to.
|
| |
|
|
|
|
|
|
|
|
| |
The patch included updates the root and child prims' AttchedAvatar
with the right UUID. It also cleans the AttachedAvatar properties
for the root and child prims on Drop and Detach
|
|
|
|
| |
side created objects
|
| |
|
|
|
|
|
|
|
|
| |
Attached is a patch that changes the oar file saving of creation date/time to an integer
instead of a string. I did this after justincc emailed me saying there is a problem
with internationalisation doing it the old way and I said I'd fix it. Its been
tested with MySQL and I've made the changes for MSSQL but that hasn't been well tested.
|
|
|
|
| |
any need for a list, as only the last entry in it was acted on. So it now has a single NewForce m_nextVelocity , which is updated (rather than a NewForce object being created every AgentUpdate). So as well as cutting out all the adds and clearing of the list, it also removes the creation of upto 100+ new objects per second per avatar.
|
| |
|
| |
|
|
|
|
|
|
|
| |
from ScenePresence into ISceneViewer/SceneViewer. Currently ScenePresence "has" a ISceneViewer, although if we had a proper Node based scenegraph then it would most likely be attached directly to the nodes.
By extracting this code, it should make it easier to experiment with different ways of managing the update process. [Next step to make this module based, could be to create a SceneViewerFactoryModule]
|
|
|
|
| |
everyone that the so called "forces" are actually velocities.
|
|
|
|
|
|
|
| |
ScenePresence.m_forcesList, so it used the List.Clear method rather than doing a loop through the list and manually removing each item. Thanks dslake.
I also fixed the issue where the code also loops through the m_forcesList and copies each force to the ScenePresence's movementVector. Which resulted in only the last force in the list actually be acted on. As each copy overrode the last one. So now it only copies the last force in the list.
|
|
|
|
|
|
|
| |
This may fix the Mantii where individual prims ctrl-z to nirvana, but
it's not tested.
|
| |
|
| |
|
|
|
|
| |
yes? Panda happy, eh?
|
| |
|
|
|
|
|
|
| |
* Changed some fields to protectesd to enable faking
|
| |
|
|
|
|
|
|
| |
Cause group deeding to apply next owner perms
|
|
|
|
|
|
|
|
|
| |
out which client connection has closed. So, in multi-region sims, things
can get messy fast.
This introduces a second parameters, which is a Scene object ref. Minor
adjustments to custom modules may be required due to this change.
|
|
|
|
|
|
| |
This patch ensures that the touch positions are set during touch_end
events (currently only working for touch_start and touch events).
|
|
|
|
|
| |
* "luke, use the sed"
|
|
|
|
|
|
|
|
|
|
| |
objects, with changes:
- Set OwnerID = GroupID for deeded objects.
- Close a security loophole that would have allowed a user with deed rights in a group to deed ANY object to that group, even if it's not owned by them and/or not set to that group
- Set LastOwnerID correctly. Handle objects vs. prims correctly.
|
|
|
|
| |
Region/CoreModules/ServiceConnectorsOut. No functional changes.
|
|
|
|
| |
get more functions as we go along. It's a very simple service and service connectors, and it served primarily to establish the design of services that dependent on Scenes and that must always have a local connector. More refactoring coming, as this showed how to do it right.
|
|
|
|
|
|
|
| |
Several improvements in the connectors themselves.
Several improvements in configurations.
Needed to add a hack in IUserService and UserManagerBase, to be removed when that service is refactored.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Applied with changes:
- removed spammy debug message
- corrected tab formatting
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change addresses two issues:
[1] It adds a flag field to the blendface call which allows the
caller to indicate whether or not the generated asset is
temporary, and whether or not the asset being replaced should
be explicitly retired fromt the memory cache. The decimal
values correspond to:
0 - Permanent asset, do not expire old asset
1 - Permanent asset, expire old asset
2 - Temporary asset, do not expire old asset
3 - Temporary asset, expire old asset
'3' corresponds to the default behavior seen today, and is
the continued behavior of the non-blendface calls.
[2] The dynamic texture routines are highly-asynchronous and can
be scheduled simultaneously on a multi-core machine. The nature
of the texture management interfaece is such that updates may
be lost, and the nature of asynchornous operation means that
they may be processed out of order. A lock has been added to
ensure that updates are at least atomic. No attempt has been
made to enforce ordering. The lock applies to the SceneObjectPart
being updated and is held for the lifetime of the TextureEntry
used to carry texture updates (the one instance carries all
faces supported by the prim).
Users of these services should remember that the dynamic texture
call is asynchronous and control will be returned *before* the
texture update has actually occurred. As a result, a isubsequent
GetTexture call may not return the expected asset id. A script
must wait for the corresponding TEXTURE_CHANGED event before
retrieving any texture information.
|
|
|
|
|
|
|
| |
how the tests are structured.
(pt1)
|
| |
|