| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Add proxy cache clearing when some properties are changed. This fixes
a problem where objects would stop colliding of they were moved
with setPosition mulitple times.
|
| |
|
|
| |
equilibrium point in the physics engine constraint.
|
| |
|
|
|
| |
Add specific error warnings for mis-matched parameter types in extended
physics functions.
|
| |
|
|
| |
parameters that control multiple axis. Add useLinearReferenceFrameA constraint parameter.
|
| |
|
|
| |
for spring constraints. Renumber parameter ops since I can as no one is using them yet.
|
| |
|
|
| |
Add setting of linkset type to physChangeLinkParams. Lots of detail logging for setting of linkset constraint parameters.
|
| | |
|
| | |
|
| |
|
|
| |
events. Normally, physics engines do not return updates for child prims so, under normal operation, this code should never execute. Will only be used when using flexible linkset linkages.
|
| |
|
|
| |
Update routines to use the new parameters list from above change.
|
| |
|
|
| |
LocalID of object which created the taint.
|
| |
|
|
| |
and array of objects rather than a mixture of parameters and array. Makes understanding and parsing what is being passed much easier.
|
| |
|
|
| |
SL heights. Correct BSParam avatar height defaults to be what's in OpenSimDefaults.ini.
|
| |
|
|
| |
implementation of physChangeLinkParams() in BSLinksetConstraint.
|
| |
|
|
| |
as case variables in switch statements.
|
| |
|
|
| |
constraints. Not fully functional. Remove double definition of ExtendedPhysics parameters by having BulletSim reference the optional module (addition to prebuild.xml and usings).
|
| |
|
|
| |
spaces better. This shouldn't affect many since this HACD routine is off by default.
|
| |
|
|
| |
constraint. Add implementation to create spring constraint. Send up property updates for linkset children at the end of flexible linkset links. The simulator probably doesn't do the right thing yet.
|
| |
|
|
| |
the linkset physics at next PostTaint time. Replace the existing calls to ScheduleRebuild to be calls to Refresh(). This allows external routines to make changes to parameters and then cause the linkset to rebuild.
|
| |
|
|
| |
linkset's link back to a fixed, non-moving connection.
|
| |
|
|
| |
should be.
|
| |
|
|
| |
constraints.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
The previous logic would generate land_collision_start and land_collision_end
but would not generate the land_collision itself.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Scene.m_clientManager still retains a reference to a dead client.
Instead, "show client stats" now prints "Off!" so that exception is not thrown and we know which entries in ClientManager are in this state.
There's a race condition which could trigger this, but the window is extremely short and exceptions would not be thrown consistently (which is the behaviour observed).
It should otherwise be impossible for this condition to occur, so there may be a weakness in client manager IClientAPI removal.
|
| |
|
|
|
|
| |
agent.
Relevant if a child agent has been allowed into the region which should not be upgraded to a root agent.
|
| |
|
|
|
|
|
|
|
|
| |
so that they work.
This is necessary because the hypergrid groups checks (as referenced by estates) require an agent circuit to be present to construct the hypergrid ID.
However, this is not around until Scene.NewUserConnection(), as called by CreateAgent() in EntityTransferModule.
Therefore, if we're dealing with a hypergrid user, delay the check until NewUserConnection()/CreateAgent()
The entity transfer impact should be minimal since CreateAgent() is the next significant call after NewUserConnection()
However, to preserve the accuracy of query access we will only relax the check for HG users.
|
| | |
|
| |
|
|
| |
for all bots if no bot number is given
|
| |
|
|
|
|
|
| |
than controlling from the main action loop
This is to avoid excessive and inconsistent delays between behaviours that currently need to embed sleeps in other actions (e.g. physics) and other behaviours.
Might need a more sophisticated approach in the long term.
|
| |
|
|
|
|
| |
or bot it disconnected.
In this case, it is used to turn off jump when physics testing behaviour is removed.
|
| |
|
|
|
|
| |
during operation.
Doesn't currently work very well as stopping physics, for instance, can leave bot travelling in old direction
|
| |
|
|
| |
behaviour <behaviour-name> <bot-number>" console commad
|
| | |
|
| |
|
|
| |
string.join(string, List<string>), or some auto casting is missing
|
| | |
|
| | |
|
| |
|
|
|
|
| |
actually filter out users shown continuously online for more than 5 days
Remove confusion in command output.
|
| |\ |
|
| | | |
|
| |/
|
|
|
|
|
|
| |
online from a standalone/robust instance.
This is not guaranteed to be accurate since users may be left "online" in certain situations.
For example, if a simulator crashes and they never login/logout again.
To counter this somewhat, only users continuously online for less than 5 days are shown.
|
| |
|
|
|
|
|
|
| |
hear chat from their source region for some time after teleport completion.
This occurs on v2 teleport since the source region now waits 15 secs before closing the old child agent, which could still receive chat.
This commit introduces a ScenePresenceState.PreClose which is set before the wait, so that ChatModule can check for ScenePresenceState.Running.
This was theoretically also an issue on v1 teleport but since the pause before close was only 2 secs there, it was not noticed.
|
| |
|
|
| |
This causes extreme console spam if a simulator running latest master and one running 0.7.5 have adjacent regions occupied by avatars.
|
| |
|
|
|
|
|
|
|
|
| |
allow different default regions for HG and direct grid logins.
This requires a new GridService.GetDefaultHypergridRegions() so ROBUST services require updating but not simulators.
This method still returns regions flagged with just DefaultRegion after any DefaultHGRegions, so if no DefaultHGRegions are specified
then existing configured defaults will still work.
Immediate use is for conference where we need to be able to specify different defaults
However, this is also generally useful to send experienced HG users to one default location and local users whose specified region fails (e.g. no "home" or "last") to another.
|
| |
|
|
| |
legacy profiles
|
