Repository navigation
Retry mesh specialization when RenderMesh is not ready - #25815
Merged
alice-i-cecile merged 2 commits intoOct 5, 2026
Merged
alice-i-cecile merged 2 commits into
alice-i-cecile merged 2 commits into
Conversation
stuartparmenter
added
C-Bug
Zeophlite
approved these changes
Sep 19, 2026
Zeophlite
approved these changes
Sep 30, 2026
kfc35
approved these changes
Sep 30, 2026
kfc35
added
S-Ready-For-Final-Review
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
4 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.
Objective
Fix meshes remaining invisible when specialization runs before their
RenderMeshis ready.Solution
Re-enqueue specialization when the mesh is unavailable in the material, prepass, shadow, 2D material, and 3D wireframe paths. This feels like the most straight forward fix w/o a larger refactor.
Testing
Tested in my game where the issue was hit
This was AI assisted w/ Fable when tracking down a bug in my game -- applied the fix to all the places where it needs to be. Looked at how to avoid so much boilerplate, but all the other solutions were signifigantly larger refactors, so went with the easiest solution.