Jump to content
HyperSync, HyperList and FTP are now back online ×
Honosuseri

Hyperspin modified for RetroArch 32bit (aka Retroarch_ra32)

Recommended Posts

Posted (edited)

Right guys as some of you are aware Google changed how things work on the Google Play Store a while back, when we install an app it will use the 32 or 64 bit version depending on what's native to the device. As we're mainly focused on the Shield TV here on the Android part of the forum, it is a 64 bit device. This has proved to be a bit of an issue for those of us who love Retroarch as there are some serious differences between the 32bit and 64bit versions. In a nutshell currently we have access to more cores for us to play our retro systems on the 32 bit version. RetroArch provide a RetroArch_ra32.apk which is a dedicated 32bit version we can sideload/install and use, however Hyperspin is NOT setup to use this version as some of the paths changed.

So...I decompiled the Hyperspin.apk and made the necessary changes (yes including the config path) to solely use RA_32. I've done some limited testing with RA_32 (1.8.7) and it seems a okay to me (even the Daphne test core works) however I don't use screen overlays or really bother with alternate config setups (in truth I've not used the STV in many months!). Feel free to download it and test yourselves, obviously backup your essential files AND do remember the .ini files need to be adjusted to use RA32....

exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture
becomes
exe=com.retroarch.ra32/com.retroarch.browser.retroactivity.RetroActivityFuture

It's easy enough to open all your .ini files with notepad++. Use the Search and replace feature to find com.retroarch/ and replace to com.retroarch.ra32/ do this for all opened files then save all.

Those who use adopted storage it's wise to move the Retroarch_ra32 app to internal storage after installing AND before running it for the first time. Let me know how it works for you, I'll do a Youtube video to help those less experienced with setting up Hyperspin when I know it's working 100% and I have the free time.

Mega Link for Hyperspin_0.1.8_Hono.apk (https://mega.nz/file/zQNBCYKI#QVrG4uVVmvXHshl8LbosQi7LAjQmUA09R5k_YqhcMBI)
RetroArch_ra32 (1.9.0) newest stable version at time of posting (https://buildbot.libretro.com/stable/1.9.0/android/)

Edited by Honosuseri
Updated link for RA_32
  • Like 1
  • Super Like 2

Share this post


Link to post
Share on other sites
1 hour ago, Honosuseri said:

Right guys as some of you are aware Google changed how things work on the Google Play Store a while back, when we install an app it will use the 32 or 64 bit version depending on what's native to the device. As we're mainly focused on the Shield TV here on the Android part of the forum, it is a 64 bit device. This has proved to be a bit of an issue for those of us who love Retroarch as there are some serious differences between the 32bit and 64bit versions. In a nutshell currently we have access to more cores for us to play our retro systems on the 32 bit version. Retroarch provide a Retroarch_ra32.apk which is a dedicated 32bit version we can sideload/install and use, however Hyperspin is NOT setup to use this version as some of the paths changed.

So...I decompiled the Hyperspin.apk and made the necessary changes (yes including the config path) to solely use RA_32. I've done some limited testing with RA_32 (1.8.7) and it seems a okay to me (even the Daphne test core works) however I don't use screen overlays or really bother with alternate config setups (in truth I've not used the STV in many months!). Feel free to download it and test yourselves, obviously backup your essential files AND do remember the .ini files need to be adjusted to use RA32....

exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture
becomes
exe=com.retroarch.ra32/com.retroarch.browser.retroactivity.RetroActivityFuture

It's easy enough to open all your .ini files with notepad++. Use the Search and replace feature to find com.retroarch/ and replace to com.retroarch.ra32/ do this for all opened files then save all.

Those who use adopted storage it's wise to move the Retroarch_ra32 app to internal storage after installing AND before running it for the first time. Let me know how it works for you, I'll do a Youtube video to help those less experienced with setting up Hyperspin when I know it's working 100% and I have the free time.

Mega Link for Hyperspin_0.1.8_Hono.apk (https://mega.nz/file/zQNBCYKI#QVrG4uVVmvXHshl8LbosQi7LAjQmUA09R5k_YqhcMBI)

Great work mate. I will try this out over the next few days and report back.

ps, I don't suppose you have the settings for Citra for 3DS now it's on Google Play ?

Thanks again for all your work.

Share this post


Link to post
Share on other sites
Posted (edited)
On 5/24/2020 at 6:16 PM, Creezz67 said:

Great work mate. I will try this out over the next few days and report back.

ps, I don't suppose you have the settings for Citra for 3DS now it's on Google Play ?

Thanks again for all your work.

If cores aren't working please check that their names haven't changed since you last setup RA and the .ini files. I look forward to hearing how it works out for you, honestly I don't use the STV much anymore. I've got a lot going on at home so my free time for testing is limited, yes even when we're in "lock down".

Regarding your P.S...I'm not a Nintendo fan and no I don't have Citra installed on the STV however you can try "exe=org.citra.citra_android/org.citra_android.ui.main.MainActivity". No guarantee it'll work the developers need to implement launch intent for the app to work with Hyperspin. I did get the Redream developer to add launch intent and tested the Dreamcast in Hyperspin with it, if you ask nicely devs tend to give their customers what they ask for.

All the best with it

Edited by Honosuseri
posted setting for wrong app...doh!

Share this post


Link to post
Share on other sites
3 minutes ago, Honosuseri said:

If cores aren't working please check that their names haven't changed since you last setup RA and the .ini files. I look forward to hearing how it works out for you, honestly I don't use the STV much anymore. I've got a lot going on at home so my free time for testing is limited, yes even when we're in "lock down".

Regarding your P.S...I'm not a Nintendo fan and no I don't have Citra installed on the STV however you can try "exe=com.citro3dmans.citro/com.citro3dmans.citro.MainActivity". No guarantee it'll work the developers need to implement launch intent for the app to work with Hyperspin. I did get the Redream developer to add launch intent and tested the Dreamcast in Hyperspin with it, if you ask nicely devs tend to give their customers what they ask for.

All the best with it

Will do, not too many have changed luckily or if they have I am not using them 😀

Share this post


Link to post
Share on other sites
3 minutes ago, Creezz67 said:

Will do, not too many have changed luckily or if they have I am not using them 😀

Keep in mind the Dolphin core is only on the 64bit version, so you won't have access to it on RA_32. The Dolphin core had graphical glitches in many of the games I tried, so I used the dedicated standalone Dolphin emulator. Things might have changed though, I'm impressed with the progress they've made on the PUAE core for the Amiga.

Share this post


Link to post
Share on other sites
8 minutes ago, Honosuseri said:

Keep in mind the Dolphin core is only on the 64bit version, so you won't have access to it on RA_32. The Dolphin core had graphical glitches in many of the games I tried, so I used the dedicated standalone Dolphin emulator. Things might have changed though, I'm impressed with the progress they've made on the PUAE core for the Amiga.

I use Dolphin so that will not be an issue luckily.

Also have not tried Amiga on RetroArch. Will they launch directly from rom now ?

Share this post


Link to post
Share on other sites
1 hour ago, Creezz67 said:

I use Dolphin so that will not be an issue luckily.

Also have not tried Amiga on RetroArch. Will they launch directly from rom now ?

FYI Amiga roms are strictly speaking BIOS (kickstart) files but I know what you meant. The PUAE core supports .zip and .lha files etc. you don't really need uae & hdf files now from what I've seen with my limited testing. We still have the problem that the Hyperspin Amiga database and media naming is out of whack to the latest Retroplay WHDLoad set.

I do have a dedicated thread for the Amiga here. I need to settle on how to statically name the games and in turn the media and obviously the database entries. How they're named can help the core decide which Amiga preset to use, it does do cycle exact emulation which is awesome so games will play at the correct speed even if the Amiga preset is "too powerful" for the game. That's something UAE4ARM can NOT do so technically RetroArch is now the best emulator for the Amiga on Android.

Share this post


Link to post
Share on other sites
On 5/24/2020 at 8:21 PM, Honosuseri said:

FYI Amiga roms are strictly speaking BIOS (kickstart) files but I know what you meant. The PUAE core supports .zip and .lha files etc. you don't really need uae & hdf files now from what I've seen with my limited testing. We still have the problem that the Hyperspin Amiga database and media naming is out of whack to the latest Retroplay WHDLoad set.

I do have a dedicated thread for the Amiga here. I need to settle on how to statically name the games and in turn the media and obviously the database entries. How they're named can help the core decide which Amiga preset to use, it does do cycle exact emulation which is awesome so games will play at the correct speed even if the Amiga preset is "too powerful" for the game. That's something UAE4ARM can NOT do so technically RetroArch is now the best emulator for the Amiga on Android.

Cool, FYI just tested over 150+ wheels  using RetroArch_ra32 1.8.8 and all load perfectly. GBA,PS1,SNES,NES, Sega Genesis, MAME, Panasonic 3DO, Sega CD etc

Only stuff not working are ones I needed to load from internal drive, it can't find them, e.g. Atari 5200, VTech Creativision

  • Super Like 1

Share this post


Link to post
Share on other sites
On 5/24/2020 at 8:41 PM, Creezz67 said:

Cool, FYI just tested over 200 wheels and all load perfectly. GBA,PS1,SNES,NES, Sega Genesis, MAME, Panasonic 3DO, Sega CD etc

Only stuff not working are ones I needed to load from internal drive, it can't find them, e.g. Atari 5200, VTech Creativision

Atari 5200 uses the Atari800 core which does a few Atari systems. Pretty sure that's broken on the 32bit version, if it won't play in Retroarch then Hyperspin obviously won't load it. It's part of my love/hate relationship with RetroArch. There are cases where 64bit is better BUT overall for me 32bit is more useful.

I'm not an Atari fan so it's no real issue for me, really REALLY retro games don't appeal to me. I don't emulate everything for bragging rights, I try to focus on systems and games myself and friends would play. I have tested emulators other than RA_32, Dreamcast with Redream and the Amiga with UAE4ARM both worked fine. I was pretty confident it was okay before posting it here, thank you for testing and letting me know.

Share this post


Link to post
Share on other sites

Yeah it is broken! I just got Atari 5200 working in RA_32 by manually installing the Atari800 core downloaded from here (http://buildbot.libretro.com/nightly/android/latest/armeabi/). I've done a Youtube video on how to manually install cores, I did this for the Daphne test core (I'll link the video below). The Atari 5200 games will probably fail to play first go though giving an error message. Just press back to get into the RetroArch quick menu, select options and change Atari system to 5200 and game should then spring to life. You can save the changes to the retroarch.cfg in the main menu for that change to be remembered

 

Share this post


Link to post
Share on other sites

This is great, today I tried the ra32 of retroarch before I found this, I changed in android.Manifest.xml from com.retroarch.ra32 to com.retroarch in the retroarch apk file. It worked. I really want to use both the 32 and 64 version, tried ZeroJay’s version of Hyperspin apk, that is supposed to work with both but I can’t get it to work, The retroarch version named  com.retroarch works but when trying aarch64 it loads but it doesnt find the configs correctly.

 

Share this post


Link to post
Share on other sites

I'm also interested on a version of Hyperspin that can reproduce Retroarch 32 and 64 bit like @mrfomt .

In my case I can't load aarch64. Say me that the exe is not correct.

Share this post


Link to post
Share on other sites
On 5/30/2020 at 10:17 PM, mrfomt said:

This is great, today I tried the ra32 of retroarch before I found this, I changed in android.Manifest.xml from com.retroarch.ra32 to com.retroarch in the retroarch apk file. It worked. I really want to use both the 32 and 64 version, tried ZeroJay’s version of Hyperspin apk, that is supposed to work with both but I can’t get it to work, The retroarch version named  com.retroarch works but when trying aarch64 it loads but it doesnt find the configs correctly.

 

Yes I'm aware of ZeroJay's modded apk and guys saying it didn't work correctly with the 64bit version of RA because of the config path. He did say he would look into it BUT that was quite some time ago now. I've been saying this for a very long time, I have NO real interest in the 64 bit version. The RA devs even admitted they were having trouble finding people to compile the cores for it. I'm sure it will improve and one day we shall all want to use it by default.

I did this modification mainly for myself and a friend of mine, he put his STV inside an old skool NES console which looks pretty sweet! I have a lot going on at home, family members with terminal cancer amongst other things. I have ZERO intention of trying to get Hyperspin on Android to work with both RA 32 & 64 bit. I've made this modded apk available for those who want to solely use RetroArch_ra32. I still have my Amiga project on the go to sort the system for both PC and Android, that is more of a priority to me.

I do use the Arc Browser frontend on my STV as well as Hyperspin. AB can use both RetroArch 32 & 64 bit versions, it has premade templates for the systems or you can configure it yourself. It's actually a very good frontend which is actively developed. I use Hyperspin for "showing off" to friends, day to day use AB does the job. I can say "Sonic" with voice search and the STV shows the movie I have in my KODI library and all the Sonic games across all systems AB has in it's library. Not that I'm knocking Hyperspin, I use it mainly on PC as that can do far more systems than Android.

Share this post


Link to post
Share on other sites

keeping an eye on this. Finally got round to reinstalling Hyperspin and Retroarch on my shield and was wondering why I was getting the blsck screen in Hyperspin when launching anything from the wheels. Will give this a go now and see how far I get. Thanks

Share this post


Link to post
Share on other sites
2 hours ago, Acet said:

keeping an eye on this. Finally got round to reinstalling Hyperspin and Retroarch on my shield and was wondering why I was getting the blsck screen in Hyperspin when launching anything from the wheels. Will give this a go now and see how far I get. Thanks

You're welcome! There's not really any more for me to add to this thread, other than perhaps a Youtube video to help "noobs" installing and setting it up. RetroArch_ra32 won't be updated by the Google Play store so if you want to update, download it and sideload the newer version.

As said earlier if some systems aren't playing, do check that the core name hasn't changed since you last made the .ini file for the system. As an example the Sega Dreamcast/ Sammy Atomiswave core is now "Flycast" it's been known as "BeetleDC" and "Reicast" in the past. You do need to adjust your .ini files to correct the exe line, as shown in the first post. The parameters line states the core to use so adjust those individually if the name has changed.

All the best with it, let me know how you get on. Creezz67 said he had over 200 wheels working, I posted a "fix" for the Atari 5200 he said didn't work.
 

Share this post


Link to post
Share on other sites
11 hours ago, Honosuseri said:

You're welcome! There's not really any more for me to add to this thread, other than perhaps a Youtube video to help "noobs" installing and setting it up. RetroArch_ra32 won't be updated by the Google Play store so if you want to update, download it and sideload the newer version.

As said earlier if some systems aren't playing, do check that the core name hasn't changed since you last made the .ini file for the system. As an example the Sega Dreamcast/ Sammy Atomiswave core is now "Flycast" it's been known as "BeetleDC" and "Reicast" in the past. You do need to adjust your .ini files to correct the exe line, as shown in the first post. The parameters line states the core to use so adjust those individually if the name has changed.

All the best with it, let me know how you get on. Creezz67 said he had over 200 wheels working, I posted a "fix" for the Atari 5200 he said didn't work.
 

Just checking, so RetroArch will not try to update this version if auto updates are left on ?

Thanks again.

Share this post


Link to post
Share on other sites

I got it working, fantastic work, thanks for the guide. 

I'm now trying to see if I can run this via a samba share from my linux box (as I wanted to serve it 3 different Shields around the house).

I've managed to mount the drive on linux and create a share, which I can view fine on my Windows 10 machine. On the Shield when I click on mount storage, it doesn't find it automatically. Instead, I added it by putting in the IP address\mount point (\\192.168.X.XX\sambashare) which seems to work, as it gets added OK and registers as connected.

However, when I then try to open Hyperspin it just gives me the pop-up saying "No Hyperspin Data folder found". I can successfully browse the folders in other apps (i.e. in MAME I can find the share and add the roms path). Any clue on what I might be doing wrong?

The root of the share has the Hyperspin folder in it, so not sure why it's not being recognised, any thoughts on this? Or do I need to look at this differently where I have the hyperspin folder on each machine and then just store the artwork/videos/roms on the share?

 

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, Acet said:

The root of the share has the Hyperspin folder in it, so not sure why it's not being recognised, any thoughts on this? Or do I need to look at this differently where I have the hyperspin folder on each machine and then just store the artwork/videos/roms on the share?

The Hyperspin folder and media has to be on the device itself (or adopted storage) not the network iirc. You can have all the games on a NAS, you point the system .ini files to where the games are for that system with the rom path line.

Share this post


Link to post
Share on other sites
4 hours ago, Acet said:

I've managed to mount the drive on linux and create a share, which I can view fine on my Windows 10 machine. On the Shield when I click on mount storage, it doesn't find it automatically. Instead, I added it by putting in the IP address\mount point (\\192.168.X.XX\sambashare) which seems to work, as it gets added OK and registers as connected.

I am fairly certain some users have located the Hyperspin remotely with success but it depends on the path seen by the Shield. I myself have always used internal storage so can’t comment exactly. It’s worth trying a few things before moving everything to internal/adopted.

 

Hyperspin will only see the folder if it’s 1 hop. (“Storage”/sdcard , storage/emulated/0, storage/Hyperspin) some NAS devices allow you to have the Hyperspin folder exposed so the Shield sees that last path but on my synology it’s exsposed as storage/NAS/Hyperspin so is not found, where NAS is what i named my synology.

 

Have a search around the Android section, I’m sure someone wrote how they did it.

Share this post


Link to post
Share on other sites
On 6/4/2020 at 8:09 AM, Creezz67 said:

Just checking, so RetroArch will not try to update this version if auto updates are left on ?

Thanks again.

Correct, it won't auto update. I have RA_32 v1.8.5 on my Nokia 8 phone, we are now up to v1.8.8 and the Google Play Store shows no update notification for RetroArch. To update just download the latest apk file from RetroArch's stable builds. 

I've updated the OP with a link for 1.8.8. I'll try to keep it updated but it's easy enough to navigate backwards from that, to check if there is a newer version. Install the new apk over your old version, run it as you might need to update assets with the online updater BUT all your cores and settings will still be intact.

P.S Did you get Atari 5200 working with the link I posted for the alternate core?

Share this post


Link to post
Share on other sites
8 hours ago, Honosuseri said:

Correct, it won't auto update. I have RA_32 v1.8.5 on my Nokia 8 phone, we are now up to v1.8.8 and the Google Play Store shows no update notification for RetroArch. To update just download the latest apk file from RetroArch's stable builds. 

I've updated the OP with a link for 1.8.8. I'll try to keep it updated but it's easy enough to navigate backwards from that, to check if there is a newer version. Install the new apk over your old version, run it as you might need to update assets with the online updater BUT all your cores and settings will still be intact.

P.S Did you get Atari 5200 working with the link I posted for the alternate core?

Thanks for info

ps, not tried Atari 5200 again yet but will let you know once i have.

Just out of interest, can you install both versions of RetroArch (1.7.7) 32bit and this new RA_32 1.88 at the same time ? If so this would allow all systems to still work.

Share this post


Link to post
Share on other sites
6 hours ago, Creezz67 said:

Thanks for info

ps, not tried Atari 5200 again yet but will let you know once i have.

Just out of interest, can you install both versions of RetroArch (1.7.7) 32bit and this new RA_32 1.88 at the same time ? If so this would allow all systems to still work.

You're welcome! I have said this a few times, this build of Hyperspin is SOLELY for using RetroArch_ra32. It works and I am not developing it further to also use the default RetroArch or aarch64, it's a stop gap measure until the 64bit version is truly viable to be used.

RetroArch_ra32 does what I need it to do. I found an Atari 800 core you can manually install that works. I don't know what that other system is you mentioned that didn't work. Vtech Creativision is probably as old as me if not older! I doubt the games are actually any good and it's only real value would be nostalgia for people who once owned it. I dare say I could probably find a core to manually install to fix that too.

I barely use Hyperspin on my STV anymore as I've said earlier in the thread, Arc Browser can use the different RA releases. In many ways it's a far superior frontend and is actively developed getting better all the time. It has to be purchased BUT it can be shared with your family, Hyperspin does not work on phones but Arc Browser does making it more versatile. I have a lot going on at home, any free time I have now will be spent focusing on my Amiga Forever project. I already have the Amiga basically done using Arc Browser and RetroArch, that was very easy to do as it can scrape artwork and metadata online. Hyperspin is a bloody nightmare in comparison!

All the best with it, I'm sure you'll at least get the Atari 5200 up and working again very quickly.

Share this post


Link to post
Share on other sites

Sweet, got the samba share working. I can now service the three Nvidia Shields in my house and hopefully also use the Retroarch ROMs share path for my Nintendo Switch too. 

Share this post


Link to post
Share on other sites
6 hours ago, Acet said:

Sweet, got the samba share working. I can now service the three Nvidia Shields in my house and hopefully also use the Retroarch ROMs share path for my Nintendo Switch too. 

Maybe you could explain your setup in a separate thread it may help others in the future. 😀

its a little off topic for this thread

Share this post


Link to post
Share on other sites

Hello. I am from Spain, and a Nvidia Shield user. Install Hyperspin 0.1.8_Hono, later Retroarch_ra32_1.8.8 and configure it downloading cores, asets and other things. When I run a selected game on Hyperspin, always get a black screen. What am I doing wrong? This is my mame.ini file on settings folder:

Quote

[exe info]
path=H:\hyperspin\emulators\MAME\
rompath=Roms/MAME/roms/
userompath=true
exe=com.retroarch.ra32/com.retroarch.browser.retroactivity.RetroActivityFuture
romextension= zip
parameters=cores/mame2010_libretro.so
searchsubfolders=false
pcgame=false
winstate            = HIDDEN
hyperlaunch=true
Per_Game_Modules=false
Skipchecks=false
Hide_Cursor=use_global
Hide_Desktop=use_global
Hide_Taskbar=use_global
CPWizard_Enabled=use_global
CPWizard_Delay=use_global
CPWizard_Params=use_global
Fade_In=use_global
Fade_Out=use_global
Fade_Color=use_global
Fade_In_Duration=use_global
Fade_Out_Duration=use_global
Fade_In_Delay=use_global
7z_Enabled=use_global
7z_Extract_Dir=use_global
7z_Delete_Temp=use_global
Keymapper_Enabled=use_global
Keymapper=use_global
MultiGame_Enabled=use_global
MultiGame_Background_Color=use_global
MultiGame_Side_Padding=use_global
MultiGame_Y_Offset=use_global
MultiGame_Image_Adjust=use_global
MultiGame_Font=use_global
MultiGame_Text_1_Options=use_global
MultiGame_Text_1_Text=use_global
MultiGame_Text_2_Options=use_global
MultiGame_Text_2_Offset=use_global
MultiGame_Use_Sound=use_global
MultiGame_Sound_Frequency=use_global
MultiGame_Exit_Effect=use_global
MultiGame_Selected_Effect=use_global
MultiGame_Use_Game_Art=use_global
MultiGame_Art_Folder=use_global

[filters]
parents_only        = false
themes_only         = true
wheels_only         = false
roms_only        = false

[themes]
use_parent_vids=true
use_parent_themes=true
animate_out_default=false
reload_backgrounds=true

[wheel]
alpha=.15
small_alpha = 1
style               = normal
speed               = high
pin_center_width    = 500
horz_wheel_y        = 512
vert_wheel_position=right
y_rotation          = right
norm_large          = 360
norm_small          = 230
vert_large          = 400
vert_small          = 240
pin_large           = 500
pin_small           = 200
horz_large          = 240
horz_small          = 150
letter_wheel_x      = 800
letter_wheel_y      = 384
text_width          = 700
text_font           = Style2
small_text_width    = 260
large_text_width    = 400
text_stroke_size=6
text_stroke_color=0x000000
text_color1=0x00BFFD
text_color2=0xFFFFFF
text_color3=0x00BFFD
color_ratio=139
shadow_distance     = 0
shadow_angle        = 45
shadow_color=0x000000
shadow_alpha        = 1
shadow_blur         = 0

[pointer]
animated=true
x                   = 975
y                   = 384

[video defaults]
path=H:\hyperspin\Media\MAME\Video\

[sounds]
game_sounds         = true
wheel_click         = true

[navigation]
game_jump=50
use_indexes=false
jump_timer=400
remove_info_wheel=false
remove_info_text=true
use_last_game=true
last_game=thunderl
random_game=false

start_on_favorites=false
[Special Art A]
default=true
active=true
x=512
y=720
in=0.4
out=0.4
length=3
delay=0
type=normal
start=bottom

[Special Art B]
default=true
active=true
x=512
y=740
in=0.4
out=0.4
length=3
delay=0
type=fade
start=none

[Special Art C]
active=false
x=512
y=384
in=0
out=0
length=3
delay=10
type=fade
start=none

[Game Text]
game_text_active    = true
show_year           = true
show_manf           = true
show_description    = true
text_color1         = 0xFFFFFF
text_color2         = 0xFFFFFF
stroke_color        = 0x000000
text_font           = Style3
text1_textsize      = 26
text1_strokesize    = 7
text1_x             = 32
text1_y             = 610
text2_textsize      = 36
text2_strokesize    = 8
text2_x             = 30
text2_y             = 640

 

Thanks for the work!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By iamthamiz
      Hi Guys if your trying to set up M64plus FZ on android this is what i did to get my one up and running with NVida Sheild TV
       
      exe=org.mupen64plusae.v3.fzurita/paulscode.android.mupen64plusae.SplashActivity
      parameters=
      romextension= n64,z64,zip,v64
      searchsubfolders=false
       
    • By therourke
      I have a fully working build for Commodore Amiga now on my NVIDEA Shield (2017 model). It took me a good while to get it up and running.

      I thought it might be useful to post an 'all in one place' tutorial. Thanks go to Honosuseri over in this post for convincing me it was possible.
      Commodore Amiga is infamously painful to configure on any and all emulation setups. Retroarch takes the pain out of some of this, since we don't need individual .uae files for every single game now. But there are still some hoops to jump through.
      Onto the tutorial
       
      1. Find/setup your own Hyperspin
      Hyperspin is free and available on this very website. Install the app on your NVIDEA Shield, and compile your roms and Hyperspin setup on an appropriately sized external harddrive/USB.
      As for the ROMs, videos, wheel images and all the aesthetic stuff you need to get your setup running, you will have to source that yourselves. The Hyperspin website is good for some material, emumovies for videos, and Google and Archive dot org for everything in between. 
      For this setup I used a properly named romset for Commodore Amiga in .zip format, but you can also use .lha or .hdf format. .lha is smaller in size, but all of these run pretty much the same on Retroarch now. 
      There is no need for those pesky .uae files anymore!!!!!!!!!!
      Once you have all your roms, you will need to allocate them to the right videos and images and build your .xml database. The info for how to do this is available elsewhere on this very website. I used HyperspinChecker to do this.
      Now, onto the part where we make Hyperspin and Retroarch play nicely so you can finally play your Commodore Amiga games 
      2. WHDLoad and kickrom setup (bios file preparation)
      I obviously can't link to kickroms or WHDload.hdf and some other stuff, but Google is your friend.
      You can get kickroms legally as part of the Amiga Forever app on Google Play Store for only £1.79.
      You ABSOLUTELY NEED to get hold of these EXACT kickroms:
      kick34005.A500 kick37175.A500 kick40063.A600 kick40068.A1200 Some info on kickrom file names and how to match them up correctly can be found here.
      MAKE SURE THE FILENAMES ARE PRECISE! I left one of those As in lowercase and Retroarch didn't like it.
      You also need a properly prepared WHDLoad.hdf file: ADD THESE EXACT KICKROMS TO YOUR WHDload.hdf file (guide to do this here using ADF Opus)
      Copy all these file to the external drive you are keeping your Hyperspin setup on (I made a 'bios' folder in mine for safe keeping).
      3. Retroarch Setup
      Install the latest Retroarch on your NVIDEA Shield (probably works on other Android setups too). You can do this through the Google Play store, but as of writing this, version 1.8.9_GIT definitely works.
      You will need to make sure you have setup a way to load the Retroarch main menu from within games. Go to 'Settings', 'Input', 'Hotkeys' and set the 'Menu Toggle Gamepad Combo' to something like 'Select + Start'.
      Download the latest Commodore - Amiga (P-UAE) core from within Retroarch (use 'Online Updater' menu)
      Now 'Load Core' and choose the P-UAE Core. Start the core, then immediately go back to the Retroarch menu (Start + Select). From the 'Quickmenu' select 'Options'. Change the 'Model' here to something with plenty of power like the 'A1200 (2MB + 8MB)'. Scroll down to 'Global Boot HD' and 'WHDLoad Support' and make sure both of these are marked as 'Files'.
      One other thing from within Retroarch: having a way to 'Quit' from within games is useful for Hyperspin. So go to 'Settings', 'Hotkeys' choose a button for 'Quit Retroarch' (I use the click of my Left Analogue, but anything will do). You may also need to mess around with button mappings, but most of this should work fine if you have a NVIDEA Shield compatible gamepad. Mouse and keyboard are also, obviously, nice additions for Amiga stuff.
      Go back to 'Quick Menu', 'Overrides' and select 'Save Core Overrides' to make sure your Retroarch Amiga setup is saved.
      Lastly, and very importantly...
      Leave Retroarch. You will need an Android directory viewing program like 'FX File Explorer' for this step. Copy the EXACT kickroms listed above and the WHDload.hdf file you created into the /Retroarch/System/ folder on the INTERNAL drive of the NVIDEA Shield.
      4. Commodore Amiga.ini Commands
      In your Hyperspin setup you should now have all your roms, videos, images, menu setup, and a Commodore Amiga.xml database file all neat and tidy.
      You now need to get Hyperspin to talk to Retroarch properly.
      Back on your PC, load your Hyperspin folder and go to the /Settings_Android/ folder.
      Create or open the Commodore Amiga.ini in a text editor. Most of the stuff in here will be the same as other systems, but you can find my ini file attached here.
      Make sure the top lines in your ini read like this:
      [exe info] path=H:\hyperspin\emulators\Commodore Amiga\ rompath=Roms/Commodore Amiga/roms userompath=true exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture romextension=zip,hdf,lha,HDF,ZIP,LHA parameters=cores/puae_libretro_android.so searchsubfolders=false pcgame=false winstate=HIDDEN hyperlaunch=true Each of these lines corresponds to your setup. So if you have your roms folder somewhere else, you need to tell the file. If you are ONLY using .zip versions of your roms, then you don't need the entire 'romextension=zip,hdf,lha,HDF,ZIP,LHA'  line - you can change this to just 'romextension=zip' and it will work fine. (But my line here covers all the possible rom extensions, so you can leave it). The 'exe' and 'parameters' entries are really important, as this tells Hyperspin to load Retroarch, and then Retroarch which core to load for Commodore Amiga.
      Save your file, and hook your Hyperspin external drive back to your NVIDEA Shield.
      5. Play some games
      Everything *should* be working now. If you are having problems with videos and roms matching up, or entries showing in the Amiga menu on your Hyperspin, then that is an issue with your original setup. There are many tutorials out there.
      I can vouch that THIS EXACT setup works great, and loads and plays most Amiga games I have thrown at it without too many glitches.
      6. Now, please answer me a Q 
      When using an external mouse in Retroarch and playing a game like Lemmings, I get TWO cursors - the in game Lemmings cursor, and the NVIDEA Shield arrow.
      Does anyone know how to get rid of this for good? Thanks
      Commodore Amiga.ini
    • By Wandurlust
      Hi all, It seems retroarch (at least on android) has removed their Mupen64plus core and replaced it with Mupen64plus-next. My hyperspin (Nvidia shield) won't launch N64 games anymore because it's trying to launch a core that no longer exist. I have tried editing my "Nintendo 64.ini" file with multiple variations to get the new core to launch, but I cannot get it to work. Anyone know the new core parameters off hand? I've searched quite a bit and am coming up empty.  Just to clarify I'm looking for the "Parameters =" line under the exe= that determines which core retro arch will use. I have confirmed manually loading the "Mupen64Plus-Next" core works with content. I just can't seem to get the command line correct to have it launch from hyperspin. Any help is appreciated thanks! I have already switched to it launching "Mupen64 FZ" in the meantime, but I prefer the launch coming from retroarch because FZ resumes mid-game where you left off when starting from hyperspin, and I prefer the WOW factor of games loading from the title screen.
    • By Honosuseri
      I realise there is already a thread for the Commodore Amiga in the Android section. I should know, as of late I've essentially taken it over! It's one of the most viewed threads in the Android section, so clearly many of you adore the Amiga as much as I do. 
      That thread has become quite long and it's quite confusing with people choosing to emulate the Amiga in different ways. I decided it would be best to start my own thread, streamlining it to show the best way to get this done. As I do have a "proof of concept" setup working! 
      This project I've taken on is a mammoth undertaking, as the Amiga is quite a complicated system to do. I'll try to explain why and how I've decided to proceed, keeping you guys up to speed with my progress here. 
      The first real issue is the naming that Hyperspin has been using for some time now. It's based from the Whdload zip file names, which was a logical choice BUT the problem is these zip names keep changing over time as they get updated. This throws the database entries and all media assets out of whack. It's my belief that this naming is what is really holding us back doing the Amiga justice.
      Second problem for us Android users anyway, is that we can't use the zip files directly with an emulator. They needed to be extracted out and we used a bootloader to patch the files for the emulator and launch the games. All seemed well and good until I started testing games and found many wouldn't work. Very confusing as the same game files worked fine from a workbench environment I'd set up, with it's own bootloader I added in. I suspected it was the "ultimate amiga" bootloader for the Hyperspin wheel at fault, which proved to be correct. 
      So the best way to launch these Amiga games from the Hyperspin wheel, is to actually use HDF versions of the games. This removes the need for the bootloader. I decided to keep the game folders extracted from the whdload zip files. Continuing to use these with the workbench (Amiga's OS) hdf I created. Having this is a nice nostalgic nod, I'm sure genuine Amiga fans will appreciate. 
      Unfortunately we can't just point the emulator to these hdf files, it's not that simple. Each game requires a config file that points to where the particular hdf game file is, what kick-start (i.e Bios) to use, video settings, control bindings etc. These files are known as uae files, as that is the extension we tell Hyperspin to look for. We trick it into thinking these uae's are the actual "game Roms".
      Sadly uae files aren't universal between emulators. So choosing the right emulator to begin with is important. Many people had chosen to use RetroArch. Which can't do the CD32, so I'll strike it off for that reason alone (although there are other reasons). I spent a long time waiting on Amiberry to be ported to Android but the devs haven't delivered. I'm not waiting any longer, so I'm continuing to proceed with Uae4arm. 
      As I write this, the latest version of Uae4arm crashes on Android TV (i.e Shield TV) but does run fine on Android phones. The devs are aware and trying to resolve this. There is an older apk version we can install for now, which does work. Another slight annoyance is that Uae4arm is quite fussy about how the uae files are named. They can NOT have special characters in them (e.g a space) or the emulator won't launch them!
      My next complaint was that Hyperspin has "rules" about what games should be included in the xml database file. I do NOT agree with these "guidelines". I want a definitive collection of Amiga games. 
      I've decided to branch the Amiga out into different wheels, ECS, AGA and CD32. As an analogy think of Sega's Megadrive and it's hardware addons. Megadrive=ECS, Sega32X=AGA (better graphics chipset on later Amigas) and finally the MegaCD=CD32 (better audio track and FMV).
      There is a "HDF game set" floating around. However... I got to know the creator, from doing videos on my proof of concept setup. I've persuaded him to rename the files to something more sensible, that should help other frontends scrape for metadata and artwork. These names will not change over time as he updates the collection. He does release notes, so this info can be used to keep the xml database file up to date. Currently he's overhauling the hdf files so they take up less storage and even adding cheat and trainer options to the loading splash screen....very cool stuff!
      I'm working on creating missing artwork (wheel, 3D box, diskette and video snaps), keeping busy until this new hdf collection is complete. Then I can start creating the uae files needed. This will be laborious, as Uae4arm doesn't do cycle exact emulation. I need to make sure each game is configured correctly to run at the proper speed, I'll also bind commonly needed keyboard keys to the gamepad on a per game basis.
      If you're confused, that's OK! It should all make sense, once I get around to uploading some more videos. Yes I will make my assets available to you all (minus the games obviously due to Hyperspin rules), once I'm happy with the collection.

      ***UAE4ARM BETA APK LINK***

      https://mega.nz/#!TYMQQKob!9pzwooQbkxVd-__mwmqtFWNF9JSR7D7rEgY8tqu31Vg
       
    • By Honosuseri
      Retroarch (Google Play) has updated itself to the latest version 1.7.8 and it seems to have broken compatibility with Hyperspin ?

      Having done some quick reading (https://www.libretro.com/index.php/retroarch-1-7-8-important-changes-for-people-using-the-google-play-build/) it seems under the "infinite wisdom" of Google. They're forced to build in both 32 and 64bit support for the app, so the device (Shield TV) will default to using the 64bit version as it is a 64bit device. I'm not entirely sure what's gone wrong as I haven't had time to delve further into it, although I know ZeroJay did a modded Hyperspin apk for 64bit support (that doesn't work either). Just wanted to warn users so they don't update and have any aggro.

      You can still side load 32bit versions of Retroarch, I'll do that later and test. I'm actually quite excited about some of the features that have now come in the latest version.

      ***EDIT***

      The retroarch_ra32.apk (v1.7.8) changes the path (typical). So it's now "exe=com.retroarch32/com.retroarch.browser.retroactivity.RetroActivityFuture". Hyperspin doesn't like this and it misbehaves as it did trying to load the original 64bit Google play version, which is why ZeroJay did the modified Hyperspin apk.
       
×
×
  • Create New...