The engine's log
flutter_scene writes what it has to say with Flutter's debugPrint: bare lines beside the app's log. The starter takes them into the application's log, under the logger flutter_scene.
Why
A bare line has no time and no level, cannot be turned down, and does not reach where the app's log goes. As records of a logger, the engine's messages have a time and a level, go where the app's log goes (the debug panel's Logs tab too), and are set like any logger.
Example
2026-11-13T19:35:55.592+02:00 INFO 48654 --- [main] flutter_scene : Unpacking glTF (nodes: 1, meshes: 1, materials: 1, skins: 0, animations: 0)
2026-11-13T19:35:55.933+02:00 WARN 48654 --- [main] flutter_scene : pipeline build took 66ms mid-frame. Draw this material once during a load screen...
# lib/resources/application.yml
logging:
level:
flutter_scene: warn # only what went wrong
The levels
A message that tells of trouble (failed, skipped, missing, a program built in the middle of a frame) is a warning; the rest is info.
Which messages are the engine's
debugPrint is one function for all of Flutter, so the engine's messages are told apart:
- by how the engine begins them (
flutter_scene:,fscene:,glTF import:...); - outside a release build, by where the call came from.
Everything else goes on to debugPrint as it was. Not caught: the few lines the engine writes with print.
The property
| Key | Type | Default | Meaning |
|---|---|---|---|
spring.flutter.scene.engine-log |
bool | true |
Whether the engine's messages are records of the application's log; false leaves debugPrint alone |
logging.level.flutter_scene |
log level | the root's | The level of the engine's logger, as for any logger |
The bean is sceneEngineLog (SceneEngineLog). It exists with scenes on and engine-log not false, and gives debugPrint back when the application closes.