...
Hyperspin (I'm assuming) can be a beyotch to setup. I'm not a pro so I put a lot of unnecessary hours behind a computer trying to figure easy stuff out.
I don't understand why people keep saying this... Hyperspin isn't that hard. I admit you have to spend some time to get to know the structure but after spending all those hours building a nice cab this time is really peanuts. I wrote a little 'Getting started with Hyperspin - the Basics' once : http://forum.arcadecontrols.com/index.php/topic,135694.msg1473193.html#msg1473193
If there is interest I could finish it with some screenshots and make it a sticky. Although I think we need a separate forum for Hyperspin as it is one of the most used frontends and there are a lot of people struggling with it.
Its totally not hard once you have it figured out. An example of something that held me up was certain emulators in hyperlaunch only support certain game types. for example a nes emulator might only recognize .zip and not .nes. So you could have an emulator working perfectly outside of hyperspin but when you do the game audit it all shows up red. Easy to fix now...but for a guy like me who doesn't know the first thing about programming and programs it can hold you up for a long time.
There are .ini files, .ahk files, .xml files, I had no idea what they were before I started toying around with H.S. Really still don't know what they are now.
I still don't know how to use daemon tools with certain emulators either.
A separate sticky in the front end thread would be great. A tutorial would be great.
You know what else would be great? Common problems and solutions like the one I explained above. "Mame Error - Failed validity" Another one that held me out for a long time.
Grippie, thanks for hosting an off topic chat thread.
Thats what you get for having such a cool and original build.