04136: Keypresses not registered when sent through Synergy

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
04136	DIP/Input	Minor	Always	Dec 12, 2010, 16:18	Dec 12, 2010, 17:23

Tester	schplat	View Status	Public	Platform	MAME (Official Binary)
Assigned To		Resolution	No change required	OS	Windows Vista/7 (32-bit)
Status [?]	Closed			Driver
Version	0.140u2	Fixed in Version		Build	I686
		Fixed in Git Commit		Github Pull Request #

Summary	04136: Keypresses not registered when sent through Synergy
Description	Noticed a similar bug for VNC (ID 03451) My setup is such: PC hooked to TV as synergy client. Has a logitech game pad plugged into it. Regular PC hooked to monitor/kb/mouse as synergy server. So I use synergy to get mame up and running, can even use mouse/kb to start the games. Once games are started, only game pad will control. Keyboard goes completely dead. I can still alt-tab out of the MAME window to shut it down, but that is it.
Steps To Reproduce	Need a synergy client and server. From synergy server move kb/mouse to client, and launch a game kb/mouse become non-functional for MAME. A controller can be used to navigate, but you can never pull up a menu (tab).
Additional Information
Github Commit

Flags
Regression Version
Affected Sets / Systems

Attached Files

No.06912 Haze Senior Tester Dec 12, 2010, 17:07 edited on: Dec 12, 2010, 17:08	again, like the other 'bug' its not really a MAME bug. Mame uses rawinput These programs don't support that. The problem lies with the other software.
No.06913 Tafoid Administrator Dec 12, 2010, 17:22 edited on: Dec 12, 2010, 18:01	Windows-based builds by default require RAW inputs from the actual machine or through a virtual machine which supports RAW inputs signal sending. The problem is that that there are not many VM's which seem to support this method - leading to failure as you describe. This is not an issue for MAME, really. There is are 3 things you could do to possibly get things working for your setup: 1) Use a MAME version 0.117 or prior - using the old input method. 2) Build yourself a Windows SDLMAME with the command: MAKE OSD=sdl. SDL version should not have suffer from this issue with input. 3) Build your own current MAME after making the following change in your source located at: SRC\OSD\WINDOWS\INPUT.C. In that file, right at the top, look for: #define FORCE_DIRECTINPUT 0 and change to #define FORCE_DIRECTINPUT 1 then compile as usual. If none of these choices resolve your issue, there is nothing that can be done. Closing this bug.

No.06912

Haze

Senior Tester

Dec 12, 2010, 17:07

edited on: Dec 12, 2010, 17:08

again, like the other 'bug' its not really a MAME bug.

Mame uses rawinput

These programs don't support that.

The problem lies with the other software.

No.06913

Tafoid

Administrator

Dec 12, 2010, 17:22

edited on: Dec 12, 2010, 18:01

Windows-based builds by default require RAW inputs from the actual machine or through a virtual machine which supports RAW inputs signal sending. The problem is that that there are not many VM's which seem to support this method - leading to failure as you describe. This is not an issue for MAME, really.

There is are 3 things you could do to possibly get things working for your setup:

1) Use a MAME version 0.117 or prior - using the old input method.
2) Build yourself a Windows SDLMAME with the command: MAKE OSD=sdl. SDL version should not have suffer from this issue with input.
3) Build your own current MAME after making the following change in your source located at: SRC\OSD\WINDOWS\INPUT.C.

In that file, right at the top, look for:
#define FORCE_DIRECTINPUT 0
and change to
#define FORCE_DIRECTINPUT 1
then compile as usual.

If none of these choices resolve your issue, there is nothing that can be done.
Closing this bug.