Mame4all 1.3
#1
Posted 05 April 2008 - 11:50 AM
Changes by Headoverheels:
- New Gaelco games added (MAME 0.37b7): Big Karnak (bigkarnk) and Biomechanical Toy (biomtoy).
- New SunA 8 bit games added (MAME 0.37b15): Hard Head (hardhead), Hard Head (Bootleg) (hardhedb) and Rough Ranger (rranger).
- Optimizations in Xain'd Sleena.
- Fixed the NEC cpu bug that caused slowdowns in Raiden (MAME 0.37b15).
- Fixed some bugs in the I86/NEC cpu emulation. This includes raster effects problems in Geostorm and the 99 credits bug in Lethal Thunder (MAME 0.66).
Changes by Franxis:
- Cheats support added.
- Auto-fire support. Thanks to the code by AGAWA Koji.
- Jackal has been corrected.
Changes by Slaanesh:
- Optimizations in Commando (now it uses tilemaps).
The download is here.
#2
Posted 05 April 2008 - 12:14 PM
#3
Posted 05 April 2008 - 12:19 PM
(I'm really getting overwhelmed by the amount of new stuff coming in.
Thanks to all of you.
#4
Posted 05 April 2008 - 01:12 PM
#5
Posted 05 April 2008 - 01:56 PM
#6
Posted 05 April 2008 - 02:07 PM
#7
Posted 05 April 2008 - 02:55 PM
#8
Posted 05 April 2008 - 04:55 PM
Haven't tested the new one, in the last release, I had a wrong aspect ratio in "TEMPEST" (vector game), scaling and aspect ratio correction seems to not work with Vector games, right? ^^"
#9
Posted 05 April 2008 - 06:00 PM
Again a update, nice.
Haven't tested the new one, in the last release, I had a wrong aspect ratio in "TEMPEST" (vector game), scaling and aspect ratio correction seems to not work with Vector games, right? ^^"
You need to run Tempest rotated to get a closer aspect. You don't want to scale vectors, that would look hideous.
#10
Posted 05 April 2008 - 08:45 PM
#11
Posted 06 April 2008 - 12:43 AM
Changes say a bug was fixed to address slowdown in Raiden, but for me Raiden is even slower than it was in 1.2. No loss though really, because it was never fast enough to be playable in 1.2 anyway.
I'd have to agree. BUT... the Raiden driver is incorrect as it defines the V30 cpus to be running at 19Mhz - which is wrong. They actually should be 10Mhz. In effect they are being viciously overclocked. The solution is to set the Video CPU setting down to say 60%.
There is another gotcha. Whilst the fix corrects the V30 CPU, it also slows it done as the cycle times for most instructions were overstated in the previous core. The effect was that it was doing less work to emulate the required speed. Now it's doing more work for the same speed. I think the net effect is that the new V30 CPU core is more accurate though somewhat slower.
#12
Posted 06 April 2008 - 10:17 AM
#13
Posted 07 April 2008 - 11:45 AM
Edited by geise69, 07 April 2008 - 11:46 AM.
#14
Posted 07 April 2008 - 01:23 PM
Franxis thank you so much for another fine update! I have one question though. Were you ever able to fix MAME to use the upper memory? I remember you saying there was a bug with that, but it probably wasn't going to be easy to fix. I was just wondering. Thanks again for you ongoing work for MAME!
I was wrong, there isn't a bug. The upper memory is used correctly. There is enough memory to emulate the big neogeo games but the new neogeo driver allocates a memory chunks of about 32 mb (instead of 2 chunks of 16 mb). This is why they don't run in the new port. Play them with gngeo because i don't know if i will be able to fix it.
#15
Posted 08 April 2008 - 08:28 AM
Franxis thank you so much for another fine update! I have one question though. Were you ever able to fix MAME to use the upper memory? I remember you saying there was a bug with that, but it probably wasn't going to be easy to fix. I was just wondering. Thanks again for you ongoing work for MAME!
I was wrong, there isn't a bug. The upper memory is used correctly. There is enough memory to emulate the big neogeo games but the new neogeo driver allocates a memory chunks of about 32 mb (instead of 2 chunks of 16 mb). This is why they don't run in the new port. Play them with gngeo because i don't know if i will be able to fix it.
Hi Franxis












