New MegaZeux Release FAQ - Revision history

Lachesis at 20:53, 23 July 2019

2019-07-23T20:53:26Z

← Older revision		Revision as of 20:53, 23 July 2019
Line 47:		Line 47:
	=== Sound ===		=== Sound ===

	''Restore GDM functionality? What??''		====Restore GDM functionality? What??====

	The module library used in DOS versions supported GDMs, which are a container for S3Ms. During the switch to the cross-platform port, MZX lost the ability to play GDMs because its new module library (libmodplug) did not support them. Instead, a program called gdm2s3m was included to convert them automatically to a format which libmodplug could read, and the extension was removed from the allowed mod extensions list in the editor. The new library in 2.90b+, libxmp, natively supports GDMs, making this conversion unnecessary. The GDM format has been readded to the allowed mod extensions list.		The module library used in DOS versions supported GDMs, which are a container for S3Ms. During the switch to the cross-platform port, MZX lost the ability to play GDMs because its new module library (libmodplug) did not support them. Instead, a program called gdm2s3m was included to convert them automatically to a format which libmodplug could read, and the extension was removed from the allowed mod extensions list in the editor. The new library in 2.90b+, libxmp, natively supports GDMs, making this conversion unnecessary. The GDM format has been readded to the allowed mod extensions list.

Lachesis at 20:49, 23 July 2019

2019-07-23T20:49:11Z

Show changes

Lachesis: /* MegaZeux 2.90X */

2018-09-05T22:57:16Z

MegaZeux 2.90X

← Older revision		Revision as of 22:57, 5 September 2018
Line 42:		Line 42:

	=== Sound ===		=== Sound ===

	''When playing MOD/S3M/XM/IT/etc music, I used to be able to set the MOD_POSITION to any row in the mod and it would work. Now, when I do that, it jumps to the start of the nearest order instead. Why?''

	This is because of the new default module sound engine in 2.90b+, libxmp. This library does not support seeking to positions inside of patterns as of the moment. Since this feature of libmodplug generally did not sound very good anyway, and most of the time '''jump mod order''' is used instead, we considered it a fair sacrifice to fix other sound engine bugs caused by libmodplug and to restore GDM functionality.


	''Restore GDM functionality? What??''		''Restore GDM functionality? What??''
Line 64:		Line 59:
	=== Utilities ===		=== Utilities ===

	''I need to port my game back to MegaZeux 2.84X. What happened to downver?"		''I'm using MegaZeux 2.90X need to port my game back to MegaZeux 2.84X. What happened to downver?"

	The downver utility ~~has been~~ temporarily removed due to the complexity of the new world format. You can export your world to the 2.84X format using Alt+X from the MegaZeux editor.		The downver utility was temporarily removed from 2.90X releases due to the complexity of the new world format. You can export your world to the 2.84X format using Alt+X from the MegaZeux editor. The downver utility has been readded as of 2.91.

Lachesis: /* Windows 10 */

2018-09-05T22:55:16Z

Windows 10

← Older revision		Revision as of 22:55, 5 September 2018
Line 35:		Line 35:
	1) When updating MZX, make sure you're running MegaZeux.exe (not MZXRun.exe), and		1) When updating MZX, make sure you're running MegaZeux.exe (not MZXRun.exe), and

	2) Do not install MZX in a system folder like "Program Files" or "Program Files (x86)". If MegaZeux is in one of the Program Files folders or is inside of a folder that uses Unicode characters, move the folder elsewhere. Ensure that your account has permissions to write to the folder MegaZeux is in, and then attempt to update MegaZeux again. OR:		2) Do not install MZX in a system folder like "Program Files" or "Program Files (x86)". If MegaZeux is in one of the Program Files folders or is inside of a folder that uses Unicode characters, move the MegaZeux folder elsewhere. Ensure that your account has permissions to write to the folder MegaZeux is in, and then attempt to update MegaZeux again. OR:

	3) As a last resort if you can't update, run the MegaZeux.exe executable as an administrator (right click and select "Run as administrator") and attempt to update. NOTE: It is not necessary to run MegaZeux.exe normally this way.		3) As a last resort if you can't update, run the MegaZeux.exe executable as an administrator (right click and select "Run as administrator") and attempt to update. NOTE: It is not necessary to run MegaZeux.exe normally this way.

Lachesis: /* Windows 10 */

2018-09-05T22:54:33Z

Windows 10

← Older revision		Revision as of 22:54, 5 September 2018
Line 25:		Line 25:

	''When I press U or F7 from the titlescreen, nothing happens. When I press enter, the option for the updater isn't even in the list! What's wrong?''		''When I press U or F7 from the titlescreen, nothing happens. When I press enter, the option for the updater isn't even in the list! What's wrong?''

	OR		OR

	''When I press U or F7 from the titlescreen, I get an error message telling me the updater failed to initialize and to check folder permissions.''		''When I press U or F7 from the titlescreen, I get an error message telling me the updater failed to initialize and to check folder permissions.''


	For some reason, the updater failed to initialize. This is probably because MegaZeux requires folder permissions it doesn't have or is located at a path that is causing issues. Do the following:		For some reason, the updater failed to initialize. This is probably because MegaZeux requires folder permissions it doesn't have or is located at a path that is causing issues. Do the following:

Lachesis: /* Windows 10 */

2018-09-05T22:54:12Z

Windows 10

← Older revision		Revision as of 22:54, 5 September 2018
Line 24:		Line 24:
	=== Windows 10 ===		=== Windows 10 ===

	''When I press F7 from the titlescreen, nothing happens. When I press enter, the option for the updater isn't even in the list! What's wrong?''		''When I press U or F7 from the titlescreen, nothing happens. When I press enter, the option for the updater isn't even in the list! What's wrong?''
			OR
			''When I press U or F7 from the titlescreen, I get an error message telling me the updater failed to initialize and to check folder permissions.''

	For some reason, the updater failed to initialize. This is probably because MegaZeux requires ~~administrator privileges~~ it doesn't have. Do the following:		For some reason, the updater failed to initialize. This is probably because MegaZeux requires folder permissions it doesn't have or is located at a path that is causing issues. Do the following:

	1) When updating MZX, make sure you're running MegaZeux.exe ~~and~~ not MZXRun.exe, and		1) When updating MZX, make sure you're running MegaZeux.exe (not MZXRun.exe), and

	2) Do not install MZX in a system folder like "Program Files" or "Program Files (x86)"~~, or~~		2) Do not install MZX in a system folder like "Program Files" or "Program Files (x86)". If MegaZeux is in one of the Program Files folders or is inside of a folder that uses Unicode characters, move the folder elsewhere. Ensure that your account has permissions to write to the folder MegaZeux is in, and then attempt to update MegaZeux again. OR:

	~~3) Run the MegaZeux~~.~~exe executable with administrator privileges (right click and select "Run as administrator") before you run the updater. It is not necessary to run~~ MegaZeux~~.exe normally this way.~~


	~~''Windows 10~~ is ~~a giant piece~~ of ~~s&^! that restarts when I'm in~~ the ~~middle~~ of ~~making my game. I lost~~ a ~~lot of progress because I don't have backups enabled for some reason~~, ~~or I had~~ the ~~robot editor open, etc~~. ~~How do I make sure this never happens again?''~~

	~~1) Create a restore point. Press the Windows key, type "Create a restore point", and select the option called "Create a restore point". You must have administrator privileges~~ to ~~perform this operation. In~~ the ~~menu that opens, select "Create...", give the restore point a descriptive name~~, and then ~~select "Create"~~.

	~~2) Run '''C~~:\Windows\regedit.exe''' as an administrator. Navigate to '''HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU'''. If there is not a value called '''NoAutoRebootWithLoggedOnUsers''', create this value by right clicking the right pane of the window, selecting '''New > DWORD (32-bit) value''', and naming it '''NoAutoRebootWithLoggedOnUsers'''. Edit this value by double clicking it and set the "Value data" field to 1. Close regedit.

			3) As a last resort if you can't update, run the MegaZeux.exe executable as an administrator (right click and select "Run as administrator") and attempt to update. NOTE: It is not necessary to run MegaZeux.exe normally this way.

	== MegaZeux 2.90X ==		== MegaZeux 2.90X ==

Lachesis: /* MegaZeux 2.90X */

2017-07-13T03:54:14Z

MegaZeux 2.90X

← Older revision		Revision as of 03:54, 13 July 2017
Line 62:		Line 62:

	This is because the color spaces don't perfectly map between each other. When changes are made in one colorspace, they must be converted to RGB (if applicable) and then the RGB values must be converted to the other colorspaces. Because of the complexity in these conversions (particularly CIELAB), alternate values may arise. This difference can be dramatic with CIELAB, which contains colors outside of the RGB (and visible light!) spectrums called ''imaginary colors''. When values are selected in these ranges, they will be converted to various (usually bright and saturated) colors with RGB values that correspond to a completely different position in the CIELAB colorspace. For technical reasons, these colors can't really be bounded out of the selection range.		This is because the color spaces don't perfectly map between each other. When changes are made in one colorspace, they must be converted to RGB (if applicable) and then the RGB values must be converted to the other colorspaces. Because of the complexity in these conversions (particularly CIELAB), alternate values may arise. This difference can be dramatic with CIELAB, which contains colors outside of the RGB (and visible light!) spectrums called ''imaginary colors''. When values are selected in these ranges, they will be converted to various (usually bright and saturated) colors with RGB values that correspond to a completely different position in the CIELAB colorspace. For technical reasons, these colors can't really be bounded out of the selection range.



	=== Utilities ===		=== Utilities ===

Lachesis: /* Editor */

2017-07-13T03:53:58Z

Editor

← Older revision		Revision as of 03:53, 13 July 2017
Line 59:		Line 59:
	=== Editor ===		=== Editor ===

	''In the palette editor, when I edit a value, change it back, and then switch between ~~color spaces~~, why are there different values in the other ~~color space~~?''		''In the palette editor, when I edit a value, change it back, and then switch between colorspaces, why are there different values in the other colorspace?''

	This is because the color spaces don't perfectly map between each other. When changes are made in one colorspace, they must be converted to RGB (if applicable) and then the RGB values must be converted to the other colorspaces. Because of the complexity in these conversions (particularly CIELAB), alternate values may arise. This difference can be dramatic with CIELAB, which contains colors outside of the RGB (and visible light!) spectrums called ''imaginary colors''. When values are selected in these ranges, they will be converted to various (usually bright and saturated) colors with RGB values that correspond to a completely different position in the CIELAB colorspace. For technical reasons, these colors can't really be bounded out of the selection range.		This is because the color spaces don't perfectly map between each other. When changes are made in one colorspace, they must be converted to RGB (if applicable) and then the RGB values must be converted to the other colorspaces. Because of the complexity in these conversions (particularly CIELAB), alternate values may arise. This difference can be dramatic with CIELAB, which contains colors outside of the RGB (and visible light!) spectrums called ''imaginary colors''. When values are selected in these ranges, they will be converted to various (usually bright and saturated) colors with RGB values that correspond to a completely different position in the CIELAB colorspace. For technical reasons, these colors can't really be bounded out of the selection range.



	=== Utilities ===		=== Utilities ===

Lachesis: /* MegaZeux 2.90X */

2017-07-13T03:50:32Z

MegaZeux 2.90X

← Older revision		Revision as of 03:50, 13 July 2017
Line 54:		Line 54:

	The module library used in DOS versions supported GDMs, which are a container for S3Ms. During the switch to the cross-platform port, MZX lost the ability to play GDMs because its new module library (libmodplug) did not support them. Instead, a program called gdm2s3m was included to convert them automatically to a format which libmodplug could read, and the extension was removed from the allowed mod extensions list in the editor. The new library in 2.90b+, libxmp, natively supports GDMs, making this conversion unnecessary. The GDM format has been readded to the allowed mod extensions list.		The module library used in DOS versions supported GDMs, which are a container for S3Ms. During the switch to the cross-platform port, MZX lost the ability to play GDMs because its new module library (libmodplug) did not support them. Instead, a program called gdm2s3m was included to convert them automatically to a format which libmodplug could read, and the extension was removed from the allowed mod extensions list in the editor. The new library in 2.90b+, libxmp, natively supports GDMs, making this conversion unnecessary. The GDM format has been readded to the allowed mod extensions list.



			=== Editor ===

			''In the palette editor, when I edit a value, change it back, and then switch between color spaces, why are there different values in the other color space?''

			This is because the color spaces don't perfectly map between each other. When changes are made in one colorspace, they must be converted to RGB (if applicable) and then the RGB values must be converted to the other colorspaces. Because of the complexity in these conversions (particularly CIELAB), alternate values may arise. This difference can be dramatic with CIELAB, which contains colors outside of the RGB (and visible light!) spectrums called ''imaginary colors''. When values are selected in these ranges, they will be converted to various (usually bright and saturated) colors with RGB values that correspond to a completely different position in the CIELAB colorspace. For technical reasons, these colors can't really be bounded out of the selection range.

Lachesis: /* MegaZeux 2.90X */

2017-07-13T03:37:56Z

MegaZeux 2.90X

← Older revision		Revision as of 03:37, 13 July 2017
Line 54:		Line 54:

	The module library used in DOS versions supported GDMs, which are a container for S3Ms. During the switch to the cross-platform port, MZX lost the ability to play GDMs because its new module library (libmodplug) did not support them. Instead, a program called gdm2s3m was included to convert them automatically to a format which libmodplug could read, and the extension was removed from the allowed mod extensions list in the editor. The new library in 2.90b+, libxmp, natively supports GDMs, making this conversion unnecessary. The GDM format has been readded to the allowed mod extensions list.		The module library used in DOS versions supported GDMs, which are a container for S3Ms. During the switch to the cross-platform port, MZX lost the ability to play GDMs because its new module library (libmodplug) did not support them. Instead, a program called gdm2s3m was included to convert them automatically to a format which libmodplug could read, and the extension was removed from the allowed mod extensions list in the editor. The new library in 2.90b+, libxmp, natively supports GDMs, making this conversion unnecessary. The GDM format has been readded to the allowed mod extensions list.



	=== Utilities ===		=== Utilities ===