You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We talked a bit about it on irc a month ago,
to recall the main lines:
At some point you can have an advanced game that require lots of resource because of heavy graphics many layered elements.Having multiple layer element and implementing dirty redrawing can be very time consuming and require a complex architecture (not easy to maintain).
I actually experienced it when I wrote a rpg where I used a particule engine to generate blood explosion where blood stayed after explosion uppon the background but behind the main character.
To fix my problem I had to sacrifice my lazy redrawing and spend several days changing my game logic.
With multiple canvas I could have move background to a another canvas, and apply those blood explosion on the background canvas.
This technique also spare performance because if you have a fancy background it will not repaint it on every frame (at least not by js)
Note that we can simply keep single canvas by default, and people who would do advanced game could use this feature just by updating simply option in a constructor.
The text was updated successfully, but these errors were encountered:
We talked a bit about it on irc a month ago,
to recall the main lines:
At some point you can have an advanced game that require lots of resource because of heavy graphics many layered elements.Having multiple layer element and implementing dirty redrawing can be very time consuming and require a complex architecture (not easy to maintain).
I actually experienced it when I wrote a rpg where I used a particule engine to generate blood explosion where blood stayed after explosion uppon the background but behind the main character.
To fix my problem I had to sacrifice my lazy redrawing and spend several days changing my game logic.
With multiple canvas I could have move background to a another canvas, and apply those blood explosion on the background canvas.
This technique also spare performance because if you have a fancy background it will not repaint it on every frame (at least not by js)
Note that we can simply keep single canvas by default, and people who would do advanced game could use this feature just by updating simply option in a constructor.
The text was updated successfully, but these errors were encountered: