Flame provides some debugging features for the
FlameGame class. These features are enabled when
debugMode property is set to
true (or overridden to be
debugMode is enabled, each
PositionComponent will be rendered with their bounding size, and
have their positions written on the screen. This way, you can visually verify the components
boundaries and positions.
To see a working example of the debugging features of the
FlameGame, check this
The FPS reported from Flame might be a bit lower than what is reported from for example the Flutter DevTools, depending on which platform you are targeting. The source of truth for how many FPS your game is running in should be the FPS that we are reporting, since that is what our game loop is bound by.
FpsComponent can be added to anywhere in the component tree and will keep track of how many
FPS that the game is currently rendering in. If you want to display this as text in the game, use