KhronosGroup / KhronosGroup/UnityGLTF
Shaders don't mark any exposed properties as "Main Color"
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 536
- PR merge metrics
- No merged PRs in 30d
Description

This breaks any code that uses "someMaterial.color" without checking and forces implementation of code paths specifically for UnityGLTF materials.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the UnityGLTF shader files and inspecting how exposed color properties are declared and identified by Unity. Reproduce the issue with a Unity material, then verify that the relevant shader properties are recognized as the material's Main Color and that material.color works without a special code path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, unity
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100