| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
AssemblyVersion("0.8.2.*")
|
| |
|
|
| |
llSetRotationalVelocity(), llTargetOmega(), llLookAt(), and probably a few more LSL features for physical objects in ODE.
|
| |
|
|
|
|
|
|
|
| |
when avatar enters the new region.
This commit addresses the following issues were causing velocity to be set to 0 on the new region, disrupting flight in particular
* Full avatar updates contained no velocity information, which does appear to have some effect in testing.
* BulletSim was always setting the velocity to 0 for the new BSCharacter. Now, physics engines take a velocity parameter when setting up characters so we can avoid this.
This patch applies to both Bullet and ODE.
|
| |
|
|
|
|
| |
problem diagnosis.
"show threadpool calls" now also returns named (labelled), anonymous (unlabelled) and total call stats.
|
| |
|
|
|
|
|
| |
unnecessary object update if the prim was not moving to target.
This involves making PhysicsActor.PIDActive get as well as set.
On physics components that don't implement this (all characters and some phys engines) we return false.
|
| |
|
|
|
| |
This is related to http://opensimulator.org/mantis/view.php?id=7067 .
But that bug complains about BulletSim, and this fix is for ODE.
|
| |
|
|
| |
condition check without changing the logic
|
| |
|
|
|
|
|
| |
forward when moving south or west.
Addresses http://opensimulator.org/mantis/view.php?id=5003
Thanks to UbitUmarov for this fix.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
This is mostly Bluewall's work but I am also bumping the general version number
OpenSimulator 0.7.5 remains in the release candidate stage.
I'm doing this because master is significantly adding things that will not be in 0.7.5
This update should not cause issues with existing external binary DLLs because our DLLs do not have strong names
and so the exact version match requirement is not in force.
|
| | |
|
| |
|
|
|
|
|
|
| |
the physics engines to return the name that is specified in the INI
file ("physics = XXX") as the type of engine.
This os function is a little different than the others in that it
does not throw an exception of one is not privilaged to use it.
It merely returns an empty string.
|
| |
|
|
|
|
|
|
| |
ODEPrim, for instance, always hits this code path twice at the moment
Firstly before any sculpt data has been loaded (hence the spurious message)
Secondly when any sculpt data has been loaded or failed to load (when the message would be valid).
Hence comment this out and rely on the message in ODEPrim.MeshAssetReceived() instead
(though this is not ideal since it requires all physics plugins to copy/paste similar code).
|
| |
|
|
| |
automatically turns off any logging enabled between tests
|
| | |
|
| |
|
|
| |
have an AssemblyInfo file.
|
| | |
|
| |
|
|
|
|
| |
ODEPrim.MeshAssetReceived() callback.
Presumably this is now more useful if the false positive from the old method of loading mesh assets have been eliminated.
|
| |
|
|
|
|
| |
exception.
In some cases (such as failure to receive response from asset service), it is possible for a null to be returned from IAssetService.Get(string, object, AssetRetrieved).
|
| |
|
|
| |
Keep methods private unless they need to be opened up to external callers. Reduces analysis complexity.
|
| | |
|
| |
|
|
| |
OdePrim.BadMeshAssetCollideBits that monodevelop inserted automatically
|
| |
|
|
| |
Fix spelling of collide, change to more self-documenting property BadMeshAssetCollideBits, add method doc, change to private to reduce code analysis complexity
|
| |
|
|
| |
the defaul basic box so they don't go off world.
|
| |
|
|
| |
assets behave like phantom by Nebadon request
|
| |
|
|
| |
Signed-off-by: Melanie <melanie@t-data.com>
|
| |
|
|
| |
No Avatar Avatar Collisions. This causes avatar to be able to walk through each other as if they're ghosts but still interact with the environment.
|
| |
|
|
| |
'pushability' av_planted see OpenSimDefaults.ini. Use when you have unruly visitors that rudely push each other around. Still allows a small amount of movement based on the avatar movement PID controller settings. You can increase the spring tension in the PID controller and really prevent any movement if you would like.
|
| |
|
|
|
| |
This introduces expected contact point hints to the ODE Collider to better determine when to throttle updates as excessive. This /should/ smooth physics objects out again, however, I cannot know every configuration of OpenSimulator, so I'm requesting that testers please examine this change on their build.
Thanks!
|
| |
|
|
| |
to control the reporting of a new angular velocity. I think that this could be here for one of two reasons, 1. vehicles and llMoveToTarget with axis lock, or 2. To attempt to make things look more stable in the physics scene then they really are, however, this also really affects the angular velocity reporting negatively causing things to spin wildly and jump back into place repeatedly. To compromise, if the prim is a vehicle or is being used as a motor target, the original functionality is still applied. If that's not the case, angular velocity is reported with a linear velocity of 0.02m/step. To be clear on the effect of the physical world... When you push things, there's still a lag time where you walk into the object but once the object is in motion, it begins to move as you would expect so results in slightly more realistic motion.
|
| | |
|
| |
|
|
|
|
|
| |
is always IntPtr.Zero and contacts returned always have a valid geometry.
Possibly this was for a feature that was never implemented or was otherwise removed.
Thanks to SignpostMarv for the spot of the warning that shows this parameter was never changed.
|
| |
|
|
| |
Fixes exception that happens when shutting down region (improvements from last patch)
|
| |
|
|
| |
rather than outside to avoid a very occasional race condition with the stat collection thread
|
| |
|
|
|
|
| |
_collisionEventPrimChanges to m_collisionEventActorsChanges to reflect their actual contents.
These dictionaries handle all actor types, not just physical prims.
|
| |
|
|
|
|
|
| |
reporting on logout, rather than stopping clearing their collision events.
This occurred in b18c8c8 (Thu May 17 2012).
This was a cause of very occasional race conditions and likely memory leakage as clients came and went from the region.
|
| |
|
|
|
| |
These will act as a sanity check with the main scene stats, to show that physics scene entities are being managed properly.
Total prims will not match scene total prims since physics total does not include phantom prims
|
| |
|
|
| |
possible. All subsequent code is only relevant if there are contacts.
|
| |
|
|
| |
native spaces or geom collision code
|
| |
|
|
| |
millisecond optional stats
|
| | |
|
| |
|
|
| |
Unnecessary since this has now been broken down into space collisions and geom collisions
|
| |
|
|
| |
listeners in physics frames
|
| | |
|
| | |
|
| |
|
|
| |
physics stat
|
| |
|
|
| |
and geom collision stats
|
| |
|
|
| |
contacts per collision and this is what is actually being measured.
|
