Introduction to the Unity Toolkit


The toolkit exports game objects that have a camera, light or mesh component attached. The toolkit also provides built in script components to support native babylon engine features at desgin time. The toolkit's Export Inspector window provides easy access to global exportation properties. Docking this window is recommended to enable the Unity Editor game development and exportation features.

Camera Rigs

Perspective and orthographic cameras are supported. The Camera Rig component supports detailed camera control allowing easy camera type selection and specfic runtime camera mode options. Please refer to the Unity Camera documentation for details.

Scene Lighting

The toolkit exports directional, point and spot lights. Realtime lights are standard lights that illuminate the scene at runtime. Mixed lights support baked lighting and require the Subtractive lightmapper mode.

Fully baked lighting (including all area lights) are used for lightmap shadow baking at design time and will not be included in the exported scene file. This will allow for detailed lightmap baking using as many baking lights as required to achieve the best shadow effects as possible without using any of the baking light resources at runtime. Please refer to the Unity Baked Lighting documentation for details.

Scene Environment

Skyboxes for the scene are primarily controlled via the Unity Lighting Window. The default scene controller Skybox Options allow for more detailed settings at runtime. The toolkit supports native hdr, exr and dds cubemaps. Please refer to the Unity Skybox Rendering documentation for details.

Default Color Space

The preferred Color Space for realistic rendering is Linear. A significant advantage of using Linear color space is that the colors supplied to shaders within your scene will brighten linearly as light intensities increase. This can be selected using the Color Space property from Edit>Project Settings>Player settings panel.

Getting Started

The Project Setup section outlines basic project setup, scene configuration and runtime script compiler options. You can auto detect the platform script compiler locations in the Project Compiler Options section on the main export panel. Check out the Getting Started Video to get started with Babylon Toolkit style game development.

Toolkit Features

Script Components

Script Components are the primary way of attaching native babylon classes to game objects and prefabs in the editor.

The Editor Script Components are C# design-time components used to input client properties. They are not intended to execute at runtime. They are simply to allow the use of design-time editor properties for your native babylon client scripts. Each editor script specifies the native javascript or typescript backing class to use at runtime. Please refer to the Unity Component documentation for details.

The client scripts are your native babylon javascript or typescript classes that actually contain your game logic code. Each class has a ready function that gets called once during the scene execute when ready phase. A start function that gets called once during the first frame. An update function that gets called every frame. An after function that gets called after the scene render phase and a destroy function that get called on component disposal.

Scene Manager

The Scene Manager application programming interface exposes a unity like scene component development pattern. This allows script components to be attached to game objects like meshes, cameras and lights. Each component type has a ready, start, update, after and destroy function that will get called by the scene manager during it's life cycle.

Shader Materials

Shader Materials are used to assign unity standard and legacy shaders to native babylon material classes. Custom shaders are supportted if they follow the unity shader property naming standard. The universial shader material component encapsulates both Unity design time shader and babylon runtime shader information. Please refer to the Unity Material Editor documentation for details.

Collision Meshes

Collision Meshes are generated to provided simple collision for each component type (box, sphere, capsule, wheel, mesh and terrain). This allows simple geometry to be be used for physics collisions and mesh intersections instead of the original detailed geometry. Please refer to the Unity Collider Components documentation for details.

Terrain Builder

Terrain Builder options are used to export dynamic terrain geometry generation at export time. Up to 12 textures and normal maps may be used to paint terrains. Texture atlas maps are created to optimize multiple terrain splat textures. Terrain mesh colliders are supported to optimize runtime collision checking. Colliders can be segmented up to 16 x 16 low poly collision meshes that cover the orginal high poly terrain surface.

The terrain builder supports custom terrain splatmap shaders to allow design time editor access to the terrain render material. If no custom terrain splatmap material is selected, default options will be used. Please refer to the Unity Terrain Settings documentation for details.

Animation State

Animation State is supported for both transform and skeleton animations. Transform animations are used to animate the position, rotation and scale of any light, camera or mesh. Skeleton animation are used to animate the bones of a skeletal mesh. Legacy Animation controls are used to enable standard bone key frame animations only.

The newer standard Animator controls are used to enable the built-in Unity Mechanim humanoid animation rigging system. Please refer to the Unity Animation Group documentation for details.

Runtime Prefabs

Runtime Prefabs are used to allow client side prefab instantiation. Game objects that are assigned to the Babylon Prefab layer are marked for client side prefab usage and will not be enabled in the scene. The scene manager function instantiate prefab is used to create fully scipted components at runtime. The scene manager uses deep cloning with hierarchy.

Static Batching

Static Batching allows design time mesh combining. Game objects that are assigned to the Babylon Static layer are marked for mesh optimization at scene export. Meshes will automatically be grouped by material, combined, baked and serialized as a single mesh per material. Texture atlas materials are supported to increase multiple texture rendering optimizations.

Navigation Mesh support is provided by Babylon-Navigation-Mesh. A path finder for AI agents. It use the A Star and Funnel algorithms to calculate a path on a navigation mesh. The toolkit supports the unity navigation mesh generation tools to produced and serialize the navigation mesh geometry into your scene. Please refer to the Unity Navigation Mesh documentation for details.

Windows Platform

The Windows Platform toolset provides built-in support to develop hosted Universal Windows Platform applications to serve as self contained web browser application for your game projects. This allows for native platform intergration support for the Windows Runtime Library including Xbox Live Services for both ** Windows 10 PC** and Xbox One game consoles.

Babylon Art Tools

The Babylon Art Tools included in the toolkit provides a number of art tools to aid in creating optimized game ready assets.

Exported Content

Editor Script Components

The toolkit provided abstract base class Editor Script Component is the only supported script component that will be exported. All other non supported components will be ignored. The pre built toolkit components and your Custom Script Components are all derived from the base editor script component class and will be included in the exported scene.

Native JavaScript Libraries (renamed to .bjs) that are included anywhere in the Assets folder will be packaged up and included in your project script file. This allow easy packaging of third-party script packages. TypeScript definition files are supported by most IDE and should also be included for auto complete usage in your game project development.

Supported Unity Features

  • Scene
  • Assets
  • Metadata
  • Cameras
  • Name
  • Position
  • Target
  • FOV
  • LOD Groups
  • Clip Range Start
  • Clip Range End
  • Check Collisions
  • Gravity
  • Ellipsoid
  • Animations (Position)
  • Lights
  • Type (Point, Directional, Spot)
  • Name
  • Position
  • Direction
  • Spot Angle
  • Intensity
  • Diffuse Color
  • Animations (Position)
  • Shadow Maps
  • Light Maps
  • Materials
  • Name
  • Diffuse Color
  • Specular Color
  • Specular Power
  • Emissive Color
  • Alpha
  • Backface Culling
  • Diffuse Texture
  • Reflection Texture
  • Emissive Texture
  • Bump Texture
  • Physically Based Rendering
  • Metallic Setup
  • Roughness Setup
  • Specular Setup
  • Multi-Materials
  • Name
  • Child Materials
  • Textures
  • Name
  • Associated File
  • Use Alpha
  • uOffset / voffset
  • uScale / uScale
  • Meshes
  • Name
  • Geometry (Positions & Normals)
  • Position
  • Rotation
  • Scaling
  • Texture Coordinates (2 Channels)
  • Check Collisions
  • Receive & Cast Shadows
  • Animations (Position, Rotation, Scaling)
  • Skeletons (Shared Cloning)
  • Shaders
  • Vertex Shaders
  • Fragment Shaders
  • Custom Shaders
  • Layers
  • Custom Layers
  • Object Layers
  • Static Layers
  • Prefab Layers
  • Ignore Layers (Void)
  • Tagging
  • Object Tag Name
  • Custom Tag Names
  • Terrains
  • Multiple Terrains
  • Splatmap Textures
  • Tree Instances
  • Grass Patches (Under Construction)
  • Detail Prototypes (Under Construction)
  • Components
  • Mesh Filter
  • Mesh Renderer
  • Skinned Mesh Renderer
  • Collisions
  • Box Collider
  • Sphere Collider
  • Capsule Collider
  • Mesh Collider
  • Wheel Collider
  • Terrain Collider
  • Navigation
  • Navigation Mesh
  • Nav Mesh Agent
  • Off Mesh Link
  • Nav Mesh Obstacle
  • Local Multiplayer
  • Multiplayer Input
  • Multiplayer Camera
  • Miscellaneous
  • Tree Component
  • Terrain Component
  • Animator Component
  • Animation Component