Ok, I am having trouble recreating this exact scenario, but the line it happens on appears below. I think this is a super edge case when materials are hot-swapped and the info member of the SuperTextMesh class is not updated in time for the call. If it fails once though, it seems to block the update happening later, as it kills the call from RecalculateMasking() before AppplyMaterials() can be called. I'm not sure whether it would work to simply return from UpdateMaskingOnAllSubmeshes() here, or if that would simply push problems downstream.
As you can see, I have a breakpoint in place here, and the next time it's hit, I will collect any relevant data that I'm able and post here. (also, I only realized as I'm looking at it now that the > should be a >=, but I didn't want to bother replacing the image ^^;).




