Themaister
commented
10 years ago So, we have retro_load_game_special(). It takes:
retro_load_game_special(unsigned game_type, const struct retro_game_info *info, size_t num_info);The "type" of special ROM (Sufami Turbo, SGB, etc) is set in game_type and multiple ROMs are passed in info/num_info. The thing however is that we don't know which types of game_type we can pass it, and the number of roms which is the problem here.
So, the proposed interface must pass a list of supported ROM types, and for each ROM type, we have to pass descriptors for what we want the frontend to put in the various info structs.
#define RETRO_ENVIRONMENT_GET_PARAMETERS 33doesn't sound quite right, maybe RETRO_ENVIORNMENT_SET_SPECIAL_GAME_TYPES? Doubt we need a GET version of that. This is something the core signals to the frontend at beginning.
struct retro_game_special_rom_info
{
const char *desc; // Describes what the ROM is (SGB bios, GB rom, etc).
const char *valid_extensions; // Same as get_system_info.
bool need_fullpath; // Same as get_system_info.
bool required; // If the ROM is required to load a game. Will probably be useful. if not loaded, just pass a blanked out retro_game_info ...
};
struct retro_game_special_info
{
const char *desc; // Human-readable string of the rom type, e.g. "Super GameBoy"
unsigned id; // The ID we pass to retro_load_game_special().
size_t num_info; // Number of ROM infos we have to pass.
const struct retro_game_special_rom_info *infos; // Infos for each ROM.
};And you could call:
struct retro_game_special_info special[] = {
{ "Sufami Turbo", 0, 3, ... },
{ "Super GameBoy", 1, 2, ... },
{ NULL }, // Terminate array
};
environ_cb(RETRO_ENVIRONMENT_SET_SPECIAL_GAME_TYPES, special);Think that can work for MESS?
andres-asm
It would be great to have a standard method to load special content. I have a few ideas but I'm not sure how to implement them, I thought I'd mention my ideas here before even trying.
I think the best way would be to follow core options, I started by defining this:
in libretro.h:
For instance mess would return an array of parameters to the frontend, something like this:
For bsnes
The frontend then would have to populate a menu similar to the shader menu, where you can select from options on some entries and choose a filename on others.
Then when loading the game instead of passing retro_game_info, frontend would pass the list retro_game_special_parameter and the core would have to figure what to do with the parameters, something like this:
For a single disk FDS game in MESS:
For a multi disk FDS game in MESS (I don't know if such a thing exists):
For a SGB game in BSNES
For a SUFAMI game in TGB
Anyway, it's just my idea on how it could work, I understand how variable works but I don't think I know enough to be able to implement something similar core_options.c to populate and return this parameters