Games not starting (noob needs help)

[Sykurmoli]

Hello.

I've been following the official video tutorials but obviously wrong because games are not launching. When I select a game, nothing happens. I've googled for the problem and nothing I have found has been of help. It's the same problem for all systems with different emulators.

Some details:

I use Windows 10 64bit
Latest versions of Hyperspin and RocketLauncher installed.
Roms have been audited with no problem.
It's also can't start any game from HyperLaunch, but when I click on the red rocket button in RocketLauncher UI, it works.
I've modified the HyperSpin settings file to include Hyperlaunch_Path=F:\RocketLauncher\RocketLauncher.exe (which is where it is on my hard drive)
I do not have any HyperLaunch or HyperSpin process that wouldn't have closed properly in my TaskManager (I've read this could cause my problem so I checked).

Any help would be greatly appreciated. It's probably something obvious but I've searched on my own for hours without putting my finger on it.

 

Here is what my log looks like (looks normal to me)

08:11:03 PM |  HyperSpin Started 
08:11:03 PM |  Going windowed mode 
08:11:03 PM |  Checking for updates 
08:11:03 PM |  Update Check Complete 
08:11:03 PM |  Startup program unavailable 
08:11:03 PM |  Playing intro video 
08:11:05 PM |  Menu Mode is multi 
08:11:05 PM |  Loading Main Menu.xml 
08:11:05 PM |  Main Menu.xml successfully loaded 
08:11:05 PM |  Main Menu wheel loaded successfully 
08:11:07 PM |  Loading Nintendo Entertainment System.xml 
08:11:07 PM |  Main Menu.xml successfully loaded 
08:11:07 PM |  Nintendo Entertainment System wheel loaded successfully 
08:11:15 PM |  Launching Game 
08:11:15 PM |  Using HyperLaunch
08:11:15 PM |  Getting Launcher path 
08:11:15 PM |  Launcher located at F:\RocketLauncher\RocketLauncher.exe
08:11:15 PM |  Running Launcher 
08:11:15 PM |  Launcher Command Line is: F:\RocketLauncher\RocketLauncher.exe "Nintendo Entertainment System" "Adventures of Bayou Billy, The (USA)"
08:11:17 PM |  Loading Main Menu.xml 
08:11:17 PM |  Main Menu.xml successfully loaded 
08:11:18 PM |  Main Menu wheel loaded successfully 
08:11:27 PM |  Loading MAME.xml 
08:11:27 PM |  Main Menu.xml successfully loaded 
08:11:28 PM |  MAME wheel loaded successfully 
08:11:36 PM |  Launching Game 
08:11:36 PM |  Using HyperLaunch
08:11:36 PM |  Getting Launcher path 
08:11:36 PM |  Launcher located at F:\RocketLauncher\RocketLauncher.exe
08:11:36 PM |  Running Launcher 
08:11:36 PM |  Launcher Command Line is: F:\RocketLauncher\RocketLauncher.exe "MAME" "mgavegas21"
08:11:41 PM |  Launching Game 
08:11:41 PM |  Using HyperLaunch
08:11:41 PM |  Getting Launcher path 
08:11:41 PM |  Launcher located at F:\RocketLauncher\RocketLauncher.exe
08:11:41 PM |  Running Launcher 
08:11:41 PM |  Launcher Command Line is: F:\RocketLauncher\RocketLauncher.exe "MAME" "vroulet"
08:11:44 PM |  Loading Main Menu.xml 
08:11:44 PM |  Main Menu.xml successfully loaded 
08:11:44 PM |  Main Menu wheel loaded successfully 
08:11:46 PM |  Exit program unavailable 
08:11:46 PM |  Quiting Hyperspin 
08:11:46 PM |  Bye! 
 

[steptoeUK]

I had something similiar, some systems worked but other refused no matter what I tried so I started checking settinsg files by hand and found the global emulators.ini was causing all my problems

 

Hyperspin is VERY picky when it comes to where files/emulators are. If it can't find EXACTLY what is in the various settings .ini files it WILL fail leaving you frustrated and wondering why. Once you have got the idea of what is where it is very easy to set-up and easy to add more systems, even if some emulators are not already set-up for some ROMs types adding more is easy once you know what settings are where

 

I've managed to get MESS to work with more systems than the default Hyperspin is set up for and also use MESS 0.188 which supports a lot more systems than ever as running them via MAME had Hyperspin assuming it was arcade ROMs and failing. Running two separate systems as MAME and MESS allows me more control and doesn't confuse Hyperspin. I'm now using MAME and MAME 0.188 and can easily update as and when new systems are working without having to use multiple emulators unless they offer better support than MESS

 

 

Basically, check your Hyperspin/settings/global emulators.ini and I think you will find your emulator filepath in RocketLauncherUI is different to what is stored in this simple text file. Manually edit the file and change the path to your emulator and you then should now find it works. I had exactly the same problem that it would via RocketLauncher or HyperLaunch but not via the wheels

Creating the system in RocketLauncherUI, being aware the system names are VERY specific if you want all the GFX to work, sets the emulator paths correctly but doesn't change it in the Hyperspin/setting/global emulators.ini. Changing the paths by editing this file manually fixed every problem I was having with emulators not being recognised