| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
default action made available in PhysicsActor.TargetVelocity. Doesn't change any physics operation but makes DSG work better as the targetVelocity value does not keep moving around.
|
|
|
|
| |
No change to existing functions.
|
| |
|
|
|
|
| |
maintaining their own properties
|
| |
|
|
|
|
|
|
|
| |
own private m_localID property but leaving get to return the then unset PhysicsActor.LocalId!
Instead, just have both subclasses use the PhysicsActor.LocalID property.
This restores collision functionality that fell away in 45c7789 yesterday
|
|
|
|
| |
only receive the very first collision.
|
| |
|
|
|
|
| |
about synchronicity for PhysicsActor.OnCollisionUpdate event doc
|
|
|
|
| |
CollisionEventUpdate() if the number of collisions falls to zero. Reuse the existing one instead.
|
|
|
|
|
|
| |
CollisionEventsThisFrame every time we need to send some new ones, reuse the existing one instead.
This assumes that the listener is using the data synchronously, which is currently the case.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Fixes: Undo, T-pose of others on login, modifiedBulletX works again, feet now stand on the ground instead of in the ground, adds checks to CombatModule. Adds: Redo, Land Undo, checks to agentUpdate (so one can not fall off of a region), more vehicle parts. Finishes almost all of LSL (1 function left, 2 events).
Direct flames and kudos to Revolution, please
Signed-off-by: Melanie <melanie@t-data.com>
|
| |
|
| |
|
|
|
|
|
| |
* Change the PhysicsCollision callback for objects to send full contact point information. This will be used to calculate the collision plane for avatars
* Send the physics engine velocity in terse updates, not the current force being applied to the avatar. This should fix several issues including crouching through the floor and walking through walls
|
| |
|
|
|
|
| |
LICENSE.txt.
|
|
|
|
|
| |
* Define low friction and medium bounce for Glass
|
|
|
|
|
|
|
|
|
|
| |
llSetHoverHeight() should not clamp the x/y position of an object the way MoveTo does,
and it should recalculate the absolute height to hover at as an object moves to reflect
the current ground/water height under it.
Correctly implementing required adjusting the Physics interfaces and implementing at
the physics plug-in level. The attached is a patch that correctly implements
llSetHoverHeight() including updates to the ODE physics plug-in.
|
| |
|
|
|
|
|
|
| |
subclassing; also add new method signatures. Thanks tuco and mikkopa.
Fix Mantis #3072.
|
|
|
|
|
| |
fixes mantis #2874
|
|
|
|
|
| |
* Converts some C# 3.0 syntax into it's 2.0 equivalent so that Visual Studio 2005 can compile it successfully.
|
|
|
|
|
|
|
|
|
|
| |
* Thanks nlin!
* To try it out, set ninja joints active in the ODEPhysicsSettings
and use the example at:
* http://forge.opensimulator.org/gf/download/frsrelease/142/304/demo-playground.tgz.
* Don't forget to change the .tgz to .oar and load it with load-oar.
|
|
|
|
|
|
|
| |
ODEPlugin and pipes them to their respective LSL method.
* NBody will need to be updated, this is an API change. Torque property and AddAngularForce
|
|
|
|
|
|
| |
* Warning! Physics API change. This means that the NBodySimulation needs to be updated!
* PhysicsActor -> void SetVolumeDetect(int) needs to go into classes that use PhysicsActor as their base class.
|
|
|
|
|
|
| |
subroutine down through the physics modules through PhysActor
and SceneObjectPart. No connection to the physics simulators.
|
|
|
|
|
|
| |
in the classes between the LSL implementation and the
underlying physics engines.
|
|
|
|
|
|
|
| |
to the various physics engines. No connection to the
underlying physics simulator yet, just plumbing through
the various classes.
|
|
|
|
|
|
|
| |
to the various physics engines. No connection to the
underlying physics simulator yet, just plumbing through
the various classes.
|
|
|
|
|
|
|
| |
* This is a HUGE OMG update and will definitely have unknown side effects.. so this is really only for the strong hearted at this point. Regular people should let the dust settle.
* This has been tested to work with most basic functions. However.. make sure you back up 'everything' before using this. It's that big!
* Essentially we're back at square 1 in the testing phase.. so lets identify things that broke.
|
| |
|
|
|
|
| |
units may not match the Linden implementation.
|
|
|
|
|
|
| |
massaging OSHttpRequestPump to not abort on exceptions...
|
| |
|
| |
|
|
|
|
| |
not the attachment.
|
|
|
|
|
| |
* Nothing user facing yet.
|
|
|
|
|
|
|
|
| |
* Currently if you apply that to only one or two axis you get unpredictable and sometimes explosive results.
* Three axis works well enough to play with it anyway. More work is needed here.
* Fixed an incorrectly named method in ODE.NET
|
|
|
|
|
|
|
| |
* It doesn't generate at_target events, because they don't exist yet in the script engine.
* The Tau is different, however, compatible with scripts I tested.
* Not perfect... but pretty good.
|
| |
|
|
|
|
|
|
| |
* Thanks for DrScofld for drawing attention to this
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
* Added osSetPrimFloatOnWater(BOOL) to make Physical prim float at the water level.
* osSetPrimFloatOnWater(TRUE); or osSetPrimFloatOnWater(FALSE);
* By default, prim do not float at the water level.
* More work is needed on the floating, but it's a start.
|
|
|
|
|
| |
* Added WaterLevel support to the ODEPlugin. More on this later.
|
|
|
|
|
|
|
|
|
| |
joints. This will change quite drastically, however it's fun to play with.
* To play with this you must link your prim before setting it physical, otherwise they won't link in the physics engine properly. This will also be fixed.
* Currently the linked prim are extremely unstable because I have yet to implement combining of forces with the same normal. This will also be fixed. In fact, the whole PhysicsActor, ODEPrim relationship will be reworked to consider groups from the get-go.
* This implementation is better then it crashing your sim, so I'm commiting it for now.
|
|
|
|
|
|
|
|
| |
* When you select a physical prim, it stops while you've got it selected.
* When you move or alter a prim in some manner, it doesn't become collidable until you de-select it
* When you select a prim, it doesn't become temporarily 'phantom' until you make some change to it while it's selected. (this prevents accidental selections in prim floor from causing it to go phantom on you(but don't move it or you'll fall))
* There's one major difference, and that's a physical object won't stop if you don't have permission to edit it. This prevents people who don't have edit permissions on a prim from stopping it while it's moving.
|