hyperspin won't run with Calamity driver loaded.

[alphadog808]

Hey guys,
  An issue I ran into when rebuilding my machine was that hyperspin would not launch with calamity's drivers installed.  When I looked at the logs, it said something about the joystick not being initialized, or something to that effect.  If I ran mame via command line, it worked fine. 

I read somewhere about having too many resolutions would cause hyperspin to have problems, but I think they said the symptom was that there was nothing in the logs....I have stuff... 

I didn't check the amount of resolutions I have in my config file, but I'll check and mess with it tonight.

BTW, I'm not sure exactly how I ended up getting it working, I kept switch back and forth between my computer monitor and arcade monitor and then one time it worked!  haha  But I'd like to know what happened so I can try messing with the resolutions more, if possible...

[Calamity]

So did you manage to get HS working?

[alphadog808]

So did you manage to get HS working?

Yup, I did, I had to change the amount of resolutions...once I did, everything worked fine.   

[Tzakiel]

Resurrecting this thread... which resolutions should be safe to get rid of?  Are there ones which groovymame would never want to use?

[Calamity]

Hi Tzakiel, search this subforum about "magic" resolutions.

[Tzakiel]

Sorry, I'm dumb. I found the magic resolution thread... Read it. Still not sure what I need to do to be honest. I know I have two options, either limit the # of resolutions available in arcade osd or vmmaker (but I don't know which resolutions are safe to delete) or use magic resolutions, which that thread didn't really explain clearly enough for me. Maybe I just missed the steps somewhere. What do I need to do in order to use magic resolutions and get hyperspin to work?

[Sledge]

just limit the number of resolutions in VMMaker to 100 or so..

[Tzakiel]

just limit the number of resolutions in VMMaker to 100 or so..

OK.  So I haven't actually has to use vmmaker so far... I guess I will download it and see where I can make that change.   Just run it in the groovymame dir or seperate dir?

[Sledge]

just limit the number of resolutions in VMMaker to 100 or so..

OK.  So I haven't actually has to use vmmaker so far... I guess I will download it and see where I can make that change.   Just run it in the groovymame dir or seperate dir?

wait.. so you're trying to fix something that you haven't even done yet?
regarding VMMaker.. read the instructions
and look in the .ini

[Tzakiel]

Sledge, I am trying to fix the fact that Hyperspin doesn't launch. Groovymame was working fine with all of the resolutions without using VMMaker. So, I've never downloaded it. Just installing the crt_emu drivers and using groovymame has worked perfectly so far, and so I didn't seem to need vmmaker. Does that make sense? So now if I download vmmaker (which says it generates modelines) I am just not sure what the purpose is vs. the crt_emu drivers and arcadeOSD. But, if it helps me get hyperspin working, I will take a look!

[Calamity]

Hi Tzakiel,

I always try to help new users but I honestly think this topic has been covered a hundred times, just take some time to read the threads about Hyperspin, magic resolutions, vmmaker. Just make sure to grab the most recent version (1.3c) here: http://mame.3feetunder.com/windows-ati-crt-emudriver/

The file named vmmaker.ini was meant to be self-explanatory. Keep vmmaker in its own folder. Setup paths as required. Just make sure not to forget enabling magic resolutions by using this option:

ModeTableMethod_XML = 2

... run vmmaker, restart... etc.

[Tzakiel]

Great, thanks. I will give it a try. I know there is a lot out there but to a new user it's pretty overwhelming. I hope some day it can be captured in a guide or post for new users. Id even be willing to help put it together once I have everything figured out myself.

Appreciate your help.