magicjoe Posted December 19, 2018 Posted December 19, 2018 My hyperspin setup is on an external HD, and I had been connecting that to my Windows 7 laptop for work, until work found out about it and said "no no". So I bought a laptop which came with Windows 10. When I first plugged it in, everything was working fine for the standalone emulators I tested. That felt nice. I thought I would be completed soon, and went on to install the emulators such as Project 64, PCSX2, and Dolphin. My Xpadder configuration carried over just fine. Games were launching, on the old laptop, and on the new Windows 10 laptop. After I thought I had completed my migration, I sat down to enjoy the fruits of my labors. However, I am now unable to launch games from Hyperspin any longer. I can go into RocketLauncher and click on a system, click on Games, run an audit, then select a game, and launch it through RocketLauncher without issue. So RocketLauncher is configured correctly, and I have attached the log of a successful run. In Hyperspin, all the media displays as it should, menu navigation works as expected, but when I press START, which I have already confirmed is set as ENTER in HyperHQ, and ENTER is mapped to my controller's Start button, but when I press START nothing happens. No error, just nothing. If I wait long enough, the "attract" setting will kick in and the wheel starts spinning. A log is attached here showing what the log shows there. It shows the command: 10:49:15 AM | Launcher Command Line is: G:\RocketLauncher\RocketLauncher.exe "Nintendo Entertainment System" "Adventure Island II (USA)" This is correct, as I can run it directly in a command prompt window, an the game will launch. To be sure, I changed the Execution setting on the Emulator tab of the Wheel Settings in Hyper HQ to "Normal" instead of "HyperLaunch" and attached the log with that output as well. Current state is that the Execution setting is back to "HyperLaunch". This is not just happening with the NES wheel, this is every wheel. Everything worked fine with this exact same drive on my Windows 7 machine before moving to this Windows 10 machine. Everything worked that was stand alone, and lived on the external HD. Once I installed emulators that require it, and their dependencies, Hyperspin stopped actually launching games, but logs that it is doing so. I know there has to be some simple thing I am missing. Someone - please help????!!??! RocketLauncher log - successful launch.log HyperSpin log - HyperLaunch selected.txt HyperSpin log - Normal selected.txt Settings.ini
magicjoe Posted December 21, 2018 Author Posted December 21, 2018 That is the version I have installed.
magicjoe Posted December 25, 2018 Author Posted December 25, 2018 UPDATE ok, so I downloaded the files through your link and extracted it to my HyperSpin folder, overwriting the existing files. Now, when I try to launch a game, HyperSpin freezes, but the video being displayed will continue to play, along with sound. However any key presses after that START is pressed, do absolutely nothing. ESC doesn't even work, you have to Alt+F4 or task manager kill to get rid of it. If I go into HyperHQ, making sure the wheel is set to Normal, and Executable is left empty, that is what I have. If I set the path the my NES emulator, it will try to launch ,but then gets another error because of the snytax of the file extension. So, right now I have 1)the exact files that were attached to this thread 2)all wheels set to Normal execution type, with the Executable path empty in HyperHQ 3)freeze issue happens as soon as START is pressed here is what the log looks like for that event: 11:08:30 PM | HyperSpin Started 11:08:30 PM | Going FullScreen 11:08:30 PM | Checking for updates 11:08:30 PM | Update Check Complete 11:08:30 PM | Startup program: Xpadder.exe 11:08:30 PM | Startup params not set 11:08:30 PM | Working directory: G:\Utilities\Xpadder\ 11:08:30 PM | Window State: NORMAL 11:08:30 PM | Launching Xpadder.exe 11:08:30 PM | Command Line is Xpadder.exe 11:08:30 PM | Playing intro video 11:08:40 PM | Error intializing joysticks 11:08:40 PM | Menu Mode is multi 11:08:40 PM | Loading Main Menu.xml 11:08:40 PM | Main Menu.xml successfully loaded 11:08:41 PM | Main Menu wheel loaded successfully 11:08:42 PM | Loading Nintendo Entertainment System.xml 11:08:42 PM | roms_only is true, checking files 11:08:42 PM | Main Menu.xml successfully loaded 11:08:43 PM | Nintendo Entertainment System wheel loaded successfully 11:08:46 PM | Launching Game 11:08:46 PM | Not using HyperLaunch 11:08:46 PM | Running in normal rom mode 11:08:46 PM | Excecutable is 11:08:46 PM | Command Line is: "" "G:\HyperSpin Template\Roms\Nintendo Entertainment System\R.C. Pro-Am II (USA).7z,zip,nes,fds" 11:08:55 PM | Quiting Hyperspin 11:08:55 PM | Bye! Now HyperSpin is not getting the System in its string to send off to the command line.
32assassin Posted December 26, 2018 Posted December 26, 2018 this is never going to work 11:08:46 PM | Not using HyperLaunch the only emulator you can set to normal launch is MAME, this is because it uses the same command line (as Hyperspin) to load games you should set ALL!!!! your emulators to launch with Hyperlaunch in HyperHQ. then test launch all your emulators in Rocketlauncher then you can test launch your emulators in Hyperspin
Recommended Posts
Archived
This topic is now archived and is closed to further replies.