Thanks for GIMX and sharing what I did
Posted: Thu Aug 03, 2023 2:02 pm
My use-case for this was maybe not the normal one. I actually wanted a way to automate some godawful long grind in an old PS3 game. Anyone who has attempted to get all the trophies for Star Ocean 4 will know what I mean.
I put together a DIY GIMX and was surprised I actually got it working without too much hassle. It's pretty ugly with a breadboard and jumper cables but it's working! Was pretty awesome when it first connected and I tried to move my house to check something on my PC, but the camera in-game moved instead. At this point I was like "Hell yeah, time to automate!"
That's when I hit some problems. I wasn't able to quickly get anything working to send inputs at all. For example my config had `t` mapped to the triangle button. Pressing t on my keyboard worked, but writing a program to send a 't' did not. I assumed this was because GIMX was set to "physical device" input mode, so I tried window event mode, and still failed. I was about ready to give up when I discovered the network mode.
I went and had a look at Matlo's example python client - https://github.com/matlo/gimx-network-c ... /client.py - and then took it and wrote my automation on top of it. It's all working really reliably now, and doesn't even steal input from my computer. It's brilliant.
Here is my current code: https://gist.github.com/Wrongdoer0179/4 ... dd2bb682a4
I don't really write Python but it should be readable enough.
I put together a DIY GIMX and was surprised I actually got it working without too much hassle. It's pretty ugly with a breadboard and jumper cables but it's working! Was pretty awesome when it first connected and I tried to move my house to check something on my PC, but the camera in-game moved instead. At this point I was like "Hell yeah, time to automate!"
That's when I hit some problems. I wasn't able to quickly get anything working to send inputs at all. For example my config had `t` mapped to the triangle button. Pressing t on my keyboard worked, but writing a program to send a 't' did not. I assumed this was because GIMX was set to "physical device" input mode, so I tried window event mode, and still failed. I was about ready to give up when I discovered the network mode.
I went and had a look at Matlo's example python client - https://github.com/matlo/gimx-network-c ... /client.py - and then took it and wrote my automation on top of it. It's all working really reliably now, and doesn't even steal input from my computer. It's brilliant.
Here is my current code: https://gist.github.com/Wrongdoer0179/4 ... dd2bb682a4
I don't really write Python but it should be readable enough.