Jump to content

Unfortunately, Hyperspin has stopped


j600com

Recommended Posts

Hi,

 

Brand new to this, so forgive me if this is just a case of me being dumb. So I've tried to follow the setup process on the forum, thought I'd done it right - did the whole process step by step.

 

So I reboot the Nvidia Shield TV, click on the Hyperspin logo - and all I get is a "Unfortunately, Hyperspin has stopped" message. I can't even open the app. I've tried then re-installing both Hyperspin and Retroarch but still not working.

 

Anyone got any ideas, completely stuck :/

 

Thanks

Link to comment
Share on other sites

You will get it going soon!

have you had the app open at all yet or was this first go?

Retroarch should be separate so I would concentrate on making sure you have your Hyperspin folder in the correct place on the root of your sdcard or internal drive.

Make sure Hyperspin is not running, check in the Shield settings/apps menu. Then try again

If you can just post up your steps so far hopefully someone can spot an easy solution for you.

At work ATM so can't remember off my head what it would be without a little testing. Don't think I have had it force close before. Maybe sometimes when I have tried to launch a game from Hyperspin that I have not closed properly in retroarch. Your not getting that far though!

Link to comment
Share on other sites

Indeed, at this initial stage, Retroarch and other emulators are a non-factor until you start launching games.

 

Take a bit of time to read through the sticky posts (known issues, basic setup, etc.)

I'm assuming this setup hasn't been tested and working on Windows yet?

 

I suggest you focus on a single wheel (reduce the entries in '/databases/main menu.xml'

Ensure your /media/frontend folder is correct and includes at least one video file in /frontend/video/transitions.

Ensure your /media/main menu has the necessary images, videos, themes

Make the theme/rom filtering modes false in the /settings/<system name>.ini file

 

If you are familiar with Android,enabling ADB so you can watch logcat helps me debug setup issues tremendously.

Link to comment
Share on other sites

I think I tried to add too much at once. Gone back and started again one console at a time and so far so good! Managed to get the following running so far;

 

Atari 5200 - roms not loading (it just flickers when you click a game)

Nintendo 64 / NES / SNES / N64 - working perfect

Sega Master System / Mega Drive - working perfect

MAME - in progress

 

Hopefully going to try and add a few more consoles later. And also wouldn't mind Commodore Amiga, but wasn't if that was supported.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...