Anybody willing to do a small test?

[EgonOlsen]

Looks fine. Your water has the same accuracy issues as mine, the Samsung Galaxy S obviously doesn't suffer from those. But that's no problem IMHO. I'll upload a version with a real benchmark path and trees soon.

[EgonOlsen]

Updated the APK again with the mentioned changes. It's a "real" benchmark run now with a result at the end. On my phone, performance is down to 1fps (giving me 1000 points... !!

[raft]

fps 13.77
score:13770

[EgonOlsen]

Many thanks. So the Nexus One is 13 times faster in this test than my phone...can't wait to see some Galaxy S results.

BTW: Today i saw some An3DBench results from the Nexus One under 2.3. It's quite an improvement when compared to 2.2 (around 20%)...nice...

[Thomas.]

Galaxy S : 26,07 / 26070

[EgonOlsen]

Wow! 26 times faster than my phone...i'm about to cry...

Edit: For the record:

Samsung Galaxy: 1.01 fps / 1010 points.

[Thomas.]

How many polygons are rendering? Only 26 fps on galaxy S, it is not good

[EgonOlsen]

Around 140.000 triangles/frame (not all are visible of course).

Edit: triangle count is only one part of the equation, the other one is object count. The test renders the water and the terrain in large chunks, but each tree is an individual object. The test has 500 trees visible (out of 3000 for the whole terrain) at a time at max. Has anybody noticed some tree popping, i.e. trees that are there in one frame but disappear in the other? That might happen if the number of visible trees exceeds the tree pool size of 500...but i can't try this for myself as my frame rate is so low.

[paulscode]

Droid X, Android 2.2 results:

Terrain rendering: 13.82 fps
TOTAL SCORE: 13820

[raft]

i havent noticed any flopping

[EgonOlsen]

Me neither...i had the possibility to run it on a Galaxy S. Lens flare textures still look bad though...i don't really know what to do here. There's no point in dithering black areas. I've no idea why it's doing this...

[keaukraine]

HTC Desire 2.2

32bit, VBO on:
14.47fps
score 1440

Absolutely the same results w/ 16bit, VBO off o_O

Water looks ugly in parts where it intersects w/ terrain. I noticed this hardware issue in my apps as well.

[EgonOlsen]

Yes, it's an accuracy issue with the zbuffer on Qualcomm chips. There's nothing i can do about this, so i'll simply live with it.

[EgonOlsen]

Sorry for bothering you all again, but i need more feedback... I've replaced the terrain test with another one on which i need some performance feedback. This time it's (unlike the terrain) not very gpu intense, but very cpu/vm intense. On my phone, it runs @2+fps...again.

Screen shot of how it's supposed to look like:


Download: http://www.jpct.net/jpct-ae/download/tmp/An3DBenchXL.apk

[Thomas.]

39,58fps on galaxy S with 2.2.1... very nice test