04/24/2006 - bsnes v0.016 released

      This version adds a new configuration interface, DSP-2 and OBC-1 special chip support, and Game Genie / Pro Action Replay cheat code support.

 

Changelog:

* Added Direct3D renderer with options for disabling hardware filtering and scanlines

* Screenshots can now be captured in BMP, JPEG, or PNG format

* Added config file option to specify default ROM and SRAM paths

* Config file is always loaded from path to bsnes executable

* Added support for analog mode joypad input

* Up to 32 joypads can be used at once now

* Fixed bug regarding enabling interlace mid-frame

* Moved PPU rendering to V=240, from V=0

* Started on new debugger. So far only debug messages and memory editor added

* Added joypad axis resistance option for analog input mode

* Added config file option to set window style attributes

* Added color adjustment settings for brightness, contrast, gamma, and scanline intensity

* Added grayscale, sepia, and invert color settings

* Added NTSC filter by blargg, HQ2x filter by MaxSt, and Scale2x filter

* PPU now renders scanline 224

* Revampled about box

* Added Game Genie / PAR cheat code support + editor, saves codes to .cht files

* HDMA channels are no longer disabled when starting DMA, fixes Dracula X [DMV27]

* Fixes to OAM priority mode (not perfect), fixes Final Fantasy: Mystic Quest [DMV27]

* Fixed ENDX sound bug, fixes voices in Earthworm Jim 2 [DMV27]

* bsnes should now compile with MinGW [DMV27]

* Added DSP-2 support

* Added OBC-1 support

* Major rewrite of SNES address bus mirroring and MMIO handlers

* Many address mirroring corrections, fixes Dezaemon, etc

* Blocked invalid (H)DMA transfers, fixes Kirby's Super Funhouse

* Wrote Win32 API wrapper and ported all GUI code to use it, should help to create Linux GUI later on

* Revampled input system, should lead to customizable GUI shortcut keys later on

* Fixed numerous bugs with input registers. Fixes many games that previous had their intro cut off (Super Conflict, etc), and many that never accepted input (Super Double Dragon, etc)

* Moved auto joypad strobing from V=225 to V=227

* Killed OAM table caching and window range caching, as they were actually hindering speed

* Rewrote input configuration screen to show currently mapped keys

* Greatly enhanced configuration options for each video profile

* Modified fullscreen mode to exit to windowed mode when menu is activated, use F11 to toggle fullscreen mode

* Fixed bugs in txs, wai, brk, cop, and rti opcodes [DMV27]

* Fixed bug with emulation-mode IRQs [DMV27]

* Initializing DMA registers to $ff [DMV27]

* Memory writes now update CPU MDR register (open bus) [DMV27]

* Improved ROM header detection, fixes Chou Jikuu Yousai Macross [DMV27]

* Reading OAM no longer updates OAM latch

* Writing to OAM high table no longer updates OAM latch

* Writing CGRAM now updates CGRAM latch

* Improved pseudo-hires rendering [blargg]

* Much, much more

>> Get it HERE.

Surprise External Submissions…

It’s always nice when something from outside the development team is submitted when you’re least expecting it, especially when the submission is of a good quality and is something we’ve considered to be very difficult to work on.

 

Tonight that’s exactly what happened, ElSemi passed along some code to me from a contributor in China (Sorry, I don’t have any more details than this, If he wishes to be credited I’ll edit the post)

 

The code was to simulate the protection in the PGM game “Puzzle Star”, another one of the Mysterious PGM games which never appeared on the IGS site when most of the other titles were up. It’s a puzzle game, very similar to Mang-Chi which was emulated a few days ago but with some extra twists (involving the stars, combos, and ‘promotions’). There may be one or two problems with the simulation, but for the most part it seems to work correctly.

 

I’ve uploaded some resized screenshots you can see below so people can get a good idea of what this PGM cart looks like should they wish to buy it.

 

Please note, once again this is _not_ my WIP, I’m just commenting on a very impressive external submission. Its easy to be critical of low quality external submissions, or people not being willing to fix things, but always very pleasing to see quality external submissions like this one.

>> Click HERE for pictures.

This has been translated from Japanese by Google

* Clipping check processing of the VDP1 was corrected.

* Windowing of the VDP2 was corrected.

* Color RAM address formation processing at the time of the bit map of the VDP2 was corrected.

* Sprite priority number formation processing of the VDP2 was corrected.

* Computing in rotary parameter coordinate of the VDP2 was corrected.

* Hook processing of the system program was corrected.

* The Warring States blade and the like moves there is no BIOS with.  * It tried to replace the ABC button and the XYZ button with 9 keys of keyboard side.

* It modified ahead job backup file retaining of the STV below  the Backup folder.

* It tried to retain the contents of the EEPROM in each every game.

* The bug where speed deviates the dual core CPU use time was corrected.

* Because environment of the Windows98 was gone,  the Windows98 is deleted from the corresponding OS.

>> Get it HERE.

Simple Bugs..

It amazes me sometimes how much users of MAME moan and complain about certain bugs, when if they simply put a fraction of the effort they do complaining into trying to fix the bug then they’d almost certainly be able to fix it.

 

Mysterious Stones has been broken since around MAME 0.77u2. There are a few bad tiles near the start of the first levels, and by the 2nd level it’s apparently unplayable.

 

I took a quick glance at the vidhrdw/mystston.c file in MAME and saw the following code.

 

 

WRITE8_HANDLER( mystston_videoram_w )

{

    if (videoram[offset] != data)

    {

        videoram[offset] = data;

        tilemap_mark_tile_dirty(fg_tilemap, offset & 0×3ff);

    }

}

 

WRITE8_HANDLER( mystston_videoram2_w )

{

    if (videoram[offset] != data)

    {

        mystston_videoram2[offset] = data;

        tilemap_mark_tile_dirty(bg_tilemap, offset & 0×1ff);

    }

}

 

 

the error stands out a mile, even if you’re not a programmer an error like that shouldn’t be too hard to fix. The mystston_videoram2_w handler is broken. As an optimization the code is meant to check if the contents of videoram is the same as the value being written to it, and then only write it if it isn’t the same. The mystston_videoram2_w handler is checking the wrong video ram. The bug was obviously introduced as the result of a simple copy & paste error.

 

fixing the bug simply involved changing

 

if (videoram[offset] != data)

 

 

to

 

if (mystston_videoram2[offset] != data)

 

 

in WRITE8_HANDLER( mystston_videoram2_w )

 

A _very_ simple one line fix. The source is available so people can make fixes like this.

>> Before and After pictures HERE.