HyperSpin Startup Script 1.08

[albert_c]

Hi all. Just set up this lovely script (with lots of help from this video ). Am I getting the same fault as others here? Hyperspin starts up, I have no control from either the stick or the keyboard. I have to either Alt-Tab or Windows Key out and back ( yeah, I'm on Windows 8 ). After that, it's fine.

Anyway, entirely probable that it's me - usually is. Here's my script setup.

I made that video a month ago, but it is already out-dated. With version 1.06, you don't need to mess with Xpadder at all. Actually, this version doesn't support a keymapper at all.

You just need to set 'Joysticks_Enabled=False' to 'Joysticks_Enabled=true'.

See if that works for you. And out of curiosity, which joystick/controller pcb are you using?

[albert_c]

Its just means does someone have the files in a convenient place to give me to me. Its just a polite way of asking

It's in the first post on this page right under the picture of the X360 controller.

[liveinabin]

I've got an arcade cab with two MC Cthulhu boards marshalling all the inputs.

I'm very confused about how to set up now. I've been fighting with this for a week or two and I'm lost. The video was (is) superb and laid everything out in one place nice and easily. So, in idiot terms, what should I be doing different with script 1.06?

Sorry to sound like an idiot, but I've been trying to keep up with the myriad 'exceptions to the rules' that pepper Hyperspin and now my brain is fried:)

[gigapig]

I've got an arcade cab with two MC Cthulhu boards marshalling all the inputs.

I'm very confused about how to set up now. I've been fighting with this for a week or two and I'm lost. The video was (is) superb and laid everything out in one place nice and easily. So, in idiot terms, what should I be doing different with script 1.06?

Sorry to sound like an idiot, but I've been trying to keep up with the myriad 'exceptions to the rules' that pepper Hyperspin and now my brain is fried:)

I'm not sure about your boards, ghutch maybe knows if it works with those, but as albert said, there is very little to set.

Here is my ini file, where I added the paths to HL & HS, set joystick to true, minimise windows and restore windows to true also.

For some reason quicklaunch had been enabled, which cut off the intro vid, but I'm quite sure I never enabled it.

[Required]
HyperSpin_Folder_Path=O:\
HyperLaunch_Folder_Path=O:\HyperLaunch
[General]
Primary_Color_RRGGBB=363636
Secondary_Color_RRGGBB=ffffff
[Controls]
Joysticks_Enabled=True
Joystick_Delay=225
Joystick_Deadzone=25
[startup]
Minimize_Background_Windows_Enabled=true
Window_Classes_To_Not_Minimize=Shell_TrayWnd,Button
Process_Name_To_Close_1=
Program_To_Run_Target_1=
Program_To_Run_Working_Dir_1=
Program_To_Run_MaxMinHide_1=
[Exit]
Restore_Windows_On_Exit=True
Process_Name_To_Close_1=
Program_To_Run_Target_1=
Program_To_Run_Working_Dir_1=
Program_To_Run_MaxMinHide_1=
[Roulette]
Roulette_Key=~1
Roulette_Min_MilliSeconds=3000
Roulette_Max_MilliSeconds=8000
[Volume_Menu]
Volume_Menu_Key=~2
Volume_Bar_Offset_From_Bottom=44
[QuickLaunch]
QuickLaunch_Key=~3
QuickLaunch_Enabled=false
QuickLaunch_Left_Offset=5
QuickLaunch_Top_Offset=10
QuickLaunch_Bottom_Offset=10
Item_1_Path=
Item_1_Parameters=
Item_1_LogoPath=
Item_1_Ignore_Process_Close=false

[albert_c]

I've got an arcade cab with two MC Cthulhu boards marshalling all the inputs.

I'm very confused about how to set up now. I've been fighting with this for a week or two and I'm lost. The video was (is) superb and laid everything out in one place nice and easily. So, in idiot terms, what should I be doing different with script 1.06?

Sorry to sound like an idiot, but I've been trying to keep up with the myriad 'exceptions to the rules' that pepper Hyperspin and now my brain is fried:)

You can skip the part of the video from 16:40 (which tells you to plug in your joystikck) up thru 33:47 (which is where you launch the HS Startup Script) for the first time to create the ini file. Basically, this portion of the video covers the Xpadder setup which is no longer needed.

Now all you have to do is launch the HyperSpin Startup Script v.1.06 and change this line from:

Joysticks_Enabled=False

to

Joysticks_Enabled=True

Make sure you set HyperHQ to start this program when you launch HyperSpin still and let us know if that works for you. In my case, I have 2 Zero Delay encoder boards for my cab and this script allows for both 1p and 2p to be able to navigate the HyperSpin front end. ghutch did some awesome work with this. The only issue I found is that the button assignments are premapped, but once I figured out the mapping, I just had to relearn which button did what. No biggie.

Edited September 20, 2014 by albert_c

[guyverjay]

It's in the first post on this page right under the picture of the X360 controller.

Ahh you mean the first page, cool thanks

Edited September 20, 2014 by guyverjay
.

[liveinabin]

This might be a question so dumb, I'm regretting it even as I type...but...

No xpadder? What, like, at all? Surely you need to be able to define what button does what, don't you?

That said, I've come to a Hyperspin PC build as a replacement for my cabs previous 'guts', a modded Xbox. I guess that system had premapped controllers.

[guyverjay]

It's in the first post on this page right under the picture of the X360 controller.

The link doesn't work

[albert_c]

This might be a question so dumb, I'm regretting it even as I type...but...

No xpadder? What, like, at all? Surely you need to be able to define what button does what, don't you?

That said, I've come to a Hyperspin PC build as a replacement for my cabs previous 'guts', a modded Xbox. I guess that system had premapped controllers.

Yeap. It's cool because there are issues using Xpadder that I ran into in different systems. It would work perfectly in my cab, but doesn't work on another PC I am building. Version 1.06 is as close as we will ever get to having HyperSpin having joystick navigation built in. ghutch hard coded the the button functions in this release. Perhaps in a later release we may get the flexibility to map the functions on our own, but even so, it works beautifully now. I looked at your controller PCB's and I suspect that they work fine. My buddy's cab has the Akishop's PS360+ and if those work, I am sure yours will work.

The link doesn't work

The link works here just fine. Weird.

[guyverjay]

Its just gives me an error when trying to download the file, tried two different browsers. Can someone possibly put it on the ftp for me? Thank you in advance

[albert_c]

I uploaded version 1.06 into my folder on the FTP.

[dlexington]

Hi all. First off, big thanks albert for the awesome video. I followed the same steps to be slightly disappointed when I came to the part about the startup script. I previously tried the startup script before following your video, but didn't like it because of the hardcoded buttons. I'm trying to use a dualshock 2 to control HS, and the mappings for the 360 are weird on the DS2.

The good news is, you can still use xpadder with the latest version of the startup script. This is how I do it: in your Startup Script .ini file set Joysticks_enabled to false, and in the Startup section set this (adjust for your profile name/location):

Program_To_Run_Target_1=C:\HyperSpin\Utilities\Xpadder\p1.xpadderprofile

Program_To_Run_Working_Dir_1=

Program_To_Run_MaxMinHide_1=

I had problems with xpadder loading the profile if it was set to Hide in the startup script. So if you experience the same issue, leave it blank in the startup script, and just set xpadder to start minimized in its settings window.

Also, one sticky point on the video that had me scratching my head for a minute was that it skipped a crucial setting in HLHQ. For the global system, click on the Settings tab, and in the Keymapper section, make sure you have xpadder set, and Enabled is true. If you don't set these values, HyperLaunch won't load your blank xpadder profiles when you launch an emulator.

Other than those minor issues, albert's video was invaluable. I would've been lost without it.

[albert_c]

I was thinking of updating that video. I don't like how I didn't use Git to install HyperLaunch, I don't like how I wasn't focused with cleaning up the MAME xml file, and of course, version 1.06 of ghutch92's script came out right after. Made the video while laying in bed on my laptop and that missing step you mentioned was an post-production editing error (first time ever using Camtasia). But will wait for the next version of ghutch92's script. Maybe then we will get function mapping.

The good news is, you can still use xpadder with the latest version of the startup script. This is how I do it:

That is cool. Xpadder frustrates me sometimes because I have different issues on different PC's. On one PC, the Xpadder UI will flash each time a profile is being switched, on another, it doesn't. Profiles will switch properly on one PC, on the other it won't. Version 1.06 allowed me to lay Xpadder to rest. Also, sounds like what you discovered is a fortunate bug. Let's hope ghutch92 doesn't patch it .

[liveinabin]

Wow. This is all very exciting. I'll give it a try later on (I think I'll temporarily delete Xpadder and all profiles just to be thorough) and I'll report back.

I believe the keymapping on the Cthulhu is pretty similar to the PS360+. They're both multi console boards for fight sticks.

[liveinabin]

Hmm, I've tried everything as suggested but all to no avail. The script does indeed control Hyperspin without xpadder (although my main fire button is now 'escape') but I still don't get any control unless I ALT-Tab in and out. As for the solution above allowing xpadder in the new script - I got that working but still the Alt-tab thing.

Ghutch was mentioning that it happened on his slow computer. This is no powerhouse but it is a new Intel pentium anniversary chip overclocked to 4.0Ghz (with a load of fast RAM and a GTX750i card) - surely that should be enough.

[albert_c]

The HyperSpin functions are hardcoded in this version of the script. I went through when I was setting up my buddy's cab to find out what buttons were what on his PS360+ PCB's. Anyhow, the trick is to figure out which of your buttons are the numeric assignments in Windows Control Panel. So open your control panel>gamepad properties and start pressing the buttons on your stick to find out which buttons on your stick is 1-7. Once you find out which those buttons are, below are the function assignments:

Button 1: Enter

Button 2: Esc

Button 3: Genre

Button 4: Roulette

Button 5: Skip up

Button 6: Skip down

Button 7: Favorites

Also, make sure if you are using v.1.06 with 'Joysticks_Enabled=True', that you go into HLHQ and disable all the keymapper settings.

Not sure what you mean about no control unless you ALT-Tab???

[guyverjay]

Hmm, I've tried everything as suggested but all to no avail. The script does indeed control Hyperspin without xpadder (although my main fire button is now 'escape') but I still don't get any control unless I ALT-Tab in and out. As for the solution above allowing xpadder in the new script - I got that working but still the Alt-tab thing.

Ghutch was mentioning that it happened on his slow computer. This is no powerhouse but it is a new Intel pentium anniversary chip overclocked to 4.0Ghz (with a load of fast RAM and a GTX750i card) - surely that should be enough.

I have the same issue as you, if I don't ALT TAB the only control that works for me is for volume. It has nothing to do with computer power, I am running on an overclocked i7 5ghz with gtx680

Edit: It seems turning on the intro video fixes it

Edited September 20, 2014 by guyverjay

[guyverjay]

Any reason why you cannot use the control pad to use the on screen keyboard in hypersearch? Or should I post this question in the hypersearch thread?

[ghutch92]

I'm not sure about your boards, ghutch maybe knows if it works with those, but as albert said, there is very little to set.

Here is my ini file, where I added the paths to HL & HS, set joystick to true, minimise windows and restore windows to true also.

For some reason quicklaunch had been enabled, which cut off the intro vid, but I'm quite sure I never enabled it.

[Required]
HyperSpin_Folder_Path=O:\
HyperLaunch_Folder_Path=O:\HyperLaunch
[General]
Primary_Color_RRGGBB=363636
Secondary_Color_RRGGBB=ffffff
[Controls]
Joysticks_Enabled=True
Joystick_Delay=225
Joystick_Deadzone=25
[startup]
Minimize_Background_Windows_Enabled=true
Window_Classes_To_Not_Minimize=Shell_TrayWnd,Button
Process_Name_To_Close_1=
Program_To_Run_Target_1=
Program_To_Run_Working_Dir_1=
Program_To_Run_MaxMinHide_1=
[Exit]
Restore_Windows_On_Exit=True
Process_Name_To_Close_1=
Program_To_Run_Target_1=
Program_To_Run_Working_Dir_1=
Program_To_Run_MaxMinHide_1=
[Roulette]
Roulette_Key=~1
Roulette_Min_MilliSeconds=3000
Roulette_Max_MilliSeconds=8000
[Volume_Menu]
Volume_Menu_Key=~2
Volume_Bar_Offset_From_Bottom=44
[QuickLaunch]
QuickLaunch_Key=~3
QuickLaunch_Enabled=false
QuickLaunch_Left_Offset=5
QuickLaunch_Top_Offset=10
QuickLaunch_Bottom_Offset=10
Item_1_Path=
Item_1_Parameters=
Item_1_LogoPath=
Item_1_Ignore_Process_Close=false

quicklaunch has nothing to do with the intro video at startup. It has everything to do with a sidebar though for you to be able to launch the same items from anywhere in the hyperspin menus. For example hyperhq is on mine and hyperlaunchhq.

[ghutch92]

I was thinking of updating that video. I don't like how I didn't use Git to install HyperLaunch, I don't like how I wasn't focused with cleaning up the MAME xml file, and of course, version 1.06 of ghutch92's script came out right after. Made the video while laying in bed on my laptop and that missing step you mentioned was an post-production editing error (first time ever using Camtasia). But will wait for the next version of ghutch92's script. Maybe then we will get function mapping.

That is cool. Xpadder frustrates me sometimes because I have different issues on different PC's. On one PC, the Xpadder UI will flash each time a profile is being switched, on another, it doesn't. Profiles will switch properly on one PC, on the other it won't. Version 1.06 allowed me to lay Xpadder to rest. Also, sounds like what you discovered is a fortunate bug. Let's hope ghutch92 doesn't patch it .[/color]

No bug here. You can see an example of another way of doing this in the first post for the example of Program_To_Run_Target_1. I've dropped built-in support, but you can still start xpadder or joytokey using the program to run options.

[ghutch92]

Any reason why you cannot use the control pad to use the on screen keyboard in hypersearch? Or should I post this question in the hypersearch thread?

the remaps only work on an active hyperspin screen, I will not change this. Other programs will need to add native joystick support. So yes this is a question for the hypersearch guy.

[liveinabin]

OK, I'm beginning to understand now. My problems are all coming from the fact that I have joypad encoders in my cab rather than keyboard encoders. The predefined keymaps that Hyperspin now understands (sans xpadder) are so far off as to be unusable (this arcade cab is meant to be easy to use) so I'll have to find some xpadder enabled route or, I guess, ditch Hyperspin.

Now I still have this problem with lack of any control at Hyperspin start when using this script. My main frustration comes from Hyperspins apparent inability to understand even a pretty default game controller without all this help, I mean it's a game launcher for goodness sake

Still, if there's absolutely no way round this control problem but to wait for an update to your wonderful script, I will dutifully do so (though I feel terrible putting the pressure on you when this is all Hyperspins fault). I'm just still wondering if it's my system and if there's anything I've missed.

Heck, would it even be an option for me to have one xpadder profile running all the time in all programs essentially mapping the sticks to the default MAME keys? That way, I probably wouldn't even need this script (?) and I could just remap other emulators to suit. Would that work?

[albert_c]

No bug here. You can see an example of another way of doing this in the first post for the example of Program_To_Run_Target_1. I've dropped built-in support, but you can still start xpadder or joytokey using the program to run options.

Was a joke g

[albert_c]

OK, I'm beginning to understand now. My problems are all coming from the fact that I have joypad encoders in my cab rather than keyboard encoders. The predefined keymaps that Hyperspin now understands (sans xpadder) are so far off as to be unusable (this arcade cab is meant to be easy to use) so I'll have to find some xpadder enabled route or, I guess, ditch Hyperspin.

Now I still have this problem with lack of any control at Hyperspin start when using this script. My main frustration comes from Hyperspins apparent inability to understand even a pretty default game controller without all this help, I mean it's a game launcher for goodness sake

Still, if there's absolutely no way round this control problem but to wait for an update to your wonderful script, I will dutifully do so (though I feel terrible putting the pressure on you when this is all Hyperspins fault). I'm just still wondering if it's my system and if there's anything I've missed.

Heck, would it even be an option for me to have one xpadder profile running all the time in all programs essentially mapping the sticks to the default MAME keys? That way, I probably wouldn't even need this script (?) and I could just remap other emulators to suit. Would that work?

Wait, wait, you said cab right? So are you shelling into HyperSpin? All kinds of crazy shieet happens when you shell Windows. Especially, loss of focus in the application that you are trying to control. Is that what is happening to you now; you are required to ALT+Tab to move focus to HyperSpin in order to gain control?

If shelling, you are really going to have to roll up your sleeves and get dirty till you find a solution. But what I can suggest is that g's script has the following functions which can help you out:

Program_To_Run_Target_1=Your Xpadder profile

Program_To_Run_MaxMinHide_=Leave blank rather than Hide as I suggested in the video. Then in Xpadder settings, set it to start minimized as suggested earlier by delexington.

Process_Name_To_Close_1

Whatever program is stealing focus when you start HyperSpin, if it is not essential you can enter it here to instruct the script to close it to prevent from it stealing focus.

Minimize_Background_Windows_Enabled=True

Enable this by setting this to True.

If you are shelling, you won't be the first one with this problem so do a Google seach for HyperSpin lose focus, Hyperspin no focus, etc. Also, what is wrong with the hardcoded functions in v.1.06? In my buddy's cab since the PS360+ is being used, the hardcoded functions are arranged in somewhat of an illogical order. But in reality, for simple navitation, the only functions that are essential are Enter, Esc, and Favorites. So it is just a matter of memorizing where those 3 functions are mapped to the 3 buttons on his cab.

Edited September 21, 2014 by albert_c

[albert_c]

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.

Edited September 21, 2014 by albert_c