HPL3/Blender HPL3 export plugin - Revision history

Darkfire: Added further reading link

2020-11-09T19:51:45Z

Added further reading link

Darkfire: removed bad line breaks

2020-11-09T19:41:41Z

removed bad line breaks

Darkfire: remove old title

2020-11-09T19:41:15Z

remove old title

Darkfire: Darkfire moved page Hpl3:Community:editors:blender to hpl3 to HPL3/Blender HPL3 export plugin without leaving a redirect: Moving to the main namespace

2020-11-09T19:40:55Z

Darkfire moved page Hpl3:Community:editors:blender to hpl3 to HPL3/Blender HPL3 export plugin without leaving a redirect: Moving to the main namespace

Darkfire: no toc

2020-11-09T19:36:14Z

no toc

Darkfire: formatting

2020-11-09T19:31:21Z

formatting

Darkfire: Added categories

2020-11-09T19:26:12Z

Added categories

Darkfire: /* Troubleshooting */ merging

2020-11-09T19:25:42Z

Troubleshooting: merging

Darkfire: /* Important usage notes */ removed bad html tags

2020-11-09T19:25:06Z

Important usage notes: removed bad html tags

Darkfire: /* Important usage notes */ merging from the other article

2020-11-09T19:23:52Z

Important usage notes: merging from the other article

← Older revision		Revision as of 19:51, 9 November 2020
Line 43:		Line 43:

	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]		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]
		+
		+	== Further reading ==
		+
		+	* [[Blender \| Working with Blender for HPL]]

@@ Line 1: / Line 1: @@
 {{shortPageTitle}}
 __NOTOC__
 [[Category:Modding]]
 [[Category:English]]
 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.

← Older revision		Revision as of 19:41, 9 November 2020
Line 1:		Line 1:
−	~~= [Add-on] Blender to HPL3 =~~
	{{shortPageTitle}}		{{shortPageTitle}}
	__NOTOC__		__NOTOC__

← Older revision		Revision as of 19:36, 9 November 2020
Line 1:		Line 1:
	= [Add-on] Blender to HPL3 =		= [Add-on] Blender to HPL3 =
		+	{{shortPageTitle}}
		+	__NOTOC__

	[[Category:Modding]]		[[Category:Modding]]

← Older revision		Revision as of 19:31, 9 November 2020
Line 7:		Line 7:

	Add-on homepage: [https://github.com/cadehaley/BlenderHPL3export GitHub]		Add-on homepage: [https://github.com/cadehaley/BlenderHPL3export GitHub]
−

	== Installation ==		== Installation ==

← Older revision	Revision as of 19:40, 9 November 2020
(No difference)

← Older revision		Revision as of 19:26, 9 November 2020
Line 1:		Line 1:
	= [Add-on] Blender to HPL3 =		= [Add-on] Blender to HPL3 =
		+
		+	[[Category:Modding]]
		+	[[Category:English]]

	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.		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.

@@ Line 35: / Line 35: @@
 * 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.
+* When using <code>Textures Per Material</code>, 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 BSDF` node
+* If materials are failing to export properly, try switching between <code>Textures Per Material</code> and <code>Textures Per Object</code>, 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 <code>Principled BSDF</code> node
 * 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.

@@ Line 28: / Line 28: @@
 * '''Rigged Meshes''': Use <code>Single Export</code> 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.
 * '''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:''' <br />Think of each material as having its own UV set. Faces assigned to Material A <br />cannot overlap in the UV editor with other Material A faces, though it is ok <br />(even recommended) for faces assigned to Material B to use up the full UV space, <br />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 <code>Alt+D</code> to create copies of an object in Blender to place around a map, since they will point to the same <code>Mesh</code> datablock. Using Copy/Paste or Shift+D creates a new <code>Mesh</code> 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.
 * 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 <code>Principled BSDF</code> node and that all UV faces lie within UV coordinate bounds

@@ Line 18: / Line 18: @@
 == Important usage notes ==
-On export, the subdirectory 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.
+On export, the sub directory and mesh file will take this name <code>Suzanne.dae</code>, and having name conflicts in HPL3 can cause the wrong textures to load. The <code>Object Name</code> does not matter as much, and will be used to name that instance of the object when placed in the map.
-* '''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.
+Give each object a unique name in the asset's <code>Object Data</code> panel (under the poly triangle icon, not to be confused with the <code>Object</code> panel under the cube icon). Example:
-* '''Baking Modes''':
+<pre>
 * '''Textures Per Material:''' <br />Think of each material as having its own UV set. Faces assigned to Material A <br />cannot overlap in the UV editor with other Material A faces, though it is ok <br />(even recommended) for faces assigned to Material B to use up the full UV space, <br />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 <code>Alt+D</code> to create copies of an object in Blender to place around a map, since they will point to the same <code>Mesh</code> datablock. Using Copy/Paste or Shift+D creates a new <code>Mesh</code> 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 ==