Experience-authorised camera distance limits that apply during Alt-camming
Eksynn Jules
I'm developing a region system with zone-based camera restrictions, and I'd like an Experience-authorised way to enforce a maximum camera-to-avatar distance.
In my testing, ordinary scripted camera control can be bypassed by Alt-camming. A preferred camera distance isn't the same as an enforced maximum. At present, achieving the latter appears to require RLV/RLVa and a supporting viewer.
Could we have a native camera-distance restriction that continues to apply during Alt-click, orbit, pan, and zoom, without requiring RLV?
Ideally:
- Requires explicit permission, with support for accepted Experiences.
- Allows a script to set and release a maximum distance in metres.
- Supports zone-based use, with scripts updating the limit as residents move.
- Reports whether the restriction was accepted and is supported.
- Automatically releases on Experience withdrawal, leaving its permitted area, or controller failure through an expiring lease.
- Handles restrictions from multiple controllers without one script clearing another's settings.
This would be useful for games, exploration, confined spaces, and optional privacy-related zone rules. It should remain clear to residents which Experience is controlling their camera and how to leave it.
I'm happy to discuss the design and help develop/test the viewer-side implementation.
Log In
AlettaMondragon Resident
"
This would be useful for games, exploration, confined spaces, and optional privacy-related zone rules.
"Games yes, limiting whatever you want on your own land, sure, but why would this be ever useful for exploration? "Disable camera constraints" was literally the first setting I ever changed in my viewer and it's on ever since. The whole point of exploration is to see things, why would you want to limit your camera distance while doing so.
Also the current experience permission system is a joke, some of us just block any experience if it wants us to accept it, because we have no way to tell what it might be able to do to us, what objects in what regions use the experience and who owns the participating objects, parcels and regions. That is what needs work the most, and to give us the option to only allow select permissions to an experience, not everything at once. Without this, experiences are a joke.