Metal Slug 2 - Super Vehicle-001/II: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
| Line 2: | Line 2: | ||
|en_title=Metal Slug 2 - Super Vehicle-001/II | |en_title=Metal Slug 2 - Super Vehicle-001/II | ||
|jp_title=Metal Slug 2 - Super Vehicle-001/II | |jp_title=Metal Slug 2 - Super Vehicle-001/II | ||
|jp_title2=メタルスラッグ 2 | |||
|developer=SNK | |developer=SNK | ||
|ngh_id=241 | |ngh_id=241 | ||
Revision as of 23:39, 29 April 2012
| General Info | |
| USA Title | Metal Slug 2 - Super Vehicle-001/II |
| Japanese Title | Metal Slug 2 - Super Vehicle-001/II
(メタルスラッグ 2) |
| European Title | Metal Slug 2 - Super Vehicle-001/II |
| NGH | 241 |
| Developer | SNK |
| Editor | SNK |
| Meg count | Unknown |
| TCRF page | None |
|
MVS Release | |
 
| |
| Release date | 1998 |
| PROG Board | PROGBK1 |
| CHA Board | CHA512Y |
| Protection Chip | none |
| MAME romset | mslug2 |
|
AES Release : No | |
|
CD Release : No | |
Technical features
- Lags. For real.
- Uses only 32bit writes to $3C0000 to update VRAM and VRAM address instead of using word writes to $3C0002. Is one of the reason it lags so badly but it also means the code is interrupt safe. Raster interrupts writing to VRAM might conflict with VRAM writes in the main program. Also allows it to work properly on overclocked systems since the VRAM writing is so slow.