Comments on: Android 3D game tutorial – Part II

By: freddyrock

freddyrock — Thu, 11 Aug 2011 09:46:26 +0000

Thanks for this tutorial Martin! Really useful stuff, and everything works great so far

By: Borange

Borange — Tue, 05 Jul 2011 12:04:27 +0000

Thanks for these great tutorials, it works fine, like a pancake for me.

Cheers

By: emre

emre — Sun, 24 Apr 2011 18:34:34 +0000

Sorry, you are right. Thanks again for the tutorial and quick responses.

By: Martin

Martin — Sat, 23 Apr 2011 10:00:53 +0000

But a vertex has 3 float values, so you need to calculate 3 vertices with 3 values each with a size of 4 bytes. Thats 3 * 3 * 4.

By: emre

emre — Sat, 23 Apr 2011 09:26:48 +0000

There is a redundant ’3′ in the first line of inittriangle I think.

1	ByteBuffer vbb = ByteBuffer.allocateDirect(_nrOfVertices * 3 * 4);

_nrofvertices is already 3

By: Sasi

Sasi — Thu, 21 Apr 2011 06:54:20 +0000

Dear bVada,
it should be ” _nrOfVertices*3*4 ” because each vertex has three float values(x,y,z).
and each of those floats are four bytes long.
that’s why we use ” _nrOfVertices* 3 *4 “

By: Daniel

Daniel — Sun, 20 Mar 2011 02:33:29 +0000

Why use FloatBuffer (NIO) instead of a float[]? Is FloatBuffer faster than a simple array?

Thx again!

By: bVada

bVada — Wed, 02 Feb 2011 08:04:56 +0000

Martin,

Shouldn’t

ByteBuffer.allocateDirect(_nrOfVertices*3*4);

ByteBuffer.allocateDirect(_nrOfVertices*4);

instead? Thanks for great tutorial!

By: Martin

Martin — Wed, 12 Jan 2011 17:47:10 +0000

If you have time to update the tutorial, feel free to do it. I appreciate every help I can get. At the time this series was written, version 2.0.1 was the newest one. Every one who complains about my tutorials is invited to write better one. I will be happy to publish them.

By: Richard

Richard — Wed, 12 Jan 2011 17:19:38 +0000

How about this… Everyone who makes tutorials or examples ALWAYS uses an earlier version of the SDK which half the code isn’t used anymore or the names changed… I.E basically obsolete…Try making the example WORK for the CURRENT SDK instead of making it work for 1.5 which is completely different from the SDK 2.0 or 2.2 or 2.2 or even 2.3 at most… This is why half cant get it to work…