Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0007782opensim[REGION] Script Functionspublic2015-12-17 00:322015-12-17 02:07
Reporteralecia ashbourne 
Assigned To 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0007782: Script time reporting error
DescriptionThere seems to be an error with region debug / top scripts reporting, by 3 decimal points.

Error reporting in both latest release Singularity and Firestorm, so I'm guessing this is the simulator Please see attached Image.

test script is as follows:

llOwnerSay(llGetObjectName()+" Script Time: "+llList2String(llGetObjectDetails(llGetKey(), [OBJECT_SCRIPT_TIME]), 0));

Top scripts region debug shows 33.000 for this object - whereas script time 'script' reports 0.033, which I know from experience is correct.

I'm guessing that this metric is still reporting in ms ? So I expect its simply a case of shifting the decimal point sim side to make it report correctly.
Steps To ReproduceOpen region debug, select top scripts.
Additional InformationAttached image shows; debug top scripts window with - 33.000 for this object - whereas script time 'script' reports 0.033
TagsNo tags attached.
Git Revision or version numberOpenSim Dev / OSgrid (Dev) 7d8b783: 2015-12-05
Run Mode Grid (Multiple Regions per Sim)
Physics EngineBulletSim
Script Engine
EnvironmentMono / Linux64
Mono VersionOther
ViewerSingularity and Firestorm
Attached Filespng file icon Snapshot___Aleciana_Engristan,_Aleciana_Engristan_(749,_630,_32.png [^] (585,030 bytes) 2015-12-17 00:32

- Relationships

-  Notes
UbitUmarov (administrator)
2015-12-17 00:38

Its just a units case. Time in seconds versus in milliseconds
Possible both cases are right, just missing the display of units
UbitUmarov (administrator)
2015-12-17 00:46

Yup, both right
llGetObjectDetails(...[OBJECT_SCRIPT_TIME]) reports time in seconds...
Top scripts in ms, a lot easier to read and saving the "0.0" display area in that case. (hopefully script times are not of the order of seconds)
alecia ashbourne (reporter)
2015-12-17 02:07
edited on: 2015-12-17 11:04

Yes, either way is fine, but e.g. this region shows a total script time in debug as '117.900 ms', so it looks a bit scary :)

- Issue History
Date Modified Username Field Change
2015-12-17 00:32 alecia ashbourne New Issue
2015-12-17 00:32 alecia ashbourne File Added: Snapshot___Aleciana_Engristan,_Aleciana_Engristan_(749,_630,_32.png
2015-12-17 00:38 UbitUmarov Note Added: 0029819
2015-12-17 00:46 UbitUmarov Note Added: 0029820
2015-12-17 02:07 alecia ashbourne Note Added: 0029821
2015-12-17 11:04 alecia ashbourne Note Edited: 0029821 View Revisions

Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker