Mame/Mala help!

Got a problem thats wrecking my head!

If I launch Mame by itself everything works fine.

But if I launch a mame game via mala the joysticks dont work!

The joysticks work in mala so I can choose the a game from my list uising them.

Now if I launch via Mala and press tab it shows no controlls set in mame.And I cant config the joysticks from there.

Is it something to do with controls.ini file?

Another problem im having now is my trakball randomly going spazz.
working perfect as mouse but if I put on a track game like shuffle shot is works for a while,spazzes out then works again then goes spazz.

Thanks in advance guys

Steve X2

urbanledge wrote: »

Got a problem thats wrecking my head!

If I launch Mame by itself everything works fine.

But if I launch a mame game via mala the joysticks dont work!

The joysticks work in mala so I can choose the a game from my list uising them.

Now if I launch via Mala and press tab it shows no controlls set in mame.And I cant config the joysticks from there.

Is it something to do with controls.ini file?

Another problem im having now is my trakball randomly going spazz.
working perfect as mouse but if I put on a track game like shuffle shot is works for a while,spazzes out then works again then goes spazz.

Thanks in advance guys

What version of MAME is it? MAMEUIFX, standard MAME from mamedev.org or another variant and also what release is it(0.144, 0.143 etc).

.

Sorry for not getting back to you Steve,
I was on the lash all weekend
ended up playing my cab with a few mates till 6am Saturday morning.There was buckfast and kebabs galore.
any ways.
We played Shuzz for hours and it was perfect.went for a few games of shuffle shot and the trackball is bananas.So im sure its a setting in the game analog controls.
I'll post up the versions of mame later when im home.
anybody else running Mala?

CathalDublin

I use to run mala but Changed to hyperspin a long time ago, I still have mala on my setup so may be able to help you out

Did you ever get this sorted? I could be miles off here, but it reminds me of an issue i had/was having on a cab i'm working on at the moment that i had to edit some of the hotkey scripting files to fix.

My frontend (hyperspin) when active, was reserving a few keys that were allocated to some of it's hotkey shortcuts, so that no other program could use them, and there was a conflict between the frontend and the emulators, which both wanted to use the same keys for different things. When i ran the emulators on their own, controls worked fine, but as soon as i ran them in the frontend it stepped in and grabbed the keys it wanted as per it's instructions in the scripting file.

Other programs i used for controlling the volume via assignable hotkeys tried the same thing, so i just made sure to assign keys that weren't being used for anything else in that case.

In the end, i edited and recompiled the AHK script for the frontend, to change the keys for that shortcut to ones that weren't being mapped to on my interface (a minipac), but i could have also reprogrammed my interface board and emulator controls setups to get the same result.

I might be miles off here, but have you tried looking through your frontend's documentation for any shortcuts or special keys or combinations that it might want to keep for itself that could be creating a conflict with your emus? Likewise for any other background software you might have running on your setup. Sometimes you can just be unlucky with this stuff and get a conflict.