secondlife / secondlife/viewer

DisableLookAtAnimation debug setting clarification

Open
#4,058 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

backlog enhancement stale
Dominant language
C++
Stars
299
Forks
146
Avg merge
1d 9h
Merged PRs (30d)
88

Description

Not necessarily a bug as it's likely working as "intended", but I suspect this feature might do more harm than is ideal currently. The original request for this feature was meant for those who essentially wish to opt-out of the client driving the LookAt animations for their avatar, but in its current state, residents may consider using this feature for one of the following reasons that it is not intended for.

DisableLookAtAnimation:

  • Turns off all LookAt animations locally, including those of other avatars who may actually want to use LookAt for its intended use (looking at things)

DisableLookAtAnimation does NOT:

  • Hide LookAt animations when viewed by others

  • Prevent LookAt from being broadcast

This is fine for debugging purposes, but for those meaning to use it to disable LookAt animations for their avatar permanently (including when perceived by others) it's not ideal. It also "breaks" the LookAt feature for others entirely who do intend to use it for its intended use.

https://secondlife.canny.io/admin/board/bug-reports/p/disablelookatanimation-essentially-breaks-the-lookat-feature

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.

Research direction

No file or test is named. Start by tracing the DisableLookAtAnimation setting through local LookAt animation handling and broadcast behavior, then determine the intended distinction between disabling local playback and preventing an avatar's LookAt from affecting others. Done should include clarified behavior and coverage for the affected cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.