Welcome!
Final Burn Neo => FBN Development => Topic started by: iq_132 on November 27, 2009, 05:49:16 PM
-
My friend JackC asked me to take a look at the Ironclad Wii Virtual Console wad.
After some work --
decrypting the wad (3rd party tool...)
extracting the archives with my donkey kong country wad extractor
and writing a small/simple tool to extract the files from the archive
I managed to get some really nice shots:
I would like to submit this to MAME, since this is almost certainly a proper dump from actual MVS/AES hardware.
The only issue I have is that it came with a single 16mb Cx rom. I split up the Cx into 4x4mb files (as Saurus's other titles of the time are the same).
If anyone has any insight on whether I should leave it as a 16mb, de-interleave it to 8mb, or deinterleave & split it to 4mb (or 2mb) please let me know.
-
maybe 4x4mb is OK, or 8x2mb
the two methods both appear in MAME
-
First thanks to my dear friend iq_132...as always you rocks GUY !!!
More snaps...
-
Hi, JacKc
It's really an easy work
why don't You do it by yourself? I thought you could...
dear iq_132, Don't you see my reply?
the volume of psikyosh, nmk16 and maybe more new dirvers is too low
Especially compared with the previous drivers
-
An easy work for someone who got pretty good skills like iq_132...But i can't pretend to make it by myself. I'm not as talented as iq_132 and don't have his skills !
-
Hi, JacKc
It's really an easy work
why don't You do it by yourself? I thought you could...
Wtf?
dear iq_132, Don't you see my reply?
the volume of psikyosh, nmk16 and maybe more new dirvers is too low
Especially compared with the previous drivers
My friend Kenshiro took look at the volume levels, he said the values were the same as in MAME. Given that, I'm not about to start adjusting the volume levels at random.
@Jack - Thanks buddy. Still awesome to see an MVS dump of this game.
BTW -- Please note that this game will absolutely not run with the region set to EUROPE or ASIA. USA and Japan run just fine, AES and MVS.
-
Nice to see more peope took a stab at Brikinger. I did last night, but i get corrupt C roms each time.
Can you explain what to do with the C-roms to get a proper formatted file ?
(http://www.zonko.nl/files/brikinbad.jpg)
In my case i used an old NGCD -> NG gfx converter and took the 16Mbyte C rom into two pieces.
All the details to build your own set of roms are in the header of the file. It's easy, i just used dd.
dd if=game.bin of=noheader.bin bs=64 count=1 skip=1 # get rid of header.
dd if=noheader.bin of=P1.ROM bs=2097152 count=1 # 16 blocks = 2M
dd if=noheader.bin of=M1.ROM bs=131072 count=1 skip=16 #
dd if=noheader.bin of=V1.rom bs=131072 count=16 skip=17 # skip 16 + 1 and get 2M
dd if=noheader.bin of=V2.rom bs=131072 count=16 skip=33 # skip 32 + 1 and get 2M
dd if=noheader.bin of=S1.rom bs=131072 count=1 skip=49 # 33+16 and get 131xxx
dd if=noheader.bin of=C1.rom bs=131072 count=32 skip=50 # 49+1 get 4M
dd if=noheader.bin of=C2.rom bs=131072 count=32 skip=82 # 32+50 = 82
dd if=noheader.bin of=C3.rom bs=131072 count=32 skip=114 # 82+32 = 114
dd if=noheader.bin of=C4.rom bs=131072 count=32 skip=146 # 114 +32 = 146
In my case i end up with 4x 4Mbyte C roms, that can join to 2x8Mb or 1x16Mb, it doesn't matter.
If i run them thru the speksnk tool, as 16Mbyte, it outputs 2x8MB, and so forth. I used Neorage to test the output, since it doesn't require any source editing/recompiling and is just plug-n-play. :)
My question is, what do we do with the raw 16MB chunk of graphics ? De-interleave doesn't work for me.. Nor does waninkoko 'swapper.exe'. I got stuck at this point last night, and figured someone would find it out when i was asleep :)
-
Apparently the M1 rom has a 2010 copyright, so has been modified in some way?
It's bound to end up being sold 100 times over as 'legit' on ebay, just like scumbags tried with Zintrick, so I imgine it'll end up in MAME eventually, but only as a bootleg.
-
Well, the M1 rom might have been remastered, or changed, i don't get it.
Ver 3.0 by MAKOTO.04/03/10 to SK (Ironclad, 1994)
Ver 2.0a by MAKOTO.03/04/05 to SK (2020 Super Baseball, 1991)
Ver 8.3 by MAKOTO.98/05/07 to SK (Shock Troopers 2, 1998)
I thought perhaps it refers to '1994 3/10' but that does not work for 2020. (Or 2020bb M1 rom was remastered in 1993?)
Then i checked Shock Troopers 2 and that clearly has a 1998 in the version line.
As far as i am concerned this is an original dump, straight from SNK. Kind of gets my hopes up of seeing other 'cd-only' games surface some day as well.
Like perhaps Crossed Swords 2.. Anyway :) Any pointers how to re-order the C roms ? (Ucon64?)
-
My friend JackC asked me to take a look at the Ironclad Wii Virtual Console wad.
After some work --
decrypting the wad (3rd party tool...)
extracting the archives with my donkey kong country wad extractor
and writing a small/simple tool to extract the files from the archive
I managed to get some really nice shots:
I would like to submit this to MAME, since this is almost certainly a proper dump from actual MVS/AES hardware.
The only issue I have is that it came with a single 16mb Cx rom. I split up the Cx into 4x4mb files (as Saurus's other titles of the time are the same).
If anyone has any insight on whether I should leave it as a 16mb, de-interleave it to 8mb, or deinterleave & split it to 4mb (or 2mb) please let me know.
It's a 1996 game.
At this time mostly CHA256 or CHA256B boards were used.
So the layout closest to the original will be 4x32mbit for C-Roms.
Edit:
This should it be then:
ROM_START( ironclad ) /* bootleg? */
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, "ym", 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_END
-
Regarding the others Saurus games from 1996 (Ragnagard / Shinoken, Pleasure Goal 5-on-5 Street Soccer / Futsal as example), it has Cx 4mb rom and CHA256 Board...
http://mvs.gotwalls.com/index.php/File:Ragnagard_set1_b2_front.jpg (http://mvs.gotwalls.com/index.php/File:Ragnagard_set1_b2_front.jpg)
http://mvs.gotwalls.com/index.php/File:Pleasure_goal_set1_b2_front.jpg (http://mvs.gotwalls.com/index.php/File:Pleasure_goal_set1_b2_front.jpg)
-
Well, the M1 rom might have been remastered, or changed, i don't get it.
Ver 3.0 by MAKOTO.04/03/10 to SK (Ironclad, 1994)
Ver 2.0a by MAKOTO.03/04/05 to SK (2020 Super Baseball, 1991)
Ver 8.3 by MAKOTO.98/05/07 to SK (Shock Troopers 2, 1998)
I thought perhaps it refers to '1994 3/10' but that does not work for 2020. (Or 2020bb M1 rom was remastered in 1993?)
Then i checked Shock Troopers 2 and that clearly has a 1998 in the version line.
As far as i am concerned this is an original dump, straight from SNK. Kind of gets my hopes up of seeing other 'cd-only' games surface some day as well.
Like perhaps Crossed Swords 2.. Anyway :) Any pointers how to re-order the C roms ? (Ucon64?)
ok.. doesn't look like they're dates then.... lots of Japanese games mark dates in Weeks instead, but it doesn't look like that either, so I guess it's just some additional versioning info.
obviously without a cart the C roms could be in any layout... but the most likely is as Johnboy states. Beyond that I don't see much point in posting info about how to convert them here, or spend time working it out because as shown from iq's shots it's already been done.
*edit* at least one of the old Geocities sites showing emulated shots of the private roms had the rom loading for MAME (including the CRC32s) included as proof. If that can be found, this dump can easily be verified as either genuine, or watermarked / modified. Of course, that depends on somebody having saved off the information ;-) If i can be verified as genuine then it can probably be added, with xacrow being given the credit as (I assume) his old CRC lists would have provided the needed evidence.
-
ROM_START( ironclad ) /* bootleg? */
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, "ym", 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_END
To get that p1, just swap the first and second halves of the Wii dump, to get the Cx, just dissect the 16mb Cx blob byte-wise and split the 2 halves into 4mb chunks.
-
To get that p1, just swap the first and second halves of the Wii dump, to get the Cx, just dissect the 16mb Cx blob byte-wise and split the 2 halves into 4mb chunks.
Well its working fine here using this driver. No rom continue so that´s use original P1 still.
ROM_START( ironclad )
ROM_REGION( 0x200000, "maincpu", 0 )
ROM_LOAD16_WORD_SWAP( "220-p1.bin", 0x000000, 0x200000, CRC(65849961) SHA1(2846081bb1451a209412159991bfac95d394fe3a) )
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, 0x800000, CRC(621f4a09) SHA1(117a8e8bea5f880d8315b48bc5884eb805c5e678) )
//ROM_LOAD16_BYTE( "220-c2.bin", 0x000001, 0x800000, CRC(7fec83e8) SHA1(769c2cb4ed4a9d7c29e3aad3f4601f1d24c96640) )
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_END
GAME( 1996, ironclad, neogeo, neogeo, neogeo, neogeo, ROT0, "Saurus", "Ironclad / Chotetsu Brikinger (Wii virtual console release)", 0 )
-
according to JB and iq_132, here's a tool to obtain the Ironclad MVS proper DUMP.
SOURCE :
*********
220-p1.bin CRC 65849961
220-c1.bin CRC 621F4A09
220-c2.bin CRC 7FEC83E8
TARGET :
*********
220-p1.bin CRC 62a942c6
220-c1.bin CRC 9AA2B7DC
220-c2.bin CRC 8A2AD708
220-c3.bin CRC D67FB15A
220-c4.bin CRC E73EA38B
-
Can someone confirm this shows as 'burikinger' in a japanese AES or MVS bios ?
Thanks for the picture below, but i mean, does it show in 'soft dip' as Burikinger or Ironclad ?
-
Why do you make this rom looks like a MVS dump?
Why do you "make" a "bootleg" with 4x4mb cx and modified p1?
Why don't keep the rom as it is be in the Wii virtual console as possible?
You want to remove the Wii virtual console information and enforce that IT IS JUST A MVS ROM
-
Why do you make this rom looks like a MVS dump?
This rom is sure a MVS dump
Why do you "make" a "bootleg" with 4x4mb cx and modified p1?
We don't made bootleg. If you take a closer look on Saurus others titles released in 1996, you will see they got 4x4mb cx and not 1x16mb cx. The p1 is just bytwsapped and reordered like it would be in real hardware...
Why don't keep the rom as it is be in the Wii virtual console as possible?
the purpose is to be closest to the original hardware...
You want to remove the Wii virtual console information and enforce that
Damn! You're totally wrong...Look at 1st post!!! It's clearly said it comes from the VC wii.
IT IS JUST A MVS ROM
Totally agreed !!!
-
Apparently the M1 rom has a 2010 copyright, so has been modified in some way?
Game ID 0227 also has a M1 v3.0 **/**/10.
There are probably more.
Edit: 0227 is Stakes Winner 2. It is also from Saurus, made in 1996.
This revision of the Sound driver is most likely the latest/final revision.
-
I mean THIS rom never ran on real MVS hardware
Yes, there is a MVS prototype (confirmed) but it is NOT this one
This rom is released at 2009 and m1 at 04/03/10, so why don't encrypt Cx,Vx,Px and use the PVC protection?
Just like zupapa (Wii VC ironclad is for memorial, so it isn't like zupapa has the release year on title. It shows 1996, but it obviously made after 1996)
haha... It's only a joke.
No more argument, If you'd like to make that bootleg, do it.
You can also burn it on cartridge, then MAME can support it
However it is a console game ever
Can someone confirm this shows as 'burikinger' in a japanese AES or MVS bios ?
Thanks for the picture below, but i mean, does it show in 'soft dip' as Burikinger or Ironclad ?
pic for you, shows as 'burikinger' in 'soft dip'
-
I mean THIS rom never ran on real MVS hardware
Yes, there is a MVS prototype (confirmed) but it is NOT this one
You seem quite sure of this. I'm waiting for your proof that this isn't a dump from a cart in SNKp's archives.
This rom is released at 2009 and m1 at 04/03/10, so why don't encrypt Cx,Vx,Px and use the PVC protection?
Probably because they use [almost] completely decoded roms in their emulator on the Wii. if you look at other games, such as metal slug, the p1 is swapped normally, but not in the dump in the emulator. Not only that, the graphics roms are already merged and interleaved, making processing easier. Also, the "date" you're looking at in the M1 rom doesn't mean a thing -- look at kof94's m1 rom.
It isn't to say that this ironclad rom is 100% original (it seems likely from the research I've done on the other Neo-Geo VC titles that the Px data has been slightly modified).
Just like zupapa (Wii VC ironclad is for memorial, so it isn't like zupapa has the release year on title. It shows 1996, but it obviously made after 1996)
Not really, Zupapa was released on cartridges rather than through an arcade emulator on a home console.
No more argument, If you'd like to make that bootleg, do it.
You can also burn it on cartridge, then MAME can support it
You can be sure that MVS/AES bootlegs will be appearing soon. The question of whether or not it belongs in MAME at that point will be completely moot as it will have been ran on actual hardware without any doubt. Getting it into MAME/FBA sooner, rather than later will help reduce the number of ebayers/whatever that get burned by buying "uuber l33t r4r3 neoprotoz unmamed ironcladz!" at stupid prices.
However it is a console game ever
Uh. No. It is an Arcade/Console game just like [almost] every other non-homebrew Neo-Geo game.
-
It seems likely from the research I've done on the other Neo-Geo VC titles that the Px data has been slightly modified.
Can you shed some details on what was modified ? Per chance, the name it shows up in 'soft dip' like Narcissus above writes ?
I could imagine for internationalization, that the naming inside the P1 would be 'fixed' for a 2009 release, with the bios showing
the correct name..
If you look in the VC p1 dump from Ironclad, it shows the BURIKINGER name at hex 0201 and 'IRONCLAD' at hex 03EA (three.)
I asked for the soft dip screenshot, so i could compare.
I guess we have at least two different versions. The proto version where those shots came from 'burikinger'
and the 2009 released VC version. Unless there is some way this would show up as 'Burikinger' in a Japanese bios ?
(i'll try some editing in the rom later today when i'm off from work, to see what triggers this.)
-
Can you shed some details on what was modified ? Per chance, the name it shows up in 'soft dip' like Narcissus above writes ?
I could imagine for internationalization, that the naming inside the P1 would be 'fixed' for a 2009 release, with the bios showing
the correct name..
If you look in the VC p1 dump from Ironclad, it shows the BURIKINGER name at hex 0201 and 'IRONCLAD' at hex 03EA (three.)
I asked for the soft dip screenshot, so i could compare.
I guess we have at least two different versions. The proto version where those shots came from 'burikinger'
and the 2009 released VC version. Unless there is some way this would show up as 'Burikinger' in a Japanese bios ?
(i'll try some editing in the rom later today when i'm off from work, to see what triggers this.)
I showed it to you...
But the screenshot was took with winkawaks
You know winkawaks doesn't use bios to change area...
-
I showed it to you...
But the screenshot was took with winkawaks
You know winkawaks doesn't use bios to change area...
Your soft dip shot is from the VC rom under Winkawaks ? (i could not find a full JAPAN bios for NeoRageX)
This isn't from a PROTO dump right ?
-
I showed it to you...
But the screenshot was took with winkawaks
You know winkawaks doesn't use bios to change area...
That really isn't proof of anything... My proof is that this game has the "winners don't use drugs" screen under the US region setting.
http://en.wikipedia.org/wiki/Winners_Don%27t_Use_Drugs
Can you shed some details on what was modified ? Per chance, the name it shows up in 'soft dip' like Narcissus above writes ?
I could imagine for internationalization, that the naming inside the P1 would be 'fixed' for a 2009 release, with the bios showing
the correct name..
Texts, such as the name in the bios often show differently under different regions.
As for what's modified, I haven't really looked into it that much. I'll have to go back at some point and examine.
-
Your soft dip shot is from the VC rom under Winkawaks ? (i could not find a full JAPAN bios for NeoRageX)
This isn't from a PROTO dump right ?
You can use Winkawaks yourself to make a try
But now I can't make it to show IRONCLAD... :S
I don't have the PROTO dump. I'm nobody so you don't believe me :redface:
-
You can use Winkawaks yourself to make a try
But now I can't make it to show IRONCLAD... :S
I don't have the PROTO dump. I'm nobody so you don't believe me :redface:
It's fairly normal that some games won't allow you to change the region properly unless you invalidate / reset the nvram.
Sengkou 3 is a good example of this, once you run the game it sticks in the first region you run it as until you either invalidate the nvram in test mode, or delete the file.
-
I compiled a FBA version with Ironclad support with last source code, I add this:
// Ironclad / Chotetsu Brikinger
static struct BurnRomInfo ironcladRomDesc[] = {
{ "220-p1.bin", 0x200000, 0x62a942c6, 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 }, // 10 Z80 code
{ "220-v1.bin", 0x400000, 0x8f30a215, 5 | BRF_SND }, // 11 Sound data
};
STDROMPICKEXT(ironclad, ironclad, neogeo)
STD_ROM_FN(ironclad)
struct BurnDriver BurnDrvironclad = {
"ironclad", NULL, "neogeo", "1996",
"Ironclad / Chotetsu Brikinger\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, neogeoDIPInfo,
NeoInit, NeoExit, NeoFrame, NeoRender, NeoScan, 0, NULL, NULL, NULL, &NeoRecalcPalette, 0x1000,
320, 224, 4, 3
};
The game is working, but only with USA - Japan bios, with asia or european doesn´t boot, also I notice a flickering in game intro.Are this thinks normal or I make a mistake adding the game to FBA?any correction in the driver?
Very Thanks!!!
-
For kicks, i've gone about and extracted the VC versions of FF1, FF2 and Top Hunter. (The others i got my hands on, have some kind of .z compression on the game.bin, not allowing me to extract..)
Fatal Fury 1/2 are both exactly the same as the dumps released back in the day. But Top Hunter has some differences... <snip>
Actually it's not, it's just "SET 2" with the sha-1 matching up exactly the same.
I think we could say for certain this dump is 100% original from production-type hardware, that was just never produced.
To confirm the other argument about the Burikinger name, just delete nvram and set to Japanese, the soft-dip cart name also changes to Burikinger instead of Ironclad.
-
Off topic:
MVS bootlegs are on sale.
Faster then I expected ...
-
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)
-
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
-
Set the region to Japan or USA. This also occurs in the NeoGeo CD version.
-
Pretty cool & interesting stuff guys! ^^
SeeYaa!
:biggrin:
-
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.
-
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.
-
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:
-
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:
-
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.
-
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.
-
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.
-
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.
// 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
};
-
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.