Skip to content
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.

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

Clip plane feature #63

Open
progschj opened this issue Mar 13, 2023 · 0 comments
Open

Clip plane feature #63

progschj opened this issue Mar 13, 2023 · 0 comments

Comments

@progschj
Copy link
Collaborator

progschj commented Mar 13, 2023

Somewhat related to #57 we should probably consider standardizing a way to define clip planes eventually.

Name Type Description
clipPlanes ARRAY1D of FLOAT32_VEC4 Each VEC4 (A, B, C, D) defines a clip equation Ax + By + C*z + D = 0. Elements where the left side is positive are visible while elements on the negative side are clipped.

Additionally the device or renderer would have an integer property "maxClipPlanes" in case there is a limit.

Since both scene level clipping and object level clipping can make sense this parameter could exist almost anywhere in the scene hierarchy as well as on the renderer. These could either be separate features KHR_RENDERER_CLIP_PLANES, KHR_SURFACE_CLIP_PLANES etc. or some a priori definition that they exist on say the world, surface and volume?

@jeffamstutz jeffamstutz added the v1.1 Issues to be decided on for the v1.1 specification label Apr 26, 2023
@jeffamstutz jeffamstutz added discussion-backlog and removed v1.1 Issues to be decided on for the v1.1 specification labels Oct 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants