When reporting bugs....

[mudlord]

1) Please report the SVN number of the build you're using. If you don't remember which SVN build you're on, at least try to include the build date. SVN builds prior to 47 are using Blargg's GB_Apu audio core which has a buggy noise channel which can result in bad quality sound. It also has problems with savestates. Both of these issues should be fixed as of the more recent builds.

2) If possible, please test to see if the same issue occurs with the official VBA 1.8 Beta 3 and/or VBA 1.7.3. Our first priority is to integrate our new features with the official 1.8 core. Chasing down bugs in the existing official sources is something we'd like to do as well, but we want to stabilize the things we're adding in first.

3) If reporting video issues, note the rendering method (DirectDraw, Direct3D, OpenGL), options (filters, vsync, triple buffering) and the video card you're using.

Remember, as of this writing, every build of VBA-M that has been released is in an pre-beta state. If you are doing any serious gaming, remember to back up SAVE STATES (.sgm) and SRAM (.sav) files before even touching them with a VBA-M build.