MakeHuman Workflows - Revision history

Fortuna: /* Moving Assets into Unreal Engine 4 */

2021-01-19T09:29:35Z

‎Moving Assets into Unreal Engine 4

Fortuna: /* Moving Assets into Unreal Engine 4 */

2021-01-19T09:18:24Z

‎Moving Assets into Unreal Engine 4

Fortuna: Moving Assets into Unreal Engine 4 - Found the content - adding a link to it so the next user finds it faster.

2021-01-19T09:16:38Z

Moving Assets into Unreal Engine 4 - Found the content - adding a link to it so the next user finds it faster.

Lordnicodemus56: /* Moving Assets into Google Sketchup */

2018-11-13T03:48:26Z

‎Moving Assets into Google Sketchup

Joepal: /* Moving Assets into Unity Game Engine */

2016-11-25T10:11:20Z

‎Moving Assets into Unity Game Engine

Joepal: /* Moving Assets into Unity Game Engine */

2016-11-25T10:11:03Z

‎Moving Assets into Unity Game Engine

Joepal: /* User contributed assets. Sharing your creations with the community */

2016-07-20T18:40:09Z

‎User contributed assets. Sharing your creations with the community

Wolgade at 16:25, 20 July 2016

2016-07-20T16:25:42Z

Robbaer: /* Moving Assets into Blender */

2015-08-02T21:21:24Z

‎Moving Assets into Blender

Robbaer: /* Moving Assets into Blender */

2015-08-02T21:17:16Z

‎Moving Assets into Blender

@@ Line 65: / Line 65: @@
 ==Moving Assets into Unreal Engine 4==
-The documentation for how to work with Unreal Engine is available in [["Documentation:Saving_models_for_Unreal_Engine_and_how_to_import_them_there"]].
+The documentation for how to work with Unreal Engine is available in [[Documentation:Saving_models_for_Unreal_Engine_and_how_to_import_them_there|"Saving models for Unreal_Engine and how to import them there"]].
 ==Moving Assets into Unity Game Engine==

@@ Line 65: / Line 65: @@
 ==Moving Assets into Unreal Engine 4==
-See [[Documentation:Saving_models_for_Unreal_Engine_and_how_to_import_them_there]]
+The documentation for how to work with Unreal Engine is available in [["Documentation:Saving_models_for_Unreal_Engine_and_how_to_import_them_there"]].
 ==Moving Assets into Unity Game Engine==

← Older revision		Revision as of 09:16, 19 January 2021
Line 65:		Line 65:

	==Moving Assets into Unreal Engine 4==		==Moving Assets into Unreal Engine 4==
		+	See [[Documentation:Saving_models_for_Unreal_Engine_and_how_to_import_them_there]]

	==Moving Assets into Unity Game Engine==		==Moving Assets into Unity Game Engine==

@@ Line 70: / Line 70: @@
 The documentation for how to work with unity is available in [[Documentation:Saving_models_for_Unity_and_how_to_import_them_there|"Saving models for Unity and how to import them there"]].
-==Moving Assets into Google Sketchup==
+==Moving Assets into Sketchup Pro==
 ==Preparing assets for use with Second Life==

@@ Line 68: / Line 68: @@
 ==Moving Assets into Unity Game Engine==
-The documentation for how to work with unity is available in [[Documentation:Saving_models_for_Unity_and_how_to_import_them_there|"Saving_models for Unity and how to import them there"]].
+The documentation for how to work with unity is available in [[Documentation:Saving_models_for_Unity_and_how_to_import_them_there|"Saving models for Unity and how to import them there"]].
 ==Moving Assets into Google Sketchup==

← Older revision		Revision as of 10:11, 25 November 2016
Line 67:		Line 67:

	==Moving Assets into Unity Game Engine==		==Moving Assets into Unity Game Engine==
		+
		+	The documentation for how to work with unity is available in [[Documentation:Saving_models_for_Unity_and_how_to_import_them_there\|"Saving_models for Unity and how to import them there"]].

	==Moving Assets into Google Sketchup==		==Moving Assets into Google Sketchup==

@@ Line 82: / Line 82: @@
 *"My_Asset.mhclo" is still a bad filename. On Windows file names aren't case sensitive. On Linux they are. On Windows "My_Asset.mhclo", "my_asset.mhclo" and "My_Asset.MHCLO    " all refer to the same file. On Linux they are three completely different files. You want your stuff to work on all platforms. Avoid uppercase letters. "my_asset.mhclo" is a good filename.
 *These rules are true for all files that belong to your asset.
 *Use self-explanatory file names for your graphic files. For this example "my_asset_diffuse.png" would be a good idea for the diffuse texture. Don't use just "diffuse.png". If there's more than one asset using this lazy naming convention files will be overwritten on export.
 *This one's obvious, but often forgotten: After renaming your files, open the .mhclo and .mhmat files and change the referenced file names to your new file names.

← Older revision		Revision as of 16:25, 20 July 2016
Line 71:		Line 71:

	==Preparing assets for use with Second Life==		==Preparing assets for use with Second Life==
		+
		+	==User contributed assets. Sharing your creations with the community==
		+
		+	You finally managed to model a cool piece of clothing or something else? You would like to share it with others? Great! A few words before you start loading up:
		+
		+	MakeHuman is available for more than one OS. Users live in different countries using different language settings. This has some consequences to think about before you upload your asset.
		+
		+	*Avoid non-ascii characters in your filenames. Depending on language settings some characters might lead to trouble. Stick to English in your file names and you're safe.
		+	*Don't use spaces in file names. Today, on most platforms you can use file names like "My Asset.mhclo", but a lot of scripts won't be able to handle it. They consider the space after "My" as a delimiter and fail. Instead of "My Asset.mhclo" "My_Asset.mhclo" would be better.
		+	*"My_Asset.mhclo" is still a bad filename. On Windows file names aren't case sensitive. On Linux they are. On Windows "My_Asset.mhclo", "my_asset.mhclo" and "My_Asset.MHCLO " all refer to the same file. On Linux they are three completely different files. You want your stuff to work on all platforms. Avoid uppercase letters. "my_asset.mhclo" is a good filename.
		+	*These rules are true for all files that belong to your asset.
		+	*Use self-explanatory file names for your graphic files. For this example "my_asset_diffuse.png" would be a good idea for the diffuse texture. Don't use just "diffuse.png". If there's more than one asset using this lazy naming convention files will be overwritten on export.
		+	*This one's obvious, but often forgotten: After renaming your files, open the .mhclo and .mhmat files and change the referenced file names to your new file names.

@@ Line 62: / Line 62: @@
 [[Moving Assets into Blender]]
-This subsection describes the restoration and use of MakeHuman's transparency and skeletal assets after importing in Blender.  The initial focus will be on using the Blender Internal Render engine.  The use of Cycles render engine will be handled separately.
+This subsection describes the import of transparent assets after importing in Blender.  The initial focus will be on using the Blender Internal Render engine.  The use of Cycles render engine will be handled separately.  The Blender tools (MakeClothes, MakeWalk, MakeTarget) for designing and working with MakeHuman internal assets are described elsewhere.
 ==Moving Assets into Unreal Engine 4==