Optimisations for GCW-Zero, Pandora

[cxong]

No description provided.

[cxong]

Profiling from visual studio on doom mission 3 shows update and draw both taking about 40% CPU. Expensive operations include:

• DrawPlayerAreas (19.63%)
• CameraDraw (17.58%)
• DrawRadar (12.69%)
• OverlapGetFirstItem (10.06%)
• CommandBadGuys (9.75%)

Two obvious optimisations: HUD is unexpectedly expensive, even more expensive than drawing the game, and also the map has lots of actors so lots of the update expense is on basic updating and collision detection.

[cxong]

FPS on GCW-Zero is about 8

[cxong]

Update AI every 4 frames; this reduced the cost of UpdateAllActors, so approximately 3% speedup.

More can be done; on this mission there are about 114 enemies. Updating a fixed number of AIs per frame (say 10) should make the AI a fixed cost. This can be improved so that enemies closer to the players are prioritised.

Next most expensive function:

• LOSCalcFrom (8.34%)

[cxong]

New profiling:

Areas to improve:

• 13.62% DrawPlayerAreas etc. - pre-draw map, use events like explore to update dynamically
• 11.61% DrawFloor - can pre-draw floor as one texture and drawing separately
• 8.95% OverlapGetFirstItem - consider not updating everything 70 times per second and using interpolation
• 7.51% DrawWallsAndThings - need more investigation; possibly mark particles as "dead" and permanently bake them into the floor?

[cxong]

Optimised DrawFloor by drawing as textures - percent of time dropped to 1.22%. Strangely now the whole game takes 75% CPU instead of 99% before.

One side effect is that the blob shadows need to be redone otherwise they don't show up properly over the floor.

• Fix blob shadows

[cxong]

Some of the optimisations have to do with rendering textures instead of to a pixel array. However we still need to render to a single "surface", for the game background and for the editor. But in this case, we should be using SDL_SetRenderTarget, so that the drawing code doesn't change. Replace the renderToTex parameters added recently.

[cxong]

Converted more blitting functions to use texture rendering. This has dropped DrawWallsAndThings from 8% down to 4%, although strangely total CPU has dropped to 50% and DrawDebris has gone up from 2% to 4%. Maybe there's some extra graphics latency here?

This has also introduced some graphics glitches. Map objects like barrels appear behind walls - perhaps walls are still being blitted. "Background" tinted objects like gas clouds no longer look right, will need to redo them.

[cxong]

Profiling results after character blitting converted to texture renders. Curiously the overall draw time hasn't reduced by much, although DrawFloor has shot up.

Need to benchmark under GCW-Zero; perhaps there is too much slowdown caused by rendering many small textures. Switching to texture atlases may be necessary.

[cxong]

Unfortunately performance on GCW-Zero has become worse, at about 6fps.

[cxong]

Abandoning this for now; will possibly revisit once we look into a handheld platform again