secondlife / secondlife/viewer
LookAt does not follow dragging physical objects while Limit setting is enabled
Open
Nobody has claimed this yet.
bug
team:viewer
- Dominant language
- C++
- Stars
- 299
- Forks
- 146
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 88
Description
Environment
Second Life Release 7.2.1.16890813157 (2025.06)
Description
The look at target does not follow a physical object being dragged while "Limit LookAt Distance" is enabled.
https://gyazo.com/3ec850cea2c6476c85f2af713c54ce20
Reproduction steps
- Enable Develop>Avatar>Show Look At. (This is for easier visual verification.)
- Check "Enable LookAt" and "Limit LookAt Distance" settings in Preferences>Privacy.
- Rez an object and set it to Physical
- Drag the object around and observe the LookAt target
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 #4545 either in the PR description or in a PR's comment.🪙 Also, everyone can tip any user commenting
/tip 20 @AtlasLinden (replace 20 with the amount, and @AtlasLinden 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
No source file, test, or entry point is named. Reproduce the issue using the listed Second Life settings with a physical object, then trace the LookAt behavior while dragging and with distance limiting enabled. Done means the visible LookAt target follows the dragged physical object under those settings without regressing the limit behavior.
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