San Angeles demo runs at 1.5fps on iPhone device

[GoogleCodeExporter]

1. Compile SanAngeles demo in Device | Release mode
2. Copy to device
3. Run SanAngeles
4. Observe extremely poor FPS and severe graphical artifacts

I'm syncd to revision 76.

Is this a known issue, or am I doing something wrong?

Original issue reported on code.google.com by robert.w...@gmail.com on 22 Aug 2008 at 7:10

[GoogleCodeExporter]

I observed that many of the projects are set to compile w/ the thumb 
instruction set.  Disabling this option 
substantially improves performance, but not in the case of the San Angeles demo.

Original comment by robert.w...@gmail.com on 22 Aug 2008 at 7:17

[GoogleCodeExporter]

That's a known issue. The graphical artefacts are because of a known bug in the
run-time that will be fixed and the poor performance is because the geometry is 
not
properly batched and there is no culling going on.

Original comment by wolfgang...@gmail.com on 22 Aug 2008 at 1:40

[GoogleCodeExporter]

With the 2.1 firmware the graphics artifacts appear to be fixed, however the
performance is still slow as expected.

Original comment by tpur...@gmail.com on 13 Sep 2008 at 1:14

[GoogleCodeExporter]

Thanks for letting me know the 2.1 firmware fix. I will look into it and report 
back 
what I see :-) and then try to fix it.

Original comment by wolfgang...@gmail.com on 13 Sep 2008 at 1:40

[GoogleCodeExporter]

Ok it runs with 3.5 fps now ... does that fix the issue :-) ... just kidding.

Original comment by wolfgang...@gmail.com on 24 Dec 2008 at 6:28

[GoogleCodeExporter]

Added AABBox culling. Now, it's run in almost-acceptable FPS (30+FPS in 
average) - I will optimize more.

Original comment by mozeal on 30 Jul 2009 at 4:28

[GoogleCodeExporter]

Fixed ... runs 60 fps on the iPad :-)

Original comment by wolfgang...@gmail.com on 21 Apr 2010 at 7:14

• Changed state: Fixed