Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0007728opensim[REGION] Script Functionspublic2015-09-28 08:572016-03-07 07:49
Assigned To 
PlatformMono-Linux x64OSUbuntuOS Version14.04 LTS
Product Versionmaster (dev code) 
Target VersionFixed in Version 
Summary0007728: Region prim count reported by the viewer is different than the one reported by osGetRegionStats
DescriptionI've made a simple Simulator statistics object that parses the return of osGetRegionStart, currently at ArcadiaShop it reports 6220 prims (prims, mesh, linden grass).
However In the About Land window of my Firestorm it reports 5135.

Tested with different viewers in regular and VAR regions. The more prims the more difference on the count.
Steps To ReproduceIn a sim populated with enough prims:

Rez a cube, add this script:

    touch_start(integer nya)
        list info = osGetRegionStats();
        llSay (0, "Prim count: " + (string) llList2Integer(info, STATS_TOTAL_PRIMS));

Click on it to get the function's prim count.

Then go to World->About Land, Tab Objects and press the refresh button to get a counter from the viewer.

Notice the difference.
Additional InformationThe more prims the region has, the more noticeable is the difference.
TagsNo tags attached.
Git Revision or version numberOSgrid (Dev) 0f6c3fb: 2015-09-14 git hash : 0f6c3fb24265b8e63815e50e4b62c73a4cee31ac
Run Mode Standalone (Multiple Regions)
Physics EngineBulletSim
Script Engine
EnvironmentMono / Linux64
Mono VersionOther
ViewerFirestorm 4.7.3 (47323)
Attached Files

- Relationships

-  Notes
Bob Wellman (reporter)
2016-03-07 07:40

I have tested this on my own grid. The about land correctly shows 6335 as the total prims in the region. However osGetRegionStart reports 6515 which is 180 prims more. I am wearing prim attachments totalling 180 prims.

So it appears that the osGetRegionStart figure includes all prims (even worn ones).

Bringing in a second avatar wearing 182 prims and running the script again caused osGetRegionStart to report 6657 which is 182 more than before. Confirming my theory.

It would be useful if osGetRegionStart could report worn and not worn prims as separate figures.

- Issue History
Date Modified Username Field Change
2015-09-28 08:57 Aaack New Issue
2016-03-07 07:40 Bob Wellman Note Added: 0030073
2016-03-07 07:49 Bob Wellman Status new => confirmed

Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker