| Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
Reduce object density by factor of 100 to bring physical mass computations
into a range better suited for Bullet.
|
|
properties for""
Found that the vehicle movement problem was not caused by these physics changes.
This reverts commit 84d0699761b8da546f9faef084240d7b15f16321.
|
|
BSPrimLinkable""
Found that the vehicle movement problem was not caused by these physics changes.
This reverts commit 7b187deb19517aa7c880458894643a5448566a94.
|
|
enabled.""
Found that the vehicle movement problem was not caused by these physics changes.
This reverts commit 5f7b2ea81b95a60e882bc65b663a2c9fe134f92a.
|
|
BSPrimLinkable""
Found that the vehicle movement problem was not caused by these physics changes.
This reverts commit c45659863d8821a48a32e5b687c7b2a6d90b0300.
|
|
on both""
Found that the vehicle movement problem was not caused by these physics changes.
This reverts commit 89857378ce79f93a265bc1eb151e17742032abfa.
|
|
Found that the vehicle movement problem was not caused by these physics changes.
This reverts commit 44543ebe638f391fc1c7ff532fe4470006dec55a.
|
|
well as the average.
This is somewhat cryptic at the moment, need to improve documentation.
|
|
|
|
waiting to be processed at the second stage (after initial UDP processing)
If this consistently increases then this is a problem since it means the simulator is receiving more requests than it can distribute to other parts of the code.
|
|
packets sent by a region per second
|
|
|
|
taking on the initial processing of a UDP packet.
If we're not receiving packets with multiple threads (m_asyncPacketHandling) then this is critical since it will limit the number of incoming UDP requests that the region can handle and affects packet loss.
If m_asyncPacketHandling then this is less critical though a long process will increase the scope for threads to race.
This is an experimental stat which may be changed.
|
|
AgentUpdate packet. This fixes the problem with vehicles not moving forward
after the first up-arrow.
Code to fix a potential exception when using different IClientAPIs.
|
|
The changes don't seem to be ready for prime time.
This reverts commit 803632f8f32d91bb4aec678d8b45a8430c2703e1.
|
|
The changes don't seem to be ready for prime time.
This reverts commit 13a4a80b3893af13ab748c177b731fed813974ca.
|
|
The changes don't seem to be ready for prime time.
This reverts commit b4c3a791aa55390bff071b3fe4bbe70c1d252703.
|
|
The changes don't seem to be ready for prime time.
This reverts commit acb7b4a09ad564d1dfae3ad12adbb593ca3942c9.
|
|
The changes don't seem to be ready for prime time.
This reverts commit d0d654e2186c8b81c1150da89a549e4f7162a2b4.
|
|
The changes don't seem to be ready for prime time.
This reverts commit b44f0e1a00eba7f76401692322e48a3b23a81164.
|
|
whole linkset.
Override physical property setting for BSLinksetCompound as there are
not children to the compound spape.
|
|
and start changing the logic to handle the base prim as a complex
object (ie, a linkset).
|
|
|
|
into the linkset implementation classes.
Add HasSomeCollision attribute that remembers of any component of
a linkset has a collision.
Update vehicle code (BSDynamic) to use the HasSomeCollision in place of
IsColliding to make constraint based linksets properly notice the ground.
Add linkset functions to change physical attributes of all the members
of a linkset.
|
|
PhysicsScene and PhysicsActor.
|
|
|
|
|
|
|
|
|
|
|
|
the equation. (head rotation was the problematic one)
|
|
lkalif for telling me how to route the information. The viewer effect is under the distance filter, so only avatars with cameras < 10m away see the beams.
|
|
is generating the effect and the cameras of the observers. In particular, this applies to LookAt (which is really verbose and occurs every time users move the mouse) and Beam (which doesn't occur that often, but that can be extremely noisy (10.sec) when it happens)
|
|
|
|
- The existing event to scene has been split into 2: OnAgentUpdate and OnAgentCameraUpdate, to better reflect the two types of updates that the viewer sends. We can run one without the other, which is what happens when the avie is still but the user is camming around
- Added thresholds (as opposed to equality) to determine whether the update is significant or not. I thin these thresholds are ok, but we can play with them later
- Ignore updates of HeadRotation, which were problematic and aren't being used up stream
|
|
observations about AgentUpdates.
|
|
|
|
need to dequeue and enqueue items every 1sec.
|
|
|
|
|
|
significant much earlier in UDP processing (i.e. before we pointlessly place such packets on internal queues, etc.)
Appears to have some impact on cpu but needs testing.
|
|
to "show client stats" (i.e. sent on for further processing instead of being discarded)
Added here since it was the most convenient place
Number is in the last column, "Sig. AgentUpdates" along with percentage of all AgentUpdates
Percentage largely falls over time, most cpu for processing AgentUpdates may be in UDP processing as turning this off even earlier (with "debug lludp toggle agentupdate" results in a big cpu fall
Also tidies up display.
|
|
AgentUpdate in packets to be discarded at a very early stage.
Enabling this will stop anybody from moving on a sim, though all other updates should be unaffected.
Appears to make some cpu difference on very basic testing with a static standing avatar (though not all that much).
Need to see the results with much higher av numbers.
|
|
threads are started/stopped
|
|
stop out" from actually doing anything
|
|
these requests actively on the processing queue if it seems they're not ready.
|
|
always performing these on a separate fired thread.
This appears to improve cpu usage since launching a new thread is more expensive than performing a small amount of inline logic.
However, needs testing at scale.
|
|
|
|
move around when standing on a stationary object.
Create proper linkage between BSCharacter and its actor by generating
a UpdatedProperties event the same way BSPrim does.
|
