Author Topic: Ironclad MVS discussion  (Read 43433 times)

Offline Haze

  • MAME Devs
  • *****
  • Posts: 184
  • Karma: +47/-0
Re: Ironclad MVS discussion
« Reply #30 on: December 10, 2009, 02:59:20 PM »
Off topic:

MVS bootlegs are on sale.

Faster then I expected ...

Roms match the expected ones.  (Somebody bought one and dumped a couple of days ago to check)


Offline iq_132

  • Administrator
  • *****
  • Posts: 3724
  • Karma: +411/-0
  • Definitely not Dink!
    • NeoSource
Re: Ironclad MVS discussion
« Reply #31 on: January 25, 2010, 06:04:38 PM »

This is likely the one you'll want to use:

+ROM_START( ironcbl )
+   ROM_REGION( 0x200000, "maincpu", 0 )
+   ROM_LOAD16_WORD_SWAP( "220-p1.bin", 0x100000, 0x100000, CRC(62a942c6) SHA1(12aaa7d9bd84328d1bf4610e056b5c57d0252537) )
+   ROM_CONTINUE( 0x000000, 0x100000 )
+
+   NEO_SFIX_128K( "220-s1.bin", CRC(372fe217) SHA1(493433e682f519bf647e1481c8bdd3a980830ffb) )
+
+   NEO_BIOS_AUDIO_128K( "220-m1.bin", CRC(3a08bb63) SHA1(d8fbbf42a006ccafc3cd99808d28c82dbaac4590) )
+
+   ROM_REGION( 0x400000, "ymsnd", 0 )
+   ROM_LOAD( "220-v1.bin", 0x000000, 0x400000, CRC(8f30a215) SHA1(0ee866a468c4c3608d55df2b5cb9243c8016d77c) )
+
+   NO_DELTAT_REGION
+
+   ROM_REGION( 0x1000000, "sprites", 0 )
+   ROM_LOAD16_BYTE( "220-c1.bin", 0x000000, 0x400000, CRC(9aa2b7dc) SHA1(6b3dff292c86f949890b1f8201bc5278f38c2668) ) /* Plane 0,1 */
+   ROM_LOAD16_BYTE( "220-c2.bin", 0x000001, 0x400000, CRC(8a2ad708) SHA1(9568ac4cc0552e7fd3e50d3cd8d9f0f4fe7df1d4) ) /* Plane 2,3 */
+   ROM_LOAD16_BYTE( "220-c3.bin", 0x800000, 0x400000, CRC(d67fb15a) SHA1(842971aeaf3c92e70f7c653bbf29058bc60f5b71) ) /* Plane 0,1 */
+   ROM_LOAD16_BYTE( "220-c4.bin", 0x800001, 0x400000, CRC(e73ea38b) SHA1(27138d588e61e86c292f12d16e36c3681075c607) ) /* Plane 2,3 */
+
+   ROM_DEFAULT_BIOS( "japan" ) // has issues with Euro / Asia bios roms
+ROM_END


Offline iq_132

  • Administrator
  • *****
  • Posts: 3724
  • Karma: +411/-0
  • Definitely not Dink!
    • NeoSource
Re: Ironclad MVS discussion
« Reply #32 on: January 25, 2010, 06:49:31 PM »
Set the region to Japan or USA. This also occurs in the NeoGeo CD version.


Offline CaptainCPS

  • FBNeo Dev
  • ******
  • Posts: 1513
  • Karma: +127/-0
  • FB Alpha Team
    • CaptainCPS's Home
Re: Ironclad MVS discussion
« Reply #33 on: January 25, 2010, 07:33:19 PM »
Pretty cool & interesting stuff guys! ^^

SeeYaa!
 :biggrin:

Offline iq_132

  • Administrator
  • *****
  • Posts: 3724
  • Karma: +411/-0
  • Definitely not Dink!
    • NeoSource
Re: Ironclad MVS discussion
« Reply #34 on: January 27, 2010, 01:50:06 AM »
Made up a NRX set, and tried it with 4.8 - the video is a lot better, and that weird flickering at the start is fixed. Not sure why mame has to have those lines flashing around. The only drawback is that the instructions are in Spanish, and I don't know how to get into the soft-settings in NRX.
The flickering is related to the raster effects (i think). I think it is correct (but I could be wrong).
As for the euro region working in kawaks, this is afaik related to the fact that kawaks doesn't properly set the region by using different bios sets.


Offline Haze

  • MAME Devs
  • *****
  • Posts: 184
  • Karma: +47/-0
Re: Ironclad MVS discussion
« Reply #35 on: January 28, 2010, 10:51:19 AM »
Er, I think I confused you.. Kawaks works fine, but it is using its default bios (whatever that is).


The part about Europe region is in Misfitmame - all bioses work in misfitmame, and it is (or should be) the same as MAME. So, I don't know why it is reported that some bioses don't work.


As for the flickering, you see the picture fading up and down.. but in MisfitMAME (and presumably MAME), it is accompanied by flashing horizontal black lines. In NRX the screen appears perfectly. In fact, I would say the video in NRX is superior in all ways - at least for this game.

You've been around long enough to know that looks better != superior

Most NeoGeo games are buggy, MAME emulates the bugs.

Offline CaptainCPS

  • FBNeo Dev
  • ******
  • Posts: 1513
  • Karma: +127/-0
  • FB Alpha Team
    • CaptainCPS's Home
Re: Ironclad MVS discussion
« Reply #36 on: January 31, 2010, 03:35:44 AM »
Still, if someone would like to run it on the Wii, we would know for certain.

I will test it ^^, I have a modded Wii so I let you know soon  ;p

SeeYaa!
 :biggrin:

Offline CaptainCPS

  • FBNeo Dev
  • ******
  • Posts: 1513
  • Karma: +127/-0
  • FB Alpha Team
    • CaptainCPS's Home
Re: Ironclad MVS discussion
« Reply #37 on: January 31, 2010, 11:26:29 PM »
I was able to test IRONCLAD.Chotetsu.Brikinger.JPN.VC.NGCD.Wii-OneUp on my Wii Console (4.0U / 417) using System Menu Preloader v0.30 and enabling Free Region Channels option. After launching the game I could notice the flickering in the intro. I tried to record the flickering using my phone camera and other cheap cam I got here but the flickering is faster than both cameras and can't be noticed.

IQ informed me that this happens using the Wii emulator as well so I think that the flickering is part of the released game. If its a bug, then its a bug that the game has not the emulators, in my opinion  :smilie:.

SeeYaa!
 :biggrin:
« Last Edit: February 01, 2010, 12:13:50 AM by CaptainCPS-X »

Offline Haze

  • MAME Devs
  • *****
  • Posts: 184
  • Karma: +47/-0
Re: Ironclad MVS discussion
« Reply #38 on: February 01, 2010, 12:46:54 PM »
Still, if someone would like to run it on the Wii, we would know for certain.

Uhh, the Wii is an emulator, it says nothing about how it performs on the real hardware either.

Anyway, like most things, they flicker it to simulate transparency, it looked better on a proper arcade monitor, see life-bars and shadows in other games.
« Last Edit: February 01, 2010, 12:48:10 PM by Haze »

Offline iq_132

  • Administrator
  • *****
  • Posts: 3724
  • Karma: +411/-0
  • Definitely not Dink!
    • NeoSource
Re: Ironclad MVS discussion
« Reply #39 on: February 01, 2010, 05:07:04 PM »
Uhh, the Wii is an emulator, it says nothing about how it performs on the real hardware either.
Seems to reason though that the people in charge of putting the emulator together would have access to the real hardware or possibly video to ensure some sort of quality (though this is SNKp we're talking about...).
I suppose it may be worth bugging one of those poor saps that bought a $500 sh** bootleg to make a video.


Offline Haze

  • MAME Devs
  • *****
  • Posts: 184
  • Karma: +47/-0
Re: Ironclad MVS discussion
« Reply #40 on: February 01, 2010, 10:10:20 PM »
Seems to reason though that the people in charge of putting the emulator together would have access to the real hardware or possibly video to ensure some sort of quality (though this is SNKp we're talking about...).
I suppose it may be worth bugging one of those poor saps that bought a $500 sh** bootleg to make a video.

That's highly unlikely, they would have got a 3rd party to do something, and the criteria would be that it runs the game as well as possible on the Wii hardware.  Accuracy would not have been their concern, and the Wii is pretty weak hardware so they would have been taking as many shortcuts as possible to get it to perform well.  Chances are their original references for the ports would have been existing emulators, that's how it usually goes with these things.


Offline JacKc

  • FBNeo Dev
  • ******
  • Posts: 1677
  • Karma: +56/-0
  • Hasta la vista, Baby !
Re: Ironclad MVS discussion
« Reply #41 on: April 13, 2010, 11:59:17 AM »
Ironclad VC Wii USA has been released...extracted the Wad and here's the results :

- Same ROMs as previous extracted set from the Wii VC except for the P1.bin and Bios.bin...Now when choose MVS USA Bios, the instructions are in English (see attached 1st snap) instead of Spanish (see attached 2nd snap) in previous set.

Code: [Select]
// Ironclad / Chotetsu Brikinger (Wii Virtual Console US release)

static struct BurnRomInfo ironcladRomDesc[] = {
{ "220-p1.bin",   0x200000, 0xce37e3a0, 1 | BRF_ESS | BRF_PRG }, //  0 68K code

{ "220-s1.bin",   0x020000, 0x372fe217, 2 | BRF_GRA },           //  1 Text layer tiles

{ "220-c1.bin",   0x400000, 0x9aa2b7dc, 3 | BRF_GRA },           //  2 Sprite data
{ "220-c2.bin",   0x400000, 0x8a2ad708, 3 | BRF_GRA },           //  3
{ "220-c3.bin",   0x400000, 0xd67fb15a, 3 | BRF_GRA },           //  4
{ "220-c4.bin",   0x400000, 0xe73ea38b, 3 | BRF_GRA },           //  5

{ "220-m1.bin",   0x020000, 0x3a08bb63, 4 | BRF_ESS | BRF_PRG }, //  6 Z80 code

{ "220-v1.bin",   0x400000, 0x8f30a215, 5 | BRF_SND },           //  7 Sound data
};

STDROMPICKEXT(ironclad, ironclad, neogeo)
STD_ROM_FN(ironclad)

struct BurnDriver BurnDrvironclad = {
"ironclad", "NULL", "neogeo", "1996",
"Ironclad / Chotetsu Brtikinger (Wii Virtual Console US release)\0", NULL, "Saurus", "Neo Geo",
NULL, NULL, NULL, NULL,
BDF_GAME_WORKING, 2, HARDWARE_SNK_NEOGEO | HARDWARE_SNK_MVSCARTRIDGE | HARDWARE_SNK_SWAPP, GBF_HORSHOOT, 0,
NULL, ironcladRomInfo, ironcladRomName, neogeoInputInfo, neogeousaDIPInfo,
NeoInit, NeoExit, NeoFrame, NeoRender, NeoScan, JBF_GAME_WORKING, NULL, NULL, NULL, &NeoRecalcPalette, 0x1000,
304, 224, 4, 3
};
« Last Edit: April 13, 2010, 01:32:39 PM by JacKc »


Offline Haze

  • MAME Devs
  • *****
  • Posts: 184
  • Karma: +47/-0
Re: Ironclad MVS discussion
« Reply #42 on: April 15, 2010, 12:24:47 PM »
There are some fairly significant code patches in the new set.

I'm guessing because the original was a prototype / limited release it didn't get widespread play / testing, and a fair number of bugs were uncovered once it had the VC release (including the Spanish / English thing, although either Bomberman or Panic Bomber is the same IIRC)

Either that, or they sourced an actual later revision from SNK, that wasn't uncovered the first time, but unlike the first set, this one does look like it has patches beyond the original release.