I'd say that an important point is that the emulator uses a software OpenGL renderer, while virtually every handset in the wild does OpenGL in hardware. In my experience, you just cannot rely on the emulator to accurately render OpenGL as a hardware device would. The emulator is "sufficient to test code for correctness," as SChaser said, but it is not a pixel-perfect image of what you'll see on a handset. Most of the time, it's pretty close, but if you're seeing something funny you really need to test it on hardware before you go chasing through your code.
Something else you've probably noticed is that the emulator's OpenGL is SLOW. I know, the emulator is slow anyway, but the OpenGL seems to be the worst part. Again, the emulator should generally show you *whether* your OGL code runs, but not how well or how fast it runs. So as a starting point, you need at least one handset to test on, and the G1 is probably as good of a "reference" set as any. Unfortunately, there are also issues with how different hardware renders the same OpenGL scene - I've chased plenty of these myself. My advice is that you really could do with at least two handsets for testing OpenGL: two different resolutions (say HVGA and WVGA), from two different manufacturers. So a G1 and Droid/Milestone would be a good pair, for example. The question is, does the budget for your project justify that? String My experience over the past year On Aug 2, 8:07 pm, Bob Kerns <r...@acm.org> wrote: > Robert Green's reply gives some specific points I couldn't because I'm > not really an OpenGL person myself, and definitely illustrates how > rendering can vary. > > But while I certainly would NOT expect identical results from > different rendering engines, it does sound to me like the differences > you note go beyond what I'd expect from my somewhat limited > experience, and the extremely large coordinates does strike me as a > point of suspicion. > > On Aug 2, 10:14 am, SChaser <crotalistig...@gmail.com> wrote: > > > > > It is entirely possible that I am doing something confused (not being > > that much of an OGL person), but even then, I would expect to see the > > same results on the emulator and the G1. In answer to another > > question, the demos work fine on the emulator. > > > Is it possible that disappearing lines are caused by the emulator > > pixels not matching exactly the Windows pixels to which they are > > ultimately rendered? > > > The varying width lines didn't appear until I used extremely large > > (but within the FP range) coordinates on a few lines. > > > I'll post the code when I get home and have access to it. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
