Jump to content
(Public Beta) HyperSpin 2 is now available for everyone ×

Settings.ini GUI (PCLauncher) Final!


Recommended Posts

  • Replies 79
  • Created
  • Last Reply
Posted

Planned Changes Include:

  1. Compatible with more Modules
    • PC Games
    • PopCap
    • OpenBor
    • MUGEN
    • Other (Uses PCLauncher Module to Create Settings file for any System)

[*]Cleaner Code

[*]Easier to Use

If there are other Systems (Modules) that require a settings file please let me know so they can be included by default instead of having to use the "Other" method.

Thank you

Posted
Are you generating txt files for the rompath? If so, you can change your extension to .png and point your path at the wheel folder.

Yes you can create text files, but that is optional. When making this I assume users read any info and documentation pertaining to any given module. This script only creates the settings.ini for modules that rely on a settings file to function. That being said, it is up to the user to decide whether or not to use txts or wheel images and to set that option accordingly in Settings\System.ini.

Actually that gives me an idea. I'll add a "View Module" function to the app. That way, if they haven't already, users can view the module so they can read the documentation and any notes within the module.

  • 2 weeks later...
Posted

Updated - v4 - 10/11/2012

  • Now compatible with PopCap, OpenBOR, and MUGEN
  • Easier to use - less content more function
  • Script remembers where your folders are. HyperSpin and Game Folders.
  • No more extra entry in the settings file for Game Folder
  • View settings file or module in notepad

  • 2 weeks later...
Posted

I'm going to update again. Nothing major. I realized that texts are required for PopCap, MUGEN, and OpenBOR. The texts have to be in the GameDir. So for these systems text files will not be optional they will be created when you fill in the gamePath for a game.

Changes

  • Texts are auto created for PopCap, MUGEN, or OpenBOR when you fill in gamePath.
  • All texts can still be created at once for said systems, but the location is not optional.

First post updated.

Posted

What system are you trying to setup?

Also in your error for the loop function I see four commas there should only be three like this - LoopityLoop(WheelPath "*.png",,, "|")

Do you have the latest version?

Are there any wheel images in the wheel folder for the system you are trying to setup?

Posted

So is this happening right after you choose PC Games or after you are already in the gui?

I cannot reproduce this even using empty\incorrect folders.

Also are your PC Games folders named "PC Games" exactly like that or is it different? If it is named differently use the "Other" option then select PC Games, however its named, from the system list.

Posted

Delete the exe and re compile it.

put the exe in your hyperspin root folder

run the exe

select yes on the first option

Then select "PC Games"

then choose you PC Games game dir

then you should get a gui

If your setup (your folders, system name) is NOT named "PC Games" exactly like that you have to use the "Other" option.

Do you have a screen record software? If so please make a short video so I can see what is going on. Also show your me your "PC Games" directories - media folder especially. If you can

I need to add error logging. v4.2 here I come.

Posted

You don't need to add any software to your PC on account of me. But it would help me help you. And that is my goal, to get this error fixed so you can continue with your build.:)

Posted

DrMoney - I had that same error initially. It was because I was not running AutoHotkey_L, one I installed that version, I was good to go. Hope this helps.

Posted

HyperLaunch uses the dll that's on the HS folder to launch the modules so you don't really need to have Autohotkey_L installed, I'm guessing most people will have the basic version.

Posted

Thanks Brolly. I'll update the first post so people will be aware that AutoHotkey_L is required. It shouldn't be a problem though if people use the compiled exe... Am I right?

I also notice that the original exe that comes in the archive gives an error about an incompatible version of Windows, would me being on Vista 32 bit be an issue?

[ATTACH=CONFIG]21240[/ATTACH]

I'm using Win7 x64. Does this matter? Could someone chime in here?

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...