Custom executable param

[ricardo85x]

Custom executable param

 

Hi guys (sorry about my english)

 

I used to use another gui(XBMC). And I could configure like that:

 

...

<application>/system/bin/sh</application>
            <args>/storage/sdcard1/retro/customLauncher.sh '%rom%'</args>
            <rompath>/storage/sdcard1/ROMs/N64</rompath>

 

...

 

 

so when I select a rom the XBMC did run this on android:

 

/system/bin/sh /storage/sdcard1/retro/customLauncher.sh /storage/sdcard1/ROMs/N64/007 - GoldenEye (USA).zip

 

The customLauncher.sh was a script I did to select the right retroarch config like :

IF is N64 it will run:

 

        am start --user 0 -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -e ROM "/storage/sdcard1/ROMs/N64/007 - GoldenEye (USA).zip" -e LIBRETRO /data/data/com.retroarch/cores/mupen64plus_libretro_android.so -e CONFIGFILE /storage/sdcard1/retropad/n64_default.cfg -e IME com.android.inputmethod.latin/.LatinIME -n com.retroarch/.browser.retroactivity.RetroActivityFuture
 

 

The main reason to use it was to use a custom Retroarch CONFIGFILE per core/or game

 

Does hyperspin have a way to run a custom script with the rom path param ?

 

 

 

Thanks

[ricardo85x]

Thanks

I did never used hyperspin before.

I will read about this Rocket launcher.

 

but for my first research

Rockt Laucher is a exe executable.

I do not belive it will run on android.

[reznnate]

 

Does hyperspin have a way to run a custom script with the rom path param ?

 

 

No scripts are supported today.   You can see examples of launcher parameter syntax in emulator 'settings' posted here: 

http://www.hyperspin-fe.com/topic/8537-settings-android-emulator-settings/

 

For rompath, you can use literal path to your roms such as "/storage/sdcard1/ROMs/N64</rompath>" or if roms are in your Hyperspin folder, you can abbreviate as "<rompath>".   This is convenient if you want to move your setup between /sdcard, /sdcard1, or /usbdrive without modifying your settings.   I show this in demo files I posted - http://www.hyperspin-fe.com/files/file/7809-settings-android-10may20157z/

 

Some emulators have an additional parameter to define cores or paths and you can see this utilized in the various sample .ini's as well - http://www.hyperspin-fe.com/files/file/7809-settings-android-10may20157z/

 

 

I would like to add a new feature (I've called "uber-wheel" in to-do feature list) that would allow you to define custom emulator-launch parameters PER game in a dbase.xml file (i.e. fields for exe=, params=, rompath=).  I haven't gotten around to this yet.