koobas.hobune.stream
UI Canvas Anchor points are stuck in the bottom left corner and disabled when in overlay mode.
My text is showing below bottom of the screen even though it is aligned to start at the top. Only by changing it to world space can i move it into position... obviously not going to fly.
Already took long enough figuring out the totally unintuitive way of even creating the canvas, only by creating it as a new object from the drop down and not by adding any component to an existing object as i've done exclusively thus far, whereas creating the Text component automatically adds and adjusts components on the gameobject, without telling you that you actually needed to create an entirely different object.
Aaaaand for those of you who may encounter this problem i have actually already solved it, but i guarantee many others will make this mistake and this question will help them.
so, if you decide to create a text component, or possibly any other ui component on the object which also holds your camera, it will do you the wonderful favor of changing the transform on that object to a Rect Transform. Eventually you will figure out how to make a UI canvas, and once again you might think you're clever and add that canvas as a child of the object with the camera. You just gave a one-two punch straight to the face of your UI and quite possibly cost yourself a lot of time. Because the camera object has a rect transform instead of a transform, for some reason the anchors on your canvas will be shoved into the lower left corner, rather than centered over the screen, starting your canvas at the bottom of the screen and going downward into the abyss of Off Screen, and of course unadjustable in overlay mode.
the fix? simply remove the Rect Transform component from the object with the camera (possibly requiring you remove that text component, which it will prompt you for, reminding you that the clever thing you thought you did was a terrible mistake that would cost you a lot of time) and for me at least the canvas anchor points instantaneously fixed themselves, and now i can get back to USING that text to figure out what is wrong with android touch and how i can slap-dash my way around it if necessary.
