AES - Emuversal Bulletin Board

You are not logged in. [Log In] Emuversal Bulletin Board » Forums » Official Emulator Message Boards » MESS » AES

Page 1 of 4

Topic Options

#61888 - 18/05/10 02:18 PM

AES

mahlemiut Offline

Senior Member

Registered: 24/12/06
Posts: 158
Loc: New Zealand

Having some issues in getting Blue's Journey running in the AES driver... It runs okay, but there are missing graphics and sound samples. The MAME source says the cart is both MVS and AES, and it fits in the (still) limited memory regions. I must be missing something but can't think what as it works in MAME fine.

layout.xml is as follows:

Code:

<?xml version="1.0" encoding="utf-8"?>
<romset version="1.0">
   <resources>
      <rom id="program" file="022-p1.bin"       crc="6a2f6d4a" sha1="b8ca548e56f1c7abcdce415ba7329e0cf698ee13"/>
      <rom id="tiles" file="022-s1.bin"         crc="843c3624" sha1="dbdf86c193b7c1d795f8c21f2c103c1d3e18abbe"/>
      <rom id="z80prg" file="022-m1.bin"        crc="8e1d4ab6" sha1="deabc11ab81e7e68a3e041c03a127ae28d0d7264"/>
      <rom id="ymsamples" file="022-v11.bin"    crc="2cb4ad91" sha1="169ec7303c4275155a66a88cc08270c24132bb36"/>
      <rom id="ymsamples2" file="022-v22.bin"   crc="65a54d13" sha1="a591fbcedca8f679dacbebcd554e3aa3fd163e92"/>
      <rom id="sprite1" file="022-c1.bin"       crc="4d47a48c" sha1="6e282285be72583d828e7765b1c1695ecdc44777"/>
      <rom id="sprite2" file="022-c2.bin"       crc="e8c1491a" sha1="c468d2556b3de095aaa05edd1bc16d71303e9478"/>
      <rom id="sprite3" file="022-c3.bin"       crc="66e69753" sha1="974b823fc62236fbc23e727f25b61a805a707a9e"/>
      <rom id="sprite4" file="022-c4.bin"       crc="71bfd48a" sha1="47288be69e6992d09ebef108b4de9ffab6293dc8"/>
   </resources>
   <configuration>
      <pcb type="standard">
         <socket id="p1" uses="program"/>
         <socket id="s1" uses="tiles"/>
         <socket id="m1" uses="z80prg"/>
	 <socket id="v11" uses="ymsamples"/>
	 <socket id="v12" uses="ymsamples2"/>
	 <socket id="c1" uses="sprite1"/>
	 <socket id="c2" uses="sprite2"/>
	 <socket id="c3" uses="sprite3"/>
	 <socket id="c4" uses="sprite4"/>
      </pcb>
   </configuration>
</romset>

_________________________
- Barry Rodewald

Top

#61890 - 18/05/10 03:32 PM Re: AES [Re: robbbert]
Firewave Senior Member Registered: 21/09/01 Posts: 476	Not to be harsh, but you just repeated what Barry wrote initially...
Top

#61892 - 18/05/10 03:40 PM

Re: AES [Re: Firewave]

Firewave Offline

Senior Member

Registered: 21/09/01
Posts: 476

Any reason "zoomy", "fixed" and "fixedbios" are differently ordered??

MAME:

Code:

	ROM_REGION( 0x20000, "fixed", 0 ) \
	ROM_LOAD( name,       0x000000, 0x20000, hash ) \
	ROM_REGION( 0x20000, "fixedbios", 0 ) \
	ROM_LOAD( "sfix.sfix", 0x000000, 0x20000, CRC(c2ea0cfd) SHA1(fd4a618cdcdbf849374f0a50dd8efe9dbab706c3) ) \
\
	ROM_Y_ZOOM

#define ROM_Y_ZOOM \
	ROM_REGION( 0x20000, "zoomy", 0 ) \
	ROM_LOAD( "000-lo.lo", 0x00000, 0x20000, CRC(5a86cff2) SHA1(5992277debadeb64d1c1c64b0a92d9293eaf7e4a) )

MESS:

Code:

	ROM_REGION( 0x20000, "zoomy", 0 )
	ROM_LOAD( "000-lo.lo", 0x00000, 0x20000, CRC(5a86cff2) SHA1(5992277debadeb64d1c1c64b0a92d9293eaf7e4a) )

	ROM_REGION( 0x20000, "fixedbios", 0 )
	ROM_LOAD( "sfix.sfix", 0x000000, 0x20000, CRC(c2ea0cfd) SHA1(fd4a618cdcdbf849374f0a50dd8efe9dbab706c3) )

	ROM_REGION( 0x20000, "fixed", ROMREGION_ERASEFF )

MESS also sets "fixed" with ROMREGION_ERASEFF instead of 0.

Top

#61894 - 18/05/10 03:53 PM Re: AES [Re: Firewave]
Firewave Senior Member Registered: 21/09/01 Posts: 476	And the audio stuff is after the fixed stuff in MAME and "audiocpu" is also using ROMREGION_ERASEFF instead of 0 in MESS.
Top

#61895 - 18/05/10 04:19 PM Re: AES [Re: Firewave]
Firewave Senior Member Registered: 21/09/01 Posts: 476	Bah...ng_aes.c and neogeo.c share a lot of code and it seems some changes didn't make it to the aes one. I think they should somehow have a file with the common functions and stuff.
Top

#61896 - 18/05/10 04:33 PM Re: AES [Re: Firewave]
R. Belmont Senior Member Registered: 17/03/01 Posts: 12492 Loc: USA	Region order cannot matter, and the erase is necessary for MESS because of some differences in how we load the ROMs.
Top

#61904 - 18/05/10 05:36 PM Re: AES [Re: R. Belmont]
Firewave Senior Member Registered: 21/09/01 Posts: 476	Yeah, sorry. I confused the regions with the memory map.
Top

#61913 - 18/05/10 11:05 PM Re: AES [Re: Firewave]
Haze Senior Member Registered: 27/05/04 Posts: 340	wouldn't it just make sense to use the MAME rom loading here.. Yeah, software lists, xml, blah blah blah, but the code is already there....... reinventing the wheel just gives you two places to maintain it, in different formats, and introduces problems like this. as for why it doesn't work, I don't know. I look at that XML and it tells me nothing about how things are actually loaded, no rom sizes, no region sizes (which can have an impact on mirroring of tiles etc. if addresses out of the range of the cart are specified). I look at the rom loading in MAME and it makes sense.
Top

#61914 - 18/05/10 11:13 PM Re: AES [Re: Haze]
etabeta78 Senior Member Registered: 27/01/06 Posts: 2060 Loc: Trondheim, Norway	how would you support the games? by loading them separately as if they were different systems (with an hack like cpschanger)? how would this help documenting the system? it would possibly lead the user to think these were plug-in game like Batman thing (or like the Radica controllers) otoh, if you want to see where things are mapped, you have to look at the aes multicart device, not to the xml. I can see aspects of the multicart which could be improved, but it is definitely better than having these as separate drivers
Top

#61916 - 18/05/10 11:26 PM Re: AES [Re: Haze]
mahlemiut Senior Member Registered: 24/12/06 Posts: 158 Loc: New Zealand	ROM sizes are simply the size of the ROMs that are loaded from the zip. Regions sizes are hard-coded currently (and are far too small for many games), which certainly needs to change at some point. But in the case of Blue's Journey, I can't see why it doesn't work. The ROM regions are large enough for the game, and it should load the ROMs the same way as MAME does, but something(s), somewhere, appears to be missing. _________________________ - Barry Rodewald
Top

Page 1 of 4

Previous Topic

Index

Next Topic

Moderator: Bletch, R. Belmont, Richard Bannister