Tags
Creators
Details
All versions
mc1.17.1-0.3.3
Release
Sodium 0.3.35 years ago 18.9K
Compatibility
Minecraft: Java Edition
1.17.x
Platform
Fabric
Supported environments
Client-side
Changes
This release contains a few important bug fixes and improvements for Minecraft 1.17.1.
Highlights
- Improved frame rates when loading or updating chunks.
- Fixed a memory leak caused by sync objects never getting released.
- Added options to control how many threads are used for chunk building, and to always defer chunk updates for improved frame times. The default number of threads used for chunk building is more optimally chosen and should help improve frame rates on slower CPUs.
- Improved the precision of the compressed vertex format, reducing texture glitches found with some texture packs and vanilla blocks
- The inner faces of leaves are no longer rendered if fast graphics are enabled, significantly reducing the geometry count of scenes with lots of foliage (thanks ADudeCalledLeo.)
- Config file handling has been greatly improved, and if a corrupted config file is found, the user will be prompted to fix the problem instead of the game crashing.
And everything else...
- Mods which provide config file overrides will no longer crash on first startup (thanks tbejos.)
- Improved our shader code slightly to reduce overhead in the vertex stage, potentially helping older graphics cards.
- Improved compatibility with the legacy AMD graphics drivers on Windows.
- Fixed a problem where empty draw calls would be submitted during chunk rendering.
- Some other minor improvements and fixes...
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:AANobbMI:3JJvf9Kn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AANobbMI:3JJvf9Kn"
}

