Releases:111 - Revision history

Joepal at 17:54, 4 March 2017

2017-03-04T17:54:58Z

Joepal: /* Known issues */

2017-03-04T09:36:04Z

‎Known issues

Joepal at 09:29, 4 March 2017

2017-03-04T09:29:03Z

Joepal at 09:26, 4 March 2017

2017-03-04T09:26:45Z

Joepal: /* All fixes */

2017-02-16T10:34:26Z

‎All fixes

Robbaer at 14:23, 15 February 2017

2017-02-15T14:23:26Z

Robbaer: /* Known issues */

2017-02-15T14:21:23Z

‎Known issues

Robbaer: /* Known issues */

2017-02-15T14:16:48Z

‎Known issues

Robbaer: /* Known issues */

2017-02-15T14:15:37Z

‎Known issues

Robbaer: /* Known issues */

2017-02-15T14:12:29Z

‎Known issues

← Older revision		Revision as of 17:54, 4 March 2017
Line 14:		Line 14:

	In general, it should be possible to replace the 1.1.0 release with the 1.1.1 release without any noticeable downside. If you use the male worksuit, please note that it has had its UV layout redone from scratch (so third part textures relying on the old UV layout will no longer work).		In general, it should be possible to replace the 1.1.0 release with the 1.1.1 release without any noticeable downside. If you use the male worksuit, please note that it has had its UV layout redone from scratch (so third part textures relying on the old UV layout will no longer work).
		+
		+	== Useful extras ==
		+
		+	In [http://download.tuxfamily.org/makehuman/releases/1.1.1 the release directory] on tuxfamily, you will also find two zip files with extras that you may be interested in installing:
		+
		+	* '''blender_plugins_for_1.1.1.zip''': These are blender plugins related to MakeHuman. This is what was called "blendertools" earlier (maketarget, makeclothes, makewalk), but now also includes the latest version of MHX2.
		+	* '''makehuman_plugins_for_1.1.1.zip''': These are extras for MakeHuman as such. The zip contains the MakeHuman side of MHX2, the asset downloader plugin, the asset editor plugin, and the MHAPI dependency.

	== Known issues ==		== Known issues ==

← Older revision		Revision as of 09:36, 4 March 2017
Line 24:		Line 24:

	Because of the cost, the release version of MakeHuman 1.1.1 is not code-signed. This means that some virus checkers, and the Windows OS may issue a warning on your initial start-up. This should be safe to ignore if you downloaded your copy of MakeHuman directly from the official download site. If you obtained your copy elsewhere please use due diligence.		Because of the cost, the release version of MakeHuman 1.1.1 is not code-signed. This means that some virus checkers, and the Windows OS may issue a warning on your initial start-up. This should be safe to ignore if you downloaded your copy of MakeHuman directly from the official download site. If you obtained your copy elsewhere please use due diligence.
		+
		+	A long standing bug, [http://bugtracker.makehumancommunity.org/issues/1054 #1054], was not possible to fix in time for the release. This causes shaders to glitch and look corrup on linux machines under the following conditions: 1. the machine runs on an integrated Intel graphics chipset and 2. the machine uses a newer graphics driver. This is known to affect Ubuntu 16.04, while older Ubuntu versions (such as 14.04) are not affected. For now, the workaround is to run MakeHuman with the parameter "--noshaders". For more info, see the [[FAQ:MakeHuman renders odd colours and weird transparency artefacts. Can you help me?\|the appropriate FAQ item]].

	== All fixes ==		== All fixes ==

← Older revision		Revision as of 09:29, 4 March 2017
Line 1:		Line 1:
−	These are the release notes for version 1.1.1, which was released in ~~February~~ 2017.	+	These are the release notes for version 1.1.1, which was released in March 2017.

	This release is primarily a bug fix release where the major effort has been spent on addressing the unicode issues which made MakeHuman crash when using certain non-ASCII characters in filenames or usernames (in certain locales) on Windows platforms.		This release is primarily a bug fix release where the major effort has been spent on addressing the unicode issues which made MakeHuman crash when using certain non-ASCII characters in filenames or usernames (in certain locales) on Windows platforms.

@@ Line 31: / Line 31: @@
 * Bug #354: Add package_name + date in window title
 * Bug #662: New malesuit01 needs minor UV touch-up
 * Bug #718: Alternative distribution for windows
 * Bug #764: SVG not supported on windows (but doesn't crash)
@@ Line 46: / Line 47: @@
 * Bug #1051: Assymetric foot vertex groups
 * Bug #1053: Help About
-* Bug #1057: ppa produced overwrite errors
+* Bug #1057: ppa produced overwrite errorserrors
 * Bug #1066: material_editor unicode warning MH 1.1.0 release
 * Bug #1070: Sort filters dysfunctional - MH 1.1.0
@@ Line 52: / Line 53: @@
 * Bug #1076: MacOS Sierra - MakeHuman 1.1.0 data directory not loading
 * Bug #1083: _cat_data["bodyproportion"] or _cat_data["bodyproportions"]?
 * Feature #1093: Easy way to copy version number to clipboard for bug reporting

@@ Line 36: / Line 36: @@
 * Bug #831: Worksuit texture touch-up
 * Bug #945: increasing eye bag slider breaks armature
 * Bug #981: Makeclothes doesn't like eyes
 * Bug #983: Modeling Face Mouth features slider images
@@ Line 43: / Line 42: @@
 * Bug #1028: MH 1.1.x - clean up / document status of genitals
 * Bug #1029: Unicode in MH path still causing trouble
 * Bug #1037: Using any translation crashes parts of the GUI
 * Bug #1043: Possible issue in module3d
 * Bug #1051: Assymetric foot vertex groups
 * Bug #1053: Help About
 * Bug #1057: ppa produced overwrite errors
 * Bug #1066: material_editor unicode warning MH 1.1.0 release

← Older revision		Revision as of 14:23, 15 February 2017
Line 1:		Line 1:
−	These are the ~~[preliminary]~~ release notes for version 1.1.1, which ~~[will probably be]~~ released in February 2017.	+	These are the release notes for version 1.1.1, which was released in February 2017.

	This release is primarily a bug fix release where the major effort has been spent on addressing the unicode issues which made MakeHuman crash when using certain non-ASCII characters in filenames or usernames (in certain locales) on Windows platforms.		This release is primarily a bug fix release where the major effort has been spent on addressing the unicode issues which made MakeHuman crash when using certain non-ASCII characters in filenames or usernames (in certain locales) on Windows platforms.

@@ Line 23: / Line 23: @@
 Inside MakeHuman the use of unicode characters is more permissive. It is possible to save MakeHuman models in folders and with filenames containing characters that are not in the primary codepage. However, in case of doubt, we would recommend using only ASCII-characters, respectively characters from your active code page, for filenames. If you plan to save files with users from another locale, it is prudent to stick with ASCII names whenever possible.
-The release version of MakeHuman 1.1.1 is not code-signed which means that some virus checkers and Windows OS may issue a warning on your initial start-up.  This should be safe to ignore if you got your copy of MakeHuman directly from the official download site.  If you obtained your copy elsewhere please use due diligence.
+Because of the cost, the release version of MakeHuman 1.1.1 is not code-signed. This means that some virus checkers, and the Windows OS may issue a warning on your initial start-up.  This should be safe to ignore if you downloaded your copy of MakeHuman directly from the official download site.  If you obtained your copy elsewhere please use due diligence.
 == All fixes ==

← Older revision		Revision as of 14:15, 15 February 2017
Line 22:		Line 22:

	Inside MakeHuman the use of unicode characters is more permissive. It is possible to save MakeHuman models in folders and with filenames containing characters that are not in the primary codepage. However, in case of doubt, we would recommend using only ASCII-characters, respectively characters from your active code page, for filenames. If you plan to save files with users from another locale, it is prudent to stick with ASCII names whenever possible.		Inside MakeHuman the use of unicode characters is more permissive. It is possible to save MakeHuman models in folders and with filenames containing characters that are not in the primary codepage. However, in case of doubt, we would recommend using only ASCII-characters, respectively characters from your active code page, for filenames. If you plan to save files with users from another locale, it is prudent to stick with ASCII names whenever possible.
		+
		+	The release version of MakeHuman 1.1.1 is not code-signed which means that some virus checkers and Windows OS may issue a warning on your initial start-up. This should be safe to ignore if you got your copy of MakeHuman directly from the official download site.

	== All fixes ==		== All fixes ==

@@ Line 19: / Line 19: @@
 While we believe we have now got a grip on all ''normal'' cases where non-ASCII characters are used in file names, it is still possible to break MakeHuman by copy/pasting characters from another codepage than the one windows is installed with. For example: if you have an US-english windows version and unzip MH in a folder named ру́сскийязы́к, chances are MH won't even start.
-However, any file name you are able to write on the keyboard (as opposed from copying from the web) should now work.
+However, any file name that you are able to write on the keyboard (as opposed from copying from the web) should now work.
-Inside MakeHuman the usage of unicode characters is more permissive. It is possible to safe MakeHuman models in folders and with filenames containing characters that are not in the primary codepage. However, in case of doubt, we would recommend using only ASCII-characters, respectively characters from your active code page, for filenames.
+Inside MakeHuman the use of unicode characters is more permissive. It is possible to save MakeHuman models in folders and with filenames containing characters that are not in the primary codepage. However, in case of doubt, we would recommend using only ASCII-characters, respectively characters from your active code page, for filenames. If you plan to save files with users from another locale, it is prudent to stick with ASCII names whenever possible.
 == All fixes ==