Collision size is affected by the parent object scale
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 7.8k
- Forks
- 1.2k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 49
Description
Version: Stride 4.3.0.2507
Platform(s): Windows
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
- Create an entity (prefab)
- Add a collision body (any kind of body from Bepu and Bullet)
- Scale the parent entity
- Reload the project
- Collision object is resized with the scale of the parent (it goes back to normal after changing a value and changing it back)
Expected behavior
I expect a consistent behavior. Collision shapes should either be always scaled with the object or should never be scaled with it and stay that way.
Screenshots
Before I update the value (scaled by 5 as the parent object's scale is (5,5,5)):

After value is updated and changed back to the original value (correct size)

Size of the collision on the scene after a prefab is added
Collision size on the prefab
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce this in Stride 4.3.0.2507 on Windows with an entity prefab, a Bepu or Bullet collision body, and a parent scale of (5,5,5), then reload the project. Compare the collision size before and after changing a value and changing it back; done means the collision shape has consistent scaling behavior after reload.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100