stden / kwaak3

Automatically exported from code.google.com/p/kwaak3
0 stars 0 forks source link

Worst performance on Froyo.... #73

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Update to froyo
2.
3.

What is the expected output? What do you see instead?
Laggier than 2.1, even when 2.2 is meant to be 4 times faster (or at least 
faster at all)

What version of the product are you using? On what operating system?

Please provide any additional information below.
As soon as I updated to Froyo I started to get worse performance. I start a 
level at around 40 fps, then it drops to around 20, and in open areas it drops 
to around 6.

It COULD be that I enabled to show FPS as soon as I got Froyo, but I doubt that 
would make a difference.
If you look at the video I made on 2.1 (YouTube: Quake 3 running on a nexus 
one) it actually runs well. Now it just lagsss like crazy on the same level.
I doubt low RAM would be the issue because 2.2 allows all 512mb to be used.

Original issue reported on code.google.com by hajamoo...@gmail.com on 29 Jun 2010 at 5:41

GoogleCodeExporter commented 9 years ago
The big performance improvements refer to Java code. This Quake3 port is 99.99% 
C code and was already fast. Froyo won't bring improvements for this.

I have done some benchmarking on my nexus one (this benchmarking stuff will 
appear in a new build soon). Using default settings with or without audio you 
get respectively 19.5fps and 21.3fps. If lightmaps (a form of lighting) are 
disabled, the performance improves to 25fps and 28.4fps, that's under heavy 
situations.

At the start of a map (except for the first intro map) performance looks 
decent, not sure what fps though.

Original comment by thunderb...@gmail.com on 11 Jul 2010 at 1:08

GoogleCodeExporter commented 9 years ago
Even if this was an issue. I can't do that much about it because I'm fully in 
native code. What I can say is that on Gingerbread on my Nexus One, performance 
improved quite a bit (from 26 to 30 fps without lightmaps).

Original comment by thunderb...@gmail.com on 4 Mar 2011 at 5:38