Poll: one or two cores for 1942/Vulgus
I am pretty much done with GunSmoke and I have moved to Vulgus. This game runs on almost the same board as 1942.
I could make the two games run on a single core. Or I could keep using the one-core-per-game approach.
What do you prefer?
Comments (11)
It would be a different approach to other cores and probably would cause confusion.
I agree with most commenters that it should be two cores if the hardware is different, no matter if it is a small or large difference. Also I am dreaming on MiST support for remembering the last selected core, so that next time I restart the machine it will automatically pick that core, much like having the original harware without needing to dedicate one SDCard per machine.
Hi Manuel, I totally agree. I have asked for it here: https://github.com/mist-devel/mist-board/issues/115
There are enough differences so ROMs cannot be exchanged on the original boards and conversion of one into the other would imply creating a daughter PCB
If there’s no difference hardware-wise, there’s no reason to multiply the cores. But regarding the user ease of use it would be much clear to have 2 cores. It would be strange to have a core named 1942-vulgus
Yo también creo que lo mejor es que sean independientes, como en el mame, que no los trata como clones.
In my opinion it should be independent cores for different games unless they really are on the same arcade system (like Sega System16, Capcom CPS1 or Irem m72)
Umm... if Vulgus was a variant of 1942 the way 1943 Kai is a variant of 1943 then merged. Otherwise my vote would be Independent cores in this situation. I know they are both shooters though different in style and feel, just my take...
vulgus isn't a variant of 1942 like 1943 kai is from 1943 :)
I think it raises a larger question. What about having one “arcade core” with a rom list that selects the appropriate core? I dunno maybe I’m crazy...
Like a front-end specific to arcade cores, maybe even with some screen shots. I think probably some scene developers will end up creating this frontends that will replace the default one.
