Da Slippery Minx
New member
Ok, so, I have a barrage of questions, which ever one you answer please reference the question number.
Is there a way to change data on the ROM on the fly so new data can be loaded into memory, something similar to how the Playstation 3 circumvented low memory by reading data off the hard drive? Perhaps there is a way to allow more data on a cart by swapping out the information in the ROM or RAM have it constantly be re-read.
Follow up question 1: Would an NES dev kit allow direct access to the memory for such an action?
Follow up question 2: is there a way to load Cart that acts as a boot for CIC chip that can hot swap multiple Carts that way you can have you game put in as chapter/volumes rather than all on one Cart? The reason I ask is due to the sever limitation of what textures are possible per Cart. if you had only one chapter or level on a Cart it could be vast and feature a lot of texture and enemies and complex background, but the game would ultimately be short unless there is a way to circumvent the limitations. With something like a Dev Cart that has direct access to the texture ROM and or RAM? Your could essentially have a master PC Board with banks to store the Chapters with their own prospective Tile Sets.
Follow up question 3: Releasing a game as chapters or individual levels could yield an incredibly diverse game even with the current set of limitations, even a master cart that can load many ROMS could load many chapters but these Carts often cost way more than what they are worth (master carts = emulator Cart that runs ROMS.)
Follow up question 4: Is there a way to swap out tile sets per chapter/volume, to expand on the level maps and enemies. Ie, keep save data on the master cart and any other necessary data (sub carts hold the Chapters), dump the old data of the chapter/level from Memory (but keeping the necessities) and load in the new chapter.
Is there a way to change data on the ROM on the fly so new data can be loaded into memory, something similar to how the Playstation 3 circumvented low memory by reading data off the hard drive? Perhaps there is a way to allow more data on a cart by swapping out the information in the ROM or RAM have it constantly be re-read.
Follow up question 1: Would an NES dev kit allow direct access to the memory for such an action?
Follow up question 2: is there a way to load Cart that acts as a boot for CIC chip that can hot swap multiple Carts that way you can have you game put in as chapter/volumes rather than all on one Cart? The reason I ask is due to the sever limitation of what textures are possible per Cart. if you had only one chapter or level on a Cart it could be vast and feature a lot of texture and enemies and complex background, but the game would ultimately be short unless there is a way to circumvent the limitations. With something like a Dev Cart that has direct access to the texture ROM and or RAM? Your could essentially have a master PC Board with banks to store the Chapters with their own prospective Tile Sets.
Follow up question 3: Releasing a game as chapters or individual levels could yield an incredibly diverse game even with the current set of limitations, even a master cart that can load many ROMS could load many chapters but these Carts often cost way more than what they are worth (master carts = emulator Cart that runs ROMS.)
Follow up question 4: Is there a way to swap out tile sets per chapter/volume, to expand on the level maps and enemies. Ie, keep save data on the master cart and any other necessary data (sub carts hold the Chapters), dump the old data of the chapter/level from Memory (but keeping the necessities) and load in the new chapter.
