secondlife / secondlife/viewer
Viewer that normally defaults to Low+ quality & speed sometimes defaults to High.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 299
- Forks
- 146
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 88
Description
Environment
Mac
511
Description
Viewer that normally defaults to Low+ quality & speed sometimes defaults to High.
Reproduction steps
- On a Mac M1, with this viewer installed - https://releasenotes.secondlife.com/viewer/7.2.2.17774206511.html
- TBD (I think there is some start condition that we have not discovered yet)
- Set the viewer to Rosetta mode (this step may not be necessary, but that's how it was set this time)
- Start the viewer, stay at the login screen.
- Open Preferences > Graphics
- Click the Reset to recommended settings button.
Observed: Move of the time, quality & speed slider goes to Low+. Occasionally the quality & speed slider goes to High.
Expected: It should always default to the same thing on a particular machine.
Log of it defaulting to High : SecondLife.log
On another run it defaulted to Mid: Mid SecondLife.log
Adding a log when it defaulted to Low+ which is expected: Low+ (expected) SecondLife.log
This repo is using Opire - what does it mean? 👇
💵 Everyone can add rewards for this issue commenting
/reward 100 (replace 100 with the amount).🕵️♂️ If someone starts working on this issue to earn the rewards, they can comment
/try to let everyone know!🙌 And when they open the PR, they can comment
/claim #4749 either in the PR description or in a PR's comment.🪙 Also, everyone can tip any user commenting
/tip 20 @Dan-Linden (replace 20 with the amount, and @Dan-Linden with the user to tip).📖 If you want to learn more, check out our documentation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue on a Mac M1 using the listed viewer build, Rosetta mode, and the Graphics preferences reset action. Compare the attached High, Mid, and Low+ SecondLife.log files to identify why the same machine receives different recommendations; done means repeated resets produce the expected consistent quality and speed setting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100