Frictional Game Wiki

<h1>[Add-on] Blender Models to HPL3</h1> <div class="level1"> <pre class="code">https://github.com/cadehaley/BlenderHPL3export ("Clone or Download" -&gt; "Download ZIP") </pre><p> </p> <p> <b>HPL3 Exporter Version 1.2</b> <br/> <br/> This addon allows you to model anything from single assets<br/> to entire maps within Blender, and synchronize them to an HPL3 engine map,<br/> automatically creating and configuring textures, material, and entity files<br/> for a fast iteration process. The script is also capable of removing objects<br/> from the HPL3 map which have been removed in the Blender scene, and baking<br/> lighting onto scene objects. </p> </div> <h2>INSTALLATION (Requires Blender 2.80 or later)</h2> <div class="level2"> <p> <br/> 1. Copy "io_export_hpl3.py" and the "nvidia" folder to Blender's addons <br/> directory ("…/Blender/2.80/scripts/addons")<br/> <br/> 2. Open Blender, go to Edit > Preferences > Add-ons > Search "hpl3"<br/> <br/> 3. Check box next to "Import-Export: HPL3 Export" and press "Save Preferences"<br/> <br/> 4. Exit window and go to the Tools bar in the left side of the 3D View. Drag <br/> the width of the Tools bar out to set fields, and press T to hide the tools <br/> bar at any time. Have fun! </p> <hr /> </div> <h2>Important usage notes</h2> <div class="level2"> <p> <br/> – Give each object a unique name in the asset's "Object Data" panel <br/> (under the poly triangle icon, not to be confused with the "Object" panel <br/> under the cube icon).<br/> Example: Object name = "evil_suzanne_by_doorway.005"<br/> Mesh Datablock name = "Suzanne"<br/> <br/> On export, the subdirectory and mesh file will take this name ("Suzanne.dae"),<br/> and having name conflicts in HPL3 can cause the wrong textures to load. <br/> The "Object Name" does not matter as much, and will be used to name that <br/> instance of the object when placed in the map.<br/> <br/> – If texture is black or has black parts, make sure UV faces are<br/> within the square UV boundary. Texture baking requires that each material use<br/> a single "Principled BSDF" node and that all UV faces lie within UV <br/> coordinate bounds.<br/> <br/> – When baking multi-material, think of each material as having <br/> its own UV set. Faces assigned to Material A cannot overlap in the UV editor <br/> with other Material A faces, though it is ok (even recommended) for faces <br/> assigned to Material B to use up the full UV space, since it won't matter <br/> if a face from Material A overlaps with a face from Material B. Just make <br/> sure your mesh only uses one UV map. Check this by going to<br/> [Object Data (Poly Triangle Icon) > UV Maps], located under Vertex Groups <br/> and Shape Keys.<br/> <br/> – Use Alt+D to create copies of an object in Blender to place <br/> around a map, since they will point to the same "Mesh" datablock. Using <br/> Copy/Paste or Shift+D creates a new "Mesh" datablock every time, and therefore <br/> a new .dae and .dds file on export, leaving you with multiple repeat numbered<br/> .dae and/or .dds files taking unnecessary space on export.<br/> <br/> – In the Level Editor, if objects fail to appear after pressing <br/> the button to reload static object or entity changes, try exiting out of the <br/> editor and reloading your map to make objects appear properly again.<br/> </p> <hr /> </div> <h2>BUGS</h2> <div class="level2"> <p> <br/> For any questions or to report any bugs, message me @cadely on the Frictional <br/> Games unofficial Discord (<a href="https://discord.gg/sXKZ9R2" class="urlextern" title="https://discord.gg/sXKZ9R2" rel="nofollow">https://discord.gg/sXKZ9R2</a>) or on frictionalgames.com/forum </p> </div>