This belonged in a separate thread, so I've created this thread.
All CH USB products, joysticks, flight yokes, pedals, throttles, gamepads, ..., include a driver feature (control manager) that provides mapping and scripting. The mapping is used to remap axis and outputs to virtual devices, mostly to create a single virtual device for games that don't support multiple controllers. The scripting is essentially a programming language that can control the output of axis data, button presses, keystrokes, mouse clicks, ....
CH USB controllers are not the only controllers to have scripting capability. The standard Logitech driver also includes scripting, including the output of both button presses and axis output, but I haven't confirmed if the standard driver would allow creation of auto-cut and auto-blip or if some special "wingman" utility would be needed.
The issue is that the scripting component can be used to create auto-cut and auto-blip.. I currently use two CH USB joysticks for game play, both racing and flight simulation games. I use the right stick to steer (or roll+pitch), the left stick for combined throttle / brake (or throttle/airbrake + rudder), the same as classic transmitters for radio control cars and the same setup as mode 2 (USA) transmitters for radio control aircraft. I often use a script for auto-cut and auto-blip for racing games that don't have this feature, and now LFS is one of those games because of Patch Y. In my clutch overheating thread, I mentioned this scripting capability, and it's clear some players consider this to be cheating.
So where to draw the line, and is it even possible to detect usage of script capable controllers? What if the throttle cut and blip are accomplished via a second and third button on a controller? In this case, the player is still issuing the control inputs, just using buttons instead of axis movements, not a lot different from gamepad players.
Note, I rarely play LFS online anymore, and I don't submit hot laps.
All CH USB products, joysticks, flight yokes, pedals, throttles, gamepads, ..., include a driver feature (control manager) that provides mapping and scripting. The mapping is used to remap axis and outputs to virtual devices, mostly to create a single virtual device for games that don't support multiple controllers. The scripting is essentially a programming language that can control the output of axis data, button presses, keystrokes, mouse clicks, ....
CH USB controllers are not the only controllers to have scripting capability. The standard Logitech driver also includes scripting, including the output of both button presses and axis output, but I haven't confirmed if the standard driver would allow creation of auto-cut and auto-blip or if some special "wingman" utility would be needed.
The issue is that the scripting component can be used to create auto-cut and auto-blip.. I currently use two CH USB joysticks for game play, both racing and flight simulation games. I use the right stick to steer (or roll+pitch), the left stick for combined throttle / brake (or throttle/airbrake + rudder), the same as classic transmitters for radio control cars and the same setup as mode 2 (USA) transmitters for radio control aircraft. I often use a script for auto-cut and auto-blip for racing games that don't have this feature, and now LFS is one of those games because of Patch Y. In my clutch overheating thread, I mentioned this scripting capability, and it's clear some players consider this to be cheating.
So where to draw the line, and is it even possible to detect usage of script capable controllers? What if the throttle cut and blip are accomplished via a second and third button on a controller? In this case, the player is still issuing the control inputs, just using buttons instead of axis movements, not a lot different from gamepad players.
Note, I rarely play LFS online anymore, and I don't submit hot laps.