![]() ![]() ![]() So naturally I changed its setting to just "TexCoord1" so that the warning goes away. For some reason, the default causes it to display a warning. ![]() I have a canvas meant to just show a number on the screen. Though come to think of it, Unity has made some other autochanges recently that were really annoying. So the autochanges seem to consist of some random position / size changes, and the majority of it is this big huge change the _typelessdata variable. ![]() I had discarded Unity's previous attempt at autochanging, but when Unity booted up again today, it changed it again (tho I don't know if it changed it on load, or if it changed it after I changed the two selected files in the screenshot). Hopefully, the UI and / or Graphics team can figure out an alternative way of handling this which doesn't result in dirtying persistent materials in the project when using a 2D It looks like a variable called _typelessdata is being constantly autochanged. This is done by the Canvas batching system and as such would affect all materials. This behavior is the result of a change in 2017.2 where the 2D RectMask now uses a shader keyword. Hopefully, the UI and / or Graphics team can figure out an alternative way of handling this which doesn't result in dirtying persistent materials in the project when using a 2D RectMask. Since this behavior will affect anything that uses a material that is persistent in the project (not only TextMesh Pro) I would suggest submitting a bug report on this. But if you were to assign a specific material to any object or use a persistent asset like a TMP Material Preset, then you will see this behavior. Since the UI Default material is an instance which does not live in a user project, you are not seeing this behavior. This behavior also affects all materials used by the canvas. This is done by the Canvas batching system and as such would affect all materials.Īs Unity batches these materials, it is setting and un-setting this keyword and depending on the order of these batches, it may end up where the last batch sets or unsets the keyword. Click to expand.This behavior is the result of a change in 2017.2 where the 2D RectMask now uses a shader keyword. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |