Canvas is a shader-based Renderer for the Fabric modding toolchain. It supports all features of the proposed Fabric Rendering API plus extensions defined in FREX.
Discord: https://discord.gg/7NaqR2e Curse: https://www.curseforge.com/minecraft/mc-mods/canvas-renderer
Except as noted in individual source files, all code in this mod, include shaders, is licensed under the LGPL-3.0 License. This means no warranty is provided.
Some elements of code are adapted from or copied from other projects with compatible licensing. The author has attempted to provide credit and/or appropriate notices in the code where applicable.
Canvas is in EARLY ALPHA. Expect it to break.
The FREX extensions, shader library, vertex formats, attribute bindings, and lighting options are subject to change - causing your code to break. Sorry. When there is a stable release I will avoid breaking changes in shipping versions. Until then, experimentation is the norm.
When people first hear about Canvas they often ask if it is a performance mod or a replacement for Optifine / shader packs. The answer is "no, but..."
Optifine and shader packs primarily target vanilla Minecraft. They work with modded, often well, but they aren't designed as tools for mod authors.
Canvas' main purpose is to give mod authors more control and options for rendering modded blocks. It can also be used for building shader packs, but the design is entirely different than OF and does not yet support all the features needed for a full shader pack implementation. Unlike OF shader packs, Canvas shader packs can be mixed together by adding multiple resource packs.
Performance-wise, Canvas tries to be be faster than Vanilla with extended features. It is optimized heavily - but the intent of these changes is to make better rendering practical, not to be a general-purpose performance mod. It isn't meant to run on low-end hardware and may or may not make your game run faster overall.
Canvas will try to fully use your hardware and will not be timid about it. It wants at least 4GB and will push both your CPU and GPU. It will stress your cooling system.
If you're looking to max performance with Canvas, the config menu tool tips indicate which features can help. Bloom is especially expensive at high resolutions. But bloom is also fun to look at, so.... your call.
More optimizations will be added after a stable release.
Add Canvas to the mods folder in your minecraft folder (%appdata%/.minecraft/mods on Windows) and make sure you have recent versions of Fabric Loader and API, plus at least 4GB of memory allocated to Minecraft. An in-game config menu is available in video options, or via Mod Menu if you have it installed.
Third-party pipeline shaders:
This list is updated infrequently.
More releases can be found in #canvas-3rd-party-releases channel on the discord server.
Before using Canvas, you should first understand RenderMaterials, Meshes, RenderContexts and other features defined by the Fabric Rendering API. For that information, consult the rendering article on the Fabric Wiki. Note: Fabric wiki is still WIP as of this writing but should be more complete "soon."
You can also see RenderBender for some (not very good) examples of usage. Avoid duplicating those examples directly - they aren't especially performant or suitable for use at scale. As soon as someone releases a model loader / library for Fabric Rendering API / FREX, that will almost certainly be a better approach.
Shaders can be attached to materials via json, which is the preferred way. Your materials are located in materials/ within your namespaced resource location.
{
"vertexSource": "example:shaders/test.vert",
"fragmentSource": "example:shaders/test.frag"
}The paths in vertexSource and fragmentSource should point to GLSL files in your resources location. The relative path and file extension must be included, and shaders/ is the suggested location but not mandatory.
Afterwards, you can map a blockstate (or entity, particle, etc) to your material using a material map located in materialmaps/, like so:
{
"defaultMaterial": "example:test_material"
}You can also load the material directly into java
Renderer renderer = Renderer.get();
// obtain the loaded material, done after resource reload
RenderMaterial mat = renderer.materials().materialFromId(new ResourceLocation("example:test_material"));Note that loading materials directly is only necessary for rendering custom meshes. For full blocks, entities, particles, or fluids, using material maps is the recommended way.
Alternatively, materials can also be created directly in java, like so:
Renderer renderer = Renderer.get();
RenderMaterial mat = renderer.materials().materialFinder().shader(
new ResourceLocation("example", "shaders/test.vert"),
new ResourceLocation("example", "shaders/test.frag")
).find();This can be more reliable in case you don't want your materials to be affected by resource packs or resource reload. In this case, material maps can't be utilized.
Your vertex and fragment shaders must have a frx_materialVertex and frx_materialFragment procedures respectively. To ensure compatibility, shaders are limited to #version 330 features.
A detailed documentation of the available API can be found in the FREX source files:
Add these maven repos to your build if not already present
repositories {
// vram guild repo
maven {url "https://maven.vram.io"}
// cloth config / used by canvas dependencies
maven {url "https://maven.shedaniel.me/"}
// spruce ui / current ui library
maven {url "https://maven.gegy.dev"}
// mod menu
maven {url "https://maven.terraformersmc.com/releases/"}
}And add Canvas to your dependencies
dependencies {
modCompileOnly "io.vram:canvas-fabric:19.3.+"
// optional for testing in dev environment
modRuntimeOnly "io.vram:canvas-fabric:19.3.+"
}Note that versions are subject to change - look at the repo to find latest.