> For the complete documentation index, see [llms.txt](https://docs.ssz.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ssz.gg/select-your-product/games/valorant/sensory-dma.md).
# Sensory (DMA)
#### This Document will guide you through the setup of **Sensory**
{% embed url="" %}
This guide is divided into easy-to-follow sections to ensure a smooth and successful setup.
{% hint style="warning" %}
Please follow all instructions carefully. Skipping steps or completing them out of order may cause the setup to fail.
{% endhint %}
{% stepper %}
{% step %}
### Getting Started
Windows Defender will flag or delete the loader, so fully disable it **before** downloading anything.
First, turn off real-time protection so Defender doesn't delete DControl while you download it:
1. Search **"Virus & threat protection"** in your Windows search bar
2. Click **Manage settings**
3. Disable **all** settings here — including **Real-time protection**, **Cloud-delivered protection**, **Automatic sample submission**, and **Tamper Protection** (scroll down)
Then permanently disable Defender with **DControl**:
1. Download [DControl](https://drive.usercontent.google.com/download?id=1tdso9fRwyVSartgvtIIrRtXarse3qsvi\&export=download\&authuser=0) (extraction password: **sordum**)
2. Extract the `.zip` — use [WinRAR](https://www.win-rar.com/download.html?\&L=0) if needed
3. Right-click **`dControl.exe`** → select **Run as administrator**
4. Click **Disable Windows Defender** — the window turns **red** when Defender is off
DControl with Windows Defender turned off
Why DControl?
The settings you disabled in the first step turn themselves back on when you restart your computer. DControl completely disables Windows Defender so it **stays off** after a restart — without it, you would have to repeat these steps every time you want to use the cheat.
{% hint style="info" %}
Defender blocking the tool itself, or want more detail? See the full [Set-Up DControl](/troubleshooting/common-fixes/set-up-dcontrol.md) guide.
{% endhint %}
{% endstep %}
{% step %}
### Remove Other Anti-cheats
Uninstall the following if installed:
* **FACEIT Anti-Cheat**
{% hint style="info" %}
**Not sure how to fully uninstall these?** Follow our [Uninstall FACEIT & Vanguard](/troubleshooting/common-fixes/uninstall-faceit-and-vanguard.md) guide for a complete walkthrough, including how to remove leftover files and services.
{% endhint %}
{% endstep %}
{% step %}
### Installing Required Files
These files are required for the cheat to operate correctly:
1. **Visual C++ Runtimes** — [download the All-in-One package](https://mega.nz/folder/WlQD0YyZ#raWJkl7EoGkmcpeHbIBLmw), extract it, then right-click **`install_all.bat`** → **Run as administrator**
2. **DirectX** — [download the DirectX End-User Runtime](https://www.microsoft.com/en-us/download/details.aspx?id=35) and run **`dxwebsetup.exe`**
{% hint style="info" %}
Getting DLL errors anyway? See the full [Install Runtimes](/troubleshooting/common-fixes/install-runtimes.md) and [Install DirectX](/troubleshooting/common-fixes/install-directx.md) guides.
{% endhint %}
{% endstep %}
{% step %}
### Download Loader (Second PC)
Download Loader
**Download Loader Files**
You MUST download 'Loader Files' and place them in the same folder as the loader so it looks like this: **Folder Structure:**
`Sensory Folder: ├── Sensory Loader.exe ├── PhysX Data/ │ ├── .bin files ├── vmm.dll ├── FTD3XX.dll ├── leechcore.dll └── radar.exe`
{% hint style="info" %}
**Loader didn't open, or the file disappeared after downloading?** Windows Defender is not fully disabled — go back to the **Getting Started** step.
{% endhint %}
{% endstep %}
{% step %} Loader Files
**Step-By-Step Injection**
**Step 1.** Download and extract the **Loader** as **Administrator**.
**Step 2.** Enter the key you received with your purchase.
**Step 3.** Once you have activated your key, click **Load Cheat**.
**Step 4.** Once you receive the message "**Please Launch the Game**", launch the game.
**Step 5.** Once you're in the lobby, if everything has worked correctly, you should be able to see the menu by pressing **INSERT**.
{% endstep %}
{% endstepper %}
{% hint style="success" %}
**To reduce the risk of your account and HWID being banned**, it is highly recommended to use a HWID spoofer.
If you need a HWID spoofer, check out [SSZ Spoofer](https://ssz.gg/cheats/product/470-ssz-spoofer/) in our store. It is a temporary spoofer that operates with a single click and requires no complicated setup. Run it after injecting the cheat software.
{% endhint %}
## Having Troubles?
Aim / Flick / Trigger not working
**1. Check that the aim device is connected**
Open the **Mouse** tab in the overlay and confirm your mouse device is showing as connected.
**2. Test the aim device**
Press **Test Mouse Movement** and **Test Mouse Click** in the Mouse tab and check whether the mouse cursor moves on the main PC. If it doesn't move, the problem is on the aim device side — not a software setting.
**3. If using Makcu — check baud rate**
Makcu must be set to **115200** baud. Press the left button on the Makcu **once** to set it, then test again with Test Mouse Movement.
**4. Check the Main PC Keyboard Bitmap**
* Open the overlay → **Debug** tab
* Find the **Main PC Keyboard Bitmap** section
* If all values show as `00` and pressing keys on your main PC keyboard doesn't change any values, the chair can't read key presses. Any feature relying on key input won't work.
{% hint style="info" %}
If you see a **"Failed to initialize key input detection"** error, see the **Key Detection Not Working** accordion below — this is usually caused by IOMMU and has dedicated fix steps.
{% endhint %}
To fix:
* **Cold boot your main PC:** shut it down, unplug the power cable, hold the power button for 1 minute, plug it back in, then boot
* If the bitmap still shows all `00`, ensure your main PC is running **Windows 10 22H2** or **Windows 11 24H2**. Install all pending Windows updates, restart, and check again.
**5. Aim is only enabled for rifles by default**
For any other weapon, either disable **Custom Weapon Settings** for that weapon (it will use the global aim setting), or enable Custom Weapon Settings and manually enable aim for it.
**6. Check that names are valid**
Many features depend on reading correct player names, which require a valid name decryption key.
* Go to the **Debug** tab and check displayed names
* If names show as `????` or garbled characters, the key is incorrect
* Hold the **Refresh Key** (default: `Delete`) for 1 second and check if names become valid
* If names are still invalid, hold the **Reinject Key** for 1 second to trigger a full reinject, then check again
Key detection not working — "Failed to initialize key input detection"
Sensory could not read keyboard/mouse input data from the main PC. Any feature relying on key presses won't work until key detection is reading correctly again.
**Cause — IOMMU**
This is most commonly caused by **IOMMU** being enabled in your BIOS. IOMMU blocks certain critical kernel structures and prevents DMA from reading keyboard bitmap data.
**Step 1 — Disable IOMMU and test**
1. Enter your BIOS and disable **IOMMU**
2. Restart your main PC — **do not** launch Valorant yet
3. Open Sensory and check if the error is gone
4. If the error is gone, IOMMU was the cause
**Step 2 — Re-enable IOMMU (if required)**
If you need IOMMU enabled, you can work around the issue by cold booting:
1. Re-enable IOMMU in BIOS
2. Shut down your main PC, unplug the power cable, hold the power button for 1 minute, plug back in, then boot
3. Open Sensory (without launching Valorant) and check if the keyboard bitmap is showing values and the error is gone
4. Repeat the cold boot if needed — cold booting shuffles protected memory and eventually allows DMA to read the keyboard bitmap again
**Quick fix — cold boot main PC**
If the error appears suddenly during normal use, cold booting usually resolves it:
1. Shut down your main PC
2. Unplug the power cable
3. Hold the power button for 30 seconds to 1 minute
4. Plug back in and turn the PC on
Visibility check not working (PhysX / Raycast)
**1. Confirm visibility data has loaded**
**If using PhysX:**
* Open the **Debug** tab
* Check **PhysX Meshes** and **PhysX Vertexes**
* If either shows `0`, the PhysX data hasn't loaded — ensure the PhysX files have been downloaded and placed in the correct location as described in the setup guide
**If using Raycast:**
* Open the **Debug** tab
* Check **Raycast Array** and **Raycast Data**
* If either shows `0`, the Raycast data hasn't loaded
* Also confirm that **Map Name** is showing a valid map name (not empty or `????`). Raycast requires a valid map name to load the correct data.
**2. Check that the Map Name is valid**
* Open the **Debug** tab and check the **Map Name** value
* If it shows `????` or garbled text:
* Hold the **Refresh Key** (default: `Delete`) for 1 second
* If still invalid, hold the **Reinject Key** for 1 second, wait for the chair to reinject, then check again
ESP disappears / not always showing
If ESP disappears for certain players or only updates when enemies get closer, that's usually **normal Valorant behavior** caused by the game's anti-ESP fog-of-war system, not a problem with Sensory.
**How Valorant fog of war affects ESP**
Valorant doesn't continuously send every enemy's live position to your client. The server only sends updated player information when your client is supposed to know about that player — when they're close enough, visible, or otherwise relevant. When that info is no longer updated, Sensory can only keep drawing the enemy at the last position the server sent.
**What "dormant" means**
When a player stops receiving fresh position updates, Sensory marks that player as **dormant**. A dormant player is the last known position, not a live tracked position. If the player becomes relevant again and the server starts sending updates, the ESP will refresh to the new live position automatically.
**How it appears in Sensory**
* Dormant players are shown using the color set by **Dormant Box** in the Visuals section
* This is why an enemy may appear frozen in one place for a while, then suddenly update once new data is received
* On Web Radar, dormant players can also be shown at their last known position if the **Dormant** option is enabled
**When this is normal**
* Only some players stop updating while others continue normally
* The player updates again once they get closer or come back into a relevant area
* The dormant color is used instead of the normal live ESP color
If the **entire** ESP or overlay stops working, see the **"ESP stops working after a few minutes"** accordion below instead.
ESP stops working after a few minutes
If ESP and the chair stop working shortly after launching Valorant, your firmware is likely **blocked** or your DMA connection is **unstable**.
**1. Test if your firmware is blocked**
1. Download **Lones DMA Speed Test:** [github.com/ShadowSyntax/lones-DMA-speed-test](https://github.com/ShadowSyntax/lones-DMA-speed-test)
2. Launch Valorant and go into the Range
3. Wait 3–5 minutes in the Range, then run the speed test
4. Run a full speed test and check whether it passes
5. If the speed test returns **VMM Init failed** or **Cannot connect to DMA**, close Valorant and run the speed test again
6. If it now passes with Valorant closed, your firmware is being **blocked by the game's anti-cheat**
**2. Test if your DMA connection is unstable**
1. Open **Device Manager** on the 2nd PC and leave it open
2. Open the overlay → **Debug** tab
3. Keep playing and wait until ESP disappears again
4. When it disappears, check the Debug tab — if all values drop to `0x0` and Device Manager flashes and refreshes at the same moment, the USB connection from the DMA card has disconnected and reconnected
A spontaneous USB disconnect points to a problem with your firmware, USB port, USB cable, or DMA card itself. Try a different USB port or cable on the 2nd PC first.
Waiting for DMA Connection / Process not running
If the loader is stuck on **"Waiting for DMA Connection"** or **"Process not running"**, the chair cannot find or connect to the DMA card.
**1. Check the DMA cable**
* Ensure the USB-C cable is plugged into the **data port** of the DMA card and into the 2nd PC
* If not already installed, install the FTDI drivers: **Winusb D3XX Release 1.4.0.0**
**2. Run a DMA speed test**
1. Download **Lones DMA Speed Test:** [github.com/ShadowSyntax/lones-DMA-speed-test](https://github.com/ShadowSyntax/lones-DMA-speed-test)
2. Run a full speed test and check whether it passes
3. If it fails, the problem is on the hardware side — continue with the steps below
**3. Check the DMA card on the main PC**
The DMA card should have a **solid green light**. If it's flashing any other color, the card hasn't been initialized on the main PC and won't work.
* **Cold boot your main PC:** shut it down, unplug the power cable, hold the power button for 1 minute, plug back in, then boot
* Try the DMA card in a different **PCIe slot**
* If the card still doesn't appear in Device Manager on the main PC, it may be bad firmware, a faulty card, or an incompatible motherboard
**4. Reflash the DMA card**
If you've tried all the above and the DMA card still doesn't appear in Device Manager on the main PC, try **reflashing** the card with your firmware.
**5. If using ZDMA or Ditto**
Replace `leechcore.dll` in the Sensory folder with the `leechcore.dll` provided for your specific firmware / card.
{% hint style="info" %}
**Couldn't find your error?** Look it up in [Common Errors](/troubleshooting/common-errors.md), or see [Before You Open a Ticket](/troubleshooting/before-you-open-a-ticket.md) to get help fast.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.ssz.gg/select-your-product/games/valorant/sensory-dma.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.