ghutch92
-
Posts
923 -
Joined
-
Last visited
-
Days Won
1
Content Type
Forums
Events
Downloads
Store
Everything posted by ghutch92
-
Thank you for the effort but that is not an autohotkey library
-
Need some help with using DInput8.dll with autohotkey. I have found a library for XInput and RawInput (useful for trackballs), but I am striking out on finding an autohotkey wrapper for the dinput8.dll. Having this library would save me a lot of time.
-
I have looked into the issues this has with joysticks and I have come to the conclusion that the issues people are experiencing is because this Autohotkey script uses the WinMM library to read joysticks. Microsoft has said that for gamepad controllers XInput is the library that should be used. For non-gamepad controllers and non-keyboard and mouse type devices then directInput8 should be used. I am currently working on adding XInput support to this script. In the meantime, I have attached the source code for anyone else wanting to customize it. HyperSpin Startup Script.zip
-
Increase the deadzone to something greater than 20. I personally like 25. Also increasing the delay might help.
-
Right now it is better to go with rocketlauncher because it has active development. HyperLaunch supposedly still has active support but to be honest I haven't seen any development on it ever since the creator of RocketLauncher left the HyperLaunch development team.
-
Is drive F a local or network drive?
-
Which operating system is this on? What troubles caused you to give it admin rights? Where did you install it?
-
No. The hyperspin install takes 3 steps. The rocketlauncher install takes 14 steps. Installing mame with rocketlauncher takes 9 steps. Installing mame with hyperspin takes 3 steps. Steps 30 and 31 are not actually steps; they are more like hints. There are 4 programs used in the install with 4 different owners that would all need to allow their programs to be put in an install script. In other words don't expect any official one anytime soon. By the way, there are typically more than just 31 steps to get hyperspin and other emulation frontends to the point of running games. This is just the tip of the ice object in the ocean.
-
I'll look into this. Which version of windows are you using? Can you post your HyperSpin Settings file? It's called Settings.ini in HyperSpin's Settings folder. Thanks.
-
No idea. Is there any more information you can give? Like cpu or ram while the app is running? Is the keyboard still responsive in these cases or is the keyboard also finicky? How many openings and closings before the problems start occurring?
-
You could try closing the chrome process when hyperspin starts (i.e. Process_Name_To_Close_1=chrome.exe) you could write your own script to maximize and activate the kodi window and have the startup script run it when hyperspin closes (i.e. Program_To_Run_Target_1=C:\Hyperspin\Utilities\my script.ahk)
-
If windows sees them as keyboard keys use hyperhq and set it there. If windows sees them as joystick buttons you will use joy1, joy2, ..., joy7, joy8 in the .ini. Try the joydetection.ahk included in the download to help you out. You will need to install autohotkey to get the joydetection.ahk thing to work.
-
Read the second sentence in the first post. Since this guide was posted it has undergone 6 major revisions. 6 videos with different instructions would be confusing. I could remove the videos but that would break shares and links. I also would need to find time to record and edit the video and I don't have the time. If someone else would like to make a video following the instructions I will be more than happy to link to it in the beginning of the first post. The file names for your roms must match the names of the games in the xml that you are using.
-
ninja2bceen it does not sound like you mixed it (mixing the settings folders together). You can use the transition tool found on rlauncher.com without any manual separating.
-
I recommend using the transition tool if you kept RocketLauncher in a separate folder and didn't mix the RocketLauncher and hyperspin settings and media folders. Although I do not recommend choosing hyperspin 1.3 as this is incompatible with the install method presented in the instructions in this thread's guide. If you did mix it, you will need to separate hyperlaunch3 settings from hyperspin settings by hand and then run the transition tool.
-
The developers for RocketLauncher and HyperLaunchHq left and started RocketLauncher. They left because they wanted to support more front ends than hyperspin. Therefore the name changed but not the program. So it's essentially the same thing. Your btw question is not a good fit for this thread.
-
Your dog ate it. The underpants gnomes stole it. Your nemesis glued it stuck. It never really existed. It waits on Congress's (Parliament's) approval. It's on strike protesting button abusers for hitting buttons too fast and too hard. Does the start button work? How did you verify x and y worked? Does the a button work in other programs? Is it only when you try to open a game? Did you modify the settings and either misspelled joy1 or forgot to add it back? Does it do the same thing on other controllers?
-
This doesn't sound related to this application. I definitely know it's not related if the keyboard doesn't work to start the game.
-
You would get a better answer on the http://www.rlauncher.com/forum/forum.php rlauncher forums instead of here on this thread. The startup script did what it was supposed to, now it's up to rlauncher / hyperlauncher to carry the baton. Here is the link to the rlauncher documentation for keymappers. http://www.rlauncher.com/wiki/index.php?title=Keymapper
-
On the emulators tab when you have a system other than global selected. You should see a place to add rom locations. Under this box there is another box for the default emulator. Now this box is labeled default emulator. Attached to the right of this default emulator box is the maginifying glass.
- 270 replies
-
- 1
-
-
- guide
- hyperlaunch
- (and 3 more)
-
Ok walked through it again and this time I caught what was going on. There is a little quirk in rocketlauncher when it checks for legacy mode. It checks for legacy mode before it ever checks the parameters to be sent. This is frustrating, I'll put up a quick fix, but hopefully the hyperlaunch team can fix this little quirk. Updated the 1.3.3 install compatibility fix file and included source. A side note, this probably all would have been solved weeks ago if someone had posted their rocketlauncher troubleshooting log on www.rlauncher.com
- 270 replies
-
- 1
-
-
- guide
- hyperlaunch
- (and 3 more)
-
I do not make tutorial videos. So do not complain on this thread about videos. You can help this tutorial become better by posting what step you became stuck on. I do this in my spare time and I am not actually affiliated with HyperSpin.
-
this script only is supposed to work for the hyperspin menu not the games themselves. You will need to map your controls for every emulator in that emulator's settings.
-
That's up to the moderators to either move this thread or lock it. If they lock this thread, I'll start a new thread over there.
-
You can not have both joysticks on in 1.4 beta and in the startup script in the settings for both programs. One of them has to have joysticks disabled. If both of them are on then you will send double presses. First see if turning joysticks off in the startup script and turning them on in 1.4 helps (not the physical controllers, just enable/disable joysticks in the respective program's settings). If turning them on in 1.4 and turning them off in the startup script does not help, try doing the opposite. Turn them on in the startup script and turn them off in HS 1.4. If it is still giving you problems and you are certain that the startup script is causing the issue (without interference from 1.4 beta) then you can either increase the deadzone or the delay between sending commands to hyperspin.
