Quickly zooming out the camera with DisableCameraConstraints can permanently break it

[Hecklezz]

Environment

Second Life Release 7.2.3.19375695301 (64bit)

Rest of environment-

Release Notes

CPU: Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (3600.01 MHz)
Memory: 16302 MB
OS Version: Microsoft Windows 10 64-bit (Build 19045.6691)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: NVIDIA GeForce RTX 2080/PCIe/SSE2

Windows Graphics Driver Version: 32.0.15.8115
OpenGL Version: 4.6.0 NVIDIA 581.15

Window size: 1920x1080
Font Size Adjustment: 96pt
UI Scaling: 1
Draw distance: 96m
Bandwidth: 10000kbit/s
LOD factor: 4
Render quality: 5
Texture memory: 8192MB
Disk cache: Max size 11468.8 MB (4.8% used)

J2C Decoder Version: KDU v8.4.1
Audio Driver Version: OpenAL, version 1.1 ALSOFT 1.24.2 / OpenAL Community / OpenAL Soft: OpenAL Soft
Dullahan: 1.24.0.202510081738
CEF: 139.0.40+g465474a+chromium-139.0.7258.139
Chromium: 139.0.7258.139
LibVLC Version: 3.0.21
Voice Server Version:

December 25 2025 10:29:55

Description

PR with possible fix: #5187

While zooming out the camera with DisableCameraConstraints enabled, sometimes if you rapidly zoom out the camera too far and too fast, it can permanently break the camera requiring a restart of the viewer. Attempting to reset the camera with Esc, or even swapping to a different region, all do not fix it.

Video Showcasing the issue:

SecondLifeViewer_2025-12-26_04-18-52.mp4

What should be expected:
There is some sort of hard maximum despite enabling DisableCameraConstraints, which should prevent this behaviour by disallowing the camera from zooming out so far that it breaks.

Reproduction steps

1. Enable DisableCameraConstraints
2. Hold Alt, click and hold somewhere and rapidly zoom out
3. Try reset the camera with Esc, if the camera stays working then repeat step 2
4. Observe the camera is now permanently bugged and can't be reset, and changing region doesn't help either

---

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 #5186 either in the PR description or in a PR's comment.

🪙 Also, everyone can tip any user commenting /tip 20 @Hecklezz (replace 20 with the amount, and @Hecklezz with the user to tip).

📖 If you want to learn more, check out our documentation.

[Dan-Linden]

I'm not able to reproduce the original bug using Second Life Release 7.2.3.19375695301 (64bit).

No rush on this, but, @Hecklezz is this issue fixed for you on 26.2.0.21655710006? https://github.com/secondlife/viewer/releases/tag/Second_Life_Release%2353fb215d-2026.02

[Hecklezz]

I just tested on the current 26.1.0.21522948608 RC build and was able to reproduce it after a few tries. Then I tested the above linked 26.2.0.21655710006 build and the issue was no longer present no matter how much I tried. So it is indeed fixed on my end in the 2026.02 release.

[Dan-Linden]

Thank you for confirming that!

Passed QA.
Verified on Second Life Release 26.2.0.21655710006 on Win11/OSX in the scope of https://github.com/secondlife/iqa/issues/606