usbuirt/eventghost and GameEx problem

[Matheus Moreira]

Hi guys!

I'm using usbuirt and eventghost to control my HTPC. My HTPC has team mediaportal, GameEx and some emulators installed, so I can play all my old games and watch my movies just using my remote and my gamepad.

Eventghost is configured to listen the infrared commands received by usbuirt and then send a combination of keys for each command.

The sendkeys sent by eventghost is working very nice with mediaportal and some emulators, like kega and nestopia, but it don't work with GameEx and some emulators, like zsnes, mess or mame. These programs don't recognize the sendkeys that eventghost raised, but recognize when i press the real key on the keyboard.

I suspect that GameEx (and mame, mess, etc) make direct access to hardware, or use directx to capture inputs or something like that.

My question is: Anyone knows why this happens? Is there any workaround or anything that I can do to make it work? Any plans to add usbuirt support to GameEx? Because of this problem, unfortunately I cannot use GameEx at my HTPC, because I only have my remote to control the computer.

Maybe GameEx can add support to usbuirt and also help to add usbuirt support to these emulators!

I appreciate any help or tip! Thanks!

[Tom Speirs]

Gameex should hopefully recognise the commands if you disable custom keyboard configuration and use the default controls.

[vsilvalopes]

Matheus.

You should configure the keys individualy in each emulator.

My setup is almost the same that you have.

But I use GameEx+XBMC+Eventghost.

For XBMC , I've configured Eventghost.

For GameEx and Emulator control , I've configured each emulator individualy.

So you have to configure each key in Zsnes , Mame etc.

If you have any doubts please let me know !

[Matheus Moreira]

@TSpeirs,

Thanks for the tip, i will try and then i post the results here!

@vsilvalopes,

Thank you very much for the reply! Did you make any special configuration to zsnes or mame to work? I made one configuration for each emulator in eventghost, so the button press on the remote will send the keys each emulator is waiting for, but it didn't work. zsnes, mame and mess simply don't recognize the keys sended by eventghost. When I press the same keys on a real keyboard, all works as expected.

To tell you an example, I configured eventghost to send the F9 key when i push the power button on my remote. Then I launched mame and tried to map the F9 key to the RESET emulator. On mame configuration, i pressed enter and mame start to wait for a key to pressed, so it can map to the desired function. No matter how many times i press the key on the remote, the mame don't recognize the F9 sendkeys that eventghost triggered.

Any ideas? Thank you so much!

[vsilvalopes]

Matheus.

For Mame , you have to compile it for Eventghost work.

Search for "Direct Input Mame" in the foruns and you should know what you have to do.

There is an Mame compiler that is very easy to use. If I'm not wrong this one is a Headkaze creation.

I had to do It because I use joy2key to send the "ESC" command to close the emulators.

And joy2key uses Direct Input, but mame "out of box" doesn't. So I have to compile it to enable this feature.

About Zsnes just go to the config part, set keys.

You will be able to configure up to 4 joypads.

Save and Exit Zsnes.

I really don´t see the point of using Eventghost to configure keys in emulators.

Even in Null DC (Wich is only compatible with Xbox 360 joysticks) I dont use it. For this specific case I use XPADDER.

So try to configure your keys BEFORE you set up GameEx. Use your emulation options !

[Matheus Moreira]

@vsilvalopes,

Thanks for the tips, I will try in the weekend and see what i can do.

My interest in using eventghost to control the emulator is not for playing, but for send the Close Emulator command (ESC or ALT+F4), send the Save Game and Load Game commands and the Reset Command. I want to do this with my remote, but I will play the games with my joystick!

Edited August 21, 2012 by Draco1962
This thread is now closed. If the problem re-occurs, please start a new thread.