Hello there, I've recently acquired Super Text Mesh (Version 1.8.5), and it seems to be very promising but I've just updated to 1.8.8 and I have some issues.  My unity project is using 2018.1.0f2 (64 bit) in PC mode.

When I instantiate a 'UI/Super Text' through the 'right-click menu', it isn't visible.  I'm guessing this might have something to do with the default shader being set to (Super Text Mesh/UI/Default). This same shader is used in the 'ShaderText' scene, and it isn't visible there either.

While I'm here, I can't quite out how to apply the 'SDF' shader on a normal font, as referenced by the documentation. I see a checkbox for SDF but it cannot be checked.

If I instead set an SDF shader directly, well, it works in the scene view, but it'll be pitch black in the game view. Any ideas?

Okay, was able to reproduce the SDF mode toggle thing in 2018.2! (I develop in 5.3.4) I'll see if I can solve this r/n

Alright, I've narrowed it down to being a bug with my inspector. If you go into your material's inspector (the material being used by your STM object), you can toggle SDF mode and pixel snap just fine from there! SO that's the quickfix, I'll see what I can do about getting the inspector to play nice.

Okay, I think this one has me completely stumped. At the moment, I have no idea why this editor code in "STMCustomInspectorTools.cs" isn't working in newer versions of Unity. The workaround of toggling SDF mode & pixel snap works fine in a material's own inspector, so that might have to be used for just a bit. I'll add this to the official bug list, and hopefully figure out a solution soon.

FYI, @KaiClavier, it looks like there is a bug that is ominously closed "ByDesign" here: https://issuetracker.unity3d.com/issues/cannot-enable-emission-when-using-materi...

However, I found a fix for this. I looked at your shader "Super Text Mesh/Unlit/Default", and see this:

[Toggle(SDF_MODE)] _SDFMode ("Toggle SDF Mode", Float) = 0

So I tried a:

mat.SetFloat("_SDFMode", [0/1]);

Instead of your EnableKeyword/DisableKeyword calls, and now the material properly toggles in the editor (and I see the SDF pass for example changing things, so it seems to function). I don't know why Enable/Disable keyword doesn't work.

PS I did see you reply to my subthread reply earlier in the main thread (I guess I'll keep to the main thread).

Oh my god, I never realized this method would work. I figured those toggles were just material inspector shorthands, I didn't think changing the value via code would actually change the keywords! Thank you so much, I'll get this implemented ASAP.

Okay yeah trying this out further, this works fine in newer version of Unity, but in 5.3.4 this method doesn't work. If I could pinpoint the exact version of Unity where this breaks, I could use platform-dependent compilation to fix this, but right now that's not really good.

From that bug report, I guess I can assume it's 2018.1? I'll try implementing this, and see if it ends up cropping up in different versions. This wouldn't be the first "by design" bug to hit STM

The bug lists 2017.1.4p2 as the oldest version it repros on, and I confirm the current way is broken on 2017.4 :/

Does the new way throw errors on 5.3.4? If not, you could just call both right away, an EnableKeyword + SetFloat(1). That'll work, until it doesn't :)

Got it, I changed the code to work for 2017.1.4.

And it doesn't throw errors in 5.3.4, it simply doesn't work like how the current code wouldn't work in 2018. Good idea leaving both options in, I'll give that a go, then I wouldn't have to worry about the unity version.