stride3d / stride3d/stride

InstancingComponent: InstancingUserArray does work when using object initializer syntax

Open
#1,945 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

Version: 4.1.0.1948

Platform(s): Windows

Describe the bug
When using object initializer syntax or just setting the Matrices property the instances are not displayed.

To Reproduce
Steps to reproduce the behavior:

  1. Create an entity
  2. Add a ModelComponent
  3. Add a InstancingComponent and use the object initializer to set it up
  4. OR Use the setter of Matrices to update them

Expected behavior
The instances are displayed/updated correctly

Additional context
Imho the setter of matrices should either be private or we could just call the UpdateMatrices method from the setter (prefferred)

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 with InstancingComponent and trace how object initializer assignment and the Matrices setter differ from the normal update path. Reproduce both reported cases, then verify that instances are displayed and updated correctly after the fix.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
computer-graphics, game-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.