New MegaZeux Release FAQ

All Versions

The new MegaZeux release has a bug that wasn't in the last release!

Please use the MegaZeux bug tracker to report the new bug. If MegaZeux crashes, or doesn't work at all, cross post the issue you're having in the new version release thread as well.

I've found a bug and I want to make a good quality report. MegaZeux crashes and I've found a way to reproduce it, but I want to pass this on to developers in the best way possible. How can I achieve this?

An excellent question! As of 2.82b, MegaZeux uses something called GNU debuglink to provide optional side-by-side debug packages which you can install (together with GDB) to produce something called a backtrace which is very useful to developers. This supplants an earlier project ajs's called the "MZX Debugging Package", but its goals are the same.

• Grab the symbols for your version (one of windows-x86, windows-x64, ubuntu i386 or ubuntu amd64 at the moment). For windows, these packages are called e.g. mzx283-x86.debug.zip
• Extract the package to the same directory (or install the Ubuntu -dbg package).
• Download GDB if you don't already have it and extract it into the MZX directory with your release and debug symbols.
• Drag "megazeux.exe" over gdb.exe.
• Type "r" and press return.
• Reproduce the crash context.
• Backtrace with "bt full" and copy/paste the results to a bug report thread.

MegaZeux 2.84c

I set the undo history size for the char editor to N but I can only undo N-1 times! WTF? MegaZeux sucks! The undo history size includes the current frame, since you can redo history too.

Tab keeps centering the editor viewport! I liked it better when I could easily ruin things with ALT+Arrows in draw mode! Why did you declaw my favorite way of destroying hours of robot code without realizing it? You can disable it with the config option 'editor_tab_focuses_view'.

I don't like the new debugger! It is too awe inspiring for me to use as it lets me access robot local variables! How do I go back to the less amazing, older version? You can't. Might want to stick with 2.84b!

What's this mumbo jumbo about saving board defaults? MegaZeux now loads an editor config file specific to each world called [world name].editor.cnf. You may put custom config here that will only affect that world, with the exception of extended macros, which will always override global extended macros and will carry between worlds. The "set as default" buttons in the I and ALT+P dialogs save a block of board default config options to the world.editor.cnf file. These options take effect immediately, but the config file isn't reloaded unless you change worlds. You may edit the contents in the editor-generated section but it is advised that you don't edit the comments themselves or add your own options between the comments, as when you resave the defaults, the editor-generated section is overwritten.

Wow! Counter creation and lookups are faster now, especially in the upper range. I hate this! How can I go back to it taking 12 minutes to create a million counters? There is no way to disable this in the compiled distributions. You may download the source code for MegaZeux 2.84c and check out the compiling and Git sections of the Wiki for help with compiling the source. Running config.sh will show several compile options, including one to turn off counter hash tables.

MegaZeux 2.83

The new 'glsl' video_output option doesn't work, or the quality is bad!

The new renderer will only work on video cards capable of OpenGL 2.0 or greater. There are known quality issues with glsl on some ATI Radeon cards (X1300) that will be looked into ASAP. Modern cards like HD Radeons should not be affected.