Table of Contents
Developing any product is a creative process with many participants who have different skills and experience. However, no matter how complex it is and what is the target it’s always possible to separate the production stage in which the bulk of assets and source code is authored.
When using Blend4Web the workflow is the following:
- Creating a New Project.
- Authoring 3D scenes in Blender.
- Running, tweaking and debugging scenes in the Viewer.
- Exporting scenes.
- Application Development.
- Building the project.
- Creating the target application.
When using the local development server
it’s possible to preview current scene using
Fast Preview button located at the bottom of Blender’s 3D View window,
and also on the
Render -> Development Server panel in Blender. In this case
the scene will be exported inside some temporary storage and loaded in the
The other method is using Run in Viewer export option. In this case the scene will be displayed in the Viewer app immediately after the export.
The export procedure converts the scene from the Blender format to one of the formats used by Blend4Web.
There are two formats: JSON and HTML.
The HTML format is used for simple stand-alone applications, where all the resources are packed into one HTML file that can then be easily deployed to a web page.
The JSON format can be used for creating such projects as well, but it also offers numerous extra features making it possible to create complex projects that require programming. Format differences and export options are described in the Export Formats chapter.
To export the scene, select
Blend4Web (.json) or
option from the
File > Export menu, or type
b4w export in the
operator search menu (available by pressing
If the scene uses Blender features not yet supported by the Blend4Web engine, errors may occur during export. Export errors are listed in this table.
Export options are described in detail in the corresponding section.