| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
from collisions before removing the collision callbacks.
Should not make operational differences.
|
|
|
|
| |
Signed-off-by: Melanie Thielker <melanie@t-data.com>
|
|
|
|
| |
protected against nullrefs
|
|
|
|
|
|
|
|
| |
than Data""
Needed after all
This reverts commit 26094c21feb8f63d7e6ed46ec2668f213d9dc623.
|
| |
|
|
|
|
|
|
| |
My bad!
This reverts commit 20326e1947f56c6c39a9e701859c286ebee062e0.
|
|
|
|
| |
Signed-off-by: Melanie Thielker <melanie@t-data.com>
|
| |
|
|\ |
|
| | |
|
|/ |
|
|
|
|
| |
the llSetPrimitiveParams family of functions adversely. Please test!
|
|
|
|
|
| |
This isn't supposed to be done and should be changed in the tests.
For now, add a protective check.
|
|
|
|
| |
as is done when adding another list.
|
|
|
|
|
| |
specific additions that should not have been there in the first place.
Sleeping and time measurement are now completely internal to XEngine
|
|
|
|
|
|
|
| |
The approach is good but the way it is written breaks the architecture.
Rewrite follows.
This reverts commit a568f06b7faea807149205d0e47454e4883e4836.
|
|\ |
|
| | |
|
| |
| |
| |
| | |
Signed-off-by: Diva Canto <diva@metaverseink.com>
|
|/
|
|
|
|
| |
Console command debug xengine now turns that on.
Also, per orenh, remove the triggers at 1000 and 10000 as they are not
useful now that top scripts works.
|
| |
|
|\ |
|
| |
| |
| |
| |
| | |
one of the existing module interfaces to denote a module that holds
agent specific state that should be transferred to other regions
|
|/
|
|
| |
we don't want to ignore case. And this seems to be causing problems in mono 4.3.
|
|
|
|
|
|
| |
RequestObjectPropertiesFamily reply and not the actual ObjectProperties packet
Signed-off-by: Melanie Thielker <melanie@t-data.com>
|
|
|
|
| |
Signed-off-by: Melanie Thielker <melanie@t-data.com>
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Diva Canto <diva@metaverseink.com>
|
|
|
|
|
|
| |
Previously the script state was never saved for a !Running script, so upon region restart the script would be Running again.
The use of the 'StayStopped' flag is needed because all scripts are automatically stopped when the region shuts down, but in that case we shouldn't save in their state that they're !Running.
|
|
|
|
| |
Sleeping doesn't use the CPU.
|
|
|
|
| |
The value shown is the number of milliseconds per frame that were spent executing scripts in this region.
|
|
|
|
|
|
| |
handling it in XEngine
Previously the "Net Time" was reported: only the time actually spent in the script's code. This is not a correct indication of how much load the script places on the simulator, because scripts that change state often or have many events use up a lot of time just in the event handlers, and previously this time wasn't counted.
|
|
|
|
|
|
|
|
| |
last 30 seconds. Use a sliding window to calculate this.
Notes:
- This metric provides a better indication of which scripts are taking up a lot of CPU (and therefore should be optimized).
- Previously the execution time was reset to 0 in every new measurement period, causing the reported time to fluctuate for no reason. This has been fixed by using a sliding window.
|
|
|
|
|
|
| |
1. Use a Stopwatch (a high-resolution timer)
2. Whenever we start a new measurement period, zero out the total execution time (previously it just kept accumulating)
3. Changed the measurement period from 30 minutes to 30 seconds. This is much more useful in the "Top Scripts" dialog, as it shows currently active scripts
|
|
|
|
| |
(milliseconds) and TimeSpan.TicksPerXXX (10000 x milliseconds)
|
|
|
|
| |
of a problem
|
|
|
|
| |
show the current log level; not crash
|
|
|
|
|
|
|
|
| |
logging
If the XML was truncated for some reason then ExecuteReadProcessors() would get into an infinite loop, using high CPU. Now it detects EOF (and several other error cases) and aborts.
The rest of the changes just improve logging of XML in case of errors, so that we can see what the bad XML is.
|
| |
|
|
|
|
|
|
|
|
| |
of race conditions and, especially, race conditions when an object is
removed and quickly re-added to a scene.
This hopefully reduces the occurance of problems when avatars TP within
a region -- the main problem being the loss of collisions.
|
|
|
|
|
|
|
| |
when Dispose() is called. This reduces chance of object leakage when
destroying objects.
Rearrange initialization and shut down of BSActorLockAxis so it is
consistant with other actors.
|
|
|
|
|
|
|
| |
inventory folders. The newest version of libomv itself is committed here. Basically, everything that was using the AssetType enum has been combed through; many of those uses were changed to the new FolderType enum.
This means that from now on, [new] root folders have code 8 (FolderType.Root), as the viewers expect, as opposed to 9, which was what we had been doing. Normal folders are as they were, -1. Also now sending folder code 100 for Suitcase folders to viewers, with no filter.
All tests pass, but fingers crossed!
|
|
|
|
| |
Another change: removed the second call to userManager.AddUser(). UserManagementModule won't modify an existing record.
|
| |
|
|
|
|
|
|
|
|
| |
initialization race conditions reported in Mantis 6792.
When a region is initializing it seems that the prim initialization code
can be interrupted part way through then taints are processed for
prims that are not completely there.
|
|
|
|
| |
Signed-off-by: Melanie Thielker <melanie@t-data.com>
|
|
|
|
| |
Signed-off-by: Melanie Thielker <melanie@t-data.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Off by default but set with [Startup]ShouldUseFireAndForgetForCollsions=true
There is a problem with physics colliions sometimes stopping. One suspicion
is that the long callback path from the physics engine into the script engine
is causing problems. Enabling this feature passes the collision into the
script engine on a separate thread and not the main simulation thread.
Tester can enable this and see if the collsions stay around. If they still
fail, this commit should be reverted and another solution looked for.
|