Performance optimizations #2

New Issue

Open

opened 2021-12-14 14:45:20 +00:00 by keith · 0 comments

keith commented

2021-12-14 14:45:20 +00:00

Owner

I haven't tested with an actual game, but the engine seems a bit overcomplicated, which probably isn't good for performance.

Rendering

Rendering should be done in the actor class itself instead of a drawable component (or a drawable object that isn't a component)
~~Update drawable cache when properties change so we don't have to check active-p, tree-active-p, and has-tag every frame~~ (superseded by #8)

Transform

Actor locations should be in pixels, not "world units" (and should be integers)
Replace 3d-vectors/3d-matrices with something more optimized?

Other

Don't fire [component (parent-activated)] unnecessarily
Do a ton of testing & profiling lmao

I haven't tested with an actual game, but the engine seems a bit overcomplicated, which probably isn't good for performance. ## Rendering - [ ] Rendering should be done in the `actor` class itself instead of a `drawable` component (or a `drawable` object that isn't a component) - ~~Update drawable cache when properties change so we don't have to check `active-p`, `tree-active-p`, and `has-tag` every frame~~ (superseded by #8) ## Transform - [ ] Actor locations should be in pixels, not "world units" (and should be integers) - [ ] Replace `3d-vectors`/`3d-matrices` with something more optimized? ## Other - [x] Don't fire `[component (parent-activated)]` unnecessarily - [ ] Do a ton of testing & profiling lmao