I'm trying to make macros. When I run them, the game character deviates from my intended commands, such as running into walls. Behaviours usually begin as intended, but typically deviate after a few seconds. Deviations are not consistent; multiple executions of the same macro will deviate differently.
I generate macros from GIMX Launcher log files by using the Python script at viewtopic.php?p=20281#p20281.
What might be the cause?
- Log file used to make macro: https://pastebin.com/qUFhDQ1r
- Macro made from log file: https://pastebin.com/Shu5aPbT
- Log file from using macro: https://pastebin.com/eP9ZsgB0
- connection method: wired
- GIMX adapter: https://www.ebay.com/itm/115939270386
- firmware: EMUPS3
- gaming target: PS3 slim
- game: FolksSoul: Ushinawareta Denshou (BCJS30009)
- configuration: X360Pad.xml
- controller: Dualshock 3 (presumably official, bought second-hand)
Deviations from macro commands
Re: Deviations from macro commands
I presume that the deviations are related to the frequency at which GimX sends commands, typically 100Hz. If a command in the macro is not synchronized with the transmission, it fails.
You can test increasing the transmission frequency using GimX through the command line: https://gimx.fr/wiki/index.php?title=Command_line. The parameter to adjust is '-r'.
I have also achieved better results by using third-party macro software. It simply requires adjusting GimX to accept window events.
You can test increasing the transmission frequency using GimX through the command line: https://gimx.fr/wiki/index.php?title=Command_line. The parameter to adjust is '-r'.
I have also achieved better results by using third-party macro software. It simply requires adjusting GimX to accept window events.
-
AgaBaga7839
- Posts: 2
- Joined: Sun Apr 28, 2024 7:37 pm
Re: Deviations from macro commands
Thanks for replying!
It seems you are right. I've now tested some transmission frequencies using gimx --config X360Pad.xml --port COM3 --nograb -r X where X is 10.1-40 (I'm assuming, for example, that -r 20 = 200Hz, is this correct?). I now have the impression values like 11-40 have 'large' and consistent deviations whereas values like <11 have smaller deviations that are random. Testing like this works, assuming it's possible to find a value that's neither deviation nor randomizing, but are there more exact methods of finding a good value?
Also, could you share what third-party macro software you've been using?
It seems you are right. I've now tested some transmission frequencies using gimx --config X360Pad.xml --port COM3 --nograb -r X where X is 10.1-40 (I'm assuming, for example, that -r 20 = 200Hz, is this correct?). I now have the impression values like 11-40 have 'large' and consistent deviations whereas values like <11 have smaller deviations that are random. Testing like this works, assuming it's possible to find a value that's neither deviation nor randomizing, but are there more exact methods of finding a good value?
Also, could you share what third-party macro software you've been using?
Re: Deviations from macro commands
it's been a while since I've used macros in gimx, so I don't recall exactly which programs I used. In Windows, AutoHotkey worked well. On Linux, I remember using Python scripts and xdotool, and possibly a software called Actiona
I believe that --refresh X follows the formula "refresh rate (Hz) = 1 / (refresh period (ms) / 1000)" so the smaller the X value, the higher the refresh rate. However, the adapter may not be able to support 1000Hz or even 500Hz, nor the console itself. Experiment and see what works best for you."
I believe that --refresh X follows the formula "refresh rate (Hz) = 1 / (refresh period (ms) / 1000)" so the smaller the X value, the higher the refresh rate. However, the adapter may not be able to support 1000Hz or even 500Hz, nor the console itself. Experiment and see what works best for you."