stride3d / stride3d/stride

Processing large convex hulls causes error code -300

Open
#318 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-Asset area-Build area-Physics bug
Dominant language
C#
Stars
7.8k
Forks
1.2k
Avg merge
2d 17h
Merged PRs (30d)
49

Description

Release Type: Official Release/GitHub (please choose appropriate option)
Official Release

Version: Version number and/or git branch
3.0.0.6

Platform(s): Does the problem occur on Windows, Android...?
Windows

Describe the bug
A clear and concise description of what the bug is.
The build fails with error code -300.

To Reproduce
Steps to reproduce the behavior:

  1. import a large complex mesh
  2. add a static collider to the mesh
  3. create a new convex hull collision shape from the model
  4. add the convex hull to the static collider
  5. try to build

Expected behavior
A clear and concise description of what you expected to happen.
The build should have gone through, without failing.

Screenshots
If applicable, add screenshots to help explain your problem (use GitHub drag & drop)
tmpshot

Log and callstacks
If any, please attach here any log or callstack (preferably in a .txt file using GitHub drag and drop)
TMPtxt.txt

Additional context
Add any other context about the problem here.

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 reviewing the attached TMPtxt.txt log and reproducing the five listed steps on Windows with Stride 3.0.0.6. Trace the convex-hull collision build path to determine why the large mesh produces error -300; done means the convex hull builds successfully without that error.

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.