Android 앱에서 Hit Test 실행
컬렉션을 사용해 정리하기
내 환경설정을 기준으로 콘텐츠를 저장하고 분류하세요.
hit-test를 실행하여 장면에서 3D 개체가 올바르게 배치되는지 확인합니다. 올바른 위치에 배치해야 AR 콘텐츠가 적절한 (눈에 띄는) 크기로 렌더링됩니다.
조회 결과 유형
다음 표와 같이 Hit Test는 네 가지 유형의 조회 결과를 생성할 수 있습니다.
Frame.hitTest()
를 호출하여 히트 테스트를 실행하고 TapHelper
유틸리티를 사용하여 AR 뷰에서 MotionEvent
를 가져옵니다.
자바
MotionEvent tap = tapHelper.poll();
if (tap == null) {
return;
}
if (usingInstantPlacement) {
// When using Instant Placement, the value in APPROXIMATE_DISTANCE_METERS will determine
// how far away the anchor will be placed, relative to the camera's view.
List<HitResult> hitResultList =
frame.hitTestInstantPlacement(tap.getX(), tap.getY(), APPROXIMATE_DISTANCE_METERS);
// Hit-test results using Instant Placement will only have one result of type
// InstantPlacementResult.
} else {
List<HitResult> hitResultList = frame.hitTest(tap);
// TODO: Filter hitResultList to find a hit result of interest.
}
Kotlin
val tap = tapHelper.poll() ?: return
val hitResultList =
if (usingInstantPlacement) {
// When using Instant Placement, the value in APPROXIMATE_DISTANCE_METERS will determine
// how far away the anchor will be placed, relative to the camera's view.
frame.hitTestInstantPlacement(tap.x, tap.y, APPROXIMATE_DISTANCE_METERS)
// Hit-test results using Instant Placement will only have one result of type
// InstantPlacementResult.
} else {
frame.hitTest(tap)
}
관심 있는 유형을 기준으로 조회수 결과를 필터링합니다. 예를 들어 DepthPoint
에 집중하려면 다음을 실행합니다.
자바
// Returned hit-test results are sorted by increasing distance from the camera or virtual ray's
// origin.
// The first hit result is often the most relevant when responding to user input.
for (HitResult hit : hitResultList) {
Trackable trackable = hit.getTrackable();
if (trackable instanceof DepthPoint) { // Replace with any type of trackable type
// Do something with this hit result. For example, create an anchor at this point of
// interest.
Anchor anchor = hit.createAnchor();
// TODO: Use this anchor in your AR experience.
break;
}
}
Kotlin
// Returned hit-test results are sorted by increasing distance from the camera or virtual ray's
// origin.
// The first hit result is often the most relevant when responding to user input.
val firstHitResult =
hitResultList.firstOrNull { hit ->
when (val trackable = hit.trackable!!) {
is DepthPoint -> true // Replace with any type of trackable type
else -> false
}
}
if (firstHitResult != null) {
// Do something with this hit result. For example, create an anchor at this point of interest.
val anchor = firstHitResult.createAnchor()
// TODO: Use this anchor in your AR experience.
}
임의의 광선과 방향을 사용하여 히트 테스트 수행
히트 테스트는 일반적으로 기기 또는 기기 카메라의 광선으로 취급되지만 Frame.hitTest(float[], int, float[], int)
를 사용하여 화면 공간 포인트 대신 공간 좌표에서 임의의 광선을 사용하여 히트 테스트를 실행할 수 있습니다.
조회 결과를 사용하여 앵커 만들기
조회 결과가 있으면 해당 포즈를 입력으로 사용하여 장면에 AR 콘텐츠를 배치할 수 있습니다. HitResult.createAnchor()
를 사용하여 새 Anchor
를 만들어 콘텐츠가 조회 결과의 기본 Trackable
에 연결되도록 합니다. 예를 들어, 앵커는 비행기 적중 결과의 경우 감지된 평면에 연결된 상태로 유지되므로 현실 세계의 일부인 것처럼 보입니다.
다음 단계
달리 명시되지 않는 한 이 페이지의 콘텐츠에는 Creative Commons Attribution 4.0 라이선스에 따라 라이선스가 부여되며, 코드 샘플에는 Apache 2.0 라이선스에 따라 라이선스가 부여됩니다. 자세한 내용은 Google Developers 사이트 정책을 참조하세요. 자바는 Oracle 및/또는 Oracle 계열사의 등록 상표입니다.
최종 업데이트: 2025-07-26(UTC)
[null,null,["최종 업데이트: 2025-07-26(UTC)"],[[["\u003cp\u003eHit-tests determine correct placement of 3D objects in AR scenes by identifying real-world surfaces and their positions.\u003c/p\u003e\n"],["\u003cp\u003eThere are four types of hit-test results: Depth, Plane, Feature Point, and Instant Placement, each with its own characteristics and use cases.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers can filter hit-test results to focus on specific surface types like planes or depth points for precise object placement.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eHitResult.createAnchor()\u003c/code\u003e enables the creation of anchors at the identified hit points, allowing virtual content to be attached to real-world surfaces.\u003c/p\u003e\n"],["\u003cp\u003eStandard and arbitrary ray hit-tests are available, offering flexibility in how virtual objects are positioned within the AR environment.\u003c/p\u003e\n"]]],["A hit-test determines the correct placement of 3D objects in AR scenes. It involves calling `Frame.hitTest()` or `Frame.hitTestInstantPlacement()` with screen coordinates or a custom ray. Hit results include `DepthPoint`, `Plane`, `Point`, and `InstantPlacementPoint`, each suited for different surfaces and scenarios. Results are filtered based on the desired type and are used to create `Anchor`s with `HitResult.createAnchor()`, allowing content to attach to `Trackable` objects and appear in the real world.\n"],null,["# Perform hit-tests in your Android app\n\nPerform a [hit-test](/ar/develop/hit-test) to determine the correct placement of a 3D object in your scene. Correct placement ensures that the AR content is rendered at the appropriate (apparent) size.\n\nHit result types\n----------------\n\nA hit-test can yield four different types of hit results, as shown by the following table.\n\n| Hit result type | Description | Orientation | Use case | Method calls |\n|------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Depth ([`DepthPoint`](/ar/reference/java/com/google/ar/core/DepthPoint)) | Uses depth information from the entire scene to determine a point's correct depth and orientation | Perpendicular to the 3D surface | Place a virtual object on an arbitrary surface (not just on floors and walls) | **[`ArDepthMode`](/ar/reference/c/group/ar-config#ardepthmode) must be enabled for this to work.** [`Frame.hitTest(...)`](/ar/reference/java/com/google/ar/core/Frame#hitTest-motionEvent), check for [`DepthPoint`](/ar/reference/java/com/google/ar/core/DepthPoint)s in the return list |\n| [`Plane`](/ar/reference/java/com/google/ar/core/Plane) | Hits horizontal and/or vertical surfaces to determine a point's correct depth and orientation | Perpendicular to the 3D surface | Place an object on a plane (floor or wall) using the plane's full geometry. Need correct scale immediately. Fallback for the Depth hit-test | [`Frame.hitTest(...)`](/ar/reference/java/com/google/ar/core/Frame#hitTest-motionEvent), check for [`Plane`](/ar/reference/java/com/google/ar/core/Plane)s in the return list |\n| Feature point ([`Point`](/ar/reference/java/com/google/ar/core/Point)) | Relies on visual features around the point of a user tap to determine a point's correct position and orientation | Perpendicular to the 3D surface | Place an object on an arbitrary surface (not just on floors and walls) | [`Frame.hitTest(...)`](/ar/reference/java/com/google/ar/core/Frame#hitTest-motionEvent), check for [`Point`](/ar/reference/java/com/google/ar/core/Point)s in the return list |\n| Instant Placement ([`InstantPlacementPoint`](/ar/reference/java/com/google/ar/core/InstantPlacementPoint)) | Uses screen space to place content. Initially uses estimated depth provided by the app. Works instantly, but pose and actual depth will change once ARCore is able to determine actual scene geometry | +Y pointing up, opposite to gravity | Place an object on a plane (floor or wall) using the plane's full geometry where fast placement is critical, and the experience can tolerate unknown initial depth and scale | [`Frame.hitTestInstantPlacement(float, float, float)`](/ar/reference/java/com/google/ar/core/Frame#hitTestInstantPlacement-xPx-yPx-approximateDistanceMeters) |\n\nPerform a standard hit-test\n---------------------------\n\nCall [`Frame.hitTest()`](/ar/reference/java/com/google/ar/core/Frame#hitTest-motionEvent) to perform a hit-test, using the [`TapHelper`](https://github.com/google-ar/arcore-android-sdk/blob/c684bbda37e44099c273c3e5274fae6fccee293c/samples/hello_ar_java/app/src/main/java/com/google/ar/core/examples/java/common/helpers/TapHelper.java) utility to obtain [`MotionEvent`](https://developer.android.com/reference/android/view/MotionEvent)s from the AR view. \n\n### Java\n\n```java\nMotionEvent tap = tapHelper.poll();\nif (tap == null) {\n return;\n}\n\nif (usingInstantPlacement) {\n // When using Instant Placement, the value in APPROXIMATE_DISTANCE_METERS will determine\n // how far away the anchor will be placed, relative to the camera's view.\n List\u003cHitResult\u003e hitResultList =\n frame.hitTestInstantPlacement(tap.getX(), tap.getY(), APPROXIMATE_DISTANCE_METERS);\n // Hit-test results using Instant Placement will only have one result of type\n // InstantPlacementResult.\n} else {\n List\u003cHitResult\u003e hitResultList = frame.hitTest(tap);\n // TODO: Filter hitResultList to find a hit result of interest.\n}\n```\n\n### Kotlin\n\n```kotlin\nval tap = tapHelper.poll() ?: return\nval hitResultList =\n if (usingInstantPlacement) {\n // When using Instant Placement, the value in APPROXIMATE_DISTANCE_METERS will determine\n // how far away the anchor will be placed, relative to the camera's view.\n frame.hitTestInstantPlacement(tap.x, tap.y, APPROXIMATE_DISTANCE_METERS)\n // Hit-test results using Instant Placement will only have one result of type\n // InstantPlacementResult.\n } else {\n frame.hitTest(tap)\n }\n```\n\nFilter hit results based on the type you're interested in. For example, if you'd like to focus on `DepthPoint`s: \n\n### Java\n\n```java\n// Returned hit-test results are sorted by increasing distance from the camera or virtual ray's\n// origin.\n// The first hit result is often the most relevant when responding to user input.\nfor (HitResult hit : hitResultList) {\n Trackable trackable = hit.getTrackable();\n if (trackable instanceof DepthPoint) { // Replace with any type of trackable type\n // Do something with this hit result. For example, create an anchor at this point of\n // interest.\n Anchor anchor = hit.createAnchor();\n // TODO: Use this anchor in your AR experience.\n break;\n }\n}\n```\n\n### Kotlin\n\n```kotlin\n// Returned hit-test results are sorted by increasing distance from the camera or virtual ray's\n// origin.\n// The first hit result is often the most relevant when responding to user input.\nval firstHitResult =\n hitResultList.firstOrNull { hit -\u003e\n when (val trackable = hit.trackable!!) {\n is DepthPoint -\u003e true // Replace with any type of trackable type\n else -\u003e false\n }\n }\nif (firstHitResult != null) {\n // Do something with this hit result. For example, create an anchor at this point of interest.\n val anchor = firstHitResult.createAnchor()\n // TODO: Use this anchor in your AR experience.\n}\n```\n\nConduct a hit-test using an arbitrary ray and direction\n-------------------------------------------------------\n\nHit-tests are typically treated as rays from the device or device camera, but you can use [`Frame.hitTest(float[], int, float[], int)`](/ar/reference/java/com/google/ar/core/Frame#hitTest-origin3-originOffset-direction3-directionOffset) to conduct a hit-test using an arbitrary ray in world space coordinates instead of a screen-space point.\n\nCreate an Anchor using the hit result\n-------------------------------------\n\nOnce you have a hit result, you can use its pose as input to [place AR content](/ar/develop/anchors) in your scene. Use [`HitResult.createAnchor()`](/ar/reference/java/com/google/ar/core/HitResult) to create a new [`Anchor`](/ar/develop/anchors), ensuring that the content attaches to the underlying [`Trackable`](/ar/reference/java/com/google/ar/core/Trackable) of the hit result. For example, the anchor will remain attached to the detected plane for a Plane hit result, thus appearing to be part of the real world.\n\nWhat's next\n-----------\n\n- Check out the [`hello_ar_java`](https://github.com/google-ar/arcore-android-sdk/tree/master/samples/hello_ar_java) and [`hello_ar_kotlin`](https://github.com/google-ar/arcore-android-sdk/tree/master/samples/hello_ar_kotlin) sample apps on GitHub."]]