Tags
Creators
Details
mc1.17-v1.1.1
Compatibility
Changes
This release primarily fixes a number of stability issues in the 1.17.1 version of Iris. Previously, the bundled version of Sodium for 1.17 was based on an older beta build, but now we've released to the much more stable Sodium 0.3.0 release. In addition, IMS fixed a memory leak in the sky horizon rendering code on Iris for 1.17.1.
Overall, Iris 1.1.1 for 1.17.1 is much more stable than Iris 1.1.0 for 1.17.1! We've been working on a much bigger update, but unfortunately that code isn't quite ready yet. Instead of continually holding back critical fixes until that code is ready, we've decided to pull the critical fixes into an intermediate build, giving us time to polish up the next update.
Fixes for 1.16.5 & 1.17.1: - Fixed Complementary not compiling on macOS in non-overworld dimensions - Avoid crashes with Physics Mod, but there are still some weird bugs with it - Fixed colored shadows not working (this was a regression shipped in 1.1.0) - Fixed clouds being cut off at low render distances when shaders are disabled - Added rudimentary support for atlasSize, needed by newer versions of Complementary Shaders - Fixed block breaking animations for block entities - Support separateAo for blocks rendered with the Fabric Rendering API - Fixed a number of issues related to the ordering of entity rendering
Fixes for 1.17.1: - Allow shader packs to detect when the player is in powdered snow - The bundled version of Sodium is now based on the 0.3.0 release instead of a beta build, fixing a memory leak - Fixed vanilla clouds not rendering in packs that use them - Fixed beacon beams not rendering - Fixed a memory leak in horizon rendering
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:YL57xq9U:lAEtBzCu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YL57xq9U:lAEtBzCu"
}

