Build Your Own Arcade Controls Forum

Main => Main Forum => Topic started by: LeedsFan on November 16, 2016, 06:39:25 pm

Title: LEDBlinky and ServoStik problem
Post by: LeedsFan on November 16, 2016, 06:39:25 pm
Just got my ServoStik installed but can't get it to switch automatically for games.  ServoStik does switch using the JoyTray program. But in Hyperspin it just sits there.

I did follow these instructions on this webpage:  http://www.projecthive.ca/?p=173 (http://www.projecthive.ca/?p=173)  Got all the file paths to control.ini and mame.xml setup and the same boxes ticked/selected as per these instructions.

But I didn't follow the instructions for the LEDBlinkyControlsEditor.exe just yet     That seems like a hell of a lot of work selecting each game individually like that. I thought the idea was to read the Mame.xml or the controls.ini file on game launch to select 4-way or 8-way?

I also am using the trial version of LEDBlinky. Wanted to make sure it was all working before buying the code for no-nag. Then I was thinking maybe ServoStik support isn't in the trial version?  Anyone know?

I did consider using hardware mode for now and then try this out later. But it seems that's a one way street if I do that as hardware mode is irreversible.  :dunno
Title: Re: LEDBlinky and ServoStik problem
Post by: LeedsFan on November 17, 2016, 03:17:43 am
OK I've dug around a bit more.  In the LBC_Errors log I am getting "BASS_RecordInit failed. Error: BASS_ERROR_DEVICE (23)"

Anyone know what this is please?
Title: Re: LEDBlinky and ServoStik problem
Post by: arzoo on November 17, 2016, 02:12:11 pm
OK I've dug around a bit more.  In the LBC_Errors log I am getting "BASS_RecordInit failed. Error: BASS_ERROR_DEVICE (23)"

Anyone know what this is please?

You are correct, no need to add mame games individually - that's what controls.ini and mame.xml are for. The controls editor is mostly for non-mame emus. As for the BASS error, LEDBlinky is unable to detect your audio card. But if you're not using audio animations then you can ignore the error. I responded to your post on the LEDBlinky thread :)