flutter3d
Showcase Changelog 62 packages API reference

flutter3d and Flutter Scene

Flutter Scene is the other engine built on Flutter GPU. It is maintained by the author of Flutter GPU itself, a former core Flutter engine team member who spent four years on Flutter, most of it building Impeller. That gives it a relationship with the underlying API that no third-party package can have: Scene's render tests are where Flutter GPU regressions get caught, because the author of Flutter GPU also writes the engine. flutter3d uses flutter_gpu the way any other package does, through the public surface.

The two projects are not after the same thing. Scene is a complete 3D game engine and toolkit for anyone building on Flutter, pre-1.0 and moving quickly. flutter3d started from a narrower question: whether a HAL, a scene graph and a game layer of this shape can be built by someone with no inside access to Impeller, tested against four games of different genres that needed no engine-level code changes between them. For 1.0.0 I took Scene's 0.24 as the bar to reach, and most of this page's old "Scene has, flutter3d doesn't" list moved as a result. This version of the page is as of 2026-10-12. The flutter3d half was read against the source tree of the 1.0.0-rc.1 release candidate, and its lines that had gone stale were corrected against the 1.0.0-rc.2 tree on 2026-10-20. The Scene half was read against flutter_scene 0.24.3, published on pub.dev on 2026-10-09: its README, its CHANGELOG, and the published package's source, which was searched for every capability the README does not name. Commits on Scene's main branch after 0.24.3 are not counted until they are released. Every "no" in the tables below carries that date, because each one is a claim about a project that moves every week.

Quick facts #

flutter3d Flutter Scene
First commit 2026-08-08 2024-02-01
Core package version 1.0.0-rc.2 0.24.3 (2026-10-09)
Maintainer An independent developer, unaffiliated with the Flutter team The author of Flutter GPU, formerly on the core Flutter engine team
Licence MIT MIT
Web backend WebGPU by default, WebGL2 where WebGPU does not start Built-in WebGL2
Windows and Linux Windows: games and editor built in CI, nobody has played them there yet. Linux: every test suite runs there, and since 1.0.0-rc.1 the conformance suite runs through Impeller under Xvfb on every CI run; until that run is green and a game has been played there, a Linux game draws through the CPU backend unless its runner turns Flutter GPU on Both listed as platforms; shipping a release build needs Flutter 3.47.1
Physics Its own core in C (flutter3d_physics_native, through dart:ffi natively and WebAssembly in the browser), compiled from source by a build hook, with the pure-Dart flutter3d_physics as its reference and fallback Native: flutter_scene_rapier (prebuilt binaries + wasm) or flutter_scene_box3d
Audio flutter_soloud, an FFI binding to the SoLoud engine, behind a pluggable backend interface flutter_scene_soloud, the same SoLoud engine, or flutter_scene_fmod (commercial middleware)
Input pad_input for gamepads, flutter3d_pointer_lock for mouse look, and rebindable controls with a settings screen in flutter3d_game flutter_scene_input 0.1.0, new with 0.24: rebindable actions for keyboard, mouse, gamepads and pointer lock, with contexts and saved profiles
CPU / GPU-less test backend Yes: flutter3d_cpu, a software rasteriser used in CI No backend of its own; CI renders its smoke scenes through Impeller on Mesa's software rasterisers (Linux), SwiftShader (Android emulator), headless Chrome and Windows, and Metal on Codemagic, compared in Argos
Multiplayer Rollback for two to thirty-two peers, spectators fed from the settled tape, an authoritative server with predicting clients, and a relay that holds parties (flutter3d_net, flame_multiplayer; WebSocket, WebRTC or dashwire underneath) flutter_scene_net, over dashwire: replicated state, client-side prediction, and physics rollback for the entity a client owns
Editor with an MCP server Yes: the level editor and the model editor are MCP servers in flutter3d_mcp on pub.dev; the level editor app builds for the desktop and, new in 1.0, for the browser, where it is offered by URL (download); native downloads not yet Yes: the Flutter Scene Editor 0.24.0, a desktop app with macOS, Windows and Linux downloads on its GitHub releases, not on pub.dev, and still "in active development"
Community, on 2026-10-12 32 stars on GitHub, 2 contributors; flutter3d downloaded 592 times on pub.dev in the last 30 days 914 stars on GitHub, 25 contributors; flutter_scene downloaded 22,989 times on pub.dev in the last 30 days

Feature by feature #

A green dot is a capability the engine has; a red one is a capability it does not. For flutter3d that is read from its source. For Flutter Scene it is read from its README and its CHANGELOG up to 0.24.3, and then checked against its source: a red dot there means none of the three names it in the engine's packages. Where Scene has something close in another form, the row is worded to the difference, and here is the form: god rays rather than volumetric fog, splats sorted on the CPU rather than on the GPU, a pure-Dart physics backend for queries and triggers with no dynamics, physics rollback for the one entity a client owns rather than every player's input, occlusion culling through planes an application supplies rather than a depth pyramid, and a selection outline rather than a high-contrast look. A row marked rc.3 is one flutter3d does not have in rc.2 and has scheduled for its third release candidate. Each row is one capability, so where both engines have something in different depths (physics, global illumination, the editor) the sections below say how they differ.

Capabilityflutter3dFlutter Scene
Rendering
Physically based materials with clearcoat, sheen, anisotropy and transmissionyesyes
User materials compiled for every backend, with lighting hooksyesyes
Rectangle area lightsyesyes
Clustered lights, so a scene can hold manyyesyes
Cascaded sun shadows with soft penumbrae and contact shadowsyesyes
Exponential variance shadow maps (EVSM) for the sunyesno as of 2026-10-12
Caustics under glass and wateryesno as of 2026-10-12
Irradiance probe field with a visibility test per probeyesyes
Horizon-based ambient occlusion and screen-space bounced lightyesyes
Screen-space reflections, depth of field, bloom, automatic exposureyesyes
Planar reflections, and a camera that renders into a textureyesyes
A physical sky, and fog that thins with heightyesyes
Volumetric fogyesno as of 2026-10-12
Order-independent transparencyyesno as of 2026-10-12
Motion bluryesno as of 2026-10-12
Local exposure, and HDR output (WebGPU only)yesno as of 2026-10-12
Temporal anti-aliasing, FXAA and SMAAyesyes
Lens flares, radial lens distortion and .cube LUTsyesyes
A light with a physical size, so glossy reflections widen to the emitter (a point light's radius)no as of 2026-10-12yes
A shadow-catcher material: a surface that shows only the shadows cast on it, for a model over a photo or a camera feedno as of 2026-10-12yes
External textures (video, a camera preview) as material inputsrc.3yes
Billboards and sprites that face the camerarc.3yes
Projected decalsyesyes
Orthographic cameras through every effectyesyes
Gaussian splatsyesyes
Splats sorted on the GPU (WebGPU compute)yesno as of 2026-10-12
Octahedral impostors for distant modelsyesno as of 2026-10-12
Automatic occlusion culling (Hi-Z)yesno as of 2026-10-12
Reversed depth, a near plane fitted to what is drawn, and depth layers for coplanar surfacesyesyes
A probe that names the nodes fighting over depth in a running sceneno as of 2026-10-12yes
Quality that adapts to measured frame timesyesyes
Debug views of material channels, and render stats per passyesyes
Assets and animation
Skinning, morph targets and blended animationyesyes
An animation graph: state machines, blend spaces, layers, IK after the poseyesno as of 2026-10-12
glTF material variantsyesyes
glTF animation pointers (a clip moves a material or a light)yesno as of 2026-10-12
Retargeting a clip onto another skeletonyesno as of 2026-10-12
An ETC1S (Basis Universal) encoder, so a build cooks textures to small KTX2 filesno as of 2026-10-12yes
Models converted at build time by a build hookyesyes
Hot reload for shaders, models, textures, environments and levelsyesyes
Backends
Impeller through Flutter GPUyesyes
WebGL2 in the browseryesyes
WebGPU in the browseryesno as of 2026-10-12
Shader variants for tvOS and visionOS (Apple's embedded platforms take the iOS Metal variant)no as of 2026-10-12yes
A software rasteriser in Dart, so rendering tests run without a GPUyesno as of 2026-10-12
Games
Native rigid bodies that rotate, with joints and continuous collisionyesyes
Physics through an established third-party engine (Rapier, box3d)no as of 2026-10-12yes
The same games on pure-Dart dynamics when the native core is not thereyesno as of 2026-10-12
Ragdollsyesno as of 2026-10-12
Cloth in the engine's packagesyesno as of 2026-10-12
Liquids, floating bodies, heat and fire in the physicsyesno as of 2026-10-12
Particlesyesyes
Audio through SoLoudyesyes
Rebindable input with gamepads and pointer lockyesyes
Multiplayer with a server and client-side predictionyesyes
Rollback of every player's input, for parties of more than twoyesno as of 2026-10-12
Navigation meshes and behaviour treesyesno as of 2026-10-12
A run recorded and replayed to the bit, with a time-travel debuggeryesno as of 2026-10-12
Levels generated from a seed (wave function collapse, erosion)yesno as of 2026-10-12
Voxel worldsyesno as of 2026-10-12
Genre packages: shooter, platformer, racing, strategyyesno as of 2026-10-12
A bridge to the Flame 2D engineyesno as of 2026-10-12
Tools and app integration
A scene editor with an MCP server for coding agentsyesyes
Editor downloads for macOS, Windows and Linuxno as of 2026-10-12yes
Render stats and the frame's draws, read by an agent over MCPyesyes
Agent skills shipped with the packagesyesyes
A declarative widget API for the sceneyesyes
The scene described to a screen readerpartly; Scene3D(semantics:) in rc.3yes
A high-contrast look with outlines, and colour-vision correctionyesno as of 2026-10-12

What Scene has that flutter3d doesn't #

Reading its README and CHANGELOG against flutter3d's own feature table:

Most of what this list held in 0.8 is now on both sides of the table. Reversed depth and depth layers, SMAA, lens flares, radial distortion and .cube LUTs; hot reload of models, textures, environments and levels as well as shaders; a declarative widget API (Scene3D with Node3D, Mesh3D, Model3D and the rest, which mounts nodes of an ordinary scene); rotating bodies with joints. Global illumination and temporal anti-aliasing had already moved off in 0.8. In each case Scene had it first, and in some it still goes further: its SMAA tunes its search at runtime where flutter3d has the 1x mode only, and its hot reload patches a changed scene document into the live graph in place.

What flutter3d has that Scene doesn't #

I read these as different bets on where a young engine spends its first months. Scene put more than two and a half years into rendering depth, physics and audio on established engines, an editor people can download, and the platforms it runs on, with a maintainer who wrote Flutter GPU. flutter3d spent the months before its 1.0 catching up on the renderer and the API, and put the rest into the simulation: deterministic runs, tools for building games on top of them, and a software rendering backend in Dart, so rendering tests need no GPU and no graphics driver. Scene is pre-1.0 and flutter3d is at its second 1.0 release candidate; both are MIT, both sit on the same `flutter_gpu` foundation.

Picking one #

If a project needs physics that other people have already shipped, FMOD, an editor to download today, Windows and Linux through Impeller, or tools that find z-fighting for you, Scene already has it, and I would pick Scene. If a project's constraints run the other way (physics that has to work with no native code when it must, rendering tests that run with no GPU or graphics driver inside flutter test, WebGPU, replays and rollback that hold to the bit, or an interest in how the genre-package split holds up across four real games), flutter3d is built to show exactly that.