Hi Matlo,
Thanks for the tip. I've compiled my own copy of gimx.exe using the latest source tree, and it appears to have fixed the IP listening problem.
Now I'm faced with a new issue - when I send commands to the gimx server instance, using a command like:
gimx -d 192.168.1.241:1234 --event PS(255) -t DS4
the server's status window shows:
1 1418092114.330356, PS (255)
and nothing happens on the PS4. This is similar to what happens if I just invoke gimx with just a single event. For example:
Code: Select all
gimx -p COM3 --nograb --status --refresh 40 --event PS(255)
option -p with value `COM3'
option -r with value `40'
option -e with value `PS(255)'
grab flag is unset
status flag is set
Detected USB adapter: DS4.
1 1418092793.556964, PS (255)
I've noticed that the first value shows a '1' instead of '0'. Actual keypress events seem to work correctly - if I send a keypress event, the PS4 responds as expected, and that value shows '0', so I'm guessing this is just the return code for the event being sent.
Code: Select all
gimx -p COM3 --nograb --status -c slim2.xml --refresh 40 --window-events
option -p with value `COM3'
option -c with value `slim2.xml'
option -r with value `40'
grab flag is unset
status flag is set
window_events flag is set
Detected USB adapter: DS4.
A device name is empty. Multiple mice and keyboards are not managed.
0 1418092941.262929, PS (255) <-- pressed 'z' on keyboard, which maps to PS button
0 1418092941.382935
Do you know why --event commands always seem to return 1 instead of 0?