Skip to content

feat: add vertex color preset system across all tools - #1

Merged
seto3d merged 1 commit into
seto3d:mainfrom
cs-dev-09:vertex-color-presets
Aug 12, 2026
Merged

feat: add vertex color preset system across all tools#1
seto3d merged 1 commit into
seto3d:mainfrom
cs-dev-09:vertex-color-presets

Conversation

@cs-dev-09

Copy link
Copy Markdown
Contributor

Description
This PR replaces the hardcoded (0.0, 0.7, 0.0) default vertex color with a customizable Color Preset system for all tools (Fake AO, Fake Damage, Edge Dirt, Smooth Edge, Decal Tool, and Surface Painter).

Why This is Needed
Manually changing Vertex colors in Vertex Paint mode often destroyed the alpha channel unless users specifically remembered to uncheck "Affect Alpha" in their settings. This PR automates color selection directly in the UI, keeping alpha channels perfectly safe.

Changes Made

  • Added COLOR_PRESETS to shared/vertex_color.py (Green, Red, White, Blue, Yellow, Custom).
  • Added a new "Vertex Colour" dropdown UI to all tool panels.
  • Updated creation operators and live-rebuild functions to apply the chosen RGB values.

Important Note
The core alpha channel calculations, geometry generation, and Sollumz integrations remain completely unaffected. This simply allows users to pick different RGB values for their BYTE_COLOR attributes instead of being locked to green!

- Replaced the hardcoded (0.0, 0.7, 0.0) default vertex color with a customizable Color Preset system.
- Added a new "Vertex Colour" UI dropdown to all 6 tools (Fake AO, Fake Damage, Edge Dirt, Smooth Edge, Decal Tool, Surface Painter).
- Users can now easily select from Green, Red, White, Blue, Yellow, or use a Custom RGB swatch.
- The core alpha channel calculations, geometry generation and Sollumz integrations remain completely unaffected.
@seto3d
seto3d merged commit 2dd36bd into seto3d:main Aug 12, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants