2010-05-11, 02:57
To boot an Xbox-executable (XBE file) within a script:
XBMC.Runxbe only accepts one parameter, that being the program you want to boot. However, you can pass shortcut files to it, and those can contain the path to your emulator as well as the path to your ROM.
The usual trick is to have your front-end generate a shortcut file, then boot that via "XBMC.RunXBE". You can ignore the <label> and <thumb> tags for this purpose, as this particular shortcut won't be presented to the user.
(Actually, you should ignore the <thumb> tags anyway, but that's a long story...)
Where it gets complex is that most emulators expect to be passed the full path to their ROMs, but some will only work when passed the name of the zip file that contains the ROM data (as opposed to the path, or even the file extension)!
For example, with something like NeoGenesis (Mega Drive emulator):
My personal ROM collection is displayed/accessed via shortcuts, as per this thread. However, via shortcuts alone, the presentation options are limited to a name and a picture.
It's my understanding that the Xtras packs contain full pre-made CUTs for every game they cover, so it may be easier to just have the front-end deal with those rather then have it attempt to deal with the path configuration issues.
Quote:xbmc.executebuiltin('XBMC.Runxbe(PathToXBE)')For eg,
Quote:xbmc.executebuiltin('XBMC.Runxbe(E:\\Apps\\Emulators\\Surreal64\\default.xbe)')(Note the double slashes).
XBMC.Runxbe only accepts one parameter, that being the program you want to boot. However, you can pass shortcut files to it, and those can contain the path to your emulator as well as the path to your ROM.
The usual trick is to have your front-end generate a shortcut file, then boot that via "XBMC.RunXBE". You can ignore the <label> and <thumb> tags for this purpose, as this particular shortcut won't be presented to the user.
(Actually, you should ignore the <thumb> tags anyway, but that's a long story...)
Where it gets complex is that most emulators expect to be passed the full path to their ROMs, but some will only work when passed the name of the zip file that contains the ROM data (as opposed to the path, or even the file extension)!
For example, with something like NeoGenesis (Mega Drive emulator):
Quote:<shortcut>But with FBA-XXX (Neogeo and other arcade systems):
<path>f:\emulators\NeoGenesis\default.xbe</path>
<custom>
<game>f:\emulators\NeoGenesis\sgenroms\Sonic the Hedgehog.zip</game>
</custom>
</shortcut>
Quote:<shortcut>Hence users will need to configure the front-end with where each of their emulators are located, and how each emulator expects to see ROM paths.
<path>f:\emulators\FBA-XXX\default.xbe</path>
<custom>
<game>mslug</game>
</custom>
</shortcut>
My personal ROM collection is displayed/accessed via shortcuts, as per this thread. However, via shortcuts alone, the presentation options are limited to a name and a picture.
It's my understanding that the Xtras packs contain full pre-made CUTs for every game they cover, so it may be easier to just have the front-end deal with those rather then have it attempt to deal with the path configuration issues.