secondlife / secondlife/viewer

Viewer should not lower the resolution of my avatar's textures simply because I zoomed out

Open
#6,068 2 comments 0 reactions 1 assignee View on GitHub

@marchcat is already working on this.

Since Aug 5, 2026.

  • #6091 by @marchcat — closed without merging
enhancement stale
Dominant language
C++
Stars
299
Forks
146
Avg merge
1d 9h
Merged PRs (30d)
88

Description

When I zoom out far from my own avatar at a club or other texture-heavy areas, say to simply look around, when I return the camera to my own avatar a lot of the textures on my avatar - including materials - are lowered drastically in resolution and it takes the viewer upwards of 20-30 seconds before they go back to full. A resident's own avatar should never have the textures lowered in resolution unless it's specifically set in graphics > advanced, and should always take priority in staying at max quality according to graphics settings.

  1. Go to a club that is avatar heavy, so lots of textures are around - shopping events will probably work here too

  2. Wait for the viewer to load everything it can do - draw distance was 128 with textures at 2k maximum for this

  3. When your own avatar has loaded fully, alt+cam onto yourself and zoom out about half way to the clip plane - just looking around the area for a few seconds will work here too

  4. Return the camera to your avatar

  5. Lots of your avatar's textures, excluding BoM, are now super blurry, and will take ages to load back again

Image 1 shows how my avatar is supposed to look > image 2 is how far I zoomed out (just across the room at this club) > image 3 shows how blurry my avatar's textures become after zooming back in, which stay like this for 20-30 seconds.

https://secondlife.canny.io/admin/feedback/bug-reports/p/viewer-should-not-lower-the-resolution-of-my-avatars-textures-simply-because-i-z

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.