stride3d / stride3d/stride

Collision size is affected by the parent object scale

Open
#3,024 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
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:

  1. Create an entity (prefab)
  2. Add a collision body (any kind of body from Bepu and Bullet)
  3. Scale the parent entity
  4. Reload the project
  5. 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)):
Image
After value is updated and changed back to the original value (correct size)
Image

Size of the collision on the scene after a prefab is added
Image
Collision size on the prefab
Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.