diff options
author | Justin Clark-Casey (justincc) | 2014-05-30 22:04:59 +0100 |
---|---|---|
committer | Justin Clark-Casey | 2014-06-10 20:21:44 +0100 |
commit | 4bc2201453be3b25788def8bca82e376d010fc10 (patch) | |
tree | f760d6c7335553136d01abf89cac5b630bcbbc46 /bin/openmetaverse_data/lipstick_alpha.tga | |
parent | Add a 0 parameter overload for RestClient.Request() for use when no auth is r... (diff) | |
download | opensim-SC_OLD-4bc2201453be3b25788def8bca82e376d010fc10.zip opensim-SC_OLD-4bc2201453be3b25788def8bca82e376d010fc10.tar.gz opensim-SC_OLD-4bc2201453be3b25788def8bca82e376d010fc10.tar.bz2 opensim-SC_OLD-4bc2201453be3b25788def8bca82e376d010fc10.tar.xz |
Fix issue with BulletSim avatar level flight jitter by commenting out RawVelocity update threshold for now in BSCharacter.UpdateProperties().
For some reason as yet unidentified (feedback?) a threshold above 0.4 here causes the RawVelocity to move between a lower and upper bound rather than remaining constant.
The RawVelocity increased until it triggered the threshold update, at which point it started to decrease until it again triggered the threshhold update.
This delta-v was enough to exceed the checks in ScenePresence.SendTerseUpdateToAllClients() and produce jittery avatar flight because of the fluctuating velocity.
With a threshold of 0.4 (or 0, as with ODE), the RawVelocity remains constant in BulletSim and so avatar flight becomes mostly smooth - remaining occasional glitches appear to be a result of errors in distance extraploation.
There are no obvious problems with commenting out the threshold.
Misterblue, if this is wrong or I've missed some subtlety here, please feel free to revert and/or correct.
The same considerations may or may not apply to object velocity updates.
Diffstat (limited to 'bin/openmetaverse_data/lipstick_alpha.tga')
0 files changed, 0 insertions, 0 deletions