GP-wiz49 not working with hyperspin

[atomikbohm]

Sorry if this has been discussed before but I couldn't find it on the forums.

I have a dual boot system (Vista Home Prem and XP 64)

Intel i7 920
6Gb Ram
1 TB SATA III (2 RAID 0 Drives)
Nvidia 9600GT (512MB I think)
Hyperspin 1.0 final (with 1.2 update Pack)
LEDBlinky 3.8.1

I can't get Hperspin's wheel to move using my GP-Wiz49 controller while in my XP install. The Vista 64 system works just fine though. I'm not sure where my problem lies.

In Hyperspin: (along with the usual mame config stuff)
1) I've configured Joy1 and 2 (and enabled both) in the controls tab in Hyperspin HQ (Hyperspin ID's the Joy directions up,down, left and right as Analog Up, ect)
2) Selected and enabled LEDBlinky support.

In LEDBlinky: (these are the only things I've done)
1) I've selected HS in the FE Drop down.
2) Selected all of the MAME files in MAME config tab (except for Controller file as I don't have one)
3) Checked GP-Wiz49 Max/Eco (in the misc tab)
4) Clicked the 4 on Control Panel Max Players (in the misc tab)
5) Checked No LEDs Mode (as I haven't gotten around to hooking up my LED Wiz just yet). (in the misc tab)

My HDD has 3 Parts.
1) Vista install
2) XP install
3) Emulators

Booting in Vista, Vista is on C:, 3 is d:, and XP is on E:
Bootng in XP, XP is on D:, 3 is on C:, and Vista is on F:

I'm at a loss for what I'm missing here can anyone please help me out? Thanks in advance.

[arzoo]

From your XP boot - does the 49 show up in the Game Controllers list (control panel). If so, does it test correctly?

So you have the FE (HyperSpin), LEDBlinky, and all your emulators installed on the same drive - yes? Maybe I'm missing something, but all those apps may have hardcoded file paths in their respective config files - so how does it work if you change the drive letter?

[atomikbohm]

I haven't attempted to change my drive letters yet (I didn't know that was possible, can anyone tell me how to do this without causing problems with windows?)  I'm not sure that this will address the issue though.  I have verified, via "Game Controllers" in the control panel that the buttons and joy sticks are working.  Plus the button presses are recognized in Hyperspin just not the joy stick movements.  I'll try anything at this point, well almost anything  .  I'll try changing drive letter designations when I get home tonight and will post my results.

Thanks for the support Arzoo, it's very much appreciated.

[arzoo]

I'm just saying that if the FE, blinky, and emulators are on the D: drive for the Vista boot and the C: drive for the XP boot then I don't see how they could be working at all - assuming it's physically the same drive for both boots. Maybe I'm confused - did you install all the arcade apps separately for each boot or just one time?

[atomikbohm]

assuming it's physically the same drive for both boots.

All 3 partitions are on the same RAID-0 array. 

did you install all the arcade apps separately for each boot or just one time?

Initially I assumed that since there is no 'Windows Install' for either Hyperspin or LEDBlinky that they were portable.  (i.e. you just extract the zip file and run.)  After I went though and verified that all of the paths were correct in HS and LEDBlinky, and was still having troubles, I deleted (HS and Blinky) in Vista, rebooted into XP and extracted the files and still hit the same problems.

The real kicker is that once a game is launched the joysticks work.  Though Blinky's speech thingy say "4way" regardless of the game loaded (SF, PacMan), I have yet to verify if the announcement is accurate.

Still at work so I haven't been able to try anything yet.  Will tonight and post the results.

[arzoo]

Ah, I understand now. So it doesn't seem to be an issue with the app installation. And it's really weird that the joystick starts working in HS after playing a game. You may want to search and/or post in the HS forums.

I should mention that LEDBlinky uses RandyT's utility (GPWIZ49S.EXE) to set the GPWiz mode and it doesn't run totally silent - so you may notice that HS loses focus for a few seconds each time the stick is programmed with a new map.

As for the mode that blinky selects for each mame game - that's based on data from the controls.ini and mame.xml.

[atomikbohm]

I'm sorry, I wasn't clear.  The joysticks only work in MAME (haven't tried any other emus just yet).  Once I exit MAME and return to Hyperspin they stop working till MAME is launched again.  The buttons work all of the time.

[atomikbohm]

I should mention that LEDBlinky uses RandyT's utility (GPWIZ49S.EXE) to set the GPWiz mode

If memory serves GPWIZ49S.exe is command line friendly.  Is it possible to run GPWIZ49S.exe with the 4 way joystick argument when Hyperspin starts?  If so will that mess up LEDBlinky's ability to switch modes when mame loads a game?  I'm willing to go this route if I can't figure out the problem with my LEDBlinky configuration.

Thanks again for all of the help.

[arzoo]

I should mention that LEDBlinky uses RandyT's utility (GPWIZ49S.EXE) to set the GPWiz mode

If memory serves GPWIZ49S.exe is command line friendly.  Is it possible to run GPWIZ49S.exe with the 4 way joystick argument when Hyperspin starts?  If so will that mess up LEDBlinky's ability to switch modes when mame loads a game?  I'm willing to go this route if I can't figure out the problem with my LEDBlinky configuration.

Thanks again for all of the help.

Yes, the gpwiz49s.exe does accept command lines parameters. But LEDBlinky should be setting it to 4-way when HS first starts up. Turn on the Debug Log and Verbose options (on the Misc Options tab) and run HS. Check the debug.log and look for messages like "Set GPWiz49 JDR Mode for...". If you want, email me the debug.zip file and I'll take a look also.

[atomikbohm]

Arzoo - I e-mailed you both my LEDBlinky and Hyperspin logs.  I hope they made more sense to you then they did to me.   

Thanks again.

[atomikbohm]

If anyone else wanted to take a look and hopefully spare Arzoo the trouble... that guy does keep busy!!!

[atomikbohm]

Arzoo had graciously taken the time to review my log files, and after reading Arzoo's analysis of my log files it seems that Hyperspin's communications with windows xp64 is the culprit.  With a new day upon me I decided to take a fresh look at my problem and here is what I discovered.

While in my XP64 OS I...
1) Opened Hyperspin then I opened Control Panel->Game controllers->Properties, and verified that my GP-Wiz49 controllers were configured as 4 way Joysticks. 
2) I then opened HyperHQ Main Settings->Controls->Joystick tab and attempted to 'Set' my joystick directions.  HyperHQ returned that the directions are Analog up, Analog down, ect. 
3) Hyperspin doesn't accept Joystick movements on the menus

At this point I thought I had discovered the issue, HyperHQ wasn't accepting the Digital restriction settings but XP was.

That was until I booted into Vista and repeated the same steps above and discovered some differences.
1) Even after loading Hyperspin (and LEDBlinky) Control Panel->Game controllers->Properties still shows the sticks as a 7x7 grid (49way sticks) instead of a 4 way that XP did.
2) HyperHQ Main Settings->Controls->Joystick tab shows the analog assignments same as above.
3) Hyperspin accepts joystick movements in Vista

Anyone have any ideas on where to go from here?

[arzoo]

Based on your new info it seems that the digital restriction maps are not loading in Vista - maybe the gpwiz49s app doesn't work in Vista. It also seems like HS only works with the 49 when it's not using any digital restriction - full analog.

Try this - boot into XP and Control Panel->Game controllers->Properties to confirm that the 49 is using the 7x7 grid (not restricted). Then from the HS config, turn off LEDBlinky completely so that the stick remains in analog mode. Run HS and see what happens. If HS recognizes the 49 correctly, then we can easily change the LEDBlinky config to keep the stick in analog mode for HS.

[atomikbohm]

Arzoo -

I just wanted to say thank you for the awesome support of your software.  I mean holiday weekend and you've responded 5 times since Friday.  Thank you, you ROCK 

Try this - boot into XP and Control Panel->Game controllers->Properties to confirm that the 49 is using the 7x7 grid (not restricted). Then from the HS config, turn off LEDBlinky completely so that the stick remains in analog mode. Run HS and see what happens. If HS recognizes the 49 correctly, then we can easily change the LEDBlinky config to keep the stick in analog mode for HS.

I was able to confirm that after rebooting into XP the controller is recognized as a 49 way (i.e. 7x7 grid) in Windows Game Controller->Properties .  But after disabling LEDBlinky Hyperspin isn't accepting any input from the GP-Wiz49 controller at all (i.e. still no joystick recognition and now no button recognition either).  After re-enabling LEDBlinky the buttons are recognized, as before, but still no improvement on the joysticks.  I was hoping you were right on this one 

If you have anymore ideas please keep them coming, I'm happy to do what ever it takes to resolve this and hopefully someone else will be able to use the information. 

[atomikbohm]

Has anyone been able to use a GP-Wiz49 controller with Hyperspin 1.0 or 1.2?  I've hit a wall here and am hoping that someone has a solution.

Thanks in advance

[arzoo]

Have you checked with the HS forums?

[atomikbohm]

Yeah I copied the same 1st post on to the HS "Emulator Setup / Settings" forum on the same day I posted it here.  Thought I would try to get the people who know these apps inside and out to tell me if I was barking up the wrong tree. 

Unfortunately, 34 views of my post on HS forums and I'm the only one who replied when I gave an up date to check this thread.  I also filled out a "contact us" online form with no response yet.  Keep in mind that this has only been on the radar since last Thursday, and it was Memorial Day weekend in the US this past weekend. 

I'm just hoping to have HS up and running for a get together this up coming weekend.