Workflow

Below is documented a typical workflow that is used internally by the Soft8Soft team and by Verge3D users (examples include the Teapot Heater demo, Industrial Robot​ demo, e-commerce website mock-up and others).
Both the 3ds Max and Blender versions of Verge3D can be used with equal success.

Modeling

At the modeling stage middle-poly objects are created (no more than 100k tris per model is recommended). In the end, meshes are triangulated - this is not a requirement of Verge3D but rather recommended for baking maps and for better transferability between 3D editors. The normal and occlusion maps are then baked using the triangulated meshes.
At this stage Verge3D’s Sneak Peek button comes in handy to check the quality of the results in the engine.

Texturing and materials

In principle, textures for standard or physical materials (PBR shader) can be created using any suitable software. In this manual we describe how to produce a set of maps to fit in the PBR shader using Substance Painter.
The models and the maps baked at the previous stage are loaded in Substance Painter via OBJ format. Overall 3 maps are produced in this software in the end: base color/transparency, occlusion/roughness/metallic and normal. The textures are exported using the Verge3D preset for Substance Painter. Instructions and the download link to the preset can be found in the Physical material section: 3ds Max, Blender.
PBR materials are set up for relevant models as described in the above-mentioned sections of the manual, being checked with Sneak Peek in the process.

Animation

Animation clips are created for relevant model parts as usual. Skinning, whole-object, morph-target and material animation can be used to produce various effects.
You might want to provide meaningful names to animated objects so that they can be easily found in the Puzzles editor.

Project

At this stage a Verge3D project is created using the App Manager with the default configuration settings.
The default .max or .blend file with a cube is overridden by the .max or .blend file with the prepared models and exported as .glTF. Be sure to move all relevant image files in the application folder (located in verge3d/applications) too.
Alternatively, you can consider creating a project at first and working using the default .max or .blend file in the application folder just like it was recommended in the Beginner's Guide.

Puzzles

An interactive scenario is created using Puzzles for triggering animations upon clicks, outlining objects upon hovering, positioning model parts, logic checks, etc.
See more info in the [page:Puzzles Puzzles] section of this manual.

Layout and UI

In this code-less workflow the HTML-based interface is built using external web design software. Any WYSIWYG editor capable of exporting HTML/CSS/JS files can work – for example, Webflow (paid, cloud-based), Google Web Designer (free, cross-platform), Pinegrow (paid, cross-platform) and Adobe Muze (paid, discontinued) all can do this. You can, of course, build the HTML interface manually with code or using other specialized software instead.
Interface elements (menus, buttons, info boxes...) are created as part of a single web page. As it is for 3D objects, you might want to provide meaningful identifiers (denoted by the id attribute) to control elements so that they can be addressed easily in the Puzzles editor.
The key thing is to add an iframe element to the layout that is required for embedding the 3D part of an application. The src attribute of the iframe should point to the .html file generated by the App Manager:
<iframe width="100%" height="100%" frameborder="0" allowfullscreen="" src="teapot_heater.html"></iframe>
Webflow, for example, offers the so called "Embed" element that suits well for this purpose.
You can just copy and paste the above-cited line of HTML code to this element contents and the iframe will appear in the exported .html file.
Another tool, Google Web Designer, offers the "custom" component specifically for such kind of a task.
Alternatively, you can add the iframe code line to the exported .html file using a text editor, so that it looks something like this:
<body> <div> <iframe width="100%" height="100%" frameborder="0" allowfullscreen="" src="teapot_heater.html"></iframe> </div> ... </body>

Assembling

The resulting set of HTML/CSS/JS files is saved right to the root of the application folder. The new .html file (usually called index.html) becomes responsible for launching the assembled application. You can run the app by clicking on the additional blue icon that should appear in the App Manager.
The 2D and 3D parts are then logically interconnected with HTML puzzles to handle user events.
See more info in the Puzzles section of this manual.

Audio

Background music and/or event sounds can be added with Puzzles to be triggered by the user. See more info in the Puzzles section of this manual.

Asset compression

When the app it complete, you can optimize the loading of its scene files as described in the corresponding section of this manual.