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

Fix the default layers used by ColliderConstructorHierarchy #649

Merged
merged 1 commit into from
Feb 5, 2025

Conversation

Jondolf
Copy link
Owner

@Jondolf Jondolf commented Feb 5, 2025

Objective

#476 changed CollisionLayers to use one membership (the first layer) and all filters by default. However, ColliderConstructorHierarchy is still using the old default!

Solution

Use CollisionLayers::default() (one membership, all filters) by default for ColliderConstructorHierarchy.


Migration Guide

ColliderConstructorHierarchy now defaults to one membership (the first layer) and all filters for the CollisionLayers of generated colliders. This is consistent with how CollisionLayers already works normally.

@Jondolf Jondolf added C-Bug Something isn't working A-Collision Relates to the broad phase, narrow phase, colliders, or other collision functionality C-Breaking-Change This change removes or changes behavior or APIs, requiring users to adapt labels Feb 5, 2025
@Jondolf Jondolf enabled auto-merge (squash) February 5, 2025 22:54
@Jondolf Jondolf merged commit c1f9722 into main Feb 5, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Collision Relates to the broad phase, narrow phase, colliders, or other collision functionality C-Breaking-Change This change removes or changes behavior or APIs, requiring users to adapt C-Bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant