stride3d / stride3d/stride

Velocity Buffer are broken on Instancing and Bepu Entities

Open
#2,918 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

Release Type: Official Release-Latest

Version: 4.2.1.2442 and MainBranch

Platform(s): All Platform

Describe the bug
Velocity Buffer value from instancing meshes and bepu entities are broken. Bepu Entities doesn't even write velocity buffer

https://github.com/user-attachments/assets/9035aa47-27d4-4822-9886-1b9c3640f292

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

Start by reproducing the velocity-buffer issue described for instancing meshes and Bepu Entities on the listed versions and platforms. Compare the buffer value for instanced meshes and verify whether Bepu Entities writes any velocity data. Done means both cases produce correct velocity-buffer output.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
computer-graphics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.