Thread Closed 
Thread Rating:
  • 76 Vote(s) - 3.04 Average
  • 1
  • 2
  • 3
  • 4
  • 5
When reporting bugs....
Author Message
mudlord Offline
not banned.

Posts: 507
Joined: Feb 2009
Reputation: 5
Post: #1
When reporting bugs....

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. Wave Ram (Channel 3) is currently known to be problematic

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.

4) Please, always provide a Screenshot of the issue, or if needs be, a .Sav(Battery) or Savestate file.
(This post was last modified: 03-23-2012 11:07 AM by Squall Leonhart.)
03-19-2008 07:29 AM
Visit this user's website Find all posts by this user
Thread Closed 

Forum Jump:

User(s) browsing this thread: 1 Guest(s)

 Quick Theme: