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

UI to change road collision layers #203

Open
TheDuckCow opened this issue Dec 5, 2024 · 0 comments
Open

UI to change road collision layers #203

TheDuckCow opened this issue Dec 5, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@TheDuckCow
Copy link
Owner

Right now, the collisions are set up automatically in the same way that collisions are auto-generated using the automatic static mesh mechanism in the UI. However, it's clearly useful to be able to manage which layers are used.

The feature request here would be some setting to specify how and where these collisions are set up. One choice to be made is whether this is a per- RoadContainer setting, or if this is something that can just live on the RoadManager itself. In my mind, the RoadManager makes the most sense as you probably would just want to assign it in one place. It opens a question for what to do with prefab scenes though, the RoadManager might have to do some extra work on scene-spawning (if "save children" is off anyhow).

Short term workaround

You can also manually ensure the right collision layers are used today with a custom script. Just subscribe to each of your RoadContainer's on_road_updated signal which will be called anything a RoadSegment is created/updated. The body of this signal is a list of RoadSegments, from which you can get to each RoadSegment's individual collision mesh/static body where you can manually specify the collision shapes.

@TheDuckCow TheDuckCow added the enhancement New feature or request label Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant