| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
we don't want to ignore case. And this seems to be causing problems in mono 4.3.
|
| |
|
|
| |
AssemblyVersion("0.8.2.*")
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
| |
physics engine.
Older physics engines will default to the legacy region size.
Update BulletSim to use the new region size information.
|
| | |
|
| |
|
|
|
| |
and processing routines in BulletSim.
Add linkset rebuild/conversion routine in BSLinkset.
|
| |
|
|
|
|
|
|
| |
on both""
Found that the vehicle movement problem was not caused by these physics changes.
This reverts commit 89857378ce79f93a265bc1eb151e17742032abfa.
|
| |
|
|
|
|
| |
The changes don't seem to be ready for prime time.
This reverts commit 13a4a80b3893af13ab748c177b731fed813974ca.
|
| |
|
|
| |
PhysicsScene and PhysicsActor.
|
| |
|
|
| |
to work with the new params. Not actually plumbed just yet.
|
| |
|
|
| |
This reverts commit c658fa1c0dd83f23c66ccfedb12e8ab02ff01d0a.
|
| |
|
|
| |
Addition of entries to PhysicsActor and setting code in SceneObjectPart.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
invisible barriers in sculptie doorways (Mantis 6529).
Bump up level-of-detail for physical meshes to 32 (the max). This
fixes the invisible barriers that showed up in prim cut arches.
NOTE: the default LOD values are removed from OpenSimDefaults.ini.
If you don't change your OpenSimDefaults.ini, you will continue
to see the arch problem.
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
Update BulletSim DLLs and SOs with simplier step function interface.
|
| |
|
|
| |
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.
|
| |
|
|
| |
mesh caching. Since BulletSim caches and tracks the unmanaged memory version of meshes, the Meshmerizer itself does not need to cache built meshes once BulletSim has made the physical proxy mesh.
|
| | |
|
| |
|
|
| |
have an AssemblyInfo file.
|
| |
|
|
| |
No change to existing functions.
|
| |
|
|
| |
Signed-off-by: Melanie <melanie@t-data.com>
|
| |
|
|
|
|
| |
themselves. For that, the physics module simply calls RequestAssetMethod, which
in turn points to Scene.PhysicsRequestAsset. This gives physics access to
the asset system without introducing unwanted knowledge of the scene class.
|
| |
|
|
|
|
|
|
|
|
|
| |
arbitrary stats.
If active, the physics module can return arbitrary stat counters that can be seen via the MonitoringModule
(http://opensimulator.org/wiki/Monitoring_Module)
This is only active in OdeScene if collect_stats = true in [ODEPhysicsSettings].
This patch allows OdeScene to collect elapsed time information for calls to the ODE native collision methods to assess what proportion of time this takes compared to total physics processing.
This data is returned as ODENativeCollisionFrameMS in the monitoring module, updated every 3 seconds.
The performance effect of collecting stats is probably extremely minor, dwarfed by the rest of the physics code.
|
| |
|
|
|
|
|
|
|
| |
whether the process is 32-bit or 64-bit
In theory, this means that a 64-bit Windows OS user can now run OpenSim.exe with ODE and use more than 2 (or 3) GB of memory.
However, this is completely untested since I don't currently own a 64-bit Windows box. Feedback appreciated.
Using OpenSim.32BitLaunch.exe should continue to work. Other platforms are unaffected.
This will currently not work with sqlite - I will add that too if this works.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
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.
|
| | |
|
| |
|
|
| |
internal to aid code reading/analysis. Remove some unused method arguments
|
| | |
|
| | |
|
| |
|
|
|
|
| |
into a DestroyOdeStructures() method
also adds some method doc
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
vertices in generated prim meshes
Signed-off-by: BlueWall <jamesh@bluewallgroup.com>
|
| |/ |
|
