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

Make CSG shape dirty after changing Snap #93242

Merged
merged 1 commit into from
Jun 17, 2024

Conversation

31
Copy link
Contributor

@31 31 commented Jun 16, 2024

@31 31 requested a review from a team as a code owner June 16, 2024 21:12
@smix8 smix8 added this to the 4.x milestone Jun 16, 2024
@Calinou
Copy link
Member

Calinou commented Jun 16, 2024

So that's why I thought changing Snap didn't have any effect…

Thanks for fixing this after so long 🙂

Copy link
Member

@Calinou Calinou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested locally, it works as expected.

csg_snap.mp4

While we're at it, I'd change CSGShape3D's snap documentation to mention that only the top-level CSG node' Snap property is taken into account. Child nodes' value is ignored for snapping vertices of the final (combined) CSG shape.

modules/csg/csg_shape.cpp Outdated Show resolved Hide resolved
Update doc to mention that Snap only takes effect at the top level.

Co-authored-by: Hugo Locurcio <[email protected]>
@akien-mga akien-mga modified the milestones: 4.x, 4.3 Jun 17, 2024
@akien-mga akien-mga merged commit 8c70c18 into godotengine:master Jun 17, 2024
16 checks passed
@akien-mga
Copy link
Member

Thanks!

@31 31 deleted the dev/31/csg-snap-dirty branch June 18, 2024 03:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Changing CSG node Snap doesn't regenerate mesh
5 participants