Home
The blender godot exporter converts models from .blend files into escn files. Going directly from blender to godot allows better preservation of values as you aren't going through an intermediary format.
Material Search Paths
One of the most frustrating things about asset pipelines are materials. Unless you are using a well defined material workflow (eg PBR), converting materials from the design tool into ones in the engine can be quite frustrating. The blender->godot exporter handles this in two ways:
First it searches for existing godot materials where the name of the resource file matches the name of the material in blender. So if you export an object with the material PurpleDots then the exporter will search for the file PurpleDots.tres. It will do this either through the entire project directory, or limited to sub-directories of the export path. If it cannot find a PurpleDots.tres file that is a SpatialMaterial or ShaderMaterial, or if searching for materials is disabled, the exporter will attempt to export the material from blender.
In blender 2.8 the materials system will change significantly, so while the exporter currently supports some blender internal material properties, integration of cycles/eevee materials will wait until after the 2.8 release
The exporter looks at various object properties in order to determine additional properties to export beyond the geometry. The most basic of these is the "allow_render" button which prevents the object from being exported:
Exporting physics properties is done by enabling "Rigid Body" in the physics tab. The highlighted properties are exported:
Most things match fairly well but:
- Collision group is exported to both collision group and collision mask
- Active vs Passive is rigid body vs static body
- The animated checkbox enabled "kinematic"
- Cone and cylinder will not be supported (Godot doesn't support them)