Hi,
I'm testing out the various features of Super Text Mesh and I consistently get a crash when I try to use the inline quads in a UI setting.

1. Create a new project with Unity 5.5.0f3.
2. Import Super Text Mesh.
3. Add a Super Text Mesh component in the scene by doing 'right click>UI>Super Text Mesh'.
4. Change the text to '<q=anybutton>'.
5. Unity crashes with this Editor.log.

If instead of '<q=anybutton>' I type '<q=cross>', it works but my console is spammed with this error (and will crash whenever I add another inline tag):

Converting invalid MinMaxAABB

UnityEngine.Mesh:SetTriangles(List`1, Int32)

SuperTextMesh:SetMesh(Single, Boolean) (at Assets/Clavian/SuperTextMesh/Scripts/SuperTextMesh.cs:2377)

SuperTextMesh:SetMesh(Single) (at Assets/Clavian/SuperTextMesh/Scripts/SuperTextMesh.cs:2345)

SuperTextMesh:Rebuild(Single) (at Assets/Clavian/SuperTextMesh/Scripts/SuperTextMesh.cs:925)

SuperTextMesh:Rebuild() (at Assets/Clavian/SuperTextMesh/Scripts/SuperTextMesh.cs:884)

SuperTextMesh:Update() (at Assets/Clavian/SuperTextMesh/Scripts/SuperTextMesh.cs:931)

Oof, yeah this looks like the whole "multiple materials on a canvas crash Unity" bug again. I tried to fix this in the latest update since it seemed to be fixed on my computer, but I suppose it's not the case? I've been asking on the Unity forums for months how to solve this and never got a reply, so it's hard to tell if this is something wrong w/ Unity, or if I'm setting materials incorrectly.

One user has already contacted me about this, but all I can really do right now is add a toggle to enable/disable multiple materials on UI? I'll be uploading that version soon, but that's not really the best fix. I'm developing on a mac, and don't have access to a PC to test this yet, and I'm not too sure where to begin...

I'm coding blind, but give this a shot:

Around line 2430 or so, you'll see a block of text like this:

c.materialCount = newMats.Length+1;

for(int j=0; j<c.materialCount-1; j++){

c.SetMaterial(newMats[j],j);

}

Try changing it to be like this:

c.materialCount = newMats.Length+2;

for(int j=0; j<newMats.Length; j++){

c.SetMaterial(newMats[j],j);

}

In the previous build, adding that +1 prevented the crash for me, so it's just a guess, but maybe this'll work?

I'm afraid it didn't work. :(

Do you need more info?

Damn, I'm really not sure, then! That log is very handy though, but it's all Unity backend stuff that I don't know how to make sense of. I'll try getting in contact w/ Unity again, but I've had no luck so far.

Til then, the non-UI canvas should work perfectly.

I entered a crash report to Unity as well. I'll let you know once the issue is created.

Sweet! Just pushed an update that makes this a toggle for now, and tried emailing someone at Unity who helped me before. I really want to get this bug taken care of once and for all

Same problem here. You have all my votes on the issue tracker when the issue is listed. I've tried to fix it myself in the previous version but Unity seems to crash no matter what and there is nearly no information available about setting CanvasRenderer materials on google.

Update:

Hey,

We have been able to reproduce this bug and have sent it for resolution with our developers.

We highly appreciate your contribution. If you have further questions, feel free to contact us.

Regards,

Lukas A.

Unity QA Team

Talking about the issue tracker, I have a fogbuz ticket because I reported it through the crash reporter. Should this create an issue tracker? Or are there 2 independent reporting systems?

I'm honestly not sure? Unity has so many different things that do the same thing so it's kinda hard to keep track of. But let me know if you get any updates, or they need more info from me. I also made this forum post about the issue, but it kinda accidentally turned into a journal: https://forum.unity3d.com/threads/canvasrenderer-crashes-unity-when-given-a-mesh-that-has-submeshes-more-than-one-material.439133/

From a comment(by one of the unity guys) I found on the unity forum

"When you submit a bug to us through the bug reporter, it goes to our internal bug tracking system FogBugz. After it's checked by someone in QA that it's not private or under NDA, the status is made public, and the Issue Tracker will pick it up and display it publicly on the Issue Tracker site (minus your machine information, logs & example projects, those are kept private). So there is no submitting bugs to the Issue Tracker, it just crawls through bugs that are public and displays them. "

So I guess you don't need to open an issue in issue tracker.

Thanks for the precisions noanoa.

I poked them to know if we can get an ETA on the fix.

Here's the issues tracker bug:

https://issuetracker.unity3d.com/issues/unity-cras...

Let's vote it up to the skies!

Just a note, this bug doesn't happen on Windows in Unity 5.3.4, which I build STM in, but happens in Unity 5.6. I'm not sure what changed between those two versions, but it's a step forward, I guess?

Apparently the issue was closed as "not reproducible"... (https://issuetracker.unity3d.com/issues/unity-cras...)
Yet I just reproduced it in 5.6.0f3.

No workaround on your side KaiClavier?

Update from Unity:

"Hey,

We've tested this on Unity 2017.1.0 and the crash does not occur there.
2017.1.0 is currently in beta but it should roll out soon.

If you are able to reproduce it with unity 2017.1.0, please respond to this email."

So I can confirm that it no longer crashes Unity on 2017.1.0b5 but instead it doesn't show anything whenever using a tag that relies on a texture (<q>, <c>, etc.)

I have a feeling this might have to do with the "Multi Material UI" bool? Make sure it's checked/unchecked to test this.

Yep, I checked and icons appeared! \o/
Although not super well:
http://imgur.com/a/KxN2p
http://imgur.com/a/lFtCV

Oh boy, that's a new one... Is anything similar happening with the non-UI mesh? If not, then it's gotta be either Unity UI itself, or the code that sets the materials.

The non UI one works as before.

Got it!
On the canvas containing the SuperTextMesh, make sure that Additional Shader Channels has at least TexCoord1.
I guess that solves it all! \o/

Thanks for the support.