The Pro version has arrived.
Friends, I’m pleased to inform you that the Pro version is now ready to download.
I want to clarify that this program was originally made for the SR1, and it might work up to the SR6. With the money from the Pro version’s revenue, I’ll be purchasing devices like the OSR6 and The Handy so I can update and improve the program properly.
On Patreon, you’ll find the Pro version available, as well as a support section for anyone who wishes to contribute to the project.
With nothing more to add—here it is.
**Attention**
To know if it works with your device, try the free version and see if you can configure it to your setup.
About Feline Tracking
)
**What Feline Tracking:**
- Captures the screen and lets you mark points for tracking using template matching (OpenCV).
- Converts movement or distance into normalized values (0–100 / 0–1000) and sends them via serial to ESP32 devices or an emulator mode.
- Features a modern PySide6 interface with controls for sensitivity, range, and presets for known devices.
- Records data in Funscript format (ready for export).
Tested with model SR1, but I also added others in case anyone wants to test and report issues.
**Tutorial**
**Recommended Configuration for SR1 Device**
Objective: To optimize the SR1 device for accurate and reliable data capture in a connected application, using the emulator for safe testing.
**Output & Device Configuration**
- Device Type: Emulator
- Reasoning: This is the correct setting for testing and development without a physical device. It simulates the device’s behavior.
- Serial Port: COM9 - Standard Serial over Bluetooth Link (COM9)
- Reasoning: This is the virtual port created for the Bluetooth connection. Ensure your application is also configured to listen on COM9.
- Status: Emulator Mode
- Reasoning: This confirms the device is operating in a simulated environment, which is ideal for initial setup and debugging.
**Device Range Configuration**
- Min: 0
- Max: 9900
- Current: 9900
- Reasoning: This sets the full scale of the device’s output. A range of 0-9900 is common for sensors that measure a value like distance, pressure, or a counter. The “Current” value being at 9900 means the emulator is simulating a maximum reading. You can change this during testing to see how your application responds to different values.
- Presets: 1
- Reasoning: This likely selects a specific scaling or calibration profile. Profile “1” is typically the default and recommended for general use.
- Invert: Unchecked
- Reasoning: Keep this disabled unless your application interprets the data in reverse (e.g., a high value should be low, or vice versa). Start with the standard, non-inverted setting.
**Tracking Sensitivity Configuration**
This is the most critical section for performance. The optimal value depends on what you are tracking.
- Sensitivity: 150 (Start with this value and adjust based on results)
- Reasoning: A medium value like 150 is a good starting point. It provides a balance between being too sensitive (causing false triggers) and not sensitive enough (missing data). You will need to fine-tune this based on real-world testing.
- Default Capture Time (seconds): 1
- Reasoning: A 1-second capture time is standard for many applications. It tells the device how long to “look” for a stable reading before sending it.
- Space Value (Sensitivity) - Range: 10-1000: 150
- Reasoning: This appears to be a duplicate or more granular control for sensitivity. Set it to match the main Sensitivity value (150) for consistency.
- Registry Value (Multiple): 1
- Reasoning: A multiple of “1” means the raw data value is sent without any multiplication. This is the standard and safest setting. Do not change this unless you have a specific requirement to scale the output data (e.g., you need the values to be 10x larger for your application).
**Summary of Recommended Settings**
| Section | Setting | Recommended Value | Notes |
|---|---|---|---|
| Device | Device Type | Emulator | For testing. |
| Device | Serial Port | COM9 | Must match your app’s port. |
| Range | Min | 0 | Standard minimum. |
| Range | Max | 9900 | Standard maximum. |
| Range | Presets | 1 | Use default profile. |
| Range | Invert | Unchecked | Disable inversion. |
| Sensitivity | Sensitivity | 150 | Key setting. Adjust as needed. |
| Sensitivity | Capture Time | 1 | Standard 1-second interval. |
| Sensitivity | Space Value | 150 | Keep consistent with Sensitivity. |
| Sensitivity | Multiple | 1 | Do not multiply the output data. |
Next Steps: After applying this configuration, run your application and test the data flow. If you experience missed readings, try increasing the Sensitivity . If you experience jitter or false readings, try decreasing the Sensitivity .
**Future Plans**
- Add game save/load support.
- Implement a simple AI assistant to help detect tracking points.
- Save enough to buy multi-axis devices and sync them.
- Add support for rotation and multi-axis devices.
Instructions for Use
-
Basic Operation: Select the two points (hambos) and press Play.
-
Modifying Patterns: If you need to modify the patterns, go back to the main window. Dent the connection (break it) and then re-establish it. Press Play again.
-
Single Sensor Mode: To use the single sensor mode, you must have already recorded the positions of both points beforehand. Now, in English, we adapt the instruction: Ensure both points are registered before switching to single-sensor
“Attention”
“Recommended single-position games. Each time the position changes, the points must be selected again; this will be fixed in future updates.”
“IN DEVELOPMENT, MAY HAVE BUGS”
DOWNLOAD HERE
