albert_c

1. Stay away from Xpadder now that version 1.06 allows for navigation in the HyperSpin UI. Use the emulators keymapper. 2. To exit an emulator, you can create a global emulator exit command (be sure to enable it or it won't work). Then set all your systems/emulators to use 'Global' for the exit command (they are all set to 'Use Global' by default anyway). This is done somewhere in HyperLaunchHQ>Global>Settings. My emulator box isn't in front of me now, so I can't tell you exactly where it is. 3. As for the slow start, some modules for some emulators have known issues and they are constantly updated. Make sure you update your HyperLaunch files using Git to insure you have the latest modules. Don't use the default download from this forum for installation of HyperLaunch and HyperLaunchHQ. Search this forum for 'HyperLaunch update Git' to find out how to perform the update.

Nice work gigapig. I directed the user here from my Youtube video. Was going to help him out, but you are much too quick.

Any chance of an out of cycle release to fix this? Hard to play fighting games with this bug.

No one has mentioned they use that controller. But I don't see why it shouldn't work with the script. If a cheap $9 Chinese made board works with the script, you should have no problem.

First time the issue has been reported that I am aware of. I will see if I can replicate it with two wired X360 controllers. Perhaps it is a Windows 8.1 thing? If makes any difference, I don't see this issue on two other cabs each with a matching set of different controllers. Cab 1: Win7 32-bit w/2 Zero Delay Encoder controller PCB's Cab 2: Win7 64-bit w/2 Akishops PS360+ controler PCB's Each of the cabs can independently control the wheel at the same time. No issue.

Get Teamviewer. I have some free time before Thursday Night Football starts. Then message me.

No worries gigapig. We are all just trying to help. Seems we are all pretty anxious to do so and are pretty good at it .

In HyperHQ, not HyperLaunchHQ. Hit the Default button on this screen.

Try one more thing. Default the HyperSpin navigation functions for both 1p and 2p in HyperHQ and give it another whirl.

I see that you don't have Intro Video Enabled ticked in HyperHQ. Some users have reported that the script doesn't work unless it is enabled. Or, if it isn't enabled, they have to ALT+Tab to shift focus to HyperSpin before it works (which isn't ideal). Anyways, enable Intro Video. Disable external key mappers in HLHQ and don't start the Xpadder profile in the script. Then give it another whirl.

X360 PCB's work great with the HyperSpin Startup Script (known to work the Madcatz Brawlsticks (X360), Microsoft X360 controllers, Akishops PS360+, and MC Cthulhu). So you shouldn't have any problems. Firstly, in HyperLaunch, disable all the external keymapper functions. Then skip Xpadder setup entirely. I think the step that you missed is starting HyperSpin Startup Script to start with HyperSpin. Setting up the ini file with 'Joysticks_Enabled=True' is not enough. Go into HyperHQ in the Startup/Exit tab and browse to the HyperSpin Startup Script.exe file is located and set it to start with HyperSpin. Once done, it should work.

You're the third person to have that error. Personally, I can't reproduce it. Perhaps post your ini settings for all 3 programs (HyperSpin Startup Script.ini, HyperSpin Settings.ini, and Xpadder.ini) for ghutch's records.

Yeah, that is similar to my buddy's setup. I think his is: Top Row: (Jab)(Medium/Enter)(Fierce) Bottom Row: (Short/Escape)(Forward)(Roundhouse/Favorites) The hardcoded functions produces a non-logical layout on these multi-system PCB controllers. But that doesn't mean it doesn't work, and I would still suffer through that until a future version of g's script gives function mapping (if at all) than use Xpadder. It's only FE navigation afterall. Welp, let us know how it goes once you figure out the focus stealing thing. Hint: I suspect that explorer.exe is what is stealing your focus. Lots of cab builders use taskkill.exe to kill explorer.exe. I think g's script can kill explorer as well with either 'Process_Name_To_Close_1' or 'Item_1_Path' along with the parameters 'Item_1_Parameters'. Just make sure to restart explorer.exe in the script on exit.

Here is a program that detects which apps are stealing focus. And here is some discussion on this program. You just need to use it to find out what program is stealing focus so you can shut it down in g's script. Never used it myself, but I thought it would help.