🤑 Indie game store🙌 Free games😂 Fun games😨 Horror games
👷 Game development🎨 Assets📚 Comics
🎉 Sales🎁 Bundles

ClementCasaRara

14
Posts
1
Topics
A member registered 236 days ago

Recent community posts

Yep. 2017.1 should be released around June. But I think you might have to display a message if the user adds a SuperTextMesh to a canvas that doesn't have the correct shader channel.

I don't think I follow you.
I'm setting the shader channel variable through the inspector field on the Canvas, not through code.
Also, I only tested on 2017.1.0b5, since that version didn't crash like 5.6, I assume they changed something.

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.

The non UI one works as before.

(Edited 1 time)

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

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.)

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."

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?

Here's the issues tracker bug:

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

Let's vote it up to the skies!

Thanks for the precisions noanoa.

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

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 entered a crash report to Unity as well. I'll let you know once the issue is created.

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

Do you need more info?

(Edited 2 times)

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.

The repro step is the following:


  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)

Hi,
First of all, great asset!
Just to add a bit more precision, this does indeed happen when you import the asset with the serialization setting set to 'ForceText'. Changing it to 'Mixed' with the asset already imported will get rid of the errors but all builtin content (Gradients, etc.) won't work. The trick is to set the serialization setting to 'Mixed' before importing the asset and then set it back to 'Force Text'. Then all the builtin content will work.

Just thought I'd save everyone the 5 mins it takes to figure it out. :P

Btw it happened to me on 5.5.0f3.