MUGEN vs SPACEBAR : what are the options?

[superbigjay]

Recently I decided to revive my uroJUKEstyc cab and remove the dust from it ...

It was build in 2007 when my first boy was delivered by one of the Joust Bird to my doorstep.
All the hardware part was prety much finished, but there was still a lot of software issues that I didn't fully resolved.

That being said, on my cab, I am using a ggg keywiz (the old PS2 model) and I decided to skip the part using the keywiz uploader to speed up the boot time.

I reconfigured some of the emulators and the default keywiz value are fine.
But now I hit a wall with mugen : the P1-button 3 is mapped to space by default.
This isn't a problem with most emulator, but for MUGEN, the spacebar can't be assign to controls.

So I am trying to see my options...

option #1 : put back the keywiz uploader to remap the key at bootup
option #2 : use AutoHotKey to remap SPACE (P1B3) to whathever other key button when mugen is launched.

I am not sure yet if option 2 would introduce a delay in the gameplay.
Option 1 seems the simplest option.

Any other solution that you see?
Jay

[BadMouth]

My advice is to swap the first four buttons to utilize other inputs on the key wiz so you don't have to mess with the uploader software.
I usually use V,B,N,M
If you don't go ahead and get it over with now, you'll just hit another stumbling block down the road when CTRL & ALT cause issues in other emulators.

That said....if you don't want to go back and remap stuff, I'd go the autohotkey route.
It doesn't add any noticeable delay in my opinion.
People have used it to remap controls for years and I'm yet to see anyone complain.

[superbigjay]

Thanks for the feedback.
I didn't received the notifications of the reply (forgot to tick the checkbox)...

I have finally decided keep the keywiz uploader in the loop for now.
I had a lot of trouble to find a valid key mapping for all emulators with the default keywiz mapping.
For now it seems to do the job fine.

I am having other issues with the keywiz uploader 2.0 that sometimes seems to crash and restart automatically at boot time.
When this happens, I end up in one of these 2 scenarios:

A) A residual window with an error message : "KeyWiz Connection Failed".
B) 2 instances of the KeyWiz Uploader running at the same time and prevent each other to successfully connect to the keywiz.

For A, I could simply use a batch file to kill the process before calling Mala, but for B, I didn't find a solution yet...
The Ledwiz Uploader is in the startup for winxp (and is only there once...).

Jay

[superbigjay]

As a trial, I removed the ledwiz uploader launch from the startup group in windows and to my surprise, it was still launched at boot up.
So I have the LedWizUploader that starts, when done, it launches Mala.

Seems it is now fixed and my setup is noe fine with all emulators.

The only thing, is that I don't remember where I have specified that "auto-launch" at boot.
It must have been when I first set up my cab a few years ago... I'll need to find it out.

cheers

[superbigjay]

The only thing, is that I don't remember where I have specified that "auto-launch" at boot.
It must have been when I first set up my cab a few years ago... I'll need to find it out.

Dooooohhhh! MSCONFIG...

So everything is working well for all emus for now. Thanks