Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is the point of checking twice whether there are bounding boxes for the same object or not? #27

Open
Kanyade opened this issue Apr 28, 2021 · 1 comment

Comments

@Kanyade
Copy link

Kanyade commented Apr 28, 2021

We already check for them in the first place(PhoneARCamera.cs):

image

And then we check again:

image

Or am I missing something? By deleting the latter it works just as fine.

@rooi
Copy link

rooi commented Jun 18, 2021

If I'm correct the later part should filter the bounding boxes over several frames while the first part only looks at the current frame. I do notice much more bounding boxes when deleting the later part.

However, with the later part enabled, the application freezes on my iPhone when there or more then 3 bounding boxes. When I remove the following line it works, but this also disables the filtering:
this.boxSavedOutlines = temp;

Does it work for you?

Does someone have an idea on what may cause the application to freeze? I thought of some multithreading conflict to the List, but add lock (also to the AnchorCreator.cs) do not seem to work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants