User Tools

Site Tools


hpl3:community:editors:blender_to_hpl3

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
hpl3:community:editors:blender_to_hpl3 [2019/12/05 00:43]
cadely
hpl3:community:editors:blender_to_hpl3 [2020/07/02 01:23] (current)
cadely
Line 1: Line 1:
 ====== [Add-on] Blender to HPL3 ====== ====== [Add-on] Blender to HPL3 ======
  
-{{https://​i.imgur.com/​OQY35kC.jpg?​nolink&​743x511}}+---- 
 + 
 +{{https://​i.imgur.com/​1PrPPuD.jpg?​nolink&​546x345}}
  
 [[https://​github.com/​cadehaley/​BlenderHPL3export|https://​github.com/​cadehaley/​BlenderHPL3export]] [[https://​github.com/​cadehaley/​BlenderHPL3export|https://​github.com/​cadehaley/​BlenderHPL3export]]
Line 7: Line 9:
 To Download: (GitHub → "Clone or Download"​ → "​Download ZIP") To Download: (GitHub → "Clone or Download"​ → "​Download ZIP")
  
-**HPL3 Exporter Version ​2.0** \\+**HPL3 Exporter Version ​3.1** \\
 \\ \\
 This addon allows you to model anything from single assets\\ This addon allows you to model anything from single assets\\
Line 39: Line 41:
  
   * **Rigged Meshes**: Use "​Single Export"​ when 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.   * **Rigged Meshes**: Use "​Single Export"​ when 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.
-  * **One Texture Set Per Material**: When baking multi-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.+  * **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.
   * **Instancing**:​ Use ''​Alt+D'' ​ to create copies of an object in Blender to place around a map, since they will point to the same "​Mesh"​ datablock. Using Copy/Paste or Shift+D creates a new "​Mesh"​ datablock 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.   * **Instancing**:​ Use ''​Alt+D'' ​ to create copies of an object in Blender to place around a map, since they will point to the same "​Mesh"​ datablock. Using Copy/Paste or Shift+D creates a new "​Mesh"​ datablock 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.
 ===== Troubleshooting ===== ===== Troubleshooting =====
Line 45: Line 48:
 ---- ----
  
-  * 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 BSDF''  ​node 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 
-  * 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.+  * 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 Material"​ and "​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 ​`Principled BSDFnode 
 +  * 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.
  
 ===== BUGS ===== ===== BUGS =====
Line 52: Line 57:
 ---- ----
  
-For any questions or to report any bugs, message me @cadely on the [[https://​discordapp.com/​invite/​frictionalgames|Frictional Games Discord]] or on [[https://​github.com/​cadehaley/​BlenderHPL3export/​blob/​master/​frictionalgames.com/​forum|frictionalgames.com/​forum]]+For any questions or to report any bugs, message me @cadely on the [[https://​discordapp.com/​invite/​frictionalgames|Frictional Games Discord]] or on [[http://​frictionalgames.com/​forum|frictionalgames.com/​forum]]
  
hpl3/community/editors/blender_to_hpl3.1575506615.txt.gz · Last modified: 2019/12/05 00:43 by cadely