reWASD 9.3.1: Stability Improvements for External Devices & Crosshair
Improved overall stability when working with external devices
This update brings multiple improvements to external device workflows. ESP32-S2 and ESP32-S3 adapters now support Ping and Latency settings. Please note that latency-related options are available only for FTDI-based adapters.
We also fixed issues affecting polling rate on ESP32-S3 adapters: Device Performance presets (Normal / High / Ultra) are now applied correctly, enabling higher and more stable polling rates when supported by the device. Authorization controller requirements for External Virtual Xbox One were refined: an authorization controller is no longer required when the target is not an Xbox console (e.g., Linux or a remote PC). This behavior now applies to GIMX and all ESP32 adapters. In addition, ESP32 firmware update diagnostics were improved, allowing users to view and download logs when an update fails.
We also fixed issues affecting polling rate on ESP32-S3 adapters: Device Performance presets (Normal / High / Ultra) are now applied correctly, enabling higher and more stable polling rates when supported by the device. Authorization controller requirements for External Virtual Xbox One were refined: an authorization controller is no longer required when the target is not an Xbox console (e.g., Linux or a remote PC). This behavior now applies to GIMX and all ESP32 adapters. In addition, ESP32 firmware update diagnostics were improved, allowing users to view and download logs when an update fails.
Custom Crosshair stability improvements
Several issues related to Custom Crosshair behavior were addressed in this release. We fixed cases where the crosshair could disappear after switching between slots, fail to appear when switching to an assigned layer, or become misaligned after reapplying a config. In some scenarios, the crosshair previously required a full config reapply or even an agent restart to restore correct behavior.
With these fixes in place, Custom Crosshair now activates reliably when entering the corresponding layer, remains centered on the screen after config reapply, and stays visible when switching between slots. This brings crosshair behavior back in line with expected logic for user configs that rely heavily on layers and dynamic slot switching.
With these fixes in place, Custom Crosshair now activates reliably when entering the corresponding layer, remains centered on the screen after config reapply, and stays visible when switching between slots. This brings crosshair behavior back in line with expected logic for user configs that rely heavily on layers and dynamic slot switching.