Fix Armourer's Workshop rendering compatibility - #3215
Open
FortyTwoCn wants to merge 1 commit into
Open
Conversation
|
try this version. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes a rendering compatibility issue between Iris and Armourer's Workshop on NeoForge 1.21.1.
The previous
mergeRenderingflag was a global boolean. While Iris was rendering merged batches, everyRenderType.draw()call could skipsetupRenderState()/clearRenderState(), including render paths that were not part of the current Iris batch. This could leak render state into Armourer's Workshop GUI/item rendering, causing black quads, broken transparency, and in some modpacks a null shader crash.Before：
