MAME Raw Input - Xpadder

[hunky-dory]

From what I understand, MAME versions after 117u1 have incorporated raw input for input devices such as controllers, which in effect overrides the ability of xpadder to map its keys. I can confirm that I can't get xpadder to work correctly after version 117. Has anyone figured out a way around this??

[Nologic]

There currently is no way...BUT...and its a big BUT at that.

There is a new build of Xpadder in the works code named T.Rex...which will solve this problem and a host of others once its done.

It will be creating virtual gamepad\keyboard\mouse\... all at the driver level...so far as Mame knows...its getting raw data.

This also opens up the door for controller combining...which has some corner cases where its nice to do.

Anyways the keyboard driver is functional and may make a beta appearance in the next week or two...others will likely quickly follow...once the keyboard is finalized.

[headkaze]

A keyboard driver would probably work, but I do have working code for injecting keys into Mame's Raw Input system. Although I would consider it a "hack" it does work.

[hunky-dory]

There currently is no way...BUT...and its a big BUT at that.

There is a new build of Xpadder in the works code named T.Rex...which will solve this problem and a host of others once its done.

It will be creating virtual gamepad\keyboard\mouse\... all at the driver level...so far as Mame knows...its getting raw data.

This also opens up the door for controller combining...which has some corner cases where its nice to do.

Anyways the keyboard driver is functional and may make a beta appearance in the next week or two...others will likely quickly follow...once the keyboard is finalized.

Great!!! I will look forward to it! If there's a will...

I was afraid that I might be doomed to using 116 forever