search

vianziro / droidar

Automatically exported from code.google.com/p/droidar
0 stars 0 forks source link

problem visualizing graphics "sometimes" (even in the library demo program) #3

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Execute ANY program using droidar (even the test program on library)
2. only shows the buttons at bottom (if any)
3. Re Execute the program several times. 
4. it finally shows graphics. 

What is the expected output? What do you see instead?
I expected to see the graphics in the world but I only see the buttons at 
bottom (if any)

What version of the product are you using? On what operating system?
I compile the last source code, I'm running it in android 2.1-samsung galaxy 
S-not rooted

Please provide any additional information below.
*the problem is present even if I the objects aren't in movement (so it's not 
that I don't see them, its just they aren't)
*I think the problem may be because of lack of memory, but i'm not sure.
*The library app shows that my phone pass all test
*There is just one case where the app always works fine, it's the collecting 
items setup

pS: very good work, finnally some library that really understand what AR is all 
about

Original issue reported on code.google.com by david.vi...@gmail.com on 18 May 2011 at 12:01

GoogleCodeExporter commented 8 years ago 
Ok thanks for the feedback, i know this problem, its due to some strange opengl 
view+camera preview problems in android. the layers normally should be in this 
order:
1. ui
2. opengl view
3. camera preview

Due to some bugs in android the first time the app comes into foreground the 
order is 
1. ui
2. camera preview
3. opengl view

So the opengl view wont be displayed until you show something in front of the 
activity. therefor i added a InfoScreen activity (its located in the gui 
package), which will be shown for some time in front of the AR-activity to 
solve this bug. I now set the InfoScreen time to 2 seconds and it will 
disappear automatically after this 2 seconds. You said the collecting items 
setup does not have this problem, and i think its because there the info screen 
is displayed until the user closes it (take a look at the _f_addInfoScreen() 
method in the CollectItemsSetup). 
So i think 2 seconds should be enough for any device but if you want to be sure 
just show some information to the user via the _f_addInfoScreen() method. Tell 
me if there are still problems.

Original comment by simon.heinen on 27 May 2011 at 8:27

GoogleCodeExporter commented 8 years ago

Original comment by Alexande...@gmail.com on 31 May 2011 at 6:38