Posted by  Chris Dillman on February 10, 2004 at 11:30:33:

Hi

Just some ideas for optimizing Quesa.
Feel free to tell me if these won't work etc or if they are being worked on.

1. Eliminate any calls to glFinish();
Apple advise againts using this at all for any high speed GL application.
So is there a reason it is in Quesa?

2. Move to vertex array range in "shared" state if possible.
WC3 uses this to very good effect.

3. How about a state flag of some sort so that Quesa knows which
objects have basically become static and have not changed from frame
to frame so that it does not need to keep building them as GL calls
everyframe?

For all I know this is going on now?

Just my ideas so far after looking at nanosaur running with Quesa
using GL profiler and shark.

4. Does Quesa make a lot of sqrt calls?
Would a look up table be faster in some cases or a less accurate sqrt call?
Or is the more accurate called really needed in Quesa?

--
Email: chrisd@plaidworld.com
iChat / AIM: crackbunny@mac.com

Buy Art : http://www.starbounce.com
Listen to Music: http://www.trance-o-matic.com
Play Games: Plaid World Studios http://www.plaidworld.com
Learn game programming at http://www.idevgames.com
Day job: Software Engineer for http://www.riskwise.com, Part of LexisNexis

Responses:

Post a Response -