Replies: 1 comment
-
|
Its not an uncommon solution, even xroar uses it. I wouldn't depend on the cart name but using the cart's hash could be a file that points to the actual cart's meta which could be any nice name for our sanity. e.g. cartId\5A3BC.....5931.meta -> cart\RoboCop.meta |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The VCC pak interface defines a way for hardware paks (.dlls) to provide a description of their function for display to the user. The MMI displays this information when a hardware pak is selected and it would not be difficult to provide means to show this information to users without selecting the pak in MMI config.
Software paks (.rom,.ccc) are most typically just copies of the ROM that came with the physical cartridge being emulated. Some other emulators maintain seperate pak metadata (by cart name) and can use it to display descriptions for users. They can also use the metadata to control behaviour for carts that have a built in MMU like the RoboCop does or for 32kb paks that have the 16kb in reversed order.
My question is do we want to do something simular for VCC?
Beta Was this translation helpful? Give feedback.
All reactions