U360's not intializing - LEDBlinky, HyperSpin, Windows XP64

[cmoses]

I recently upgraded my arcade machine to XP64, I am using Hyperspin and the trackball works, but I cannot seem to get the joysticks to work.  They are seen fine in UltraMap and in the Game Controlers section in XP Control Panel.  I just got the most recent version of LEDBlinky, 5.0.0.1 and I have also updated the firmware on the U360's.  I have Joysticks checked in Hyperspin setup.

Here is my HyperSpin log

02:19:44 PM |  HyperSpin Started
02:19:44 PM |  Going windowed mode
02:19:44 PM |  LEDBlinky is set to active
02:19:44 PM |  Found LEDBlinky.exe
02:19:44 PM |  Running LEDBlinky
02:19:44 PM |  Command Line is: "C:\HyperSpin\LEDBlinky\LEDBlinky\LEDBlinky.exe" 1
02:19:44 PM |  Checking for updates
02:19:44 PM |  Update Check Complete
02:19:44 PM |  Startup program unavailable
02:19:44 PM |  Error intializing joysticks
02:19:44 PM |  Menu Mode is single
02:19:45 PM |  Loading MAME.xml
02:19:45 PM |  Command Line is: "C:\HyperSpin\LEDBlinky\LEDBlinky\LEDBlinky.exe" 7 "MAME"
02:19:45 PM |  themes_only is true, checking files
02:19:46 PM |  MAME.xml successfully loaded
02:19:47 PM |  MAME wheel loaded successfully
02:19:48 PM |  Command Line is: "C:\HyperSpin\LEDBlinky\LEDBlinky\LEDBlinky.exe" 9 "dkong"
02:19:59 PM |  Exit program unavailable
02:19:59 PM |  Quiting Hyperspin
02:19:59 PM |  Command Line is: "C:\HyperSpin\LEDBlinky\LEDBlinky\LEDBlinky.exe" 2
02:19:59 PM |  Bye!

I also get an error from LEDBlinky saying that there is a problem with my settings.ini file, here is the contents of it.

[Main]
Menu_Mode=single
Single_Mode_Name=MAME
Enable_Exit_Menu=true
Enable_Exit=true
Exit_Default=yes
Exit_Action=exit
Version=1.0.0.0

[Resolution]
FullScreen=false
Width=640
Height=480
Scanlines_Active=false
Scanlines_Image=
Scanlines_Scale=2
Scanlines_Alpha=0.1

[Optimizer]
CPU_Priority=normal
Quality=HIGH
Image_Smoothing=true
Animated_Backgrounds=true
Inter_Backgrounds=false
Level1_Backgrounds=true
Level2_Backgrounds=true
Level3_Backgrounds=false
Level4_Backgrounds=false
Special_Backgrounds=false
Wait_For_Special=false
Animated_Artworks=true
Level1_Artworks=true
Level2_Artworks=true

[IntroVideo]
Use_Intro=false
Stop_On_Keypress=false

[Sound]
Master_Volume=100
Video_Volume=100
Wheel_Volume=20
Interface_Volume=100

[AttractMode]
Active=true
Time=60
MaxSpinTime=10
HyperSpin=true
Wait_For_Video=false

[Keyboard]
Key_Delay=true

[P1 Controls]
Start=49
Exit=27
Up=38
Down=40
SkipUp=37
SkipDown=39
SkipUpNumber=70
SkipDownNumber=86
HyperSpin=32
Genre=71
Favorites=76

[P2 Controls]
Start=50
Exit=81
Up=87
Down=83
SkipUp=65
SkipDown=68
SkipUpNumber=74
SkipDownNumber=77
HyperSpin=88
Genre=72
Favorites=90

[P1 Joystick]
Enabled=true
Joy=0
Threshold=40
Start=
Exit=Button_2
Up=Analog_Up
Down=Analog_Down
SkipUp=Analog_Left
SkipDown=Analog_Right
SkipUpNumber=Button_3
SkipDownNumber=Button_4
HyperSpin=Button_5
Genre=Button_6
Favorites=Button_7

[P2 Joystick]
Enabled=true
Joy=1
Threshold=40
Start=Button_1
Exit=Button_2
Up=Analog_Up
Down=Analog_Down
SkipUp=Analog_Left
SkipDown=Analog_Right
SkipUpNumber=Button_3
SkipDownNumber=Button_4
HyperSpin=Button_5
Genre=Button_6
Favorites=Button_7

[Trackball]
Enabled=true
Sensitivity=90


[Spinner]
Enabled=false
Sensitivity=90

[Startup Program]
Executable=
Paramaters=
Working_Directory=
WinState=
[Exit Program]
Executable=
Paramaters=
Working_Directory=
WinState=

[LEDBlinky]
Active=true
Path=C:\HyperSpin\LEDBlinky\LEDBlinky\

[HiScore]
Active=false
Y=550
Delay=2


I hope someone can take a look and let me know what might be causing the problem. 

Thanks

[arzoo]

What exactly is not working with the joysticks - do they not work at all (in-game or FE) or is it the u360 map that is wrong?

As for LEDBlinky - what is the error?

[cmoses]

arzoo,

I do not get any response from the joysticks in the Front End.  I am not sure if I launch a game if I will get any response.  I will check and see. 


The LEDBlinky pops up a small window and says "There is a problem with the settings.ini file".  But that is all I get.

Thanks

[arzoo]

The LEDBlinky pops up a small window and says "There is a problem with the settings.ini file".  But that is all I get.

I don't think that error is coming from LEDBlinky. HS also stores its configuration in a file called settings.ini - I think the error is coming from HS (the data you listed above as LEDBlinky's settings.ini is actually the HS settings.ini).

You may want to post this issue on the HS forum.

[ntk]

arzoo,

I do not get any response from the joysticks in the Front End.  I am not sure if I launch a game if I will get any response.  I will check and see. 


The LEDBlinky pops up a small window and says "There is a problem with the settings.ini file".  But that is all I get.

Thanks

you need to enable joystick support in hyperHQ

[cmoses]

I have enabled joystick support in HyperHQ.  In the controls section, I have player 1 and player 2 joysticks checked.  I have a trackball and it is working fine.

[VanillaGorilla]

I have had the same issue. Are you running anything like joytokey? That will ---fudgesicle--- things up bigtime. My experience was I could not change the main emulator on the first menu, but I could select the 'selected' or current emu. Then when I get to the game list, the joystick would automagically start working again, so I select a game. all good. Then it would be fine in the game. Then I exit the game. Then the joystick no-worky. alt-f4, start over.

[Triangel7D]

cmoses --

Did you ever solve this problem? I've read your posts in this forum and in the Hyperspin Forum, and I loved to know how (or if) you finally solved it. I'm running into this exact problem (XP64 + Hyperspin = unresponsive joystick in Hyperspin), and I'm pulling my hair out. I really hope there's a solution aside from downgrading to XP32.

[Triangel7D]

In case anyone else is running into this, I came up with a workaround: Xpadder. I know a previous poster said avoid joy2key-like programs, but it works as a quick-fix solution. I set Xpadder to activate only when Hyperspin is open, and converted joystick presses to keyboard inputs.

If cmoses is still out there, I'd still love to know what you finally did. BTW, you're Taito cabinet was a huge inspiration for me. The junker cabinet I ended up buying was a basic Taito (unfortunately without the cool side graphics).

[cmoses]

Triangel7D,

Wow, it's been a long time, since I have been on here.  Ran into that problem last year and couldn't solve it.  Got busy with other things going on and haven't really worked on it.  One of my New Year's resolutions was to get my game back up and running and then finish it all up. 

So I logged on today to look and see what's new and ran across this old post.  I have been considering reloading it with just the 32 bit version as the 64 bit version gave me all kinds of problems.  The main reason I went to 64 bit was my plan to upgrade the processor.  Well since I never got the 64 bit version working I never upgraded the processor.  Was hoping to take advantage of true 64 bit. 

So if there is a solution, preferably without Xpadder I would be interested.  Otherwise I think I might go back to 32 bit Windows XP.

Glad my Taito build was a big help.  I really liked the Taito cabinet, but wanted a little more, so I upgraded to MKII cabinet that had been converted to NFL Blitz.  I liked the larger control panel and it is better for 2 player.  The cabinet doesn't get a lot of 2 player action, but when it does the extra room is great.

[Triangel7D]

cmoses -- Weirdly, someone posted the problem to the Main Forum a few days ago and there's been some discussion about this problem (but no solution):

http://forum.arcadecontrols.com/index.php?topic=117243.0

I know Xpadder isn't the most elegant or cleanest solution, but as I posted in this new thread, it does have one nice advantage: It allows you to use the Keyboard Delay function, which I think makes it much easier to select games. One weird thing I found, though is that the Keyboard Delay only seems to work with the arrow keys and not with letters (which is not a problem since I just assign Xpadder to send arrow keys from both joysticks).

So what finally happened to your Taito cabinet? Since I didn't have the cool graphic on the side, I painted it black with a pseudo-Tron theme, but as I learned from your photos, it really has such a classic, elegant shape for an arcade cabinet. But I can totally see why you might want a bigger cabinet for two players. Although in my case, the smaller the cabinet, the happier my wife is!

[yakk11]

In case anyone else is running into this, I came up with a workaround: Xpadder. I know a previous poster said avoid joy2key-like programs, but it works as a quick-fix solution. I set Xpadder to activate only when Hyperspin is open, and converted joystick presses to keyboard inputs.

If cmoses is still out there, I'd still love to know what you finally did. BTW, you're Taito cabinet was a huge inspiration for me. The junker cabinet I ended up buying was a basic Taito (unfortunately without the cool side graphics).

What did you add to your hyperspin config to have xpadder working only when hyperspin is running?  i am also using xpadder, but i think it is interfering with ledblinky's u360 joystick configuration changing.  It switches games in MAME, but not Model 2 or any other emulator.  Any help?