tokumaru wrote:
...since AFAIK there aren't MMC3 clones available for building new carts, meaning that for each copy of your game you are gonna have to destroy an original MMC3 game.
No! Destroying old carts is against my belief system.
tokumaru wrote:
If you want to be able to destroy the whole level, then yeah, you are going to need the extra RAM, but if it's something around 2000 blocks or less you can probably remember the states of those using just the regular RAM. You just have to create a way to associate the groups of destructible blocks to the bitmaps that represent their state.
Yeah, I've considered doing something like this... Like a 1 bit-per destructible object (normal and destroyed state), but for what I want to do I might need more than two states.
tokumaru wrote:
...I'm just presenting some options you might not have considered, so that you can make an educated decision, or "weigh your options", like you just said.
Cool, yes I greatly appreciate the input.
tepples wrote:
And how hard is it with a status bar? Sonic doesn't use one, but SMB3 does.
I'm pretty sure I'm going to want a status bar. But from what I understand I can use a sprite 0 hit if I don't have scanline IRQs. Is that correct?
tepples wrote:
I came up with a compromise in which the engine restricts the map geometry to have only one destructible object per column of the map.
This seems like a really effective way of handling it, though again for what I want to do I might need more than one tile per row.
MottZilla wrote:
...If you have a compelling enough game I would imagine the effort would be made to get your game cartridges built.
This is good to know. I am going to do my best to use the least amount of resources as possible, but it is good to know that if I have no other option they might be able to work with me.
MottZilla wrote:
Now if you wanted something more fancy like MMC5...
Nah, as far as I can tell MMC3 will be plenty for what I'm planning. Out of curiosity what mapper, and how much RAM is Battle Kid?
65024U wrote:
Yeah, and since the best thing about MMC5, The extra sound, has been limited on US consoles, it seems like a waste anyway.
I actually wouldn't want that extra sound capability anyway, I want it to sound like the way I remember it as a young boy
Memblers wrote:
Maybe RetroZone could and will, but I wouldn't stake my project on it.
Point well taken, I'm going to try to keep this in mind along the way.
Memblers wrote:
On the PowerPak even with an FPGA, MMC3 doesn't work right...
Oh, how bad is it?
Thanks for all the great input everyone.