Anybody willing to do a small test?

[EgonOlsen]

I'm thinking about doing a version of An3DBench for faster devices, but i don't have access to one. I need to know how fast a current device actually is under load to tailor the tests accordingly. I've created a little terrain hack and would be interested in the frame rate. So if anybody with a fast device is willing to test it, i would be very grateful. Here it is: http://www.jpct.net/jpct-ae/download/tmp/An3DBenchXL.apk
It loads a terrain and runs forward in a straight line in fixed intervals, i.e. no timing or even an end (just exit the test with the home button). It logs fps to the console and i would be very interested in three things:

• the hardware/Android version being used
• does it look ok?
• and finally: the fps!

Here's how it is supposed to look (including z-accuracy problems that occur on my phone):


On my Samsung Galaxy with 1.5, it runs @ 2fps...i expected less, so it's actually not that bad...

[Thomas.]

I tested it, but I dont know how can I gen some results... console? what is it? ...

[EgonOlsen]

The DDMS logcat tab in Eclipse shows it for example. Or, if you are on the phone only, Android System Information (available in the market) can display it.

[raft]

* stock N1 / Android 2.1
* it looks mostly ok. there are some tiny vibrations on some parts, possibly related with z-accuracy thingy. but mountains look gray as opposed to green ones in your screenshot
* starts with 16fps and increases up to 32 fps (when nothing seen)

here is a shot. dony worry about vertical lines. it happens since eclipse cant capture screen atomically

[EgonOlsen]

Performance is ok, but it looks like as if your phone/driver doesn't care about vertex alpha...too bad...

[Thomas.]

On Galaxy S with custom tweaked 2.2.1 starts with 38fps and 43fps when is nothing to see... looks be fine

[EgonOlsen]

Fine means that there is some green visible? On which kind of device?

Edit: Sorry, i somehow missed that Galaxy S part...

[raft]

Performance is ok, but it looks like as if your phone/driver doesn't care about vertex alpha...too bad...

maybe updating to 2.2 fixes it. i'll retry it when i upgrade (dont now when)

[Thomas.]

You are very fast, I edited my post... It looks same as your screenshot

[paulscode]

On my Droid X, Android 2.2, it runs at a steady 21-22 fps, and looks gorgeous (edit: that is when the mountains are visible, goes up a couple fps once nothing is visible, of course)

[EgonOlsen]

Looks like as if the Nexus One has a problem with vertex alpha while other phones (including my sucky Samsung) work fine. That's pretty sad, because i can't use this feature in this test then, which will make the terrain look much more dull. I will increase the polygon count instead and add some trees, i think...

[EgonOlsen]

Updated the test with a version that doesn't use vertex alpha but some lens flares and lighting effects instead. Does that work on Nexus One? It works fine on my phone except for some z-fighting in the water which creates a kind of saw tooths at the coasts...but i can live with that.

[Thomas.]

On galaxy S with 2.2.1 it is running about 42fps, but I think that textures of lenses are bad... scene is nice

[EgonOlsen]

The textures are actually fine, but the rendering isn't that good. The gpu somehow thinks that dithering the black parts is needed...i've no idea why, it's the same on my phone. I'll see if i can fix this...

[raft]

seemed ok to me. but not sure?