Problem with picking “gameObject” in ARCore
up vote
0
down vote
favorite
Now, I understand that in most cases picking object in ARCore has nothing to do with ARCore itself in terms of Unity but standard approach just does not work for me.
RaycastHit hitObject;
Ray ray = FirstPersonCamera.ScreenPointToRay(hit.Pose.position);
if(Physics.Raycast(ray, out hitObject)) {
if(hitObject.collider != null) {
Debug.Log(hitObject.collider.gameObject.name);
Debug.Log(hitObject.collider.gameObject.tag);
if(hitObject.collider.gameObject.tag == TAG_SCHEME_OBJECT) {
movement = false;
}
}
}
Don't mind the hit.Pose.position
I was testing very different elements here. Now the problem is:
When i touch the screen I'm putting an Andy object - perfect
I'm blocking putting the next one using
if (currentNumber < objectsAllowed && placeNext)
- works great. I can improve the limit (place more Andy`s) when I tap on button. This also works perfectThe funny thing is happening with my collider. So I have my Andy on screen and I'm tapping the screen somewhere else. My Debug.Log shows that I've tapped my Andy. And I don't mean that I have a big finger, I'm tapping like 1m away from him. Where ever I tap on screen my Debug.Log shows that I've tapped my Andy.
What I am doing wrong? This is very simple code from documentation. Why do I always receive info that my ray is colliding with the gameobject if it is not?
UPDATE:
The problems was the simplest as it can be. The collider was too big.
android unity3d raycasting arcore collider
add a comment |
up vote
0
down vote
favorite
Now, I understand that in most cases picking object in ARCore has nothing to do with ARCore itself in terms of Unity but standard approach just does not work for me.
RaycastHit hitObject;
Ray ray = FirstPersonCamera.ScreenPointToRay(hit.Pose.position);
if(Physics.Raycast(ray, out hitObject)) {
if(hitObject.collider != null) {
Debug.Log(hitObject.collider.gameObject.name);
Debug.Log(hitObject.collider.gameObject.tag);
if(hitObject.collider.gameObject.tag == TAG_SCHEME_OBJECT) {
movement = false;
}
}
}
Don't mind the hit.Pose.position
I was testing very different elements here. Now the problem is:
When i touch the screen I'm putting an Andy object - perfect
I'm blocking putting the next one using
if (currentNumber < objectsAllowed && placeNext)
- works great. I can improve the limit (place more Andy`s) when I tap on button. This also works perfectThe funny thing is happening with my collider. So I have my Andy on screen and I'm tapping the screen somewhere else. My Debug.Log shows that I've tapped my Andy. And I don't mean that I have a big finger, I'm tapping like 1m away from him. Where ever I tap on screen my Debug.Log shows that I've tapped my Andy.
What I am doing wrong? This is very simple code from documentation. Why do I always receive info that my ray is colliding with the gameobject if it is not?
UPDATE:
The problems was the simplest as it can be. The collider was too big.
android unity3d raycasting arcore collider
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Now, I understand that in most cases picking object in ARCore has nothing to do with ARCore itself in terms of Unity but standard approach just does not work for me.
RaycastHit hitObject;
Ray ray = FirstPersonCamera.ScreenPointToRay(hit.Pose.position);
if(Physics.Raycast(ray, out hitObject)) {
if(hitObject.collider != null) {
Debug.Log(hitObject.collider.gameObject.name);
Debug.Log(hitObject.collider.gameObject.tag);
if(hitObject.collider.gameObject.tag == TAG_SCHEME_OBJECT) {
movement = false;
}
}
}
Don't mind the hit.Pose.position
I was testing very different elements here. Now the problem is:
When i touch the screen I'm putting an Andy object - perfect
I'm blocking putting the next one using
if (currentNumber < objectsAllowed && placeNext)
- works great. I can improve the limit (place more Andy`s) when I tap on button. This also works perfectThe funny thing is happening with my collider. So I have my Andy on screen and I'm tapping the screen somewhere else. My Debug.Log shows that I've tapped my Andy. And I don't mean that I have a big finger, I'm tapping like 1m away from him. Where ever I tap on screen my Debug.Log shows that I've tapped my Andy.
What I am doing wrong? This is very simple code from documentation. Why do I always receive info that my ray is colliding with the gameobject if it is not?
UPDATE:
The problems was the simplest as it can be. The collider was too big.
android unity3d raycasting arcore collider
Now, I understand that in most cases picking object in ARCore has nothing to do with ARCore itself in terms of Unity but standard approach just does not work for me.
RaycastHit hitObject;
Ray ray = FirstPersonCamera.ScreenPointToRay(hit.Pose.position);
if(Physics.Raycast(ray, out hitObject)) {
if(hitObject.collider != null) {
Debug.Log(hitObject.collider.gameObject.name);
Debug.Log(hitObject.collider.gameObject.tag);
if(hitObject.collider.gameObject.tag == TAG_SCHEME_OBJECT) {
movement = false;
}
}
}
Don't mind the hit.Pose.position
I was testing very different elements here. Now the problem is:
When i touch the screen I'm putting an Andy object - perfect
I'm blocking putting the next one using
if (currentNumber < objectsAllowed && placeNext)
- works great. I can improve the limit (place more Andy`s) when I tap on button. This also works perfectThe funny thing is happening with my collider. So I have my Andy on screen and I'm tapping the screen somewhere else. My Debug.Log shows that I've tapped my Andy. And I don't mean that I have a big finger, I'm tapping like 1m away from him. Where ever I tap on screen my Debug.Log shows that I've tapped my Andy.
What I am doing wrong? This is very simple code from documentation. Why do I always receive info that my ray is colliding with the gameobject if it is not?
UPDATE:
The problems was the simplest as it can be. The collider was too big.
android unity3d raycasting arcore collider
android unity3d raycasting arcore collider
edited Nov 11 at 17:31
ARGeo
5,30052147
5,30052147
asked Nov 11 at 11:24
Fixus
3,04492761
3,04492761
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53248229%2fproblem-with-picking-gameobject-in-arcore%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown