Unity raycasthit2d update#
Unity raycasthit2d code#

Quick fix 2: use the Collider.Distance to remove penetration after moving the body (assuming i'm using this distance to move the body closer to the obstacle). RaycastHit2D hit new RaycastHit2D() Ray2D ray2D new Ray2D(new Vector2(p.x,p.y), Vector3.down ) //Ray2D ray new Ray(transform.position,new Vector3. Today, my only way to 'fix' that, is using the event 'OnMouseDown' on my object.

Unity raycasthit2d code#

I tried the code above for detection of Sprites on the screen, but don't worked, as the code I did for the previous version (that had worked) in Unit圓D.

The question is, How can i know this offset is going to be consistent across different Unity versions? What about different platforms?. I upgraded my Unity to the last version (4.5), but I am get some problems, mainly with collision. Quick fix 1: Manually removing that 0.015 from the distance value. It goes from pointA (red object's outer skin) to pointB (green box's outer skin).Īs you can see in the console, the distance from the query differs from the colliderDistance2D.distance. The white segment represents the ColliderDistance2D data. Notice how both of these crosses penetrate ( +0.015) the box 'outer skin' (defined by the contact offset). Now, also change the second parameter of Debug.DrawLine to transform.position + transform.right distance. Ive looked around for other solutions, such as Unity - Raycast not hitting to BoxCollider2D objects, but when I change my code to the one used in that answer: RaycastHit2D hit Physics2D.Raycast( (Input.mousePosition), Vector3. Take a look the will see that it is too shot. The problem is that the provided direction is too short. The yellow cross represents the 'raycastHit.point'. Mathf.Infinity is for internal physics system for how far the raycast should go from the provided direction. I'm testing a circle (+ CircleCastNonAlloc) and a box (+BoxCastNonAlloc) against a big box (green). i'm using a high contact offset value (=0.1) in order to be able to see the effect (it doesn't matter, this value doesn't affect the result at all. I'm not saying Collider.Distance should always be equal to raycastHit.distance. Please notice one important thing, if the ray starts inside the collider of the object than the object will be reported as the object hit by the ray, if you want to avoid this you can either change the start position of the ray outside the object collider or assign the object to a specific layer and ignore that layer with a mask. I should mention that i'm using Collider.Distance in a very specific setup (see the image below). Collider.Distance does return the expected value, whereas RaycastHit.distance does not. Based on what i know about the contact offset (only circles and capsules don't get affected by the c.offset), the 'expected distance' doesn't match with the raycastHit.distance.Ģ. You should check if the RaycastHit2D collider is null to know if you actually hit something or not. RaycastHit, in Unity, is a structured data object that is returned when a ray hits an object during a raycast.

By the way, the 'raycastHit.point' value is also incorrect.ġ. A Unity ID allows you to buy and/or subscribe to Unity products and services. This 'offset' is big enough to be ignored, we are not talking of some floating-point precision error. Store a reference of it in your script and use that. For some reason your suggested change could not be submitted. Although we cannot accept all submissions, we do read each suggested change from our users and will make updates where applicable.

Unity raycasthit2d update#

ANOTHER EXTREMELY IMPORTANT THING 1: Do not use Camera.main in Update (), as it uses a GetComponet call, which can cause perormance decreases. Thank you for helping us improve the quality of Unity Documentation. For a ray this is obvious as it has no size. I'm getting a +0.015 offset all the time no matter what (Unity 20 as well). You just input the mouse position and then use this new ray to do the raycast. RaycastHit2D SecondHit Physics2D.CircleCast (hit.centroid, 0.3307159f, reflectDir, 100, 1 << 9 1<<10) If you look at the RaycastHit2D docs youll see both a 'point' property (which youre using) which is the actual position the shapes intersected. Ra圜astHit2D (see later), which is a class that specifies all the details of. I want to be sure about this before reporting it as a bug.Īll my 2D physics queries distance values are apparently 'wrong'. Hi i guess you are the only one who can help me (since this issue might be related to some internal implementation, constant or something else). But basically, if you just want to click the mouse directly on an object and have the raycast hit it, this should work: Code (csharp): RaycastHit2D hit Physics2D.Raycast( ( Input.mousePosition), Vector2.