Skip to content

Fix incorrect claim about visibility range #11511

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
skyace65 merged 1 commit into from
Dec 7, 2025
+2 −2
Merged

Fix incorrect claim about visibility range #11511

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions tutorials/3d/visibility_ranges.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,12 +82,12 @@ In the inspector of any node that inherits from GeometryInstance3D, you can adju
the following properties in the GeometryInstance3D's **Visibility Range** section:

- **Begin:** The instance will be hidden when the camera is closer to the
instance's *origin* than this value (in 3D units).
*center of the instance's AABB* (axis-aligned bounding box) than this value (in 3D units).
- **Begin Margin:** The hysteresis or alpha fade transition distance to use for
the close-up transition (in 3D units). The behavior of this property depends
on **Fade Mode**.
- **End:** The instance will be hidden when the camera is further away from the
instance's *origin* than this value (in 3D units).
*center of the instance's AABB* than this value (in 3D units).
- **End Margin:** The hysteresis or alpha fade transition distance to use for
the far-away transition (in 3D units). The behavior of this property depends
on **Fade Mode**.
Expand Down