Scene Lab
An open source project by FPL.
 All Classes Namespaces Files Functions Pages
Scene Lab


Scene Lab is a library that allows game developers who are using Fun Propulsion Labs technologies for their games to lay out objects in the game world and change their properties, all within the game itself.

Go to our landing page to browse our documentation and see some examples.


This initial release of Scene Lab is focused on letting you perform certain core tasks needed for editing a game world:

  • Fly around the game world with mouse and keyboard to look at the current layout.
  • Right-click to enter edit mode, which allows you to:
    • Click on entities to select them and view their properties.
    • Move, rotate, and scale entities in the game world by dragging with the mouse.
    • Edit properties of an entity via a text-based FlatBuffer editor.
    • Duplicate or delete entities in the game world.
  • Save in-game entities to a binary FlatBuffer file that can be loaded back into your game, and optionally to JSON files.


The library is written in portable C++ and has been tested on the following platforms:

Important: The Scene Lab world editor uses submodules, so download the source using:

git clone --recursive


Scene Lab depends on the following libraries:

This initial version of Scene Lab only supports desktop (Linux, Mac, Windows) builds.

In order to use Scene Lab to lay out your scene, you must use CORGI and its included component library for your in-game objects. Your objects should use the following components:

  • MetaComponent (all objects must have this)
  • TransformComponent (for moving / rotating / scaling objects)
  • PhysicsComponent (optional, for selecting objects with the mouse)
  • RenderMeshComponent (optional, for highlighting the selected object)

You must also use an entity factory based on the component library's EntityFactory, which uses a prototype-based system for instantiating entities, and ensure that you have included the EditOptionsComponent and associated data in your code.

Additionally, if you have any custom components, you must implement their ExportRawData functions if you want the user to be able to edit an object's properties from those components.


For application on Google Play that integrate this tool, usage is tracked. This tracking is done automatically using the embedded version string (kSceneLabVersionString), and helps us continue to optimize it. Aside from consuming a few extra bytes in your application binary, it shouldn't affect your application at all. We use this information to let us know if Scene Lab is useful and if we should continue to invest in it. Since this is open source, you are free to remove the version string but we would appreciate if you would leave it in.


To contribute to this project see CONTRIBUTING.