Anyone played the Frogger? Do you experience some timing issues / speedups in the game? Also I experience some random deaths for perfect jumps (not very often but still...). Even so the core is very playable, I just wanted to check with others if they have same experience or it is just me?

The latest Scramble (brighter version) introduced a problem.The main (front) bullets are not visible any more. They exist, hit enemies, but it us not possible to see them. Previous version worked fine.

Released pretty weird arcade - Dream Shopper. Not that i like this arcade, but i found original Pacman core doesn't emulate 8 sprites as it should. It emulates only 6 (as Pengo). So spend several days to understand the HW and ended with big refactoring of the code. Documents have non-true info about sprites and the HW capability. Anyway, i'm glad that i could make 8 sprites to work.

toromand wrote:The latest Scramble (brighter version) introduced a problem.The main (front) bullets are not visible any more. They exist, hit enemies, but it us not possible to see them.Previous version worked fine.

I've read good review about Computer Space with very precise technical description. It was written that missiles start from weird positions. So, it's odd even in original HW. I don't remember the link.. May be later i will find it.

uphhhhh... exhausted..All arcades (except homebrew and non-ROM) have been re-worked.Now ROMs are not included so there should be no risk when some copyright holder will come.

Some cores were improved a little like VanVanCar which is turned out used 8 sprites instead of 6. Old cores with separate coin button now merged with start button. Screen rotator has been improved and includes some top and bottom margins for better visibility. Some other improvements which i've forgot to mention.Since i have to rework 37 cores - it's possible some bugs will i will fix if you will find it.

Sorgelig wrote:uphhhhh... exhausted..All arcades (except homebrew and non-ROM) have been re-worked.Now ROMs are not included so there should be no risk when some copyright holder will come.

Some cores were improved a little like VanVanCar which is turned out used 8 sprites instead of 6. Old cores with separate coin button now merged with start button. Screen rotator has been improved and includes some top and bottom margins for better visibility. Some other improvements which i've forgot to mention.Since i have to rework 37 cores - it's possible some bugs will i will fix if you will find it.

Thank you for updating the Arcade cores. I've started to update the arcade cores on my MiSTer and ran into a problem with Xevious where it keeps looping through the ROM check (In game).No errors creating a.xevs.romThe only other one I've updated is Time Pilot and it works fine.

NML32 wrote:ran into a problem with Xevious where it keeps looping through the ROM check (In game).

what you mean by "in game"? It jumps to ROM check while you're playing?

When you start the game it goes through a rom/hardware check then goes to the title screen then starts the rom/hardware check all over again. I've tried a few different xevious.zip files all give the same results.

Darfpga wrote:Ok, let me know what do you decide to keep and what you don't when it's done.

I've updated my port with your code. Of course i prefer to use a synthesized audio which is awesome! I've also added some minor tweaks like option to use color mode and inversion synchronized to vsync.

Since you are good at audio synth, may be you can improve the galaxian core? Original HW uses several NE555 chips to synthesize the audio, while core uses some pre-recorded samples. Actually core uses some kind of synth audio, but still uses the samples - probably for noise.

NML32 wrote:When you start the game it goes through a rom/hardware check then goes to the title screen then starts the rom/hardware check all over again. I've tried a few different xevious.zip files all give the same results.

try this version:

Arcade-Xevious.zip

I've added some tweak. For me it works without ROM check cycling.

You do not have the required permissions to view the files attached to this post.

NML32 wrote:When you start the game it goes through a rom/hardware check then goes to the title screen then starts the rom/hardware check all over again. I've tried a few different xevious.zip files all give the same results.

try this version: Arcade-Xevious.zipI've added some tweak. For me it works without ROM check cycling.

I'm sorry you had to make a tweak. I finally found a rom that works. Now, the difficult part is going to be trying to figure out what rom set to use. I tried many roms and they all passed the build bat but only one (48k) works without the looping issue.

Update: I've updated my MiSTer with the latest Arcade cores and all are working great.

NML32 wrote:I'm sorry you had to make a tweak. I finally found a rom that works. Now, the difficult part is going to be trying to figure out what rom set to use. I tried many roms and they all passed the build bat but only one (48k) works without the looping issue.

Update: I've updated my MiSTer with the latest Arcade cores and all are working great.

Thanks sorgelig!!

I think, you need to find the site which doesn't rename the ROMs - so you will be able to match the ROM by names. Every different ROM set has its unique name according to MAME database. For example Xevious game has different ROM sets: xevios.zip, xevious.zip, xeviousa.zip, xeviousb.zip, xeviousc.zip. And only xevious.zip is the right one.My script doesn't check checksumms or hashes, so it's difficult to find the right ROM if zip name has been altered.

Sorgelig wrote:I think, you need to find the site which doesn't rename the ROMs - so you will be able to match the ROM by names. Every different ROM set has its unique name according to MAME database. For example Xevious game has different ROM sets: xevios.zip, xevious.zip, xeviousa.zip, xeviousb.zip, xeviousc.zip. And only xevious.zip is the right one.My script doesn't check checksumms or hashes, so it's difficult to find the right ROM if zip name has been altered.

Do you know which version of MAME did you use as reference? There have been cases of zip files changing across version so it's best to have a reference to help finding the right files.

Newsdee wrote:Do you know which version of MAME did you use as reference? There have been cases of zip files changing across version so it's best to have a reference to help finding the right files.

Anyway, good call to keep the ROMs out.

I don't think they rename existing ROMs. Since MAME doesn't include the ROMs, it would produce a big mess. I know some sites provide ROMs based on MAME names.Anyway, i've cloned MAME repository not long ago, so it should be one of latest versions.

By the way, if some one will create the tool or script which will check the ROMs parts against SHA-1 hash (which is available in MAME sources) then it would help a lot! And it doesn't require programming except making the bat/script file.

Newsdee wrote:Do you know which version of MAME did you use as reference? There have been cases of zip files changing across version so it's best to have a reference to help finding the right files.

Anyway, good call to keep the ROMs out.

I don't think they rename existing ROMs. Since MAME doesn't include the ROMs, it would produce a big mess. I know some sites provide ROMs based on MAME names.Anyway, i've cloned MAME repository not long ago, so it should be one of latest versions.

By the way, if some one will create the tool or script which will check the ROMs parts against SHA-1 hash (which is available in MAME sources) then it would help a lot! And it doesn't require programming except making the bat/script file.

Of course roms are renamed, for that reason Rom Managers exist like clrmamepro. They build the correct set based on CRC (checksum).Easy Solution, make a DAT for those needed ROM Files so everyone can build the correct Set with a Rom Manager.I am kinda busy atm and have no time to hunt down the correct Files for every core. I someone PM me those Files, i build the DAT for RomVault this evening.