| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
avatars sitting on the same scene obejct, instead of wrongly popping up request permissions dialog.
Resolves http://opensimulator.org/mantis/view.php?id=6478
|
|
|
|
| |
avatar count rather than independently inspecting every scene presence
|
|
|
|
|
|
| |
link number.
As per http://wiki.secondlife.com/wiki/LlGetLinkName
|
|
|
|
|
|
|
|
| |
As per http://wiki.secondlife.com/wiki/LlGetLinkKey
This is done by keeping a scene-object wide list of sitters.
This also fixes bugs in this function where linknums 0 and 1 weren't treated properly if there were sitting avatars on a single prim.
This also fixes a minor race condition for multiple concurrent sitters on a prim with no current sitters by locking on the object-wide list rather than individual sop lists
Addresses http://opensimulator.org/mantis/view.php?id=6477
|
|
|
|
| |
we're deselecting the prim in code before scheduling an update on attachment
|
|
|
|
|
|
|
|
| |
properly.
It seems this is happening because we send a kill for objects that are selected when attached.
A code comment says that this is to get the client to deselect it, but v3 and v1 clients do this just fine without the kill.
Aims to address http://opensimulator.org/mantis/view.php?id=6456
|
|
|
|
| |
based on doxygen error output
|
|
|
|
| |
output; changing an xml-style hint to a uri-style hint in the class summary, improving documentation of Initialise method and removing a superfluous parameter, improving documentating of ClientClosed method and documenting an omitted parameter
|
|
|
|
| |
If an avatar moved between regions: A -> B -> A, then when returning to region A the AvatarEnteringNewParcel wasn't triggered. This happened because the ScenePresence in region A still remembered its previous 'currentParcelUUID', so it appeared as if the avatar didn't change parcels. Now, however, when a ScenePresence becomes a child presence we clear its 'currentParcelUUID'.
|
|
|
|
|
|
| |
from Warn.
This is to stop this unnecessarily triggering log analysis code which reports warn and error level statements.
|
|
|
|
| |
console command
|
|
|
|
| |
rather than having to ToString() them first
|
|
|
|
| |
Scripts dialogs
|
|
|
|
| |
This shows the current animation sequence and default anims for avatars.
|
|
|
|
|
|
|
| |
llRequestPermissions()
This is consistent with all other OSSL NPC functions that allow unowned avatars to be manipulated.
Aims to address http://opensimulator.org/mantis/view.php?id=6483
|
|
|
|
| |
every so many frames. Default to off.
|
|
|
|
| |
into the unmanaged Bullet interface class.
|
|
|
|
|
|
|
|
| |
Copied BulletSNPlugin.BulletSimAPI to a new
BulletSPlugin.BSAPIXNA.cs and then modifyed the latter to
comply with the BSAPITemplate definition. Not totally debugged
but the code is all there for an INI variable to select either
unmanaged C++ Bullet or the C# version of Bullet.
|
| |
|
|
|
|
|
| |
to have pointers and managed to have objects.
Initial paste of XNA code. Commented out.
|
|
|
|
|
| |
A different approach to the patch in http://opensimulator.org/mantis/view.php?id=6462
that doesn't involve further forking of SmartThreadPool
|
|
|
|
| |
BSAPITemplate.
|
|
|
|
| |
relied on prebuilt construction info structures.
|
|
|
|
|
| |
Remove all related calls from the unmanaged and BSAPITemplate interfaces.
Update DLLs and SOs to include the version without HeightMapInfo structures.
|
|
|
|
| |
Update BulletSim DLLs and SOs with simplier step function interface.
|
|
|
|
| |
Only initialization and debug fuctions left.
|
|
|
|
| |
(.ToString(X)) and replace it with a method on BulletBody, BulletShape, ...
|
|
|
|
| |
functions.
|
|
|
|
| |
unmanaged (C++) and managed (C#).
|
|
|
|
| |
BulletSim core to using the BulletSimAPITemplate. Physical object creation and destruction first.
|
|
|
|
|
|
| |
instantiations for PhysBody and PhysShape when BSPhysObject is created
to account for them being classes and not structures.
Update TODO list.
|
|
|
|
|
|
|
|
| |
by reversing the sign on the recoil computation and adding a
[XEngine]RecoilScaleFactor parameter which defaults to zero.
Testing in SL seems to show that there is not a recoil action there.
Or, at least, it is very small. If someone knows how small, the default
for the scale factor should be changed.
|
| |
|
|
|
|
|
|
| |
did the right thing for stopping (speed reducing to zero), it prevented
movement from starting (speed increasing from zero). Will revisit
when the generalize PID motor is debugged.
|
|
|
|
|
|
|
| |
Looks like the viewer bombards the server with avatar orientation
information (we're talking several hundred a second) when the avatar
is being turned or when walking. This change just reduces the number
of 'set' calls into unmanaged code.
|
|
|
|
|
|
|
|
|
| |
asymmetrical avatar capsule work now that rotation is being passed
from the simulator. Turns out the Bullet capsule is just not very
functional: it doesn't scale properly, the implementation only half
does asymmetry and, in general, is hard to work with.
Avatar shape is about what it was before these changes.
Added initial data structures for avatar shape mesh.
|
|
|
|
| |
will be a no-op for ODE but enables asymmetrical avatars for BulletSim.
|
|
|
|
| |
to implement the 'always run' feature.
|
|
|
|
|
| |
by moving the movement motor to a pre-step action and out of its
questionable previous home in UpdateProperties.
|
|
|
|
| |
Remove unused code. Add comments and TODOs.
|
|
|
|
|
| |
Another instance of the underlying Bullet doing, ah, helpful things
when items are added to the world.
|
|
|
|
| |
dynamially turn on/off detailed, unmanaged data dumping of prims and vehicles.
|
|
|
|
| |
individual sub-classes and up to parent BSPhysObject class.
|
|
|
|
| |
velocities of zero.
|
|
|
|
|
| |
object is selected.
Update TODO list.
|
|
|
|
|
| |
rebuilt linkset. I was burnt by making get/set methods with side
effects. I should know better.
|
|
|
|
| |
like raw numbers scattered around the code.
|
|
|
|
| |
I did last time).
|
| |
|
|
|
|
|
| |
step time so it will be applied completely the next step. The internal
AddForce routine does not scale the force.
|