HaxeFlixel / HaxeFlixel/flixel
Cache transformation calculation results
Nobody has claimed this yet.
- Dominant language
- Haxe
- Stars
- 2.2k
- Forks
- 522
- Avg merge
- 34m
- Merged PRs (30d)
- 1
Description
we need to find the way to cache transformation calculation results, which could improve perfomance due to less calculations done at each frame.
as you can see here: https://github.com/Beeblerox/flixel-spine-hx/blob/transform-sprite/source/flixel/addons/display/FlxTransformableSprite.hx#L65-L123 there are a lot of repetative calculations. and they should be reduced as much as possible.
But having multiple camera support making it harder to achieve (but not impossible i think)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with source/flixel/addons/display/FlxTransformableSprite.hx, especially lines 65-123 in the linked branch, and inspect the repeated transformation calculations. Determine how cached results could work with multiple camera support; done means reducing per-frame recalculation without breaking that support.
Written by the indexing model from the issue text.
Assessment
- Domain
- game-dev, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100