Determining Plane's UV under the cursor

Unity Engine
1

Hi!
I have a plane object. This plane is fixed relative to camera (plane is camera’s child and always facing the camera – image attached). This plane has some RenderTexture on it. Now I want to know, what UV coordinate is currently under the mouse cursor.
The following script is sitting on this plane object:

//....
_collider = gameObject.GetComponent<Collider>(); // Plane's mesh collider
//....


void FixedUpdate()
        {
            RaycastHit hit;

            var p = UnityEngine.Input.mousePosition;

            if (_collider.Raycast(Camera.main.ScreenPointToRay(p), out hit, 100f))
            {
                var meshCollider = hit.collider as MeshCollider;
                var rend = hit.collider.GetComponent<Renderer>();

                if (rend == null || rend.sharedMaterial == null || rend.sharedMaterial.mainTexture == null || meshCollider == null)
                    return;

                var pixelUV = hit.textureCoord;

                pixelUV.x *= rend.material.mainTexture.width;
                pixelUV.y *= rend.material.mainTexture.height;

                Debug.Log("UV=[" + hit.textureCoord.x + ";" + hit.textureCoord.y + "]" + ", XY=[" + pixelUV.x + ";" + pixelUV.y + "]");
            }
        }

But coordinates I see in the log are very strange. First of all, when I change aspect ratio in a viewport, point that had XY[51,466] in 16:10 becomes XY[95,464] in 4:3 and so on. Secondly, offset is so huge that I am getting UV readings even if mouse pointer is nowhere near this plane.

How to correctly get these UV readings regardless of screen size?

3371305--264295--UVs.jpg
3371305--264295--UVs.jpg1920×997 402 KB

2

UPD: I ended up ditching mouse pointer entirely. Code above actually works well if you hide cursor and just look at the collision detection. Now I am showing a really small sphere at the ray hit point, and when you move your mouse, this sphere smoothly follows plane surface: now this is my “pointer”. It works really well, and even better than “real” pointer: my 3d-cursor actually follows object geometry. And as this sphere represent actual raycast hit point, precision is great.

I really like this workaround, but question is still open.