Thanks
Matt
--
You received this message because you are subscribed to the Google Groups "android-ndk" group.
To post to this group, send email to andro...@googlegroups.com.
To unsubscribe from this group, send email to android-ndk...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-ndk?hl=en.
Thanks
Matt
> <mailto:andro...@googlegroups.com>.
> To unsubscribe from this group, send email to
> android-ndk...@googlegroups.com
> <mailto:android-ndk%2Bunsu...@googlegroups.com>.
On 7 Mrz., 10:56, Matt McMinn <matt.mcm...@gmail.com> wrote:
> Nothing concrete yet, we just got in to trying to get things running on
> a phone, so we haven't gotten in to it too much. At this point, I think
> I'm just hoping that as we get things ported to GLES, the rendering in
> the emulator and on the phone converge to render pretty much the same.
>
> Thanks
>
> Matt
>
> On 3/6/2010 5:26 PM, David Turner wrote:
>
> > OpenGL ES leaves certain things open to the implementation, even when
> > rendering,
> > so pixel-level differences are likely to occur between devices using
> > different GLES implementations (the Droid uses its GPU, while the
> > emulator uses its own software
> > renderer)
>
> > Do you have concrete information about these differences ?
>
The same app works fine on the G1 and Droid:
http://imgur.com/Da4c4.png
These surfaces are pretty close, not at the distance where I would
expect z-fighting. Using GLSurfaceView's
setDebugFlags(DEBUG_CHECK_GL_ERROR) doesn't reveal any errors in the
code.
A recent Motorola podcast with an Android game developer also
mentioned problems with the emulator:
http://community.developer.motorola.com/t5/MOTODEV-Blog/Game-Development-on-Android-with-Bendroid-agamedev25/ba-p/4406
So I guess it is pretty common.