git404hub

what is shader-core fr?

lilxyzw/shader-core — explained in plain English

Analysis updated 2026-05-18

72C#Audience · developerComplexity · 4/5Setup · hard

tl;dr

A modular shader system for Unity that lets developers write platform independent shader modules while keeping the main shader itself simple and easy to rewrite.

vibe map

mindmap
  root((shader core))
    What it does
      Modular shader system
      Platform independent modules
      Localized material editor
      Unique module IDs
    Tech stack
      C sharp
      Unity
      HLSL
    Limitations
      No new render passes
      No MaterialPropertyDrawer
      Japanese docs only
    Use cases
      Reusable shader modules
      Multi language editor
      Avoid property conflicts

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Build reusable shader modules for a Unity project that work across different render pipelines.

VIBE 2

Create a localized material editor interface using translation files for different languages.

VIBE 3

Avoid property name collisions when combining multiple shader modules in one material.

what's the stack?

C#UnityHLSL

how it stacks up fr

lilxyzw/shader-coreemrekaya567787616/cursor-ai-pro-download-2026tor-browser-download/tor-browser
Stars727171
LanguageC#C#C#
Setup difficultyhardeasyeasy
Complexity4/51/51/5
Audiencedevelopergeneralgeneral

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · hard time til it works · 1h+

Requires familiarity with Unity's shader and VisualElement editor systems, documentation is Japanese only.

No license information was found in the README.

in plain english

Shader Core is a modular shader system built for the Unity game engine. The main shader itself still depends on the target platform and rendering pipeline, but individual modules can be written to handle basic processing without depending on either one, so pieces of shader logic can be reused across different setups. The project defines modules that stay platform independent, supports localization of the material editor through .po translation files, and avoids variable name clashes between modules by giving each one a unique module ID. It also lets creators copy and paste material settings as plain text in a way that does not depend on the platform. The documentation makes clear several things the project intentionally does not try to do. It does not support modules that add new rendering passes, since that would cause conflicts between modules, multi pass setups need to be defined in the main shader itself. It does not support Unity's built in MaterialPropertyDrawer, because the editor interface is written using Unity's VisualElement system instead of IMGUI. The main shader still depends on the platform, and is expected to handle only simple things like the main texture, normal maps, or outlines, so it stays easy to rewrite. Modules generally cannot use Unity specific features directly, though shader keyword handling is supported through a special attribute that turns generated shader keywords into constant properties. Modules are also not meant to change behavior defined by the main shader or by other modules, again to avoid conflicts. The documentation for this project is written only in Japanese, with the expectation that readers can use browser based machine translation if needed. The full README is longer than what was shown.

prompts (copy fr)

prompt 1
Explain how Shader Core's module ID system prevents variable name collisions between shader modules in Unity.
prompt 2
Show me how to write a Unity shader module using Shader-Core that avoids depending on a specific render pipeline.
prompt 3
How would I use the SCConstValue attribute in Shader-Core to expose a shader keyword as a constant property?
prompt 4
Walk me through setting up a localized material editor with .po files using Shader-Core.

Frequently asked questions

what is shader-core fr?

A modular shader system for Unity that lets developers write platform independent shader modules while keeping the main shader itself simple and easy to rewrite.

What language is shader-core written in?

Mainly C#. The stack also includes C#, Unity, HLSL.

What license does shader-core use?

No license information was found in the README.

How hard is shader-core to set up?

Setup difficulty is rated hard, with roughly 1h+ to a first successful run.

Who is shader-core for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.