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

azimuth problem #9

Open
costamatrix opened this issue Apr 26, 2011 · 5 comments
Open

azimuth problem #9

costamatrix opened this issue Apr 26, 2011 · 5 comments

Comments

@costamatrix
Copy link

Hi Zac...thanks for this wonderful project...

i got a problem....on your example when you turn the iphone slighly to the left or right, in an angle different from the 90o the points start to "run" to the sides and disappear.... you know this...

there is a way to simply fix this points on the screen disregarding the angle of the iphone?

thx for your help!

@nielswh
Copy link

nielswh commented Nov 20, 2011

Check out this fork. I fixed this issue.
https://github.com/nielswh/iPhone-AR-Toolkit

@Tibolte
Copy link

Tibolte commented Oct 8, 2012

Hi!
I'm also working on this location-based augmented reality. Now, I've got the same problem. It works like a charm most of the time, but sometimes the markers on the screen jump suddenly to another position, or "run" as you say costamatrix. I'd like to keep them fixed on the screen. I looked at your fork nielswh, but I did'n't get how you did to fix this issue, could you explain it please?

@Tibolte
Copy link

Tibolte commented Oct 16, 2012

Get it! Figured out later by myself ;)

@hanneslarsson
Copy link

please explain what you figured out Tibolte, I'm having the same problem

@Tibolte
Copy link

Tibolte commented Oct 19, 2012

Hi,

First I don't really know if my question was suiting this topic. My problem was that at a specific range of azimuth my annotations were suddenly disappearing (in landscape mode), strange... The thing is, when you rotate your device, you have to adjust your azimuth by substracting 90° for example (landscape right), here you get the range from Portrait [90;359] becoming [-269;-1], you have to add 360° to correct it, it looked like having a "ghost range".

Another thing is, I got a jumpy problem, at first I was thinking I asked too much performance to the device, but I forgot to use pointers, and the problem was solved. The critical point was when we update the locations, we should use a pointer to point at our current azimuth while we are calling the function to calculate the delta azimuth between our current location and the location being processed. Before I wasn't doing it, and now it is much smoother.

I don't really know if I answered your question, but I hope it will help some people who will perhaps find this topic!

@zac zac closed this as completed Apr 4, 2013
@zac zac reopened this Apr 4, 2013
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

5 participants