Re: Performance Profiling

if you want to know "what is sent to the screen" fps (what is generally done on other engines), it will correspond to the draw() 8 fps.
More the logic will take time and more it will be reflected on the screen fps anyway.

But it's good to record on the side the duration of one update call (can be slow generally because of physics or IA).

Re: Performance Profiling

I had a go with using gDEBugger, but it's made by AMD so it only really supports ATI graphics cards. It claims to also have some support NVidia too, but neither of those would help my crappy Intel graphics chip. Oh well. Back to trying to trying to do this the slow way tongue