On Tuesday, 26 December 2006 at 2:37, Dennis Schridde wrote:
> I just profiled Warzone using gDEBugger.
>
> The logs are horrible and attached.
> (I monitored ~3 frames)
>
> Basically it looks like this:
> Lots of Matrix popping
Which is bad, especially if uses any glGetWhatever functions, those just
kill performance (I think the shadow code uses that).
> Lots of texture binding
Shouldn't be too bad, just uses up memory.
> Lots of redundant enabling of various things
Yeah, well, like I already said, the graphics engine is not really
suited for OpenGL. That's the one thing that really slows the game down,
and no changes to any other code can change anything about that.
> When looking at the profiler output you'll see that Warzone loads all
> textures
> again and again, everytime I exit to mainmenu or start a new game.
> (Allways increases the number of loaded textures by 30.)
> For easier understanding of the CSV: When about 50k GL calls are executed we
> are in the game, otherwise in the menu or somewhere in between.
--
Well, I think Perl should run faster than C. :-)
-- Larry Wall in <[EMAIL PROTECTED]>
_______________________________________________
Warzone-dev mailing list
[email protected]
https://mail.gna.org/listinfo/warzone-dev
