Tags
Creators
Details
All versions
1.14.1+mc26.2-rc2-2026-06-13
Beta
Vulkan PostFX 1.14.1+mc26.2-rc2-2026-06-132 months ago 16
Compatibility
Minecraft: Java Edition
26.2-rc-2
Platform
Fabric
Supported environments
Client-side
Changes
Vulkan PostFX 1.14.1 — Stability & Shadow Tuning
This is a stability-focused update for Minecraft 26.2-rc2.
Added
- Added safer VPFX shader pack auto-selection behavior.
- Added configurable sun/moon shadow tuning through JVM properties.
- Added throttled shadow diagnostics to reduce log spam.
Changed
- Improved sun/moon primary light selection near sunset and moonrise.
- Moonlight shadows are now much weaker by default.
- Shadow intensity now fades more smoothly during light transitions.
/vpfx reload autois safer in-world and avoids unnecessary hard resource reloads.
Fixed
- Fixed cases where VPFX could get stuck on the built-in invert debug effect.
- Fixed fallback behavior when external VPFX pack loading fails.
- Fixed excessive per-frame shadow pipeline logging.
- Fixed sunset/moonrise shadow flickering caused by sun/moon light source fighting.
Notes
- Native VPFX runtime work is still experimental.
- Entity shadows and player shadows are not yet part of this release.
- If a shader pack fails to load, VPFX should fall back to vanilla rendering instead of disrupting the world.
Shadow tuning properties
Advanced users can tune shadow behavior with:
-Dvulkanpostfx.shadow.moonMaxIntensity=0.10
-Dvulkanpostfx.shadow.baseDarkness=0.42
-Dvulkanpostfx.shadow.logIntervalFrames=300
These are optional and mainly intended for testing.
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:xsTlAEf2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:TsmOcOBN:xsTlAEf2"
}

