|
|
|
[
Permlink
| « Hide
]
Vektor Linden added a comment - 05/Aug/08 12:56 AM
I haven't yet had a chance to test this myself, but saw the TD drop while in the region as they tested it. I will look into this on Tuesday.
Add this MONO-script to a box, name it "rezzed object":
default } Make another box, add "rezzed object" and also add this script (MONO or LSL): default timer() { llRezObject("rezzed object", llGetPos() + <0, 0, 1>, ZERO_VECTOR, ZERO_ROTATION, 0); }} This will slow a 1.24.0.93754 sim down to a dilation of 0.83 Not always though, we're still searching. A fix has been checked in, pushed to aditi, and confirmed.
Si Linden notes that the majority of Mono rezzes will happen slightly faster than LSL, however there is still considerable room for improvement. Babbage will look into this himself upon his return. This issues is no longer a blocker, so resolving. We're very happy to have found a way to 100% cure an affected sim:
-Rez a box default -Set the script to not running. ======= Amazing, isn't it? Please provide a description of what this is supposed to do.
To confirm Moon's observations:
Previously observed: Rezzing objects containing mono scripts can still cause a significant drop in time dilation. Also Observed: The presence of particular avatars seems to solve the time dilation issues. If there is a NON-running, Mono script in the region (attached to an avatar, or in a rezzed object), the lag disappears. I'm aware this sounds crazy, and can't explain why it works, but it is 100% reproducable. I have seen the subject of the preceding few comments in action.
While running our Mono-scripted-object rezzers, and lagging the region's time dilation, toggling off the script above (or any Mono compiled script), returns the region's time dilation to normal. I agree that this sounds odd, but I showed babbage this behavior firsthand. As long as one Mono compiled script in the region is set to 'not running', the region's time dilation seems to behave itself. Setting the script to running will dip the region's time dilation once again. Past the second of the 3 stages of the rollout to the main grid and I hate to say this, but.. This doesn't seem to be fixed after all
I'm testing this in a live environment (Sandbox Cordova) with many other people in the region, but I do firmly believe it is my interceptors that caused the lag I observed. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||