Tags
Creators
Details
1.9.0+mc26.2-snap2-2026-05-12
Compatibility
Changes
Vulkan PostFX 1.9.0
Highlights
Vulkan PostFX 1.9.0 introduces VPFX v1 alpha, a new standardized shader pack / post-processing pack format for declaring pack metadata, capabilities, render graph structure, shader paths, and runtime resources.
This release focuses on VPFX infrastructure rather than new visual effects. It adds the pack format, validation pipeline, runtime materialization tests, backend abstraction, test packs, and authoring documentation.
Added
- Added VPFX native pack format v1 alpha.
- Added
pack.jsonmanifest parsing and validation. - Added VPFX graph parsing and validation.
- Added pass
id/debug_labelsupport for clearer diagnostics. - Added non-
post/shader path support.- Shader references now use
<namespace>:<path>. - Zip entries are resolved as
shaders/<path>.vshandshaders/<path>.fsh.
- Shader references now use
- Added shader include preprocessing.
- Supports
#include "...". - Rejects
..path traversal. - Detects recursive include cycles.
- Supports
- Added VPFX validation smoke test.
- Added VPFX runtime materialization smoke test.
- Added
positive_minimalminimal VPFX test pack. - Added multiple
negative_*test packs for validator coverage. - Added explicit VPFX runtime backend abstraction:
VpfxRuntimeBackendVpfxRuntimeBackendCapabilitiesVpfxPostChainBackend
ActivePostEffectBridgenow materializes VPFX packs through the explicit runtime backend abstraction.- Added VPFX v1 pack format documentation.
- Added VPFX testing documentation.
- Added VPFX minimal pack authoring guide.
- Added known issues documentation.
Improved
- VPFX graph validation now checks:
- undeclared output targets
- missing input targets
- undeclared texture inputs
- self read/write passes
- missing final output to
minecraft:main - future target dependencies
- Runtime materialization now runs through the explicit
minecraft_postchainbackend. - Backend information is now visible in runtime/test logs.
- VPFX documentation now describes the current alpha boundaries, test workflow, and known limitations.
- The minimal example pack uses
composite/finalto verify that VPFX no longer depends on the legacypost/path assumption.
Known Limitations
- VPFX v1 is still an alpha spec.
- The current execution backend is still Minecraft PostChain.
- The native VPFX runtime is not complete yet.
- Compute shaders are not supported.
shadow_depthis experimental.- Iris / Sodium compatibility is not guaranteed.
- This build primarily targets Minecraft 26.2 snapshot / Fabric.
- VPFX schema may still change during the alpha period.
For Shader Pack Authors
Start with:
docs/vpfx-pack-format-v1.mddocs/vpfx-authoring-minimal-pack.mddocs/vpfx-testing.md
A minimal VPFX pack contains:
pack.json
post_effect/main.json
shaders/composite/final.vsh
shaders/composite/final.fsh
VPFX shader references use:
<namespace>:<path>
and resolve to:
shaders/<path>.vsh
shaders/<path>.fsh
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:TsmOcOBN:QHN9VI5p"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:TsmOcOBN:QHN9VI5p"
}

