Repository navigation
Releases: CybersharpX/Vim
Releases · CybersharpX/Vim
Release list
Vanadium beta release 0.0.2
Vanadium Beta Release Notes (v0.1.0-beta)
Release Date: February 22, 2026
Highlights
- Added support for loading precompiled
.mcshaderpacks from<gameDir>/shaderpacks/. - Introduced strict
metadata.jsonvalidation for safer and more predictable pack loading. - Added SPIR-V module validation for stage and entrypoint consistency.
- Implemented graphics and compute pipeline activation flow for supported packs.
- Added hot reload support via file watching and
/vanadium reload. - Added in-game shader controls in
Options -> Video Settings -> Vanadium Shaders.
Improvements
- Improved Vulkan backend safety checks with compatibility guard handling.
- Improved logging clarity for pack load, activation, and reload operations.
- Improved command workflow for listing, status checks, and pack activation.
Commands
/vanadium list/vanadium status/vanadium activate <pack_id>/vanadium reload
Known Limitations
VulkanModis required.- Shader packs must be precompiled SPIR-V (
.spv). - Strict metadata validation rejects incomplete or nonconformant packs.
Upgrade Notes
- Ensure existing packs include complete and valid
metadata.json. - Re-test pack activation after upgrading to confirm pipeline compatibility.
New Shader Format: Folder Structure
<pack-name>.mcshader
├── LICENSE
├── README.md
├── metadata.json
├── shaders/
│ ├── pack.json
│ └── *.properties.xml
├── lib/
│ └── <shared SPIR-V modules and categories>
├── world-0/
├── world-1/
├── world-2/
├── textures/
└── config/
├── defaults.json
└── toggles.json
Vanadium beta release 0.0.1
Beta Release Notes (v0.1.0-beta)
Added
.mcshaderpack discovery and loading from<gameDir>/shaderpacks/- Metadata validation using
metadata.json - SPIR-V verification for shader stage and entrypoint consistency
- Graphics/compute pipeline initialization for supported packs
- Hot reload support via file watching and
/vanadium reload - In-game shader configuration screen under video settings
Improved
- Safer Vulkan backend handling with compatibility guard checks
- Structured logging for pack load/activate/reload diagnostics
- Clearer command flow for listing, status checks, and activation
Known Limitations
- Requires VulkanMod; fallback rendering behavior depends on backend state
- Shader packs must be precompiled to SPIR-V (
.spv) - Strict metadata validation may reject incomplete or nonconformant packs
Upgrade Notes
- Existing shader packs should include complete
metadata.jsonfields - Re-test pack activation after updates to ensure pipeline compatibility