text is white bars

[Kurt-Dekker]

Without pictures we’re just guessing.

Maybe this?

tofu fonts and / or blank buttons:

I read recently this can be fixed by specifying OpenGLCore in the preferences, as follows:

Unity editor windows content texts are broken on MacOS

Probably found a solution. MacBook Pro 2019, MacOS Venture 13.0 - Unity 2020.3.41f1 Go in Project Settings > Player and expand the Other Settings tab (Desktop tab). Check off the Auto Graphic API for MacOS and add the OpenGLCore. [8549690--1143023--upload_2022-10-30_10-43-0.png] After the editor restart, every thing should be resolved. [8549690--1143026--upload_2022-10-30_10-43-8.png]

Package Manager's words looks like tofu

Sorry, I'm japanese so my English may be strange for you..... I would like to ask a question as I could not find a solution no matter how much I looked for one on the internet... In unity 2020.3.36, when I launch the package manager or shader graph, it looks like the attached image .... I have tried creating a new project and opening it, downloading unity itself again, and starting up the PC again, but nothing has cured the problem..... I would like to know if anyone has a solution to thi…

Or perhaps:

The proper way to set scales:

OnPointerEnter - loose image

Never use Vector2 to assign scales. The reason is because the third term (Z) is zero. The code above is actually: new Vector3(1.1f,1.1f,0.0f); // infinitely thin, hence invisible When setting scales, you must always write: new Vector3(1.1f,1.1f,1.0f); // correct way to scale stuff ALWAYS use Vector3, and make sure that the Z term is either 1.0f or your scale. Similarly never set scale to Vector3.zero, especially in a UI, because this will cause layout divide-by-zeros and damage all y…

NEVER set scale (or any part of scale) to zero or negative.

NEVER use Vector2 because that makes the third term (Z) zero.

ALWAYS use Vector3, and make sure that the .z is either 1.0f, or else your non-zero scale.

Similarly never set scale to Vector3.zero, especially in a UI, because this will cause layout divide-by-zeros and damage all your hierarchy with either NaN or Infinity.

Otherwise…

How to report your problem productively in the Unity3D forums:

http://plbm.com/?p=220

This is the bare minimum of information to report:

• what you want
• what you tried
• what you expected to happen
• what actually happened, log output, variable values, and especially any errors you see
• links to actual Unity3D documentation you used to cross-check your work (CRITICAL!!!)

The purpose of YOU providing links is to make our job easier, while simultaneously showing us that you actually put effort into the process. If you haven’t put effort into finding the documentation, why should we bother putting effort into replying?

If you post a code snippet, ALWAYS USE CODE TAGS:

How to use code tags: Using code tags properly

• Do not TALK about code without posting it.
• Do NOT post unformatted code.
• Do NOT retype code. Use copy/paste properly using code tags.
• Do NOT post screenshots of code.
• Do NOT post photographs of code.
• Do NOT attach entire scripts to your post.
• ONLY post the relevant code, and then refer to it in your discussion.