I tested.
## Summary
I have identified a fully reproducible regression in Synapse 4 affecting both the Tartarus V2 and Tartarus Pro.
When the D-Pad is configured as **8-Way**, pressing any D-Pad direction while **HyperShift** is active causes the D-Pad to ignore its configured bindings and instead generate the default Arrow Key inputs.
This issue does **not** occur when the D-Pad is configured as **4-Way**.
The exact same hardware and workflow worked correctly in Synapse 3.
---
## Environment
* Windows 11
* Synapse Version: **4.0. [removed by moderator] **
* Guest Mode (not signed in to a Razer account)
* Clean installation using the official Razer Driver Clean-up Tool
* Default profile only (no imported or cloud-synchronized profiles)
Devices tested:
* Tartarus V2
* Tartarus Pro
The issue is reproducible on both devices.
---
## Steps to Reproduce
1. Install Synapse 4.
2. Launch Synapse in Guest Mode.
3. Configure the D-Pad as **8-Way**.
4. Set **every D-Pad direction** on both the Normal layer and the HyperShift layer to **Disabled**.
5. Assign any key (for example, Key 15) as HyperShift.
6. Hold the HyperShift key.
7. Press any D-Pad direction.
---
## Expected Result
Because every D-Pad direction is explicitly configured as **Disabled**, pressing the D-Pad while HyperShift is active should produce **no input**.
---
## Actual Result
Instead of respecting the configured bindings, Synapse generates the default Arrow Key inputs (Up / Down / Left / Right).
The configured D-Pad bindings are ignored only while HyperShift is active.
---
## Additional Verification
The issue has been verified under the following conditions:
* Clean installation using the official Driver Clean-up Tool
* Guest Mode
* No Razer account
* No cloud synchronization
* No imported profiles
* Default profile only
* Windows Notepad
* Games
* Multiple applications
* Tartarus V2
* Tartarus Pro
The issue occurs consistently under all of the above conditions.
---
## Additional Observations
* The problem only occurs when the D-Pad is configured as **8-Way**.
* The problem does **not** occur when the D-Pad is configured as **4-Way**.
* The issue is reproducible in multiple Windows applications, including Notepad, Google Sheets, ChatGPT, and games.
* Even when every D-Pad direction is configured as **Disabled**, default Arrow Key inputs are still generated while HyperShift is active.
* The exact same hardware and configuration function correctly in Synapse 3.
Based on my testing, this appears to be a regression introduced in Synapse 4. However, I would appreciate it if other Tartarus users could confirm whether they can reproduce the same behavior.