Radar only or full ESP with aim: which first build
A radar-only DMA build needs no fuser and no input device. See how it compares with a full ESP-plus-aim build on cost, complexity, failure surface and what each does for your gameplay.
Short answer
A radar-only build needs a card, firmware, a second PC, a cable and a spare monitor, but no fuser or input device. Full ESP with aim adds both layers, two new failure types and a much longer setup, so radar suits most first builds.
On this page12
- Which build should you start with?
- What does a radar give you?
- What do ESP and aim assistance add?
- How the two builds compare
- Why more parts mean more ways to fail
- How each build fails, and how to fix it
- What each option changes in your games
- When is radar only the right choice?
- When is full ESP with aim the right choice?
- Can you upgrade from radar later?
- Questions about radar and ESP
- Sources
Which build should you start with?
Almost every DMA discussion assumes the goal is a full stack, with boxes on your main monitor, assistance on target and every layer present. That is one valid build out of several, and it is also the most expensive and most fragile one. For most first-time buyers the right build is a radar on a second screen, and the reason is not money. A radar-only build has four things that can be wrong, while a full build has eight.
What does a radar give you?
A radar shows positions on a map, updated live, on a second screen or a phone, and nothing more. In practice that is most of the benefit in any game where knowing where people are changes what you do. It tells you which way to rotate, whether a building is occupied, whether the fight ahead is one against one or one against three, and when to leave. It does not help you win a duel you have already entered, but in extraction and objective games the decisions it changes happen before the duel starts. That is why experienced players often stop at radar and never add the rest.
What do ESP and aim assistance add?
ESP adds information during a fight: a box, a distance, a health value, sometimes a skeleton, sometimes loot. On a second screen this is awkward, because the middle of a fight is exactly when you cannot look away, and solving that problem is the whole reason fusers exist. Aim assistance is a separate thing again, because it changes your mechanics rather than your information. It needs a device that presents itself to the gaming PC as a real USB mouse. ESP and aim assistance are two separate purchases that solve two separate problems, and people routinely buy both when they only wanted one.
How the two builds compare
Neither column wins every row. Cost is given relative to the card itself, because that is the figure you already know.
| Radar only | Full ESP plus aim | |
|---|---|---|
| Parts to buy | Card, firmware, second PC, cable | Card, firmware, second PC, cable, input device, fuser, video cables |
| Extra hardware cost over radar-only | None | From about the card itself up to several times it, by input device and fuser class |
| Needs a fuser | No | Yes, if you want the overlay on your main monitor |
| Needs an input device | No | Yes. Aim assistance is impossible without one |
| First-time setup | One evening | Two evenings, and the fuser is its own project |
| Things that can be wrong | Card seating, firmware, USB path, software config | All four, plus HID enumeration, mouse descriptors, EDID, resolution and refresh negotiation |
| Where you look | A second screen or a phone, between engagements | Your main monitor, during engagements |
| What it changes | Your decisions before a fight | Your decisions and your mechanics inside one |
| Recoverable when it breaks | Usually, and there are few places to look | Usually, but diagnosis takes longer because the surface is larger |
For a first build, the row that should decide this is "things that can be wrong". Four is few enough to debug on your own, but on a first build eight usually is not.
Warning
Why more parts mean more ways to fail
Every layer you add is not just a cost but a new category of fault, one you have never seen before. A radar-only build fails in ways that are already documented. The card is not seated, the cable is in the flashing port instead of the data port, the memory map is missing, or the cable is charge-only. Add an input device and you inherit HID enumeration and descriptor problems. Add a fuser and you inherit video negotiation problems, which show up as a black screen with no error message at all, the least pleasant failure mode in the whole stack. The build is not more likely to break per part; it simply has more parts.
How each build fails, and how to fix it
The top four rows apply to both builds. The rows below them only appear once you have added a layer, and they are the price of adding it.
| Symptom | Likely cause | Fix |
|---|---|---|
| Second PC sees no device at all | Card not fully seated, cable in the flashing port, charge-only cable, or missing driver | Reseat the card, move to the data port, swap in a known data-rated USB 3 cable, install the driver, cold-boot the gaming PC |
| Device found but nothing resolves | Firmware layer, or the reader cannot locate kernel structures | Confirm the firmware is for your exact board, then generate a memory map |
| Radar updates but lags badly | Read rate lost to the USB path, or a missing memory map making the reader probe blindly | Measure the read rate on a clean direct rear port, then add a memory map before blaming the board |
| Everything works, then dies mid-session | Marginal USB link, a hub or dock in the path, or the card has hung | Go direct to a rear port, remove every hub, and cold-boot the gaming PC rather than restarting it |
| Cursor does not move at all (aim builds only) | The input device is not enumerated as a mouse, or the wiring order is wrong | Confirm the device appears as a HID mouse on the gaming PC and check the cable order between mouse, device and PC |
| Main monitor is black after adding a fuser (fuser builds only) | EDID not presented convincingly, or a resolution and refresh combination the fuser does not support | Drop to a resolution and refresh rate inside the fuser's documented range, then work back up |
| Overlay appears but the game image tears or drops frames (fuser builds only) | Fuser class below the signal you are feeding it | Match the fuser class to your monitor's actual resolution and refresh rate, or lower the signal |
What each option changes in your games
Three different things are being sold as one. A radar changes what you decide, ESP changes what you see inside a fight you have already chosen, and aim assistance changes how well you carry that fight out. They are not steps on a ladder of quality but three different products, and which one is worth money depends on what is actually losing you games. If you die because you walked into three people, a radar fixes that and ESP does not. If you die because you lose duels you were right to take, a radar will not help you at all. Work out which of these describes you before you spend anything.
When is radar only the right choice?
Most first-time buyers can say yes to most of these.
- This is your first DMA build and you have not debugged one before
- You play an extraction or objective game where positioning decides fights
- You have a spare monitor, or a phone you are happy to put a radar on
- You would rather have four things to check than eight when something breaks
- You are not sure yet whether you want aim assistance
- You want the smallest total spend that still produces a build you actually use
When is full ESP with aim the right choice?
Fewer people can honestly say yes to these than think they can.
- You have already run a DMA build and are comfortable diagnosing hardware faults
- Looking at a second screen is the specific thing that stopped you using your last build
- You have checked your monitor's resolution and refresh rate against a fuser class you can afford
- You specifically want assistance on target, and understand that needs its own device
- You accept that the build has more ways to fail and will take longer to diagnose
- You have the budget for the fuser class that matches your display, not the one that is cheapest
Tip
Can you upgrade from radar later?
Nothing in a radar-only build is wasted when you add layers later, because the card, the firmware, the second PC and the cable remain the foundation of a full stack. An input device and a fuser are both additions on top of that foundation. Starting small does not mean choosing a lesser build. It means building the same stack in stages, so that when something goes wrong you can tell which layer caused it. If you buy the whole stack at once, the first failure has eight suspects and no history to compare against.
Questions about radar and ESP
Is a radar-only build actually useful, or is it a compromise?
It is useful. In games where knowing where people are changes your rotations and your choice of fights, a radar provides most of the practical benefit, and plenty of people run radar only permanently by choice.
Can I get ESP without a fuser?
Yes, ESP on a second monitor needs no fuser at all. A fuser only exists to put the overlay on the screen you are already looking at, which matters for ESP and barely at all for a radar.
Can I get aim assistance without an input device?
No. The memory read path is one-directional and runs on another machine. Something has to present itself to the gaming PC as a real USB mouse, and that is a separate device you buy.
Which build is safer?
Neither is safe, and nobody can promise you a detection outcome. A radar-only build has a smaller hardware surface because there is no input device presenting a USB descriptor, but your behaviour in a match is a factor no build addresses.
If I only want a radar, can I buy a cheaper card?
Usually yes, because an entry FPGA class is generally adequate for radar work. The limit is firmware availability, so buy the class your provider still publishes images for, not the cheapest class that exists.
Sources
The failure table, the setup times and the choice between the two builds come from the team's own bench work.
- 01Microsoft Learn, USB device descriptors
an input device having to enumerate as a real USB mouse
learn.microsoft.com
- 02
- 03VESA E-EDID standard, release A2
a black screen when the fuser does not present a convincing EDID
glenwing.github.io
Read next
Still stuck? Open a ticket on Discord
All guides