Blender HPL3 export plugin
This addon allows you to model anything from single assets to entire maps within Blender, and synchronize them to an HPL3 engine map, automatically creating and configuring textures, material, and entity files for a fast iteration process. The script is also capable of removing objects from the HPL3 map which have been removed in the Blender scene, exporting rigged and animated objects, and baking lighting onto scene objects.
Add-on homepage: GitHub
The add-on requires Blender 2.80 or later.
- Go to GitHub → "Clone or Download" → "Download ZIP"
/nvidiafolder to Blender's addons directory (
- Open Blender, go to Edit → Preferences → Add-ons → Search "hpl3"
- Check box next to Import-Export: HPL3 Export and press Save Preferences
- Exit window and go to the Tools bar in the left side of the 3D View. Drag the width of the Tools bar out to set fields, and press T to hide the tools bar at any time. Have fun!
Important usage notes
On export, the sub directory and mesh file will take this name
Suzanne.dae, and having name conflicts in HPL3 can cause the wrong textures to load. The
Object Name does not matter as much, and will be used to name that instance of the object when placed in the map.
Give each object a unique name in the asset's
Object Data panel (under the poly triangle icon, not to be confused with the
Object panel under the cube icon). Example:
Object name = "evil_suzanne_by_doorway.005" Mesh Datablock name = "Suzanne"
- Rigged Meshes: Use
Single Exportwhen you have an animated mesh broken into separate objects (e.g. shirt, head, hair) that are deformed by the same armature (skeleton). Exporting meshes that are deformed by different armatures to one file/entity is not supported by HPL3 and will produce unexpected results.
- Baking Modes: Textures Per Material: Think of each material as having its own UV set. Faces assigned to Material A cannot overlap in the UV editor with other Material A faces, though it is ok (even recommended) for faces assigned to Material B to use up the full UV space, since it won't matter if a face from Material A overlaps with a face from Material B.
- Textures Per Material: Think of each material as having its own UV set. Faces assigned to Material A cannot overlap in the UV editor with other Material A faces, though it is ok (even recommended) for faces assigned to Material B to use up the full UV space, since it won't matter if a face from Material A overlaps with a face from Material B.
- Instancing: Use
Alt+Dto create copies of an object in Blender to place around a map, since they will point to the same
Meshdatablock. Using Copy/Paste or Shift+D creates a new
Meshdatablock every time, and therefore a new .dae and .dds file on export, leaving you with multiple repeat numbered .dae and/or .dds files taking unnecessary space on export.
- If texture is black or has black parts, make sure UV faces are within the square UV boundary. Texture baking requires that each material use a single
Principled BSDFnode and that all UV faces lie within UV coordinate bounds
- Hover your pointer over options for more in-depth info on how to use them
- When using
Textures Per Material, if texture is black or has black parts, make sure objects are UV unwrapped and UV faces are within the UV boundary. This mode requires that all UV faces lie within UV image bounds.
- If materials are failing to export properly, try switching between
Textures Per Materialand
Textures Per Object, as one mode may work better with your material setup than the other. Also, keep in mind that texture baking requires that each material use a single
- In the Level Editor, if objects fail to appear after pressing the button to reload static object or entity changes, try exiting out of the editor and reloading your map to make objects appear properly again.