diff options
| author | Beq Janus <beqjanus@gmail.com> | 2024-08-08 17:10:03 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-08-08 19:10:03 +0300 |
| commit | fe0f1be17bfd83323f2fcda124f3327cc14b0cad (patch) | |
| tree | 2359eb64cd644dc47024ab05eebcc4fe7c7ea1cb /indra/newview/app_settings | |
| parent | 77d50cad495511a91ca1461d9e6f43a7e8656965 (diff) | |
Auto-scaling amortisation of dynamic BB calcs (#2226)
* Auto-scaling amortisation of dynamic BB calcs
This fix limits the overhead of the dynamic BB calcs to
AvatarExtentRefreshMaxPerBatch per AvatarExtentRefreshPeriodBatch frames
default is 5 avatar per 4 frames. Thus a standard busy region 25 avatars would
take 20 frames to refresh the BBs.
* Add comments to give context to the amortised BB recalcs
explain the frequency of updates given the number of avatars present as to how that limits the impact on frame rate in busy scenes
Diffstat (limited to 'indra/newview/app_settings')
| -rw-r--r-- | indra/newview/app_settings/settings.xml | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/indra/newview/app_settings/settings.xml b/indra/newview/app_settings/settings.xml index eb053ebaa0..887a8584d8 100644 --- a/indra/newview/app_settings/settings.xml +++ b/indra/newview/app_settings/settings.xml @@ -1874,6 +1874,28 @@ <key>Value</key> <real>64.0</real> </map> + <key>AvatarExtentRefreshPeriodBatch</key> + <map> + <key>Comment</key> + <string>how many frames do we spread over by default when refreshing extents (default is 4)</string> + <key>Persist</key> + <integer>1</integer> + <key>Type</key> + <string>S32</string> + <key>Value</key> + <integer>4</integer> + </map> + <key>AvatarExtentRefreshMaxPerBatch</key> + <map> + <key>Comment</key> + <string>how many avatars do we want to handle in total per batch (default is 5)</string> + <key>Persist</key> + <integer>1</integer> + <key>Type</key> + <string>S32</string> + <key>Value</key> + <integer>5</integer> + </map> <key>DebugAvatarAppearanceMessage</key> <map> <key>Comment</key> |