stride3d / stride3d/stride

Tracking issue for mikktspace tangent generation

Open
#1,534 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Assimp does not use mikktspace tangent generation algorithm which is recommended by khronos for gltf.

assimp/assimp#2363

More details on the linked issue as of why it's recommended

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 reading assimp/assimp#2363, which contains the referenced details about Khronos's recommendation for mikktspace tangent generation. Determine the affected Stride asset or rendering entry points and define the integration scope; done means Stride uses the recommended algorithm for glTF tangent generation.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
computer-graphics, game-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.