Which DMA upgrade actually helps
Which upgrade actually improves a DMA build you already own? Compare a better cable, a memory map, a bigger FPGA, a better second PC, an input device and a fuser by cost per improvement.
Short answer
Fix cheap layers first, since a proper USB 3 cable, valid memory map and direct rear-port USB path cost almost nothing and cause most complaints. A bigger FPGA is the last upgrade, not the first, because it fixes nothing a bad cable caused.
On this page10
- What to measure before you buy an upgrade
- Which upgrades give the most for the money?
- What to upgrade for each symptom
- Why the USB cable is the most common fix
- Why a memory map should come first
- When is a larger FPGA worth buying?
- What does a better second PC change?
- What to check before buying any upgrade
- Which purchases feel like upgrades but are not?
- Questions about upgrades
What to measure before you buy an upgrade
Upgrade questions usually follow the same pattern. The build works but something about it is unsatisfying, so the owner goes looking for a part to replace. Almost always they pick the most expensive part, while the fault is in the cheapest one. Before you buy anything, run a read-speed test on a clean direct USB path and check whether a memory map exists. Those two checks take ten minutes between them, and they settle most upgrade questions without a purchase.
Which upgrades give the most for the money?
The top of the list is where money works hardest, so work down the list rather than up. Costs are relative, because the order of the rows is what matters and that order does not change with currency.
| Upgrade | Relative cost | What it fixes | When it is wasted money |
|---|---|---|---|
| Generate a memory map | Nothing but time | Slow scans, missing ESP, kernel structure failures, the reader probing blindly | Never wasted. If you do not have one, do this before reading further |
| Move to a direct rear USB 3 port | Nothing | Dropouts, unstable read rates, devices that vanish mid-session | Only if you were already direct with no hub or dock in the path |
| A proper USB 3 data cable | The cheapest paid step there is | Read rates far below expectation, links that negotiated USB 2, intermittent disconnects | Only if you have already proven the current cable sustains USB 3 rates |
| A clean Windows install on the second PC | Nothing, or an SSD | Driver conflicts, controller contention, a machine that was never set up for this job | If the second PC is already clean and dedicated |
| An input device | Well under an entry card | Nothing about stability. Adds a capability you did not have: assistance on target | If what bothers you is the overlay's location, not your mechanics |
| A better second PC | About an entry card | Persistent dropouts from shared USB controllers, and a machine too slow to keep up with a read stream | If your current second PC has clean USB topology and is not the bottleneck |
| A fuser | An entry card, up to several times one, by class | Nothing about stability. Moves the overlay onto your main monitor | If you have not matched the class to your monitor's resolution and refresh rate |
| A larger FPGA class | Up to roughly double an entry card | A genuine throughput or image-complexity ceiling, once everything above is proven clean | Almost always, if anything above this row is still unfixed |
This order is not a preference. Each row is cheaper than the rows below it and fixes a more common fault, so buying out of order means paying more to fix something rarer.
What to upgrade for each symptom
Find your symptom in the first column. The third column is the purchase people usually make for that symptom, and it does not fix it.
| Symptom | What to upgrade | What NOT to buy |
|---|---|---|
| Read rate is a fraction of what it should be | The USB cable, then the port. Verify the link negotiated USB 3 | A larger FPGA class. A high-headroom card on a bad cable is slower than an entry card on a good one |
| ESP feels laggy but the read rate measures fine | Generate a memory map. This is the classic missing-MMAP symptom | Any hardware at all. Nothing you buy fixes a reader probing blindly |
| Device appears, then vanishes mid-session | Remove every hub, dock and extension. Go direct to a rear port | A replacement card. The card is rarely the fault when the failure is intermittent |
| Read rate is unstable between runs | Strip other devices off that USB controller, or move to a second PC with cleaner topology | A more expensive cable, if you already have a data-rated one |
| Overlay is on the wrong screen and it annoys you mid-fight | A fuser, in the class that matches your monitor | A bigger card, an input device, or a better second PC. None of them move the overlay |
| You want assistance on target and do not have it | An input device. That is the only thing that provides it | A card upgrade, or firmware. Reading memory cannot move a cursor |
| Firmware provider has stopped publishing for your board | The card, to a class they still support | A fuser or an input device, while the foundation layer is unsupported |
| The build worked, then stopped after a game patch | Nothing. Wait for the software to catch up and watch the status board | Anything. Buying hardware during a post-patch outage is how people end up with two of everything |
Warning
Why the USB cable is the most common fix
This can sound like we are avoiding the question, but we are not. USB-C cables vary enormously in what they can sustain, and many of the ones shipped in boxes are made mainly for charging. A cable that carries power without trouble will still negotiate a link two generations below what the card can do. The failure is silent: nothing shows an error, the device appears, and you simply get a fraction of the throughput. Swap in a short USB 3 cable that is known to be data-rated, and measure again before you conclude anything about your board.
Tip
Why a memory map should come first
A memory map tells the reader which physical address ranges are real memory, so it stops probing ranges that are slow, meaningless or actively dangerous to touch. Without one, the reader works far harder for a worse result. The symptoms that follow, such as slow scans, entities that go missing now and then, and kernel structure failures, look exactly like a hardware limitation, but they are not one. Generate the map, because it is the highest-value ten minutes in the whole upgrade path and it does not involve an order.
When is a larger FPGA worth buying?
There is a real case for a larger FPGA, but it is narrow, and several things have to be true already. You have a clean direct USB 3 link on a known-good cable, a valid memory map and a second PC that is not the bottleneck. You have also measured a stable read rate that still will not feed the features you want. The other case is when your provider publishes an image your current class cannot hold. At that point the FPGA really is your ceiling and a higher class is a real upgrade, but before that point it is the most expensive way to leave your problem unfixed.
What does a better second PC change?
It helps to know what you are and are not buying, because this upgrade is often made for the wrong reason.
- Changes
- USB controller contention, dropout frequency, how many devices can share the path
- Changes
- Whether the machine can keep up with sustained reads without stuttering
- Does not change
- Read rate, if the current machine already has a clean direct rear USB 3 port
- Does not change
- Anything about detection risk
- Does not need
- A graphics card. The reading machine renders nothing
- Does need
- Rear-panel USB 3 ports on separate controllers where possible, and a clean Windows install
What to check before buying any upgrade
- You have measured your read rate on a clean direct rear USB 3 port with nothing else on that controller
- You have confirmed that a memory map exists and is current
- You have tried a second USB 3 cable that is known to be data-rated
- You have cold-booted the gaming PC, not just restarted it
- You have checked the status board, so you are not buying hardware to fix a software outage
- You can say in one sentence which measurement the upgrade is supposed to change
Which purchases feel like upgrades but are not?
Some purchases feel like progress but change nothing you can measure. Examples are swapping one mainstream card for another of the same class, or buying a higher fuser class than your monitor can use. Replacing a working input device with a more expensive one of the same category is another, and so is adding a capture card to a build that already has a working display path. None of these are exactly mistakes, but they are not upgrades either. If you cannot name the measurement a purchase changes, it is not changing one.
Questions about upgrades
My ESP is laggy. Should I buy a bigger card?
Almost certainly not. First measure the read rate on a clean direct USB path and confirm that a memory map exists, because those two checks resolve most lag reports and neither costs anything.
Will a larger FPGA reduce my detection risk?
No. FPGA capacity is logic capacity, not a stealth rating, and nobody can promise you a detection outcome. A high-headroom card running a generic firmware identity is more exposed than a mainstream card running a good one.
Is it worth replacing a working entry card?
Only if your firmware provider has stopped publishing images for it, or you have proven a throughput ceiling with everything else clean. The real reason to retire a board is firmware availability, not its class.
Should I upgrade the second PC or the card first?
Neither, until you have ruled out the cable, the port and the memory map. If those are clean and you still get dropouts, the second PC's USB topology is the more likely cause of the two.
My build broke after a game update. What should I upgrade?
Nothing, because post-patch outages are a software problem that hardware does not fix. Watch the status board and wait for the build to come back.
Sources
The ranking is our own, ordered by what fixes the most support tickets for the least money rather than taken from any document.
Read next
Still stuck? Open a ticket on Discord
All guides