- Status
- Offline
- Joined
- Mar 3, 2026
- Messages
- 330
- Reaction score
- 7
Has anyone else been testing color-based solutions on the Splitgate 2 build? I have been running UniBot via Arduino, and while it maps perfectly in AimLabs, the performance in SG2 is erratic at best.
The Current Setup:
The Issue:
Movement triggers correctly when the defined color is detected, but the snapping is completely unstable. It doesn't lock onto the target; instead, the crosshair jitters wildly across the screen. I have spent hours messing with sensitivity multipliers and smoothing offsets in the config, but it feels like the game handles mouse input input smoothing or acceleration in a way that breaks standard color-tracking logic.
I am curious if the issue is the game's anti-cheat jitter suppression or if there is a specific sensitivity curve I need to match to stop the 'going everywhere' behavior. While others are waiting for internal signatures or full-blown DMA dumps, I'm trying to figure out if this color-based approach is even viable without a custom overlay sync.
Has anyone managed to get a stable lock in Splitgate 2, or is this just a dead end for colorbots?
The Current Setup:
- UniBot (GitHub base)
- Arduino HID bridge
- Testing with native client settings
The Issue:
Movement triggers correctly when the defined color is detected, but the snapping is completely unstable. It doesn't lock onto the target; instead, the crosshair jitters wildly across the screen. I have spent hours messing with sensitivity multipliers and smoothing offsets in the config, but it feels like the game handles mouse input input smoothing or acceleration in a way that breaks standard color-tracking logic.
Some of the movement overhead might be down to how the game handles raw input versus Windows API calls. If you are using an Arduino, ensure your firmware isn't adding unnecessary latency, though this feels more like a target-acquisition/view-matrix interpolation mismatch.
I am curious if the issue is the game's anti-cheat jitter suppression or if there is a specific sensitivity curve I need to match to stop the 'going everywhere' behavior. While others are waiting for internal signatures or full-blown DMA dumps, I'm trying to figure out if this color-based approach is even viable without a custom overlay sync.
Has anyone managed to get a stable lock in Splitgate 2, or is this just a dead end for colorbots?
