Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
  • Announcement

    Sorry for the recent downtime. Still much to do but we have the site updated, secure and back online.  Expect more changes.


Section Admin
  • Posts

  • Joined

  • Last visited

  • Days Won


thatman84 last won the day on August 1 2020

thatman84 had the most liked content!

About thatman84

Profile Information

  • Gender
    Not Telling


  • Location
    essex uk

Recent Profile Visitors

9,216 profile views

thatman84's Achievements


Apprentice (3/14)

  • Reacting Well Rare
  • First Post Rare
  • Collaborator Rare
  • Posting Machine Rare
  • Very Popular Rare

Recent Badges



  1. No sorry, It needs to be Storage/Hyperspin Best bet is to transfer all media to the shield and leave the roms on the nas.
  2. Hyperspin can work with NAS so long as the Hyperspin folder is a root directory. Must be Storage/Hyperspin not /Storage/mynas/Hyperspin
  3. You can only have 1 emulator per system on Android. Collections like Stree Fighter can be made only for say all the games emulated by 1 mame emu/core
  4. It’s a fork of Final Burn Alpha so you can use the assets from that. There shouldn’t be to many name changes to the romset depending on how old the assets you find here are.
  5. 1st tip is to match folder & file names throughout example based on FBNeo you need database file in its folder. Databases/FBNeo/FBNeo.xml settings file Settings/FBNeo.ini The system needs adding to your main menu Databases/Main Menu/Main Menu.xml OR Main Menu_Android.xml you will then need all the media images for it to be visible. Media/FBNeo etc Media/FBNeo/Wheel and Theme as a minimum
  6. it does sound like a naming issue possibly, not seen it described like that befor. Try matching the artwork names against the N64 database you have. /Hyperspin/Databases/N64/ whats listed there is the file name. Case sensitive
  7. You need to have the correct parameter line pointing to the core in “systemname”.ini you need make sure the core is downloaded and tested with same roms in retroarch directly 1st
  8. That’s not aloud on the forum. We do have a PM system. 😉
  9. This is not the correct topic to ask for help. Try in support and please be more specific with your question
  10. Thanks for updating your findings. I removed the reference to the romsite, that's not allowed FYI that romsite is notorious for messing with the original released material so there's no surprise the themes are messed up.
  11. As @Honosuseri said your rompath looks incorrect, hence the error of hyperspin saying it cannot find them So this line in the ScummVM.ini should be rompath=Emulators/ScummVM/roms
  12. Hi Hyperspinners, We now have an official Discord chat server for anyone who is interested. @Circo is looking at integrations with the forum in the near future. If you want to jump in, the link is below. We will refine the server over time, suggestion are welcome. https://discord.gg/cn8T3Sd
  13. 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
  14. 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.
  15. Android OS forced apps to only release to play store in 64bit. RetroArch doesn't have as many or as good 64bit cores.
  • Create New...